Runway Planning for Bootstrapped Founders

Runway planning is calculating how many months of cash you have before your money runs out, then using that number to make decisions early instead of in a panic. For a bootstrapped founder it means adding your personal savings to any business cash, dividing by your net monthly burn (spending including your own living costs, minus revenue), and watching that date move as revenue grows.

I am a solo founder, pre-revenue, building several products at once from Bharatpur, Nepal. So I am writing you the math and the decision rules, not reporting my exact bank balance. I have savings and a monthly burn like anyone else, and I am not going to invent precise figures to sound authoritative on a blog. Every number below is illustrative and labeled as such. The formulas are universal. The judgment is what I actually use to decide when to keep building and when to change course.

Runway is a cash question, but it lives next to your revenue metrics, so read this alongside break-even MRR, the metric founders ignore, the founder finance dashboard that tracks cash and burn week to week, and the bootstrapped founder metrics dashboard that houses the wider set. All of it sits under the broader Founder Systems pillar, where the operating rituals live.

Key takeaways

• Runway planning for a bootstrapper counts personal savings plus business cash, divided by net burn that includes your own living costs. The venture formula that ignores the founder’s rent does not apply to you.
• Runway is always computed on net burn, not gross burn. Every dollar of monthly revenue subtracts from burn and pushes the date out.
• Run four scenarios, not one: base case, cut-costs case, raise-price case, and revenue-grows case. Each moves the runway date by a different amount.
• Act at the 6-month mark, not the last 30 days. Cost cuts and price changes take weeks to reach your bank account, so early decisions do more work.
• Crossing founder break-even, where revenue covers business plus living costs, makes runway effectively infinite. That is the finish line, not a fundraise.

What runway really is for a bootstrapper

Runway is the number of months your cash lasts at your current rate of spending. That definition is simple. The trap is that the standard version, borrowed from venture-backed startups, quietly leaves out the one cost that dominates a solo founder’s life: you.

A funded startup calculates runway as company bank balance divided by company burn. The founder draws a salary that is already inside that burn number. Your rent, groceries, and health costs are the company’s problem, paid from investor cash.

A bootstrapper has no investor cash and often no salary. Your living costs do not show up on a company P&L, so they are easy to forget in the math. But they drain the same pool of money that funds the business. If you leave them out, your runway looks twice as long as it is, and that error is the one that ends companies.

So the honest version has two changes. First, the cash pool is your personal savings plus any business cash, because for most solo founders those are the same wallet. Second, the burn includes your personal living costs, because you have to eat while you build.

That gives you the real bootstrapper’s runway: total cash you can spend, divided by how fast you actually spend it, with revenue counted as a brake. Everything else in this post is a consequence of getting those two adjustments right.

How to calculate your runway

The formula has three inputs. Cash on hand, gross burn, and revenue. Two of them combine into net burn, and net burn is what you divide by.

Cash on hand is every dollar you can put toward this venture: personal savings you are willing to spend, plus any money already sitting in the business account. Do not count money you would never actually risk, like an emergency fund you have mentally walled off. Runway is built on spendable cash, not net worth.

Gross burn is everything that leaves that pool in a month. For a solo founder that is business costs (hosting, tools, contractors, the occasional ad test) plus your own living costs (rent, food, utilities, insurance, everything). If you have no outside salary, your living costs are the biggest line by far, and pretending otherwise is how the math lies to you.

Revenue is the recurring money coming in each month. Early on this is often zero, which is fine. As it grows, it slows the drain.

Net burn is gross burn minus revenue. Runway is cash on hand divided by net burn.

Here is the labeled illustrative math. Say you have $20,000 in spendable savings. Say your gross burn is $2,000 a month: $1,700 in living costs and $300 in business costs. Say you earn $500 a month in revenue. Net burn is $2,000 minus $500, which is $1,500. Runway is $20,000 divided by $1,500, which is about 13.3 months.

Change one input and watch the date move. If revenue in that example were zero, net burn would be the full $2,000 and runway would drop to 10 months. That $500 of revenue bought you more than three months of time. That is the whole game.

One honest note. This is a straight-line estimate. Real runway is lumpy: an annual invoice hits, a launch month costs more, revenue arrives unevenly. The formula gives you the planning number. Your bank balance, tracked weekly, gives you the truth. Keep both.

Gross burn versus net burn as revenue grows

The single most useful idea in runway planning is that net burn falls as revenue rises, even if you never cut a dollar of spending. Founders who only watch gross burn miss this, and they undervalue every bit of early revenue.

Gross burn is mostly fixed in the short term. Your rent does not change because you shipped a feature. Your hosting bill barely moves. So the lever you actually control month to month is the revenue side of net burn.

Walk it forward with illustrative numbers. Suppose gross burn holds steady at $2,000 a month across a year. In month one, revenue is $200, so net burn is $1,800. By month six, revenue has grown to $900, so net burn is $1,100. By month twelve, revenue is $1,600, so net burn is $400.

You spent the same $2,000 every month. But your net burn fell from $1,800 to $400, and your runway got dramatically longer as you went, because the thing you divide by kept shrinking. Static runway math, calculated once at the start on today’s net burn, badly understates how long a growing business lasts.

