Skip to main content

    Driver-Based Forecasting

    Instead of 'revenue grows 8%,' you build revenue from its real components — price × volume, customers × ARPU, stores × sales per store. It's more work but far more defensible and lets you stress-test the actual business levers.

    Definition

    Driver-based forecasting is a modeling approach that projects a company's revenue and costs by building them up from underlying operational drivers — such as units sold × average selling price, customers × average revenue per user, or square footage × sales per square foot — rather than applying a single blanket growth rate to last year's number, producing a more defensible and diagnosable three-statement model or DCF.

    Driver-based vs growth-rate forecasting

    The lazy approach grows each line by a flat percentage — revenue +8%, COGS +6% — which is fast but a black box: you can't say why growth is 8% or test what happens if pricing slips. Driver-based forecasting decomposes the number into operational levers you can defend and flex. For a SaaS business: revenue = beginning customers × (1 − churn) + new customers, all × ARPU. For a retailer: revenue = number of stores × average sales per store, with a separate same-store-sales growth and new-store build. For a manufacturer: units × price. Each driver can be sourced from management guidance, industry data, or historical trends, making the forecast auditable and connecting it to real-world events (a price increase, a new store opening, a churn improvement).

    Why bankers and investors prefer it

    Driver-based models let you do meaningful sensitivity and scenario analysis — you can ask 'what's the IRR if churn rises 200bps?' which a flat-growth model simply can't answer. They also surface internal contradictions: if you assume 40% volume growth, the model shows whether capacity (capex) and working capital can support it. In diligence, driver-based forecasts let the deal team challenge each assumption independently rather than debating a single opaque growth figure. The downside is they take longer to build and require more data, so analysts reserve full driver builds for the key revenue lines and use simpler ratios for immaterial ones.

    Common drivers by line item

    Revenue: price × volume, customers × ARPU, installed base × utilization, backlog conversion. COGS and gross margin: cost per unit, input commodity prices, or a margin percentage that itself trends with scale. Operating expenses: often a percent of revenue, or headcount × fully-loaded cost per employee for people-heavy businesses. Capex: percent of revenue, or capacity additions × cost per unit of capacity. Working capital: days sales outstanding, days inventory, days payable outstanding applied to revenue or COGS. The art is choosing the right granularity — enough to be defensible without drowning in detail.

    Worked Example — With Real Numbers

    A SaaS company: start with 10,000 customers, ARPU of $1,200/year, and revenue of $12.0M. Forecast Year 1 with annual churn of 10% and 3,000 new customers: ending customers = 10,000 × (1 − 0.10) + 3,000 = 12,000. With ARPU rising 5% to $1,260, Year 1 revenue = 12,000 × $1,260 = $15.1M (a 26% increase). A flat-growth model would have just said '+26%' with no way to test it. Now you can flex churn to 15% (ending customers = 11,500, revenue = $14.5M) and instantly see the revenue impact of retention — the whole point of driver-based work.

    Key Takeaways

    1

    Driver-based forecasting builds revenue and costs from operational levers, not a single growth rate.

    2

    Common drivers: price × volume, customers × ARPU, stores × sales per store, units × cost per unit.

    3

    It makes forecasts defensible and auditable — every number traces to a testable assumption.

    4

    It enables real sensitivity and scenario analysis on the actual business levers (churn, pricing, volume).

    5

    Reserve full driver builds for material revenue lines; use simpler ratios for immaterial items.

    Common Mistakes in Interviews

    Defaulting to a flat growth rate when the interview clearly wants driver decomposition.

    Choosing drivers that don't fit the business (price × volume for a subscription company).

    Over-engineering immaterial lines while leaving the key revenue driver as a single growth assumption.

    Forecasting drivers that ignore constraints — 40% volume growth with no added capex or working capital.

    How Interviewers Test This

    Interviewers ask 'how would you forecast revenue for [company type]?' Don't say 'grow it 5%.' Identify the drivers: for SaaS, customers × ARPU with a churn assumption; for retail, stores × sales per store with same-store-sales growth; for a manufacturer, units × price. Naming the right drivers for the specific business model shows you think about the operations behind the numbers, not just spreadsheet mechanics.

    Related Concepts

    Directly referenced in this topic

    More Financial Modeling

    12 more concepts in this category

    Topic Guides

    Firms That Test This

    Practice Driver-Based Forecasting questions

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

    Start Practicing

    Master Driver-Based Forecasting 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