“Burn Rate Tracker Template: Gross vs Net Burn, Runway Math and a Filled Example”

What is burn rate, and why does the definition decide the answer?

Burn rate is the rate at which a company spends cash, usually expressed per month. That definition is simple enough to be useless until you specify which cash, over which period, and whether money coming in has been subtracted.

Three definitions circulate in board decks, and they produce three different runways from the same accounts.

Gross burn is total operating cash outflow: payroll, contractors, rent, software, marketing, travel, professional fees. It answers “what does it cost to run this company for a month” and it is the number you need when modelling a cost base.

Net burn is gross burn minus cash receipts from customers. It answers “how much of the bank account disappeared this month” and it is the number that determines survival.

Net cash burn including financing and capex is what your accountant will eventually reconcile. If you raised money, bought equipment, or repaid a loan in the month, that belongs in the cash flow statement but not in the operating burn you use for runway planning.

Confusing the first two is the most common analytical error in early-stage finance, and it is not harmless. A company with $420,000 gross burn and $185,000 of collections has a net burn of $235,000. Report gross burn to the board as “our burn” and the runway looks 44% shorter than it is; report net burn while describing it as the cost base and you will under-price your hiring plan. Keep both columns, label them clearly, and never let a slide say just “burn”.

Gross burn vs net burn: which one goes in the runway formula?

Runway uses net burn. Gross burn belongs in the cost model and the hiring plan. The table shows why the distinction is structural rather than cosmetic.

One subtlety: collections are not revenue. If you invoice $210,000 in a month and collect $185,000, the $25,000 difference sits in accounts receivable and will arrive later — or not at all. Runway based on recognised revenue flatters; runway based on collected cash survives. Use collections, and treat a growing receivables balance as a warning rather than an asset.

How do you calculate runway, and what does the formula hide?

Runway in months equals cash on hand divided by average monthly net burn:

Runway = Cash ÷ Net burn

With $4,200,000 in the bank and $235,000 net burn, runway is 17.9 months. That is the whole formula. The judgement sits in the three inputs.

Which cash. Use unrestricted cash: bank balances plus money market funds, minus outstanding cheques, minus any cash you cannot legally spend (customer deposits held in trust, restricted grant money, escrow). Committed but undrawn credit lines are not cash; they are a separate line called “runway including facility”, and they usually carry conditions that fail exactly when you need them.

Which burn. Use a three-month trailing average of net burn, not last month. Seasonal collections, a quarterly software bill, or one late invoice can move a single month by 30%, and a runway figure that swings 30% month to month trains people to ignore it.

Which scenario. Report a base case and one stress case. The stress case is not pessimism; it is the version where your two largest customers pay 45 days late.

There is also a definition trap worth naming: runway assumes burn stays flat. It rarely does. If you are hiring, burn rises and true runway is shorter than the formula implies. If revenue is growing faster than costs, true runway is longer. The formula is a snapshot, and the monthly tracker exists to keep refreshing it.

What does a 12-month burn tracker look like when it is filled in?

Below is a worked tracker for a 42-person software company starting the year with $4.2 million in cash. Collections grow about $10,000 a month; two hires land in March and three in July, which is why gross burn steps up in April and July. All figures are monthly, in USD.

Two readings matter here, and they point in opposite directions.

The encouraging one: net burn falls from $250,000 to $211,000 across the year even though gross burn rises by $76,000, because collections grow from $150,000 to $265,000. That is operating leverage, and it is the thing investors actually want to see.

The uncomfortable one: runway falls from 15.8 months to 6.6 months in twelve months, because cash is being spent faster than the burn reduction compensates. Nothing went wrong. Growth simply consumed the buffer, and the year-end position is a fundraising trigger, not a crisis. This is the pattern that catches teams out — they watch burn improve and stop watching cash.

Note also what the tracker reveals about the July step: gross burn jumps $26,000 while net burn rises only $16,000, because three hires started mid-month and one large annual software renewal was paid up front. Splitting one-off payments into a separate column is what stops a renewal from looking like a permanent cost increase.

How sensitive is runway to hiring?

Hiring is the biggest lever available, and the arithmetic is brutally linear. A senior engineer at $165,000 fully loaded costs $13,750 a month. Six of them cost $82,500 a month, or $990,000 a year.

The marginal version is the one to memorise: at $4.2 million and $235,000 burn, every additional $13,750 a month of cost removes roughly one month of runway. That means a single senior hire is priced not at $165,000 but at $165,000 plus a month of company life, and a hiring plan of ten people is a decision to raise a round four months earlier.

The deferral row is the useful compromise. Moving three of six hires out by two quarters recovers 1.9 months of runway while still delivering half the capacity — and it is a decision you can make in an afternoon, unlike a layoff.

Two caveats. First, hiring costs land before productivity does: recruitment fees of 15–20% of salary, equipment at $3,000–$5,000 per person, and two to three months of ramp before the hire removes work from someone else. Add roughly 25% to the first-year cash cost of any hire. Second, the model assumes revenue does not respond. If those six engineers ship a product line that adds $40,000 a month in collections by month nine, net burn is higher early and lower later, and the tracker should show both paths rather than the average of them.