This is why “months of runway” is a moving target for anyone with revenue, and why you recalculate it every month rather than trusting the number you wrote down on day one. A flat gross-burn line and a rising revenue line together bend the runway curve upward. David Skok’s SaaS metrics work frames revenue growth as the engine of a subscription business; runway planning is where you feel that engine directly, as time bought.

Scenario planning: four futures, four dates

One runway number is a guess about a single future. Scenario planning replaces it with a small set of futures you can actually act on. You do not need a model with twenty variables. You need four cases, because there are only four levers a bootstrapper pulls.

The base case is your current trajectory: today’s cash, today’s burn, and revenue growing at the rate it is actually growing. This is your default clock. Every other scenario is measured against it.

The cut-costs case asks what happens if you reduce gross burn. For a solo founder the big cuts are usually personal, not business, because living costs dominate. Trimming $400 a month of spending lowers net burn and pushes the date out, but there is a floor: you cannot cut your way past rent and food.

The raise-price case asks what one pricing change does. Raising prices lifts revenue per customer immediately, which lowers net burn with no new customers required. This is often the strongest move a bootstrapper has, because it moves the revenue term without the slow work of acquisition.

The revenue-grows case is the one that actually saves you: revenue climbing month over month until it approaches your burn. It is the slowest to arrive and the most powerful, because it is the only scenario that ends the countdown for good instead of just extending it.

Here is the framework as one table.

The Runway Scenarios

Scenario	What changes	Effect on the runway date
Base case	Nothing. Current cash, current burn, revenue growing at its current rate.	Your default clock. The date you are actually running toward today.
Cut costs	Lower gross burn, usually by trimming personal living costs.	Extends the date, but hits a hard floor at rent and food. A brake, not an engine.
Raise price	Higher revenue per customer from a pricing change, no new customers needed.	Extends the date immediately by lowering net burn. Strong effect, fast to apply.
Revenue grows	Revenue climbs month over month toward your burn level.	Bends the date outward and, at break-even, removes it. The only permanent fix.

Run these with your own labeled illustrative numbers on a single spreadsheet tab. Change one input per scenario and read off the new runway. The point is not precision. The point is seeing which lever buys the most time, so you pull that one first.

What should you cut first when runway gets short?

Cut in this order: unused subscriptions, then paid acquisition, then discretionary personal spending, and only then housing or location. The ordering follows two rules. Cut what takes effect fastest first, and never cut anything that removes your ability to earn. A cut that saves $40 a month and costs you a working laptop is not a cut.

The lag matters as much as the amount, and it is the reason a bootstrapper sets the action line at 6 months rather than 2.

Cut	Illustrative monthly saving	Lag before your bank feels it	Real risk
Unused SaaS subscriptions	$30-150	Next billing cycle	Almost none. Do this one today
Annual plans you are mid-way through	$0 now	Next renewal date	Sunk. Cancel the renewal, expect no relief now
Paid ads and experiments	Whatever you were spending	Immediate	You lose a demand signal you may still need
Contractor hours	Their monthly total	One notice period	The work returns to you, so your build time falls
Discretionary personal spending	$100-400	Within a month	Morale, which is a genuine operating input
Housing or location	Often the largest single line	One to three months	Biggest saving, slowest and most disruptive

Two lines are usually mispriced. Founders cancel a $15 tool and keep spending $400 on ads, because cancelling a subscription feels like discipline while stopping an experiment feels like giving up. And they defer the housing question for a year because it is uncomfortable, even when it is the only cut large enough to move the runway date by more than a few weeks.

The floor is real and worth naming. Rent, food, health cover, and the tools you actually build with are not negotiable. A founder who cuts into those buys three weeks of runway at the price of the next six months of output.

The decision points: act while you still have options

Runway planning is worthless if you only look at the number when it is nearly gone. The entire value is in the early warning, and that means deciding at thresholds, not at empty.

Set two lines. The first is the planning line at roughly 12 months out, or wherever you start. At this point you are not worried, you are watching. You recalculate monthly and confirm the trend is going the right way.

The second is the action line at roughly 6 months of runway. When you cross it, you stop watching and start doing. This is where you pick a scenario and execute it: cut a cost, raise a price, take on contract work, or push harder on the revenue lever.

Six months sounds early. It is early on purpose. Every real fix has a lag. A price change takes a billing cycle or two to show up. Cutting a subscription saves money next month, not today. Landing contract work can take weeks of outreach before the first invoice clears. If you start at 6 months, your fixes have time to land while you still have cash.

If you wait until 2 months of runway remain, your option set collapses. You cannot wait for slow revenue growth. You cannot run a careful pricing test. You are left with the desperate moves: fire-sale discounts, a rushed job hunt, or shutting down. The founders who survive are rarely luckier. They just decided earlier. Paul Graham’s How Not to Die makes the blunt version of this point: most startups end because the founders run out of money or morale, and both are things you manage on a schedule rather than discover at the end.

Should you take contract work to extend your runway?

