Burn rate and runway are the two numbers that tell you how long your startup can survive: burn rate is how much cash you lose each month, and runway is how many months you have left before the bank account hits zero. The runway formula is simple: cash in the bank divided by your monthly net burn.

That’s the whole idea. The hard part isn’t the math, it’s doing the math every month, being honest about the inputs, and picking the date you’ll make a call before the number makes it for you.

What burn rate and runway actually measure

In the video above, Y Combinator partner Tim Brady puts it in one line: “burn rate is a measurement of cash flow, not profit and loss.” That’s the bit most founders get wrong. Your P&L can say you had a great month while your bank balance tells a very different story, because a signed contract that pays next quarter does nothing for this month’s cash.

Brady’s other line is the one I’d tape to the monitor: “running out of cash is usually how startups die.” Not bad ideas. Not competitors. Cash.

So when people say startup runway or cash runway, they mean the same thing: months of cash left at your current pace. Everything below is about getting that number right and then acting on it.

Gross burn vs net burn: which one matters?

There are two burn numbers, and you need both.

• Gross burn is every dollar of cash going out the door in a month: payroll, contractors, rent, software, ads, insurance, all of it. It ignores revenue. It tells you how heavy your cost base is.
• Net burn is gross burn minus the cash that actually came in from customers that month. It tells you how fast the bank balance is really shrinking.

Runway uses net burn. Gross burn is still worth watching, because it’s the number that stays with you if a big customer churns or pays late. A founder with $80,000 gross burn and $30,000 of revenue is in a very different spot from one with $50,000 gross burn and zero revenue, even though both have $50,000 net burn. The first one has more to lose if sales wobble.

One rule I’d hold firm on: money from investors, loans or your own pocket isn’t revenue. A fresh SAFE makes the bank balance bigger. It doesn’t make your burn smaller.

How to calculate burn rate and runway, step by step

Here’s how to calculate burn rate without fooling yourself. Do it from your bank statements, not your accounting software’s profit report.

1. Pull the last three months of bank activity. One month lies. An annual software renewal or a big quarterly tax payment can make a single month look awful or great. Three months smooths that out.
2. Add up all cash out for each month. That’s gross burn. Average the three months.
3. Add up cash in from customers only. Leave out funding, loans, transfers between your own accounts and anything you put in personally.
4. Subtract. Average gross burn minus average customer cash in equals net burn.
5. Divide your current cash by net burn. That’s months of runway.
6. Re-run it with what’s already committed. The hire who starts next month, the new office lease, the price increase from your cloud provider. Backward-looking runway is a comfort blanket. Forward runway is what’s real.

A worked burn rate example (with example numbers)

Picture a founder with a small software company and $600,000 in the bank. These are example numbers for teaching, not benchmarks. Her average month looks like this:

Twelve months feels like plenty. Now she adds the engineer she’s been planning to hire in month three, at $12,000 a month all-in. After two months at the old pace she’s got $500,000 left, and her net burn jumps to $62,000. $500,000 divided by $62,000 is about 8 more months. Total runway: roughly 10 months, not 12.

One hire just cost her two months. That’s not an argument against hiring. It’s an argument for knowing the price before you sign the offer letter.

And notice her own salary is in there. If you’re paying yourself nothing to stretch the runway, you’re hiding a cost that comes back later, so work out how to pay yourself as a business owner and put the real number in the model.

Default alive or default dead? The question behind the runway formula

Runway assumes nothing changes. Revenue usually does. That’s why I like Paul Graham’s test from his 2015 essay Default Alive or Default Dead? He asks founders: “Assuming their expenses remain constant and their revenue growth is what it has been over the last several months, do they make it to profitability on the money they have left?”

Run that on our example founder, with expenses flat at $80,000 and revenue starting at $30,000:

• Revenue growing 5% a month: she crosses $80,000 in month 21 with about $45,000 left. Default alive, technically. That’s a terrifyingly thin cushion, but she lives.
• Revenue growing 3% a month: the cash runs out in month 15. Default dead.

Two points of monthly growth is the difference between a company and a cautionary tale. That’s why I’d rather see founders obsess over this one question than over a fancy dashboard.

