Growth drivers are the business-level forces that cause financial outcomes. When FP&A analysts skip identifying them upfront, the model becomes a spreadsheet exercise rather than a decision tool.
Most teams build assumptions first and only afterward look for drivers to justify them — a sequencing problem that produces fragile models and weak forecasts.
According to the 2024 FP&A Trends Survey, only 37% of FP&A teams have adopted driver-based models in their planning, despite a direct link between driver-based modelling and improved forecast quality. The gap is not a technology problem. It is a sequencing problem.
This article lays out a practical framework: how to identify growth drivers, translate them into assumptions, stress-test those assumptions, and communicate them in a way that holds up under scrutiny.
Growth Drivers Come Before Assumptions
Most FP&A teams set a revenue growth assumption and then work backwards to justify it. That sequence produces fragile models.
Growth drivers are the specific business-level forces that cause financial outcomes: customer acquisition rates, pricing power, capacity utilization, market expansion, product launches, and retention. Assumptions are the numerical expressions of those drivers.
The correct sequence is:
- Identify the relevant growth drivers for the business
- Quantify each driver based on available data
- Translate driver estimates into model assumptions
- Build the forecast from those assumptions
Growth drivers split into two categories:
- Internal drivers: sales headcount, conversion rates, product pipeline, distribution channels, customer lifetime value
- External drivers: macroeconomic conditions, interest rates, regulatory changes, FX movements, competitive dynamics
Anchoring every assumption to at least one identifiable driver is what separates a defensible model from a formatted guess.
Mapping Growth Drivers to Financial Statement Lines
This is where many financial models begin to lose internal consistency. Growth drivers do not affect only the revenue line.
Every significant driver has consequences across all three financial statements, and those consequences must be consistent.
| Growth Driver | Income Statement Impact | Balance Sheet Impact | Cash Flow Impact |
| New customer acquisition | Revenue growth | Higher receivables (DSO) | Working capital drag |
| Volume expansion | COGS increase (variable) | Inventory build | Capex if capacity constrained |
| Price increase / value-based pricing | Margin expansion | Minimal | Positive operating cash flow |
| Geographic expansion | SG&A increase | Fixed asset additions | Capex outflow |
| Retention / churn reduction | Stable recurring revenue | Lower receivables volatility | Predictable operating cash |
A common modeling error: projecting 20% revenue growth driven by volume while leaving inventory days, headcount costs, and capex flat.
As Wall Street Prep notes, Periods of higher revenue growth directly correspond to increased capital expenditure, and the same logic cascades through working capital and headcount.
The growth driver implies that related assumptions elsewhere in the model must also change. If it does not, the assumptions are inconsistent.
Turning Drivers Into Defensible Assumptions
Defensible assumptions typically draw from three sources used in combination:
- Historical performance: establishes the baseline trend and normal range. Strip out one-time events before calculating averages.
- Internal guidance: management plans, signed contracts, pipeline data, capacity decisions. This is where strategic signals like new store openings or product launches get quantified.
- External benchmarks: industry databases (IBISWorld, Capital IQ), competitor filings, analyst reports. Use these to sanity-check margins and growth rates against sector norms.
Each source catches what the others miss. Historical data misses strategic pivots. Management guidance can be optimistic. External benchmarks may overlook company-specific advantages or operational constraints.
The override decision is the hardest part. When historical trends and management guidance conflict, the FP&A analyst needs a clear test.
Ask: Is there a structural reason why the future should differ from the past? A new distribution channel, a pricing model change, or a regulatory shift can justify a break from trend. An optimistic sales forecast without a supporting operational mechanism cannot.
One practical rule: document the why behind every assumption, not just the number.
Each assumption input should include documentation explaining the underlying driver logic. “7% revenue growth” is incomplete. “7% revenue growth based on 3-year average of 6.5-7.5%, adjusted upward for confirmed enterprise contract pipeline” is defensible.
Stress-Testing Driver-Based Assumptions
Sensitivity analysis is most effective when applied directly to the underlying business drivers rather than the financial outputs themselves.
Identify the two or three growth drivers with the highest model sensitivity.
These are typically:
- Revenue growth rate
- Gross margin (COGS as % of revenue)
- A key working capital ratio (DSO or inventory days)
Build a sensitivity table around those drivers, not around net income or EBITDA directly.
Example: Revenue Growth Driver Sensitivity
| Revenue Growth Assumption | Gross Profit | EBITDA Margin | Free Cash Flow |
| 5% (downside) | $52M | 14.2% | $8.1M |
| 8% (base) | $56M | 16.5% | $11.4M |
| 12% (upside) | $61M | 18.1% | $15.2M |
A practical red flag: if a 1% change in a single growth driver moves net income by more than 15-20%, the model likely has a structural issue, such as an assumption embedded in a formula rather than isolated in its own input cell.
Scenario analysis adds another layer. Build a base case, upside, and downside scenario by varying the primary growth drivers together, not individually. Real business conditions rarely change in isolation, and scenario construction should reflect that.
Communicating Growth Driver Assumptions to Stakeholders
Leadership rarely challenges a percentage in isolation; they challenge the business rationale behind it. The most common reason FP&A assumptions get rejected in budget reviews is that the analyst cannot connect the number to a business reality in plain language.
Present assumptions as driver narratives:
- “We are projecting 11% revenue growth because we are entering two new geographic markets in Q2, and our historical conversion rate in new markets averages 22% within 12 months.”
- “SG&A grows 9% against 11% revenue growth because the new market expansion requires upfront hiring, which normalizes after 18 months.”
As NetSuite notes, some SG&A costs are linked directly to business strategy, and accurate projections depend on researching the potential costs rather than applying a flat growth rate. The narrative behind the number is what makes it defensible.
A one-page assumption summary accompanying any financial model should include:
- The key growth drivers selected and why
- The source behind each assumption (historical data, guidance, benchmark)
- Sensitivity to the top two or three drivers
- What would have to be true for the upside and downside cases
This approach builds the credibility that turns FP&A from a reporting function into a strategic partner.
Conclusion
The framework itself is straightforward: growth drivers first, assumptions second, and the financial model third.
Every assumption in a financial model should trace back to a business-level driver, be sourced from at least two data points, and be documentable in a single sentence.
FP&A analysts who apply this approach build models that survive budget reviews, management scrutiny, and mid-year revisions without losing their internal logic.
If you want to build financial models structured around this framework, at Financial Modelling University, we offer practical, practitioner-led training that covers driver-based forecasting from the ground up.