Yes, but cap the hours before you start. Contract work is the fastest cash lever a bootstrapper has, because it does not require a product to grow first. It is also the lever most likely to end the company quietly, since paid client hours crowd out unpaid product hours and the crowding stays invisible while the bank balance improves.

Run the arithmetic before you accept anything. Say gross burn is $2,000 a month, illustratively. Twenty billable hours a month at $50 an hour covers half of it and costs roughly one day a week once you include the unbilled overhead of scoping, calls, and invoicing. That is a defensible trade. Forty billable hours a week at the same rate makes you solvent and makes you an agency of one, and the product stops moving entirely.

Three rules keep it honest. Write the hour cap down before the first project, because the pressure to accept one more engagement is strongest exactly when accepting it does the most damage. Prefer short, well-defined projects to open-ended retainers, since retainers renew by default and quietly become the job. And schedule product time first in the week, then sell what remains, rather than promising client time first and hoping for leftovers.

Here is the strongest argument against my own position. For some founders, contract work is not a bridge, it is the business. If the client work is repeatable, well paid, and something you would happily keep doing, the honest move may be to run a services company that funds a product on the side, and to say so out loud. That is a legitimate outcome, and often a better one than a product that never gets time. What kills people is doing both by accident, at forty hours a week, while telling themselves it is temporary.

The psychological reality: decide from runway, not panic

The hardest part of runway planning is not the arithmetic. It is that a shrinking number is frightening, and fear makes bad decisions. The whole system exists to move your decisions upstream of the fear.

Decisions made at 6 months of runway are calm. You can test a price and wait a month for data. You can decline a bad client. You can keep building the thing you believe in, because you have time to be patient.

Decisions made at 6 weeks of runway are not decisions, they are reactions. You take the first client who offers money, at any price. You slash your pricing to book anything. You ship a half-built feature because you are desperate for a signal. Every one of these is worse than the calm version of the same move, and you make them because panic narrows your vision to the next 30 days.

Paul Graham’s ramen profitable idea is really a psychological one: the moment your revenue covers your minimal living costs, the fear lifts, and you can make good long-term calls because the clock stops threatening you. The number on the dashboard is a proxy for how much freedom your future self has to think clearly.

So treat runway as a commitment device, not a source of dread. You decide the thresholds now, while you are calm, and you agree with yourself to act when you hit them. That way the frightened version of you never has to make the important call. The calm version already made it.

The link to break-even: when runway becomes infinite

Every scenario in this post is a way to buy time. Only one of them ends the game, and that is crossing founder break-even. Understanding this reframes the whole exercise.

Founder break-even is the month your revenue covers everything: business costs and your personal living costs. At that point net burn is zero. And runway is cash divided by net burn, so when net burn hits zero, the division stops making sense. Your cash is no longer draining. The countdown stops.

That is what people mean when they say a bootstrapped business has “infinite runway.” It is not that you have unlimited money. It is that you are no longer spending down your savings, so the amount of time you can keep going is no longer capped by a bank balance. You can run indefinitely on the revenue itself.

Walk it with labeled numbers. If gross burn is $2,000 a month and revenue climbs to $2,000, net burn is zero. Your savings stop moving. If revenue passes $2,000, you are now adding to savings, and runway is not just infinite, it is growing. The finish line for a bootstrapper is not a fundraise. It is this crossing, and runway is simply the clock measuring how long you have to reach it.

This is why break-even and runway are the same conversation from two directions. Runway asks how much time you have. Break-even is the event that makes the question stop mattering. Track your progress toward break-even, in real dollars, using a live view like Baremetrics once revenue is flowing, or a spreadsheet before then. The day revenue meets burn is the day you stop planning runway and start planning growth.

How do you calculate startup runway?

Divide your spendable cash, personal savings plus any business cash, by your net monthly burn. Net burn is total spending, including your own living costs, minus revenue. Say you have $20,000, burn $2,000, and earn $500. Net burn is $1,500, so runway is about 13 months.

How much runway should a bootstrapped founder have?

Start with at least 12 months of net burn, and treat 6 months as the point where you act instead of watch. A bootstrapper cannot count on a raise to refill the tank, so the buffer must absorb slow months and the time it takes revenue to grow toward covering your burn.

What I would do differently

If I were starting over, I would calculate runway on net burn including my living costs from day one, not the flattering business-only version. That single honest number changes how aggressively you spend in the first months, which is exactly when overspending does the most damage.

I would also set the 6-month action line in writing before I ever needed it, and I would recalculate runway on the same day every month. The founders who get caught are not bad at math. They just stopped looking at the number until it was too late to change it, and by then the calm options were gone.

The last thing I would do differently is treat every early dollar of revenue as time bought. When you are pre-revenue it is tempting to dismiss $200 a month as noise. But in the net-burn formula, that $200 is a direct extension of your runway and a step toward break-even. Small revenue is not small. It is the brake pedal, and the only one you fully control.

Want the system, not just the article?

This post is one piece of a larger operating system I am building for bootstrapped founders. The full workbook turns runway planning into a live spreadsheet: the net-burn formula wired up, the four scenarios ready to fill in, the action thresholds built in, and the break-even tracker beside them, so you always know your date.

It is $29, and it is the tool version of everything above. Get the workbook →