Graham also says half the founders he talks to don’t know which one they are, and that the trap is assuming it’ll be easy to raise more money: “that assumption is often false, and worse still, the more you depend on it, the falser it becomes.” His fix is blunt. Write down “precisely what you’ll need to do to survive if you can’t raise more money, and precisely when you’ll have to switch to plan B if plan A isn’t working.”

That second part, the “when,” is your decision date.

How long does a raise take? Set your decision date before you need it

Your decision date is the day you commit to one of three paths: raise, cut, or get to profitable. Pick it while you still have options, because every month you wait takes options off the table.

If raising is on the list, be realistic about time. DocSend’s research with Harvard Business School professor Tom Eisenmann found that “the average length of time it takes to complete a seed round is 11-15 weeks,” and DocSend recommended allowing “six months of runway to raise funds,” three months to pitch and three more to work out a plan B if nobody bites (DocSend, 2019). That data is a few years old, so treat it as a floor, not a promise.

The gap between rounds is longer than most first-time founders expect too. Carta’s Q1 2026 report says “the typical period between seed and Series A stands at an even two years,” with a median of 2.1 years from Series A to Series B (Carta, State of Private Markets Q1 2026). That’s a median, so half of companies took longer.

Back to our founder with 10 months of real runway. If she wants six months for a raise plus plan B, she has to be pitching by month four. Give her a month to prep the numbers and the deck, and her decision date is about month three. Not month nine. Month three.

Raise, cut, or get profitable: what to do on your decision date

When the date arrives, you look at the default alive math and pick. No hand-waving.

• Raise if growth is strong enough that investors will actually care, and you’ve got at least six months of runway to run a real process. Graham’s warning applies: never treat fundraising as more than plan A.
• Cut if you’re default dead and growth isn’t going to fix it in time. Cut early and once, not a little every month. Graham calls hiring too fast “by far the biggest killer of startups that raise money,” so payroll you added ahead of demand is the first place to look.
• Get profitable if you’re close. Raise prices, chase overdue invoices, move customers to annual prepay, drop the spend that isn’t pulling its weight. Founders who bootstrap a startup without investors live on this path every month, and it’s a lot less scary once you’ve done the math.

None of these is the “right” answer in general. The right answer is the one you choose on purpose, with numbers in front of you, instead of the one forced on you in month nine.

The monthly runway habit that keeps you honest

Knowing the formula is worthless if you calculate it once for a pitch deck and never look again. This is the gap I see everywhere: founders who can explain burn rate perfectly and still couldn’t tell you this month’s number.

Put 30 minutes on the calendar on the first business day of every month. Pull the bank data. Update gross burn, net burn and runway. Re-run the default alive check. Look at your decision date and ask if it’s moved. Then tell your co-founder or your board the number, out loud, even when it’s ugly. Especially when it’s ugly.

Do that for a year and you’ll never be surprised by your own bank account. That alone puts you ahead of half the founders Paul Graham talks to.

Frequently Asked Questions

What is the difference between gross burn and net burn?

Gross burn is all the cash you spend in a month. Net burn is gross burn minus the cash customers paid you that month. Runway is calculated with net burn.

What is the runway formula?

Runway in months equals cash in the bank divided by monthly net burn. With $600,000 in cash and $50,000 net burn, you have 12 months, before any new hires or changes.

Is burn rate the same as net loss?

No. Burn rate measures cash leaving the bank, while net loss is an accounting figure. Revenue you’ve booked but haven’t collected doesn’t reduce your burn until the cash arrives.

How much runway should a startup have?

There’s no single number, but leave room to raise or change course. DocSend’s research found seed rounds took 11 to 15 weeks and suggested six months of runway for a raise plus plan B.

What does default alive mean?

Paul Graham’s term for a startup that reaches profitability on the cash it has, assuming expenses stay flat and revenue keeps growing at its recent rate. If it doesn’t get there, it’s default dead.

Most startup advice sounds bulletproof until you look under the hood and realize that another wildly successful company did the exact opposite.

You will read a viral thread about how a massive tech giant built a billion-dollar empire entirely on inbound marketing—writing ebooks, hosting webinars, and patiently educating their audience. Then, you look across the street, and a competitor just hit a $1.6 billion valuation by ignoring content entirely, leaning heavily into aggressive outbound sales and a self-serve product. Another company becomes a unicorn while bragging about bootstrapping and raising zero dollars, while the next one raises $150 million in venture capital to ruthlessly dominate a crowded market.

