Runway Isn't Months. It's Iterations.
Why cutting costs can leave you with FEWER chances to survive
Hey there! 👋
You're reading Open Scout 👀
Most founders calculate runway the same way: cash balance divided by monthly burn. $3 million in the bank, $250K burn, 12 months. Simple. And almost entirely useless for predicting whether the company survives.
Runway denominated in months tells you when you die. It doesn’t tell you how many chances you have to live. A startup burning $500K/month with 18 months of runway that ships one major iteration per quarter gets 6 shots. A startup burning $300K with 24 months that ships every two weeks gets 48 shots. The first company has more cash. The second has 8x more chances to find what works.
If you had to bet on one, you’d pick the second every time, and it wouldn’t be close.
Before we begin... a big thank you to this week’s sponsor: EnergyX
AI Has an 80,000-Ton Lithium Problem
From AI data centers to EVs, energy storage demand’s exploding, and lithium powers it all.
Now Morgan Stanley estimates the market will face an 80,000-ton shortfall this year alone. With 5X lithium demand growth expected by 2040, the deficit is just starting.
Great timing for EnergyX. Their patented tech can recover up to 3X more lithium than traditional methods in a fraction of the time, earning them a $1B private valuation and investment from leaders like General Motors and POSCO. Now, they hold rights to up to 13M tons of lithium across North and South America.
Join 50K investors and buy private EnergyX shares. But don’t wait: you have until July 16 to invest.1
If you’re interested in sponsoring this newsletter, please reach out here.
The iteration budget
Two variables control how many iterations you get. Only two.
→ Cost per iteration. How much does each meaningful experiment cost? If a product experiment burns $50K of engineering time and you find a way to do it for $20K through better tooling or tighter scoping, you’ve more than doubled your shots without raising a dollar. Nobody at the company will notice. It won’t show up in any board deck. Might be the most important thing that happened that quarter.
→ Cycle time. How fast do you complete each iteration? Quarterly shipping gives you 4 cycles a year. Biweekly gives you 26. Same burn. Same runway in months. 6.5x more shots.
Most founders obsess over cost because it shows up in the P&L. But cycle time is often more powerful because faster iterations give you faster LEARNING. Each cycle teaches you something about the market. Faster cycles accumulate intelligence at a higher rate than competitors. That intelligence leads to product-market fit. Revenue arrives sooner. Revenue extends runway organically.
Superhuman understood this. When they launched, only 32% of users said they’d be “very disappointed” without the product. Below the 40% threshold that signals real product-market fit. Instead of a big pivot or a fundraising panic, they ran rapid iteration cycles. Segment users. Identify what the “very disappointed” users had in common. Build specifically for them. Retest. They ran this loop repeatedly until the number hit 58%. Each iteration was small, fast, and informed by the last one. The speed of the loop, not the size of the bank account, is what found product-market fit before the money ran out.
Two feedback loops
Efficiency and speed create two completely different dynamics depending on which direction you’re moving, and once you’re in one, switching is very hard.
The compound loop:
→ Better efficiency → longer runway → more iterations → higher odds of finding what works → revenue arrives sooner → revenue extends runway → even more iterations → growth compounds
Each turn makes the next easier.
The panic loop:
→ High burn → short runway → panic → across-the-board cuts → slower iteration because the wrong things got cut → fewer shots → miss the market → more panic → death
The panic loop almost always starts the same way. A founder treats runway as a financial metric instead of an iteration metric, realizes they’re low, and cuts 20% everywhere. Sounds fair. Sounds disciplined. Except it fires the engineer who shipped fastest and kills the experimental line that was two weeks from a breakthrough and cuts the marketing spend that was generating the most learning. The cuts extended runway by 3 months and cut iterations per month in half. Fewer total shots than before.
You bought time and lost chances.
What to iterate on (changes by stage)
“Iterate faster” is incomplete without “iterate on what.” The target changes as the company matures, and confusing stages is how you end up iterating fast on the wrong thing.
→ Pre-PMF: iterate on value proposition and ICP. Who wants this and why? The question isn’t “how do we grow.” It’s “who SPECIFICALLY would be very disappointed without this and what exactly do we do for them.” Superhuman’s iteration loop was entirely here: segment, build for the segment, retest fit. Every cycle targeted a tighter ICP.
→ Post-PMF, pre-scale: iterate on the growth engine. You know who wants this. Now figure out what channel compounds. Content? PLG? Community? Outbound? Most founders try them all simultaneously. Better to run focused experiments on one channel at a time, measure properly, kill what doesn’t work, double down on what does. Each experiment should have a specific structure:
The iteration structure:
Hypothesis: “We believe [doing X] will improve [metric Y] by [Z%] within [timeframe]”
Minimum viable test: smallest possible version that proves or disproves → Success criteria: defined BEFORE the experiment runs
Learning: what did we learn regardless of outcome?
Next: iterate, pivot, or kill
Without this structure, “iterating fast” is just shipping random changes fast. Speed without direction burns runway with nothing to show for it.
→ Scale: iterate on efficiency. Growth engine works. Now make it cheaper per unit. Reduce CAC. Improve activation. Increase LTV. Each iteration at this stage directly improves the burn multiple, which extends runway, which funds more iterations. The virtuous loop.
The repricing experiment
Probably the most underused iteration in the entire playbook, and the one with the highest ROI per experiment.
Most companies iterate on product features 50 times before iterating on pricing once. That’s backwards. A single pricing change can shift your burn multiple by 0.5-1.0x overnight. No feature change in history has had that kind of immediate financial impact.
If you’re charging $50/month and your burn multiple is 2.0x, raising to $80 might drop it to 1.3x. Same product. Same team. Same iteration speed. Dramatically extended runway. The customers who leave at $80 told you something valuable: they weren’t your ICP. The ones who stay told you something more valuable: your product is worth more than you thought.
Most founders avoid repricing because they fear churn. But churn from a price increase is the most informative data you’ll ever collect. High churn means you haven’t built enough perceived value yet and need to iterate on the product. Low churn means you’ve been leaving money on the table and can immediately extend your runway without cutting anything.
Run it as an experiment. A/B test new pricing on a cohort. Measure retention at 30, 60, 90 days. Compare LTV. The data will tell you whether the price increase is net positive or net negative, and either answer is useful.
The math is stark. A 20% price increase with 10% churn is massively net positive. You lose 10% of customers and gain 8% more revenue from the remaining 90%. Your burn multiple improves. Your runway extends. Your iteration budget grows. One experiment. One week. More impact than months of feature development.
Which bucket you’re actually in
Sequoia put out a framework with three buckets that I think is useful:
→ Bucket 1: Less than 12 months. Existential. Fundraising is priority one.
→ Bucket 2: 12+ months but not enough to hit the metrics your next round requires. Dangerous. You feel safe but the math doesn’t work.
→ Bucket 3: Enough runway to reach the next milestone or profitability. Genuine safety.
Most founders in Bucket 2 think they’re in Bucket 3 because 18 months sounds comfortable. But do the math:
→ Last round at $100M valuation → Current ARR: $3M → Flat round requires roughly $15-25M ARR → At current growth: 2.5-3 years → Current runway: 18 months → Gap: 12-18 months short
Now the real question: can you reach profitability on current trajectory without raising? Project your revenue growth and expense growth forward month by month. If revenue crosses above expenses before cash hits zero, you survive. If cash hits zero first, you need either a raise, a fundamental change, or both.
Most founders don’t run this calculation because the answer is usually uncomfortable. But knowing the answer changes every decision you make, because it tells you how many iteration cycles you have to find the lever that changes the trajectory. At biweekly speed with 18 months, that’s 36 shots. Might be enough. At quarterly speed, 6 shots. Probably not.
The burn multiple
The metric investors use to evaluate iteration efficiency: net burn ÷ net new ARR.
2026 benchmarks:
2.0x was fine at Series A in 2023. Top quartile is now 1.0-1.2x. AI-native companies at 0.8-1.2x reset investor expectations for everyone. 56% of seed, 83% of Series C+ investors call it critical.
At 0.8x, each iteration cycle is nearly self-funding. At 2.5x, each cycle drains reserves fast. Same starting cash, the 0.8x company gets 3x more iterations. Pair with the Rule of 40 (growth + margin ≥ 40%, 2-3x higher multiples) and you have the full efficiency picture.
An interesting signal from the data: bootstrapped SaaS grows at 23% annually, VC-backed at 25%. Two percentage points. But bootstrapped companies show higher revenue per employee at every ARR band. The growth gap is nothing. The efficiency gap is enormous. Which means venture capital typically isn’t buying growth rate. It’s buying headcount. And headcount doesn’t correlate with growth as strongly as the industry assumes.
Where to find iterations
Every dollar either contributes to iteration speed or doesn’t.
Protect (drives iterations):
Engineering that ships. The iteration engine itself.
Customer-facing roles that generate learning.
Deployment infrastructure that reduces shipping friction.
AI tooling that multiplies per-person output.
Scrutinize (doesn’t drive iterations):
32% of cloud spend is wasted. 15-25% of budgets go to redundant tools. Consolidation isn’t austerity. It’s removing complexity tax.
Headcount that neither ships nor learns.
Fixed overhead disconnected from output.
Learning velocity > growth velocity
Most founders, most investors, most board meetings focus on growth velocity. How fast is revenue growing? What’s the month-over-month ARR trajectory?
But before product-market fit, growth velocity is the wrong metric. Learning velocity is the right one. How fast are you accumulating understanding about what works? How quickly do you move from “we think this might work” to “we know this works” or “we know this doesn’t”?
A company with high learning velocity and low growth velocity is about to find product-market fit. A company with low learning velocity and high growth velocity is about to discover its growth was artificial. The first company is Superhuman running its “very disappointed” loop weekly. The second is a company burning cash on paid acquisition to hit an ARR milestone that looks good in a board deck but isn’t backed by real retention.
Every efficiency lever in this essay, faster iterations, lower cost per experiment, the repricing test, protecting engineering while cutting overhead, works because it increases learning velocity. More experiments per dollar. More data per cycle. More understanding per month. The company that learns fastest doesn’t always win. But the one that runs out of iterations before learning enough always loses.
38% of startup failures come from cash depletion. Not because the founders weren’t smart. Because they ran out of shots before finding what works. The iteration count is the real runway. Everything else is accounting.
Thanks for reading.
If you enjoyed this issue, send it to a friend—it helps more than you think.
Back in your inbox Thursday,
Energy Exploration Technologies, Inc. (“EnergyX”) has engaged Open Scout to publish this communication in connection with EnergyX’s ongoing Regulation A offering. Open Scout has been paid in cash and may receive additional compensation. Open Scout and/or its affiliates do not currently hold securities of EnergyX.
This compensation and any current or future ownership interest could create a conflict of interest. Please consider this disclosure alongside EnergyX’s offering materials. EnergyX’s Regulation A offering has been qualified by the SEC. Offers and sales may be made only by means of the qualified offering circular. Before investing, carefully review the offering circular, including the risk factors. The offering circular is available at invest.energyx.com/.
Comparisons to other companies are for informational purposes only and should not imply similar results. Past performance is not indicative of future results. Market shortfall are forward‑looking estimates and are subject to substantial uncertainty.
Definitely the best shift in perspective that I have came across, thank you for this!