How to Forecast Revenue for Runway Without Fooling Yourself
How to forecast revenue for runway: use three buckets, contracted, probable and hoped, and steer by the first two. Revenue recognised is not revenue received.
To forecast revenue for runway, sort every expected receipt into three buckets, contracted, probable and hoped, and build the runway you steer by on the first two only. Keep the third visible as upside, and count money when it arrives, not when it is earned.
Revenue is the half of the runway calculation that founders are most tempted to flatter. Spending is known: it has already been agreed or paid. Revenue lies in the future, and the future is where optimism lives. This post is about forecasting that half honestly, so the figure does not quietly fund decisions it cannot afford.
How to forecast revenue for runway: three honest buckets
The method rests on one habit, which is refusing to put different kinds of certainty on the same line. Each expected receipt goes into exactly one of three groups.
| Bucket | What qualifies | Does it fund decisions? |
|---|---|---|
| Contracted | Signed, and you have a date | Yes |
| Probable | An existing customer renewing on their normal pattern, or a deal at a stage that historically closes | Yes |
| Hoped | The pipeline | No, it is shown as separate upside |
The runway you steer by is built on contracted and probable only. Hoped revenue sits beside it as a clearly labelled line, so that you can see what it would do if it arrived without letting it justify a hire or a commitment.
Why the base case drifts upward
Almost every dangerous runway figure has optimistic pipeline quietly baked into the base case. The founder usually does not know it is there, because they built it themselves on a good day. It was not a lie. It was a reasonable guess made in a hopeful mood and never revisited.
This is why the bucket labels matter. Without them, every row looks the same, and a deal that has had one friendly conversation sits next to a signed contract in the same column. With them, the question what is this row doing here has to be answered every time.
Contracted does not mean received
Even the safest bucket is a promise about the future, not money in the account. A signed agreement with a date tells you when money is due. It does not tell you when it will land.
That gap is the reason runway is a cash calculation. Revenue recognised is not revenue received. An invoice sent is not cash, and depending on your customers it may arrive after a long wait, or never. If your customers pay slowly, the difference between what your accounts show and what your bank shows is the thing that can end a company, and it does most damage while you are growing, since growth consumes cash before it produces any.
In the forecast, this means the date attached to a contracted line should be the date you expect the cash, not the date you issue the invoice. If you are unsure, use the later date. A forecast that errs towards late is far less dangerous than one that errs towards early.
What makes something probable
The probable bucket is where judgement enters, so it deserves a stricter test. The guide gives two examples. One is an existing customer renewing on their normal pattern. The other is a deal at a stage that historically closes.
Both examples share a feature: they rest on something observed in your own business rather than on a feeling. A renewal is probable because that customer has behaved that way before. A late-stage deal is probable because deals at that stage have closed before. A deal is not probable merely because you like the customer, or because the conversation went well.
- Ask what the evidence is. If the answer is a pattern you have already seen, the row can stay.
- Ask what would have to go right. If it is more than one thing, the row probably belongs in hoped.
- Ask what you would do if it did not arrive. If the answer is a scramble, treat it more cautiously.
Where hoped revenue earns its place
Keeping a hoped line is not pessimism. It tells you how much upside is sitting in the pipeline and what it would do to your timeline if it came in. That is useful information for planning, as long as it stays out of the base case.
A good habit is to look at the two figures together every month. If the runway on contracted and probable alone is comfortable, you have room to take risks. If it is only comfortable once the hoped line is added, you have a plan that depends on things you do not control, and it is better to know that now than later.
Moving rows between buckets
A forecast is not set once. Rows should move as facts change, and the movement should be deliberate and recorded.
| Event | Where the row goes |
|---|---|
| A hoped deal is signed with a date | Moves up to contracted |
| A probable renewal does not follow its normal pattern | Moves down to hoped, or out |
| A contracted payment is received | Leaves the forecast and joins opening cash |
| A contracted payment slips to a later month | Stays contracted, with the new date |
The third row is the satisfying one: money that has arrived stops being forecast and becomes balance. The fourth is the one to watch. A slipped payment is a movement in the runway, and the monthly review should ask about it. The routine for that is in how to review runway monthly.
Keep expected money out of the balance
There is a related discipline for the opening figure. Money that a customer has committed to but not sent does not count as cash until it is sent. Neither does a signed term sheet, an undrawn credit facility or a grant that has been awarded but not paid out. Keep a separate line for near-certain incoming amounts, with expected dates, and never let it merge into the balance.
The forecast and the balance therefore work as a pair. The balance holds what has arrived. The forecast holds what is expected and how confident you are. Mixing them is how a founder ends up surprised by their own runway. The full treatment of counting cash is in how to calculate startup runway.
How revenue changes the burn figure
Because runway is calculated on net burn, every revenue assumption feeds straight into the rate at which the balance is expected to fall. A flattering revenue line makes the net figure look smaller and the runway look longer. This is why revenue assumptions deserve the same scrutiny as spending decisions, and why the difference between gross and net matters. If you want the background, see gross burn versus net burn.
When comfort in the net figure comes from the probable bucket, the fragility behind it is real but invisible, and it stays that way until a renewal fails to arrive.
The question to ask of every row
If you remember one test, make it this: if I had to bet the next hire on this row, would I? A signed agreement with a date might pass. A renewal with a long history of arriving on time might pass. A conversation that went well will not. The answer is not a precise measure, but it sorts rows into buckets more reliably than a feeling does, because it forces you to connect the forecast to a real consequence.
The same test explains why hoped revenue must not fund decisions. A hire is a commitment that outlasts the mood in which it was made. Priced against money that never arrives, it shortens the runway you thought you had. How to cost a role properly is covered in how to price a hire in months of runway.
Why this is easier to do early
Sorting revenue into buckets is far more comfortable when the company is calm. When the figure is under pressure, the temptation is to promote hoped rows to probable, one at a time, until the runway looks acceptable. Each promotion seems defensible in isolation. Together they rebuild the optimistic base case you set out to avoid.
Writing the rule down in advance is the cure. Decide now what evidence a row needs to count as probable, and apply it the same way in a good month and a bad one. If the rule changes only when the news is bad, it is not a rule.
A short checklist for the revenue side
- Every expected receipt sits in exactly one bucket.
- The base case uses contracted and probable only.
- Hoped revenue is visible as a separate upside line.
- Dates reflect when cash is expected, not when invoices go out.
- Each probable row has evidence from your own history.
- Rows are reviewed monthly and moved when facts change.
This takes little time once the structure exists, and it protects the one assumption that most often turns a good-looking runway into a bad surprise.
Frequently asked questions
Should I include pipeline in my runway?
Show it as a separate upside line, but keep it out of the base case. The runway you steer by should rest on contracted and probable revenue only.
What is the difference between revenue recognised and revenue received?
Recognised revenue is what your accounts say you have earned. Received revenue is cash in the bank. Runway depends only on the second.
What counts as probable?
An existing customer renewing on their normal pattern, or a deal at a stage that historically closes. Both rest on something you have observed in your own business.
When should a forecast row move?
Whenever the facts change: when a deal is signed, when a renewal behaves unusually, when a payment arrives or when it slips. Record the move so that you can see it next month.
The full method, with the checklists, is in The Runway Playbook, a free 31-page playbook.