Skip to main content

    Revenue Model & Build

    A revenue model breaks revenue into its building blocks — units × price, customers × ARPU, or market size × share — instead of just guessing a growth rate. It's the foundation of any good financial model.

    Definition

    A revenue model (or revenue build) is the section of a financial model that projects future revenue by breaking it down into its component drivers rather than simply growing the top line at a flat rate. The two primary approaches are top-down (starting with market size and market share) and bottom-up (building from units, pricing, customers, or contracts). A well-constructed revenue model captures the key levers management can pull, enables meaningful sensitivity analysis, and provides the foundation for the entire three-statement model.

    Top-Down vs Bottom-Up

    Two approaches to estimating revenue

    Top-Down

    Market-based

    TAM

    Total Addressable Market

    $50B

    SAM

    Serviceable Available

    $12B

    SOM

    Serviceable Obtainable

    $1.8B

    Revenue

    Capture rate applied

    $600M

    Bottom-Up

    Unit-based

    Units

    Products sold

    50K

    Price

    Avg selling price

    $12K

    Revenue

    Units × Price

    $600M

    Growth

    YoY expansion

    +15%

    KPI

    Revenue Drivers

    Key metrics that move the top line by industry

    ☁️

    SaaS

    ARR / MRR
    Net Retention
    New Logos
    ARPU
    🏪

    Retail

    Same-Store Sales
    New Stores
    Avg Ticket
    Traffic
    🏦

    Banking

    NIM
    Loan Growth
    Fee Income
    AUM
    Σ

    Revenue by Segment

    Stacked build showing growth across product lines

    $450M

    2022

    $550M

    2023

    $660M

    2024E

    Product A
    Product B
    Services

    Top-Down vs. Bottom-Up Approaches

    The top-down approach starts with total addressable market (TAM) and estimates the company's market share penetration over time. It's useful for early-stage companies or when detailed operational data isn't available. The bottom-up approach builds revenue from granular operational drivers: units sold × average selling price, number of subscribers × average revenue per user (ARPU), or number of stores × revenue per store. Bottom-up is more defensible and preferred in investment banking because it connects revenue directly to operational assumptions that can be verified and stress-tested. Most sophisticated models use a combination: a bottom-up build for the near term and a top-down sanity check for the outer years.

    Segmentation and Key Drivers

    Breaking revenue into segments — by product line, geography, customer type, or channel — dramatically improves model accuracy and analytical utility. A retail company might be modeled as: same-store sales growth + new store openings × average store revenue. A SaaS company might use: beginning ARR + new ARR + expansion ARR − churned ARR. Each segment should have clearly identified drivers with distinct growth rates and margin profiles. The revenue build connects directly to operating margin and gross margin assumptions because different segments often carry different profitability, which affects the entire P&L forecast.

    Building the Revenue Model in Practice

    Start by analyzing 3-5 years of historical revenue data to identify trends, seasonality, and growth drivers. Break historical revenue into the same segments you'll project forward. For each segment, identify 2-3 key drivers and build your projections from those drivers. Cross-check your bottom-up build against management guidance, consensus estimates, and industry growth rates. Build in sensitivity analysis on the most impactful drivers — typically volume/units and pricing — to show the range of outcomes. The revenue model feeds directly into COGS (to calculate gross margin), operating expenses, and ultimately free cash flow.

    Revenue Models in Different Industries

    The right revenue model structure varies significantly by industry. For subscription/SaaS businesses: cohort-based models tracking new customers, retention rates, and ARPU expansion. For retail: same-store sales + new store rollout schedule. For manufacturing: volume × price with separate assumptions for each product category. For financial services: assets under management × fee rate, or loan book × net interest margin. For healthcare: patient volume × reimbursement rates by procedure. Knowing which revenue model structure to use for a given industry demonstrates the kind of sector awareness that impresses interviewers and is essential for producing credible projections in live deal models.

    Worked Example — With Real Numbers

    A SaaS company with $100M ARR: Beginning ARR $100M. New customer ARR: 500 new customers × $20K average contract value = $10M. Expansion ARR: 15% of beginning ARR = $15M (upsells and price increases). Churned ARR: 8% annual churn × $100M = ($8M). Ending ARR = $100M + $10M + $15M − $8M = $117M. Implied growth rate: 17%. Revenue (recognized ratably): midpoint of beginning and ending ARR ≈ $108.5M. Sensitivity: if churn rises to 12%, ending ARR drops to $113M (13% growth). If new customer acquisition increases to 600 customers, ending ARR rises to $119M (19% growth). This bottoms-up build is far more useful than simply assuming '17% growth.'

    Key Takeaways

    1

    Bottom-up revenue builds (units × price, customers × ARPU) are more defensible than simple growth rate assumptions

    2

    Segment revenue by product, geography, or customer type — each segment has different growth rates and margins

    3

    Top-down (TAM × market share) provides a useful sanity check, especially for outer-year projections

    4

    The revenue model is the foundation of the entire financial model — errors here cascade through every line item

    5

    Always build sensitivity analysis on the 2-3 most impactful revenue drivers

    Common Mistakes in Interviews

    Using a flat growth rate without any driver-based logic — this provides no analytical insight and can't be stress-tested

    Projecting revenue growth that implies impossible market share gains when checked against TAM

    Not reconciling the bottom-up build to management guidance or consensus — large deviations need justification

    Forgetting that revenue recognition timing can differ from bookings — especially critical for SaaS and long-term contract businesses

    How Interviewers Test This

    If asked 'how would you project revenue for Company X?', first identify the industry, then describe the appropriate build: 'For a SaaS company, I'd model beginning ARR plus new customer ARR, expansion, and minus churn. For a retailer, I'd use same-store sales growth plus new store openings.' This shows you understand that revenue modeling isn't one-size-fits-all and that you think about the business drivers, not just the math.

    Related Concepts

    Directly referenced in this topic

    More Financial Modeling

    12 more concepts in this category

    Topic Guides

    Firms That Test This

    Practice Revenue Model & Build questions

    400+ interview questions with AI feedback. Free to start.

    Start Practicing

    Master Revenue Model & Build and 100+ More Concepts

    Get the full IB Flash experience and walk into your interview with confidence.

    AI Interview Coach

    Real-time feedback on your answers

    1,000+ Practice Questions

    Across IB, PE, HF, VC & more

    Financial Modeling Tests

    Excel-based skill assessments

    Start Free Trial

    Or explore our free tools to get started