Your Cash Runway Is a Valuation Lever, Not a Deadline

A SaaS business at scale can believe it has eighteen months of runway and have twelve. It happens often enough to be a pattern rather than an accident, and the six months almost always go to the same four places.

Nothing has to have gone wrong for this to be true. The bank balance is what the board thinks it is, the forecast has been prepared carefully, and nobody has been careless. The eighteen-month figure is simply the answer to an easier question than the one that matters.

Six months is not a rounding difference. It is the difference between raising on your own timetable and raising on somebody else's.

How cash runway is actually calculated

Cash runway is the closing cash balance divided by net monthly burn. The arithmetic is trivial. Almost every error is in the inputs, and there are four that recur.

Gross burn is not net burn. Gross burn is total monthly outgoings. Net burn is outgoings less cash receipts. Companies quote runway on whichever produces the more comfortable number, often without noticing they have chosen.

An average burn rate hides the shape of the year. A business with a flat £400,000 average may be spending £320,000 in three months and £520,000 in three others. Runway is exhausted by the worst months, not the mean ones.

Cash receipts are not revenue. This is the one that produces the biggest gap in subscription businesses. Annual contracts are recognised monthly, correctly, while the cash arrives in clusters around renewal seasons. A forecast that spreads receipts evenly describes a business that does not exist, and the trough between the clusters is where the runway actually runs out.

Commitments outside the profit and loss are still cash. Corporation tax, VAT quarters, deferred consideration, capitalised development, lease payments and the working-capital drag of growth all consume cash without appearing where a founder tends to look for them.

Correct those four and eighteen months routinely becomes twelve. No new information is required. The information is already in the business; it is in the wrong shape to be seen.

Why a single forecast is not a model

A budget answers one question: what happens if the plan holds. That is the least useful of the questions a board needs answered, because the plan holding is the case requiring no decisions.

A rolling model answers a different question. It runs monthly out to eighteen or thirty-six months, is rebuilt against actuals as they land, and is structured so that any assumption can be moved and the consequences read off directly. The value is not the number it produces. It is the speed with which it answers the next question.

Four questions are worth building it around.

1. What is the current burn actually doing?

Not the average, but the profile: which months are heaviest, what drives them, and where the trough sits. This is usually where the missing months surface.

2. Which levers extend runway, and at what cost?

Every extension buys months and gives something up. Price each lever separately, so the trade can be seen rather than argued about.

3. What happens if revenue falls twenty per cent?

Not as a disaster scenario, but as a planning one. A twenty per cent shortfall against plan is an ordinary outcome in a difficult year, and a business that has already decided what it would do has a considerable advantage over one deciding under pressure.

4. When is the right time to raise?

The most valuable question of the four, and the one a static budget cannot address at all, because the answer depends on the three above.

The three levers that move the number

Runway extension is rarely one decision. It is usually three, and the order matters.

Retention. The cheapest cash in any subscription business is the cash you already have. Improving retention lifts collections without lengthening the sales cycle or adding acquisition spend, and it improves the forecast the eventual raise will be judged on. It is slow, which is why it has to be started first.

Prioritised spend, not cost-cutting. The distinction is not semantic. Uniform cuts damage the things that were working alongside the things that were not. The model's job is to separate spend that protects revenue from spend that merely assumes it, so that only the second category is reduced. Cutting the first buys months and costs you the raise.

Vendor payment terms. The most immediate of the three and the most often overlooked. Renegotiated terms move cash out of the trough without reducing what is spent in total. They change timing rather than quantum, which is precisely what a runway problem usually is.

Applied together and started early enough, twelve months can become twenty-four. Not by spending less in aggregate, but by spending it in a different order and collecting it sooner. Identifying which levers are available, and what each is worth, is what a cash runway model is for.

Why this is a valuation exercise, not a treasury one

Here is the part that matters, and the reason runway modelling belongs alongside valuation work rather than bookkeeping.

Doubling runway lets a raise be delayed by a year, and that delay does three things at once.

It takes the company to market at a materially higher ARR, so the same multiple is applied to a larger number.