Every single one of these companies cleared the $100 million revenue mark. Every single one of them had completely contradictory strategies.

If you just copy someone else’s famous playbook without understanding why they ran it, that exact same strategy will quietly destroy your business. The winning move always depends entirely on the biggest constraint holding your specific company back.

The Constraint-First Strategy

A growth engine only works when it solves the actual problem blocking your revenue. Let’s look at four original examples that prove why identifying your core constraint is the only strategy that matters.

Constraint 1: The Market Lacks Belief (The Education Play)

When Gainsight launched, the concept of “Customer Success” barely existed. Companies had customer service departments that answered angry phone calls, but they didn’t proactively manage customer health to prevent churn.

Gainsight couldn’t just run Facebook ads or cold-call people to sell their software, because their target buyers didn’t even know they had a problem yet. Their constraint was belief.

To solve this, they practically had to invent and define the entire category of Customer Success. They wrote the definitive books, hosted massive industry conferences, and pumped out endless educational content. They didn’t just sell a tool; they taught the market a new way to view business. Once a CEO believed in the framework of Customer Success, buying Gainsight’s software was the only logical next step. The Lesson: If your customers do not fundamentally understand the problem you solve, you have to let education create the market.

Constraint 2: The Market Lacks Speed (The Product-Led Play)

On the complete opposite end of the spectrum is Calendly.

Nobody needed to read a 40-page whitepaper about how annoying it is to send six emails back and forth to schedule a 15-minute zoom call. The pain was obvious, and the market was highly aware of it. Calendly’s constraint was not belief; it was access and friction.

Because the problem was universally understood, they didn’t waste time on massive educational inbound marketing. They built a self-serve, product-led growth engine. You sign up for free, you send a link, and the person on the other end experiences the product instantly. It spread virally because they shortened the distance between a known problem and a useful result. The Lesson: If the market already knows they are bleeding, stop trying to educate them. Remove the sales friction and let them experience the bandage immediately.

Constraint 3: The Market is Fragmented (The Infrastructure Play)

When Plaid entered the fintech space, developers were pulling their hair out trying to connect their new apps to thousands of different legacy banking systems.

The constraint here wasn’t a lack of focus or a need for education. The constraint was brutal fragmentation. Plaid’s strategy was pure utility. They built the infrastructure that connected everything. Every time Plaid added support for a new bank, their product became exponentially more valuable to the developers using it. Their distribution was built directly into their massive scope. The Lesson: When your users are drowning in disconnected tools, your best growth strategy is becoming the universal bridge.

Constraint 4: The Market Lacks Focus (The Niche Play)

When Nathan Barry started ConvertKit, the company was flatlining. It was a flexible email marketing tool, which sounds great on paper, but it meant they were competing with massive giants like Mailchimp for every single type of customer.

Their constraint was a total lack of focus. The product could do too many things for too many people, meaning the marketing message was watered down and easily ignored.

Barry made a terrifying decision: he narrowed the product aggressively to serve only “creators” (bloggers, authors, podcasters). He essentially fired the rest of his potential market. By doing this, he could talk to creators about their specific pain points in a way that Mailchimp never could. That narrow focus built intense credibility, sparked massive word-of-mouth growth within that specific community, and scaled the company to hundreds of millions in revenue. The Lesson: If your product is a “nice-to-have” for everyone, it is a “must-have” for no one. Shrink your market to find your leverage.

The 3-Step Constraint Audit

Before you commit your limited cash and runway to a new growth strategy, you have to find your real constraint. Ask yourself these three ruthless questions:

1. Where does our growth actually break down? Look at the math, not your emotions. Do people fail to discover you at all? Do they discover you, but bounce because the pitch is confusing? Do they sign up, but never hit the “aha” moment in the product? Or do they use it once and churn? Those are four entirely different constraints, and they require four radically different strategies. You cannot fix a retention problem with a better marketing funnel.

2. Does our runway match the strategy timeline? An inbound, SEO-heavy education engine like Gainsight’s takes years to compound and mature. If your startup only has six months of cash left in the bank, you physically cannot afford to copy a strategy that takes three years to yield a return. You have to match your playbook to your bank account.

