AWS re:Invent is a learning conference hosted by AWS for the global cloud-computing community.
December 2nd, 2024 - December 6th, 2024
Las Vegas, Nevada
320
Read More
If you’ve ever ventured the halls – real or virtual – of your company’s sales organization at the end of the quarter, you’ve likely found sales managers unraveling BANT for their latest opportunities. Four ingredients can make or break any deal:
After many thousands of badge scans and conversations at industry events, and nearly as many onsite customer visits, we’ve identified an interesting trend.
Without question, platform teams and development leads recognize the clear benefits of cloud development environments. However, after their excitement peaks and their tinkering with our open-source platform concludes, reality sets in. They release a visceral sigh when they realize they need to sell the promise of CDEs up the chain of command to capture the necessary budget.
Defeated, these stewards of developer experience and operational excellence wander off, unsure of what to do next. Is it even worth the frustration? Is their folded tradeshow data sheet enough to spark a conversation?
You might have influence or even authority. You absolutely have a need. And the timing? Yesterday, of course. However, one key ingredient is missing: budget.
We partner with platform teams and other technical buyers daily to help them navigate these complicated waters. Here are a few strategies we’ve found effective in advancing internal conversations about cloud development environments.
By framing the conversation around company goals and providing a clear business case, you stand a better chance of turning what could be perceived as a “nice to have” into a “must have.” You often have one swing at this, so let’s make it count.
We’re all technically minded, but it’s important to refrain from immediately diving into the feature-level details, take a step back, and consider what your leadership team cares about most. In the era of doing more with less, but not at the expense of speed and security, it’s a safe bet that your company’s objectives closely align to:
Your role is to connect the dots between these strategic objectives and the outcomes a CDE like Coder offers. While you might get excited about how you can scale Coder on K8s, your leadership team wants to know how that translates into tangible benefits for the business.
One of the first things executives want to know is how a new tool or initiative impacts the bottom line. If you ask them to invest in Coder, you must show how it will save money, improve efficiency, or ideally both.
Starting points to consider:
Your case becomes much more compelling when you quantify these benefits in terms of dollars saved or hours gained. If you need air support for this, let us know. One of our first steps is to help you craft a detailed value hypothesis because if we can’t help you prove the value, then nothing else matters.
Security is another high-priority issue for leadership teams. A security breach or non-compliance can result in massive financial penalties, reputational damage, and operational disruptions. For many companies, the cost of mitigating these risks is a primary driver behind new investments.
Key points to address:
By focusing on how Coder minimizes security risks, you’ll help leadership see that it’s not just a productivity tool – it’s a risk management solution.
Another important step is to tie Coder’s benefits to any ongoing or planned strategic initiatives within your company. Is your organization undergoing a digital transformation? Is there a push toward remote work? Are local development environments the final boss fight in a broader migration to the cloud?
Show how Coder fits within these broader efforts and helps support key initiatives.
Possible angles to explore:
By linking Coder to larger, organizational initiatives, you’ll help leadership see it as a strategic investment, not just another tool for developers.
Ultimately, most purchasing decisions come down to ROI. If you can demonstrate a clear return on investment, you’re much more likely to get the green light. We can help you use hard data and real-world examples wherever possible.
Here’s how to build a strong ROI case for Coder:
Providing a clear, numbers-driven argument can be the key to unlocking the budget for Coder. We’ve found that conservative value hypotheses are a powerful strategy for advancing the conversation around CDEs. Even if we cut those projections in half (and in half again), they still deliver a compelling business case that is hard to dismiss.
When it comes to winning executive buy-in for a CDE, it’s all about making the case in terms of business value. Developers and engineers naturally focus on the technical side of things, but leadership is more interested in how a tool will impact efficiency, security, and the company’s bottom line.
By tying Coder’s benefits to organizational goals like cost savings, risk reduction, and strategic initiatives, you’ll be better positioned to secure the support you need. Approach the conversation from their perspective, show measurable benefits, and frame Coder as a critical piece of the bigger picture.
Next steps: Prepare your case, gather your data, and let us help you present Coder as a business solution your company needs.
Subscribe to our Newsletter
Want to stay up to date on all things Coder? Subscribe to our monthly newsletter and be the first to know when we release new things!