It removes the discount that attaches to necessity. An investor can tell the difference between a company raising because the timing is right and one raising because the alternative is running out of cash, and the second is priced accordingly. Nothing in a data room signals weakness more clearly than a short runway, and no amount of narrative offsets it.

It changes who sets the terms. A company with two years of cash can decline a term sheet. A company with four months cannot, and both sides know it.

The result is a higher pre-money valuation on the same business, achieved without a single additional customer at the moment of the decision. The model does not make a company more valuable. The months it buys do, and so does being able to evidence them.

That is the argument for the whole exercise. A cash runway model is not a forecast. It is a value optimisation strategy that happens to be denominated in months.

The model is the easy part

The prize described above is large, and most companies do not collect it. The reason is not that the modelling is difficult.

A model can answer all four questions in a fortnight. None of the three levers moves in a fortnight. Retention improves over quarters, not weeks, and only if somebody owns the churn analysis and acts on it. Vendor terms are renegotiated one supplier at a time by a person willing to have the conversation. Spend is re-sequenced by someone senior enough to tell a department its budget has changed and explain why.

Trigger points fail in the same way. A threshold with a decision attached is worthless unless somebody is watching the threshold and has authority to act when it is crossed. Most are agreed at a board meeting and never looked at again.

So a model nobody acts on buys no months at all. It produces a more accurate description of the same problem, which is worth something, but it is not worth what the exercise is capable of being worth.

That is the honest division between the two pieces of work. The runway model tells you what your position is, which levers exist, and what each is worth. Fractional CFO and advisory work is somebody in the business pulling them, month after month, and holding the trigger points when it becomes inconvenient. The first is a fixed-price diagnostic. The second is why the diagnosis turns into months.

How the question changes by sector

The arithmetic is universal. What sits in the inputs is not.

SaaS. Deferred revenue and annual prepayments make recognised revenue and collected cash diverge sharply, which is the trap described above. Retention is the strongest lever available, and the slowest to act.

Marketplaces. Payment float can flatter the cash position considerably. Money held on behalf of sellers sits in the bank and is not the company's to spend, and a runway calculated on the gross balance is wrong by however much of it belongs to somebody else.

FinTech. Regulatory capital cannot be spent to extend runway at all. It is on the balance sheet and unavailable, so headline cash overstates the position by the full amount of the requirement.

eCommerce. Inventory is cash in a different form, and growth consumes working capital before it produces margin. A profitable brand can run out of money while trading well, which is a distinctively uncomfortable way to fail.

The two horizons, and the trigger points between them

A runway model is really two models, and confusing them is a common failure.

The short horizon is a rolling thirteen-week cash flow, built on receipts and payments rather than revenue and costs, and reforecast weekly. Its job is operational: it finds the trough far enough ahead that something can still be done about it. Thirteen weeks is not arbitrary. It is roughly the notice period on most of the decisions that would help.

The long horizon is a monthly model running eighteen to thirty-six months. Its job is strategic. It informs when to raise, how much, and what the business will look like on the day it does.

Between them sit trigger points, and they are the most underused part of the exercise. A trigger point is a threshold agreed in advance with a decision already attached: if cash falls below a stated level by a stated month, the hiring plan pauses, or the marketing commitment is not renewed, or the raise begins.

The purpose is not the alert. It is that the decision was taken in calm conditions by people thinking clearly, rather than in the week it becomes urgent. Boards are considerably better at deciding what they would do than at deciding what they must do.

When to build one

The honest trigger is not a number of months. It is any of these:

• A raise is expected in the next eighteen months
• The board has asked a question the current forecast cannot answer
• Growth has slowed against plan, or costs have risen against it
• A material commitment is being considered: a hiring plan, an office, an acquisition
• Nobody can say, without a week's work, what happens if revenue falls a fifth

The last is the most common and the most telling. If the answer takes a week to produce, it will not be produced in time to be useful.

Final thought

Runway is not a fact about a bank account. It is a function of decisions that have not been made yet, which is why it can be changed and why the number on its own is close to meaningless.

A company does not have twelve months. It has twelve months on its existing decisions, and potentially twice that on better ones. A model does not tell you how much time you have. It tells you how much time you can choose to have, and what each additional month will cost.

That is a different exercise from forecasting, and it is worth considerably more.