How to Build a Three-Year Revenue Forecast

A three-year model is a different instrument than a quarterly forecast. Nobody expects the year three number to be accurate. What people expect is that the path to it is arithmetically possible and that the assumptions holding it up are visible. Most long-range models fail that second test, because the growth rate was chosen first and the drivers were reverse-engineered to reach it.

What is a three-year revenue forecast for?

Testing whether a growth target is reachable with the drivers you can actually move.

It supports decisions with long lead times. Hiring plans, market entry, and capital raises all require a view that extends past the current quarter. It also serves as the reference point for board conversations about trajectory.

What it is not is a commitment. Years two and three carry uncertainty that grows with distance, and treating them as promises produces the worst possible behavior, which is defending a number instead of updating a model. Build it to be revised.

What structure should the model use?

An ARR waterfall, monthly for year one and coarser after that. Those figures illustrate the structure rather than serving as a benchmark. In a working model, split the expansion and churn lines further into new product ARR, product increases, churned product ARR, and product decreases, so a mix shift between customer-level and product-level movement is visible.

Beginning ARR for each period equals ending ARR from the period before. That constraint is what makes the waterfall useful, because it forces every assumption to reconcile rather than sitting in an isolated cell. Reconciling this waterfall by month in year one is the highest-value part of the build.

How do you set assumptions you can defend?

Start from a rate you measure today and state every change as a named mechanism.

A model that assumes win rate improves from 22 percent to 26 percent over three years is making a claim about something specific happening. Enablement, a product gap closing, a segment shift. Write the mechanism next to the assumption. If no mechanism exists, hold the rate flat.

The same applies to the retention lines. Improving net revenue retention by ten points requires either a new expansion motion or a product change. Assuming it happens because the model needs it produces a plan that misses in year two and takes the credibility of the whole exercise with it. Definitions for the retention inputs are in the net revenue retention glossary entry.

Hold assumptions on one tab with a source and a review date for each. When the board asks what would have to be true for the year three number, the answer should be a short list of labeled cells rather than an exploration of formulas.

How do you connect year one to the operating plan?

Year one of the long-range model and the annual operating plan must be the same number, built at different resolutions.

This is where most three-year models diverge from reality. The long-range file is built by finance, the operating plan is built by revenue operations, and the two never reconcile. When they disagree, the sales team works to one and the board hears the other.

Force the connection through capacity and coverage. Year one new customer ARR implies a certain number of closed deals at your average deal size, which implies pipeline at your win rate, which implies pipeline creation volume and a ramped headcount that can carry it. Any of those four checks failing means the year one number is wrong regardless of how attractive the growth rate looks.

Coverage is the check people most often skip. Standard coverage sits between 3x and 5x. Across ORM's customer base most accounts sit near 3.5x, and some run as low as 1.4x. If your plan requires 8x coverage in a segment that has never exceeded 4x, the plan has a pipeline generation problem that the model is currently hiding. The argument for treating coverage as an input rather than a conclusion is in why the 3x pipeline coverage rule is wrong.

How do you handle uncertainty across three years?

Model a small number of named scenarios rather than a probability band.

Build a base case from current rates held flat, an upside case where one or two named mechanisms deliver, and a downside case where a specific risk lands. Each scenario should differ by which assumptions changed, not by a percentage applied to the total.

Name the downside risk explicitly. Pricing pressure from a new competitor reducing average deal size. Buyer hesitation stretching the time from qualified to closed. A capital market shift where rising rates slow deployment, valuations compress, companies cut costs, and win rates fall as a result. Those are the mechanisms that actually move a long-range plan, and modeling them by name is more useful than applying a haircut.

What kills a three-year model?

Assumptions that were true when the file was built and never revisited.

The most common reason a forecast misses is that something in the business or the market changed while the model kept running on old assumptions. Over three years, the probability of that happening approaches certainty. A model that cannot respond to changing conditions will be wrong, and the longer the horizon the more expensive the error.

Refresh year one quarterly against actuals and rebuild the full model annually. Rebuild immediately after a structural change. Track the variance between what the model predicted for the trailing period and what happened, using the standards in the forecast accuracy glossary entry, because a long-range model that has never been graded against a completed year is an assertion rather than a forecast.