The Hidden Costs That Make Your Burn Rate Calculation Wrong
I've been deep in startup financial data for a while now, and there's one thing I keep seeing over and over: founders think they know their burn rate, but the number in their head is almost always too optimistic.
Not by a little. By enough to think they've got 18 months of runway when it's really closer to 12. That's the difference between a comfortable fundraise and a panic round.
Here's where it usually goes wrong.
You're probably counting revenue that isn't really there
Your Stripe dashboard says $30K MRR. Cool. But that's not $30K hitting your bank account.
Stripe skims about 3% off the top. Then you've got failed payments, someone's card expired, a charge got flagged, that quietly eats another 1-3%. And if you're selling annual plans, that cash came in upfront but you're recognizing it over twelve months, which makes your monthly picture look different depending on how you're tracking things.
When I looked at the data, healthy SaaS companies typically see a 5-15% gap between what their dashboard reports and what actually lands in the bank. That's not a rounding error. If your runway calculation is based on the dashboard number, it's off by that same gap.
The boring fix that actually works: stop calculating burn from your metrics dashboard. Use your actual bank statements.
People are way more expensive than their salary
This one burns founders (pun intended) more than anything else.
You hire someone at $70K and budget $5,800 a month. But the real cost is more like $7,500-8,000 once you pile on employer-side payroll taxes, health insurance, a laptop, software licenses, and the fact that they're going to be at maybe 60% productivity for the first couple months while they ramp up.
And look, I get the appeal of contractors. The hourly rate looks cleaner, there's no commitment, no benefits to pay. But once someone's doing 30+ hours a week for you, the math often flips. You're paying a premium rate for someone who doesn't have the full context, needs more back-and-forth, and isn't building institutional knowledge.
The pattern I keep seeing validated: every pre-revenue hire cuts runway by 20-30%. Most founders hire too early because it feels like progress. Sometimes the highest-leverage move is just... not hiring yet.
Your hosting bill is lying in wait
Infrastructure costs don't grow smoothly with your user count. They're more like a staircase. You're cruising along at one tier, everything's fine, and then you hit some threshold and your bill jumps overnight.
It might be a database connection limit. Or your logging tool's ingestion cap. Or an API you depend on that charges dramatically more past a certain request volume. Every SaaS tool you use has pricing cliffs somewhere, and they all seem to hit at the worst possible time.
If you're modeling infra costs as "current cost + 10% per month" or something like that, you're going to get caught off guard. It's worth actually mapping out where each service's pricing jumps are and when you'll hit them based on projected growth.
The question nobody wants to answer
Here's an exercise that's uncomfortable but clarifying. Split your spending into two piles:
Pile one: everything it takes to keep the product running for the customers you already have. Hosting, support, maintenance, current team payroll. The lights-on number.
Pile two: everything you're spending to grow. Marketing, new features, hires you're making ahead of revenue.
Now ask: if you stopped everything in pile two tomorrow, are you profitable?
If yes, you have options. Growth is a choice, not a survival requirement.
If no, you're dependent on future growth to stay alive. That's not inherently bad, but it's a fundamentally different risk profile, and you should know which side you're on.
Paul Graham framed this as "default alive vs default dead." Take your revenue growth rate and your expense growth rate, project them forward. Do the lines cross before your cash runs out? If yes, default alive. If no, something has to change. Faster growth, lower spending, or more funding.
A surprising number of founders have never actually run this calculation. It takes ten minutes and it might be the most important ten minutes you spend this month.
Some benchmarks for gut-checking
For what it's worth, here's roughly what the data shows at different stages:
Pre-seed companies typically burn \(15-30K a month and target 12-18 months of runway. Seed stage is more like \)50-100K monthly with an 18-24 month target. Series A, $150-300K with the same 18-24 months.
The consistent advice across all stages: start fundraising when you have 6 months left. The process takes 3-6 months, and trying to raise when you're almost out of cash means you're negotiating from a position of weakness. Investors know what desperation looks like.
On unit economics, even early, it's worth tracking LTV:CAC (aim for 3:1+), CAC payback period (under 12 months), and gross margins (70%+ for SaaS, and if you're below 60%, fix that before you scale because scaling negative-margin customers just makes the problem bigger faster).
Run your own numbers
I built free calculators for all of this because I got tired of the same spreadsheet gymnastics every time:
No signup, no paywall. Just plug in your numbers and see where you actually stand, not where you hope you stand.