Every enterprise executive who has been in their role for more than three years has a cloud horror story. The migration that came in at three times the original budget. The lift-and-shift that lifted costs without shifting any outcomes. The cloud-native rewrite that took two years and still is not done.
When you walk into a room to propose a cloud transformation, you are not starting from zero trust. You are starting from negative trust. The people in that room have approved programs that failed. Their reputations are partially staked to those failures. The last thing they want is to approve another one.
Stop leading with technology
Nobody in the C-suite cares about the orchestrator. They care about speed to market, operational cost, and competitive risk. If your pitch deck has an architecture diagram on slide three, you have already telegraphed that you do not understand what the meeting is for.
Lead with the business problem. A Nordic retailer losing market share because their release cycle is quarterly while their main competitor ships weekly. A financial services firm spending 38% of their engineering budget on infrastructure maintenance instead of product development. A manufacturer who cannot get real-time insights from their IoT fleet because the on-premises stack cannot scale to the event volume the new product line requires.
The technology is how you solve the problem. It is not the story.
Acknowledge what went wrong before
If the organization has had a failed cloud initiative, name it. Not to assign blame, but to demonstrate that you have done the work to understand the pattern and have a concrete view on why the previous attempt failed.
The common failure modes are not mysterious. Scope was too ambitious: someone tried to migrate a full datacenter instead of picking a single workload that would prove the model. Success was not defined: the objective was “move to the cloud” instead of “reduce deployment time from two weeks to two days for the payments team.” The team was not ready: technology changed, but processes, skills, and organizational incentives did not.
When you show that you have diagnosed which of these applied in this specific case, you are demonstrating something that no reference customer case study can demonstrate. You understand them. That is how trust gets rebuilt.
Frame it as a capital allocation decision
Cloud transformations that get funded and stay funded are positioned as business investments with measurable returns, not IT modernization projects buried in the technology budget. The framing matters more than the substance, because the framing determines who is in the room and what decisions they feel authorized to make.
Structure the conversation around three things executives actually have discretion over.
Revenue acceleration. How does this help us ship faster, enter new markets, or serve customers better? Be specific. “Faster” is not an answer. “Three-week reduction in the deployment cycle for the product team working on the checkout flow” is an answer.
Cost structure change, not cost reduction. “Cloud is cheaper” is not true in the first two years and experienced executives know it. What is true is that cloud changes the cost model from fixed to variable, and frees engineering capacity from infrastructure maintenance. That argument works. The oversimplified one does not.
Asymmetric risk. What happens if we do not do this? What is the competitive cost of staying on the current platform for another three years while faster-moving competitors are iterating weekly? The do-nothing option has risk too. Make it visible.
Start small, prove the model, expand with evidence
The era of fifty-million-pound multi-year transformation programs approved in a single meeting is over. The executives who approved those programs have the scar tissue to show for it.
Propose a focused engagement. One workload. One team. Ninety days. Clear success metrics agreed upon before work starts. Not metrics you define and present back to them, but metrics they name in the scoping session because these are the numbers they already report to their own management.
When the focused engagement works, the results do the selling for the next phase. Every successful ninety-day program I have been part of generated more long-term revenue than any big-bang proposal could have. Trust is built in increments, and so are durable transformations.
The executives who have been burned before are not the hardest audience. They are the most important one, because their buy-in carries more organizational weight than any committee approval. The path to that buy-in runs through honest diagnosis, specific framing, and the discipline not to oversell.