3. Does this get cheaper as it scales? If you are running a proper growth strategy, the unit economics should improve over time. If you are producing content, your customer acquisition cost should slowly fall as your library attracts organic traffic. If you are relying on outbound sales, the lifetime value of the contracts you close must comfortably exceed the cost of hunting them down. If you are just burning cash without seeing these efficiencies improve, you are not building a growth engine—you are just funding an expensive hobby.

Here is a great video on why some startups fail:

Stop Looking at Their Highlight Reel

Founders love to debate the merits of bootstrapping versus venture capital, or inbound versus outbound marketing. But the market does not care about your philosophy. Your revenue numbers are the only things that settle the argument.

Before you read another guru’s advice or try to carbon-copy the strategy of a famous unicorn, lock yourself in a room and identify the exact choke point starving your business of revenue. When you understand what is actually holding you back, you stop playing someone else’s game and start engineering the exact tool required to break through your own ceiling.

The Big Lie of the Tech Press

In March of 2026, MyFitnessPal acquired a calorie-tracking app called CalA. By the time it sold, the app reportedly had over 15 million downloads and was generating north of $30 million in annual revenue. It was built by teenagers still in high school.

The detail that actually matters? They never raised a single dollar.

When the acquisition offer arrived, there was no board of directors to consult, no venture capital firm taking a massive liquidation preference, and no complicated term sheets dictating the payout. The founders owned 100% of their equity, and the entire sale belonged to them.

There is a quiet revolution happening underneath the flashy headlines of the startup world. A new generation of founders is rejecting the venture capital playbook. They are using AI to build hyper-lean, hyper-profitable software businesses that reach seven and eight figures in revenue without ever taking an investor’s check.

From the outside, a bootstrapped startup and a funded startup look identical. Inside the bank account, they operate like entirely different species. If you want to know how to bootstrap a startup without losing your mind—or your equity—here is the unvarnished playbook.

The Financial Anatomy of a Bootstrapped Business

Picture two artificial intelligence startups, both generating $2 million in Annual Recurring Revenue (ARR).

The Funded Startup:

• Headcount: 20 to 50 employees.
• Operations: Heavy spending on aggressive marketing and a bloated sales team.
• Cash Flow: Intentionally burning $50,000 to $300,000 a month.
• The Trap: The bank account holds a massive sum of investor cash, but it burns down on a strict schedule. The plan is not to be profitable; the plan is to grow fast enough to raise the next round before the money evaporates. The founder owns 20% to 40% of the company, and they only get paid if the company goes public or sells for a massive multiple.

The Bootstrapped Startup:

• Headcount: 5 to 10 employees.
• Margins: 70% to 85% gross margins.
• Cash Flow: Generating a 20% to 40% net profit.
• The Freedom: The profit builds a 6-month cash runway, and the remainder is paid out directly to the founders as distributions (often $200k+ a year each). The founder owns 80% to 100% of the company.

Bootstrapping forces extreme operational discipline. Every new software tool, ad dollar, and hire must pay for itself quickly because there is no safety net. But that paranoia creates resilience. Data shows that the best bootstrapped companies reach $1 million in ARR only four months slower than venture-backed companies.

Four months of speed in exchange for owning 100% of your company. That is the ultimate founder trade.

The 4 Business Models Built for Bootstrapping

Not every business can be bootstrapped. If you are building a two-sided marketplace (like Uber), a consumer social app, or a hardware product, you need massive upfront capital. Bootstrapping those models is a death sentence.

However, if you want to scale on your own revenue, you must choose a model where the cash comes in faster than the expenses go out.

1. Vertical SaaS (Software as a Service): You build software for one highly specific industry—gyms, roofers, or salons. The problem is painful, the churn is low, and customers pay $50 to $500 a month reliably.
2. Productized Services: You take a messy service (like design, consulting, or SEO) and package it with a fixed scope and a fixed price. Clients pay upfront. Margins reach 40% to 70%, and you use the cash flow to build your software later.
3. Information & Community: Paid newsletters, specialized courses, and private communities. The margins are 80% to 95% because delivering one more digital copy costs you nothing.
4. The Self-Serve AI Tool: A single, lightweight utility that solves one specific problem so cleanly that customers sign up without ever talking to a human. Think AI headshot generators or specific data scrapers.

