How to Build a Revenue Build in Excel

A revenue build is the structured forecast of a company's top line, broken into the drivers that actually move it. The two broad approaches are top-down, sizing a market and taking a share, and bottom-up, building revenue from price times volume or from customer cohorts. A good revenue build ties every number back to a visible assumption so a reviewer can change one driver and see the forecast respond.

What a revenue build is and which approach to use

A revenue build replaces a single growth rate on the top line with the underlying drivers of revenue. Instead of assuming revenue grows ten percent, you model what produces that growth: units sold, average price, customers acquired, or contracts renewed. This makes the forecast defensible and lets you test specific assumptions.

There are two broad styles. Top-down starts with a total addressable market and applies a market share, useful early or for new markets where unit data is thin. Bottom-up builds revenue from the company's own operations, price times volume or cohort by cohort, and is more credible when you have operating history. Many models blend the two and reconcile them.

Build a price times volume forecast step by step

Price times volume is the most common bottom-up driver. This example forecasts one product line where units and price each grow off explicit assumptions.

1. Set beginning units and a unit growth assumption: =prior_units * (1 + unit_growth).
2. Set average price and a price growth assumption: =prior_price * (1 + price_growth).
3. Compute revenue per line: =units * price.
4. Repeat per product or segment and sum to total revenue.
5. Link unit and price growth to a visible assumptions block, not inside the formula.
6. Add a cross check against a top-down market share estimate to flag unrealistic figures.

Revenue of 56,650 is the product of a unit driver and a price driver, each sourced from a visible assumption.

Driver and cohort approaches

Beyond simple price times volume, two driver patterns are common. A capacity or productivity driver multiplies a resource by a yield, for example stores times sales per store, or sales reps times quota. A cohort approach is standard for subscription businesses: you track each acquisition cohort, apply a retention curve, and sum surviving customers times average revenue per user.

Whatever the pattern, the discipline is the same: revenue equals a quantity driver multiplied by a value driver, and both come from named assumptions.

• Price times volume: =units * average_price.
• Capacity driver: =stores * sales_per_store or =reps * revenue_per_rep.
• Cohort revenue: =surviving_customers * average_revenue_per_user.
• Surviving customers: =cohort_size * retention_rate ^ months_since_join.
• Total revenue: =SUM of all product lines, segments, or cohorts.

Pitfalls and what reviewers check

The leading pitfall is hardcoding revenue or growth directly into the top line so no one can see what drives it. Every revenue cell should resolve to a quantity times a price, with both pulled from a labeled assumptions area. If a reviewer cannot find the driver, the forecast is a guess dressed as a model.

Reviewers sanity check the build against reality: implied market share that exceeds the whole market, unit growth that outruns capacity, or prices rising faster than any comparable. A bottom-up build that implies an impossible top-down share is a signal to revisit assumptions.

Finally, reviewers confirm the build sums correctly to total revenue and that the same revenue figure flows into the income statement. Keep segments, units, and prices clearly separated from the consolidated total so the links stay auditable.