The conversation with a founder about cloud costs is different from every other stakeholder conversation
Not because founders are harder to talk to. Because they're carrying the full weight of the context
They know the runway. They know what the next funding milestone requires. They know which engineers are overwhelmed and which projects are already delayed. They know the customer who complained about performance last week and the investor who asked about infrastructure costs in the last check-in
When you walk into that conversation with a list of optimization recommendations, you're not just talking about compute instances. You're talking about time, money, risk, and what's possible
The conversation goes better when you start with their frame, not yours
What is the cloud bill doing to your planning right now? Is it a constraint on what you can hire? Is it eating runway faster than expected? Is it something you think about or something you've mostly accepted?
Let them tell you what it means to them before you tell them what you found
Because what you found means different things depending on their situation
$5,000 a month in savings is a rounding error to one founder and three months of additional runway to another
The same finding lands completely differently depending on what they're trying to do
After you understand their context, present the findings in their terms
Not "we found an oversized RDS instance" but "this one change reduces your monthly cloud spend by $1,400 and requires about half a day of work with low rollback risk"
Not "we should implement S3 lifecycle policies" but "this is a four-hour change that reduces storage costs permanently and requires no ongoing maintenance"
Make the decision easy
Founders are making a hundred decisions. Make the cloud cost decision the simplest one they make this week
The technical work is yours. The decision to proceed is theirs. Respect that boundary and the conversation will almost always go well
Top comments (0)