The Audience Is Your Seed Round

Funded startups buy their customers. They spend massive venture rounds on Facebook ads and Google clicks. Bootstrapped startups cannot afford to play that game early on.

Instead of buying attention, they own it.

The most successful bootstrapped companies scale via organic search (SEO), content marketing, tight-knit communities, and raw word-of-mouth. The financial difference is staggering.

A funded company might spend $300 on ads to acquire a customer who pays them $500 over a year. A bootstrapped company spends zero dollars on ads to acquire a customer via their newsletter who pays them $500 over three years.

Furthermore, ad traffic is transactional; community traffic is loyal. Customers who find you through your content already trust you, which means they churn slower and pay upfront more often. When you bootstrap, your audience acts as your seed round. It provides the initial capital and distribution without demanding a board seat in return.

The Fatal Flaw: The Comfort Trap

When you raise venture capital, discipline is forced upon you by investors analyzing your burn rate. When you bootstrap, nobody is watching. And that absolute freedom is what kills most profitable companies.

A solo founder hits $20,000 a month in recurring revenue. For the first time in years, they feel rich. The “ramen days” are over. So, they upgrade their apartment, buy a new car, and hire an assistant because they “earned it.” They go from scrappy and paranoid to soft and comfortable.

Then, an algorithm changes, churn spikes, or a stripe payment gets delayed. That massive cash buffer they thought they had turns out to be only six weeks of runway. The founder is forced to fire their team and slash growth just to maintain a lifestyle the business could never truly afford.

The Fix: You must enforce a rigid corporate salary on yourself from day one. Pay yourself the market rate for your role. Every dollar above that is company profit, not personal spending money. Half of that profit goes into a cash buffer and growth; the rest can be distributed. You only raise your personal salary after the company’s revenue has held at a new high for six consecutive months.

The Ultimate Leverage

The strangest part of bootstrapping is how it ends. The founders who fight through the grind, optimize their margins, and build a multi-million-dollar company without ever needing an investor… become the exact founders investors aggressively hunt down.

When a profitable, $5M ARR bootstrapped founder finally takes an investor meeting, the dynamic is entirely flipped. They are not asking for survival money. They are saying, “This is my machine. It prints cash. Your money will simply make it spin faster.”

Because they survived the hardest phase without help, they command insane valuations, keep their board seats, and often sell secondary shares to pull millions in cash off the table before an exit.

Bootstrapping requires you to trade speed for control. It demands that you build clean financial books (using tools like Rho to separate personal and business expenses from day one), maintain absolute discipline, and scale only when the customer revenue allows it.

But when the acquisition offer finally arrives, you are the only one sitting at the table.

The company’s task list used to live in three places:

A pinned message in a Slack channel that nobody scrolled back to. A rambling Apple Note on my phone that only I could see. And the version I kept in my own head… which was always more detailed than the other two, and almost always inaccurate by 5:00 PM.

A client would request a small scope change on a Thursday afternoon call. I would say yes, type a quick summary into a team Slack channel alongside a dozen other open discussions, and assume someone would pick it up.

Sometimes someone did. Other times, the request got swallowed by an unrelated conversation about an invoice or a software bug. Three weeks later, the client would follow up asking where their deliverable was, and I would suddenly remember the conversation at 11:00 PM while trying to fall asleep.

I would fire off a late-night Slack message to the team that sounded like an accusation.. even though I was the person who dropped the ball in the first place.

The team adapted to the chaos. Nobody pushed back, and nothing suffered a catastrophic crash.

And that was the dangerous part. When a system fails loudly, you are forced to fix it. When it fails quietly through constant minor leaks, you just work an extra hour each evening and convince yourself you’re being a dedicated founder.

Answering With a Story Instead of a List

During that season, I could give you a rough, poetic description of what the company was doing. What I couldn’t give you.. without opening four browser tabs and interrupting two team members.. was a clear answer to three basic questions:

• What is currently past due?
• What is stuck because it’s waiting on an executive decision from me?
• What did we promise a client last week that we have already forgotten?

