Revenue Build Model: Project Sales from Real Drivers

Key Takeaways

• A revenue build model decomposes top-line revenue into two or more auditable drivers whose product equals sales, replacing an opaque single growth rate.
• In a SaaS build, net revenue retention of 120 percent means the retained customer base alone grew ARR by 35 percent above the prior churn-adjusted base.
• Typing "=prior revenue × 1.10" is the most common mistake; it cannot be stress-tested by driver and hides whether growth comes from price, volume, or new customers.
• Because revenue drives margins, working capital, and valuation, small build errors compound through every downstream output in the three-statement model.

What It Is

A revenue build decomposes the top line into two or more drivers whose product equals sales. The simplest form is quantity times price. More sophisticated builds layer in cohorts, churn, mix shift, or capacity constraints. The point is to make growth auditable. An analyst can ask "why is revenue up 18 percent next year?" and the model should point to a specific assumption (e.g. 12 percent more customers at 6 percent higher prices) rather than a single opaque growth rate.

The build sits at the top of the income statement forecast and drives everything downstream. Revenue is the largest single number in most models, so small errors here compound through margin, working capital, and valuation.

The Intuition

High-level growth rates hide the mechanics of a business. A retailer growing revenue 10 percent could be opening new stores while same-store sales decline, or holding store count flat and raising prices, or doing both. Those three paths have very different risk profiles and very different implications for cost structure. A driver-based build exposes which one is actually happening.

It also lets you stress-test what matters. If revenue is 70 percent driven by price and 30 percent by volume, a recession that hits units harder than prices hurts differently than one that compresses pricing. Without a build, that sensitivity is invisible.

How It Works

Pick a revenue structure that matches how the company actually earns money. Three common patterns cover most cases.

Volume times price. For manufacturers, retailers, and commodity producers. Multiply units sold (or stores, rooms, flights) by average price per unit. Project each driver separately.

Revenue = Units x Average selling price

Cohort times ARPU. For subscription businesses. Start with the existing customer base, apply a retention rate, add new customers from each sales channel, and multiply by average revenue per user (ARPU) or account (ARPA).

Ending customers = Starting customers x (1 - churn) + New customers
Revenue = Average customers x ARPU

Capacity times utilization times rate. For service and asset-heavy businesses. Airlines multiply available seat miles by load factor by yield. Hotels multiply available room-nights by occupancy by average daily rate.

Revenue = Capacity x Utilization x Price per unit

Within a SaaS build, analysts often split ARR into three buckets: new ARR from fresh logos, expansion ARR from existing accounts growing, and churn ARR lost to cancellations. The sum plus the prior period's balance is the current ARR. Revenue is then recognized from ARR on the appropriate schedule.

Worked Example

A hypothetical B2B SaaS company ends year 0 with 1,000 customers paying 12,000 per year (12 million ARR). Management guides to 85 percent gross retention, 120 percent net revenue retention (which means expansion from the retained base adds 35 percentage points), and 300 new customer logos added at year-end at the same 12,000 ARPU.

Year 1 build:

Starting ARR                    12,000,000
Churn (15 percent of start)     (1,800,000)
Expansion (35 percent of start)  4,200,000
Retained ARR                    14,400,000
New logos (300 x 12,000)         3,600,000
Ending ARR                      18,000,000

Average ARR for revenue recognition is roughly 15 million, implying year 1 recognized revenue near that figure depending on timing. An analyst reviewing this build can immediately pressure test the three drivers. If expansion drops from 35 to 20 percent, ending ARR falls to 16.2 million, a visible and specific impact instead of a mystery.

Common Mistakes

1. Single growth rate masquerading as a build. Typing "=prior revenue * 1.10" in a cell is not a revenue build. Reviewers cannot audit it, scenarios cannot stress specific drivers, and the number tells you nothing about why growth is happening. Always break revenue into at least two drivers.

2. Double counting new customers in ARR and in revenue. New logos added mid-year contribute a partial year of revenue, not a full year. A build that treats each new customer as contributing 12 months of ARR when they only signed in month 9 overstates the top line.

3. Ignoring pricing mix. If a company sells three tiers at different prices, volume-weighted average price is not the same as simple average price. Failing to track mix hides the impact of customers downgrading to cheaper plans even when total customer count grows.

4. Forgetting capacity constraints. Hotels cannot have occupancy above 100 percent, airlines cannot fly more seats than their fleet allows, factories run up against line speed. A build that implicitly assumes infinite capacity will eventually produce a forecast that is physically impossible.

5. Letting retention assumptions drift higher without evidence. Analysts often extrapolate strong recent cohorts forward forever. Real cohorts decay, and the retention curve flattens only after several years. Holding 95 percent gross retention for a decade in a startup model is usually fiction.

Frequently Asked Questions

Q: What is a revenue build model in simple terms? A revenue build model projects future sales by multiplying underlying business drivers, such as units times price or customers times average revenue, rather than applying a single percentage growth rate to last year's total.

Q: How does a revenue build model affect investment decisions? It lets an investor or analyst quickly identify what is actually driving growth and stress-test the specific driver that matters most. A retailer growing revenue 10 percent through new stores carries very different risk than one growing through same-store price increases.

Q: What is a real-world example of a revenue build model? A SaaS company with 1,000 customers, 85 percent gross retention, 120 percent net revenue retention, and 300 new logos per year produces a year-end ARR of 18 million, each input can be changed separately to see which one moves revenue the most.

Q: How can investors use or avoid revenue build errors? Investors should ask whether the model breaks revenue into at least two independent drivers. If the analyst cannot name the specific driver behind a growth assumption, the forecast is an opaque number, not an analysis.

Q: How is a revenue build model different from a simple growth rate forecast? A growth rate forecast produces a number with no auditable source. A revenue build shows exactly which combination of volume, price, and customer additions generates that number, making it possible to challenge, update, or scenario-test any single component.

Sources

1. Wall Street Prep. "Recurring Revenue | Formula + Calculator." https://www.wallstreetprep.com/knowledge/recurring-revenue/
2. Wall Street Prep. "Average Revenue Per Account (ARPA) | Formula + Calculator." https://www.wallstreetprep.com/knowledge/average-revenue-per-account-arpa/
3. Corporate Finance Institute. "Financial Forecasting Guide." https://corporatefinanceinstitute.com/resources/financial-modeling/financial-forecasting-guide/
4. Stripe. "SaaS Revenue Forecasting: Models, Metrics, and Best Practices." https://stripe.com/resources/more/saas-revenue-forecasting

Disclaimer

This article is educational content only and is not financial advice. Nothing here is a recommendation to buy, sell, or hold any security. Consult a licensed advisor before making investment decisions.