What columns should the tracker contain?

A useful tracker is small enough that someone updates it in fifteen minutes and complete enough that it answers the next question without a rebuild.

Two design rules make the difference between a tracker that survives and one that is abandoned in March. Keep formulas in the sheet rather than pasting values, so a corrected collection figure flows through every downstream number. And put the decision log in the same table as the numbers: six months later, the only question anyone asks about a variance is “why”, and a comment in a separate document will be lost.

What breaks a burn model in practice?

Five things, and all five are common.

Annual prepayments. Paying twelve months of insurance or software in January creates a $60,000 spike that is not a burn increase. Amortise it in the planning view and show the cash movement separately, otherwise you will “discover” a problem that does not exist and miss one that does.

Deferred revenue. Collecting a year of subscription up front inflates cash and flatters runway. The cash is real, but the obligation is too: if you spend it on hiring, you are financing payroll with next year’s service delivery.

Receivables ageing. A $25,000 monthly gap between invoiced and collected is $300,000 a year of runway sitting in someone else’s accounts payable process. Track days sales outstanding next to burn; a ten-day improvement is often worth more than a 5% cost cut.

Capitalised spend. Hardware, capitalised development, and deposits leave the bank but do not appear in an operating burn figure. If you use an accounting-derived burn number, reconcile it to the bank statement every month.

Currency and tax timing. Paying a foreign team in a weakening currency, or a VAT bill that arrives quarterly, moves cash without changing the underlying business. Model these as a separate line so the operating trend stays readable.

None of these are exotic. They are the reason a founder’s spreadsheet and the finance lead’s cash flow statement disagree by 8%, and reconciling them monthly is cheaper than explaining the gap to a board.

What are the trade-offs in cutting burn?

Cutting burn always works arithmetically and sometimes destroys the company. The trade-off is between runway and the capacity that produces revenue.

Cutting marketing reduces burn immediately and reduces pipeline in 60 to 90 days, which is precisely when you need the runway to have been real. Cutting headcount reduces burn by $13,750 a month per senior role and costs one to three months of severance, plus a measurable productivity dip among the people who remain. Renegotiating software and office costs is slow, small, and almost always worth doing first because it carries no capability cost.

The sensible order is: one-off and discretionary spend, then vendor renegotiation, then deferred hiring, then reduced contractor spend, and only then permanent headcount. Most companies invert this order because headcount is the largest line and therefore the most satisfying to cut in a spreadsheet.

There is also a floor. A company with $4.2 million and $235,000 burn that cuts to $150,000 buys seven extra months and loses the ability to ship. If the plan requires shipping to raise the next round, the cut has purchased time it cannot use. The right frame is not “maximise runway” but “reach the next milestone with at least three months of buffer”.

How should the tracker be used each month?

Run it as a monthly ritual with a fixed agenda, on the same day, with the same three questions.

Close the month and reconcile to the bank. If closing cash in the tracker does not match the bank statement, stop and fix it. Every downstream number depends on this one.

Explain variances above 5%. Not every line, only the ones that moved. Writing the explanation in the decision log is the entire value of the exercise.

Test one scenario. Pick the decision actually pending — a hire, a price change, a contract renewal — and run it through the model. The scenario does not need to be sophisticated; it needs to be specific.

Set the trigger. Decide in advance what would cause action: cash below $1.5 million, runway below nine months, or net burn above plan by 10% for two consecutive months. A trigger agreed in a calm month is easier to honour in an uncalm one.

The output of the meeting is one page: current runway, the scenario tested, the decision taken, and the date it will be reviewed. Anything longer will not be read.

How does Doitify fit into burn and runway tracking?

Doitify is our product, so treat this as disclosure. The tracker above can live in a spreadsheet, and often should at the start. Where a work platform earns its place is in the operational layer around the numbers: the hiring plan as a project with dated milestones and owners, the cost-reduction initiatives as tasks with real due dates, the vendor renegotiations as a checklist, and the monthly close as a recurring project with a fixed checklist.

Because projects, tasks, owners, due dates, documents, and reports sit in one workspace, the decision log stops being a comment in a spreadsheet and becomes a record attached to the work it describes. A runway scenario that says “defer three hires to Q3” is only useful if someone can see which three, what they were going to deliver, and when the deferral gets revisited. That traceability is the part spreadsheets are worst at.

Conclusion

Burn rate is not a number, it is a pair of numbers and a definition. Gross burn tells you what the company costs to run; net burn tells you how fast the bank account empties; runway divides cash by the second one. Writing all three on one line, every month, prevents most of the confusion that surrounds them.

Then use the tracker for decisions rather than reporting. Model every hire before you approve it, keep the decision log beside the numbers, and agree the triggers while you still have options. A company that knows its runway to the month, and knows what each hire costs in months of life, negotiates its next round from a different position than one that finds out in a board meeting.

If this post on burn rate was helpful, you might also enjoy How to Automate Repetitive Project Tasks (Step-by-Step) and Resource Scheduling: Complete Guide.