A rough, intuitive sense of work is fine when you’re running a solo shop from a coffee table. It completely falls apart the moment you bring other people into the room. We saw an early version of this friction in what to set up before you pay your first employee, where one person can still just barely hold the entire operational state in their skull.

Once you add three, five, or ten people, that habit doesn’t scale—it just gets louder.

More channels. More “hey, quick question” DMs. More work assigned to whoever happened to be looking at their screen when a message landed. The entire company’s delivery schedule became dependent on my personal memory, and my memory was bankrupt.

The Single-Home Rule

The fix did not involve a two-day retreat, a consultant, or a hundred-page operations manual.

It was a single, stubborn rule: If a task is not in the system, it does not exist.

We chose ClickUp. Not because it has better features than everything else on the market, but because it could hold a task, assign one single owner, and stamp a non-negotiable due date without demanding that I become a full-time software administrator. Tools like Asana or Monday handle the exact same job for other teams.

The software brand mattered far less than the death of our three-place system. The work stopped depending on whether I remembered to check a personal note.

                  THE OPERATIONAL ARCHITECTURE SHIFT

┌──────────────────────────────────────┐        ┌──────────────────────────────────────┐

│        THE THREE-PLACE MESS          │        │       THE SINGLE-HOME SYSTEM         │

├──────────────────────────────────────┤        ├──────────────────────────────────────┤

│ • Pinned Slack messages nobody reads │        │ • One tool (ClickUp / Asana)         │

│ • Private phone notes only you see   │  ───>  │ • Exactly one assigned owner         │

│ • Founder memory (always incomplete) │        │ • Clear, visible due date            │

│ • Delivery dates answered with stories│       │ • Status answered with a clear list  │

└──────────────────────────────────────┘        └──────────────────────────────────────┘

The first two weeks were irritating. Tasks were filed in the wrong folders. Team members still posted informal project updates in Slack and waited for someone else to log them. I had to repeat the same sentence like a broken record during every check-in: “If it isn’t in the tool, it isn’t happening.”

By the third week, conversations started getting noticeably shorter.

When a client asked for an adjustment on a call, the reply shifted from “Let me look into that and get back to you” to “It’s already scheduled in the queue for next Tuesday.” I stopped having to mentally reconstruct the entire operational week before answering a simple status question.

What Visibility Actually Uncovers

The major breakthrough was not the software. It was the decision that company work must have a single home. The software simply made that standard visible.

Once our tasks were laid out in plain daylight, problems that had been hiding in chat threads for six months became impossible to ignore:

• The Chronic Fire-Drill Client: The account that constantly demanded same-day emergency turnarounds had their chaos laid bare in black and white. 
• The Zombie Tasks: Tasks that had been sitting untouched for fourteen days because they had two co-owners—which meant nobody actually owned them. 
• The Runaway Meetings: Recurring internal calls that produced four new speculative ideas and closed zero open items.

Those dysfunctions had been draining our margins the entire time. They just had nowhere to show up before. When tasks live in chat messages, a stalled project looks like a lively conversation. When tasks live in a structured queue, a stalled project looks like an overdue ticket with someone’s face next to it.

The Real Source of Founder Burnout

For a long time, I assumed the fatigue of running a business was tied to workload volume. It wasn’t.

As we explored in why task management systems are the antidote to workplace burnout, the real exhaustion comes from constant background reconstruction.

It’s the quiet, relentless tax of keeping mental tabs on five different deliverables while trying to review a contract, eat dinner with your family, or pitch a prospective account. Your brain is running a background tracking program 24 hours a day, waiting for the shoe to drop.

Once that mental reconstruction stops, the actual work feels dramatically smaller. The company doesn’t need fewer tasks; it needs a brain that doesn’t belong to the founder.

If you lead an organization that still runs on chat threads, good intentions, and founder memory, skip the grand software presentations. You do not need a tour of a new dashboard. You just need to shut down the three places where work currently hides, give the team one shared home for tasks, and enforce the rule until it sticks.

If you’ve lived through this messy operational shift and can tell the story without trying to sell an affiliate link in the opening sentence, our Write for Us page is open.

The original pinned Slack message is still sitting in our general channel. Nobody has clicked on it in over a year. That’s how you know the system is finally working.

How many separate places.. Slack DMs, phone notes, or your own head.. are you currently relying on to track what your business is supposed to deliver this week?