How many drivers should I use?

For revenue, 3-5 drivers per stream is typically sufficient. For costs, 1-2 drivers per major line item. The total model might have 15-25 key drivers. More than that and the model becomes unwieldy; fewer and you lose the benefit of driver-based planning.

How do I validate driver assumptions?

Compare each driver against 12-24 months of historical data. Check the trend, seasonal patterns, and any step changes. For new drivers without history, use industry benchmarks or management estimates with explicit confidence levels.

Is driver-based planning harder than traditional budgeting?

It requires more upfront work to identify and calibrate the drivers. But once built, it is actually easier to maintain because you update assumptions rather than re-building the entire model. It also makes reforecasting much faster -- just update the drivers and the P&L recalculates.

Can I use driver-based planning for costs too?

Absolutely. Common cost drivers include headcount (for salary costs), customer count (for support costs), revenue (for COGS), and square footage (for facilities). The more cost lines you can tie to drivers, the more responsive your model becomes to changes in the business.

Example

Driver-Based Budget Example

A 50-person subscription business in Edinburgh with £3.2M ARR. The FP&A team is replacing last year's static spreadsheet budget with a driver-based model where every line item is linked to an operational assumption. Changing one driver automatically recalculates the entire P&L.

Example data

Financial model

Driver

Assumption

Starting Customers

420

445

472

502

New Customers

8%/qtr

Churned Customers

3%/qtr

(13)

(14)

Ending Customers

445

472

502

534

ARPU (Monthly)

+2%/qtr

£620

£632

£645

£658

Quarterly Revenue

£828k

£894k

£972k

£1,054k

New Customers

New customer acquisition at 8% per quarter is based on current pipeline conversion rates and planned marketing spend. Each new customer costs £4.5k to acquire (CAC).

ARPU (Monthly)

ARPU grows 2% per quarter through a mix of plan upgrades and a planned 5% price increase in Q3. The price increase alone is worth £18k additional quarterly revenue.

Quarterly Revenue

Revenue accelerates from £828k to £1,054k across the year. The compounding effect of more customers at higher ARPU creates a powerful growth curve.

Formulas

Key formulas

fxEnding Customers = Starting + New - Churned

The customer count model is the foundation. Starting with 420 customers and adding ~25 net new per quarter reaches 534 by year end, a 27% growth rate.

fxQuarterly Revenue = Avg Customers * ARPU * 3

Revenue is purely derived from customer count and ARPU. The average customer count across the quarter is used to avoid overstatement from end-of-quarter wins.

fxCost of Support = Customers * £45/customer/month

Support costs are a driver-based cost line: they scale with customer count, not revenue. Each customer requires approximately £45/month of support resource.

Analysis

What makes this example good

Every revenue pound traces back to an operational assumption

Changing one driver (e.g., churn rate) automatically recalculates everything

Assumptions are explicit and can be debated individually

The model naturally handles non-linear relationships

Variance analysis can identify which driver deviated from plan

Customisation

How to adapt for your business

Add cost drivers for each major expense line (e.g., headcount * avg cost)

Include a sensitivity table showing revenue impact of each driver changing +/-10%

Break customers into segments with different ARPU and churn rates

Add a cohort model layer for more sophisticated retention analysis

Connect the revenue drivers to a full P&L for end-to-end driver-based planning

Common variations

--E-commerce driver model (traffic * conversion * AOV * frequency)
--Marketplace model (suppliers * listings * fill rate * commission)
--Services model (consultants * utilisation * day rate * working days)
--Hybrid model with driver-based revenue and category-based costs

Keep exploring

Related examples

Revenue Model Example

A 45-person marketplace company in Manchester with three revenue streams: transaction fees, subscriptions, and advertising. The Head of FP&A is building a driver-based revenue model that starts from operational metrics (users, transactions, ARPU) and builds up to total revenue.

View example

SaaS Budget Example

A 35-person B2B SaaS company in Bristol with £2.1M ARR. The company is post-Series A and needs a budget that speaks the language of SaaS metrics while maintaining a proper P&L. This budget bridges operational SaaS KPIs with financial reporting.

View example

Annual Budget Example

A 120-person B2B software company based in Manchester with £5.2M annual revenue. The business sells a subscription product to mid-market companies and is forecasting 18% growth this year. The finance team is building the annual budget for FY2026.

View example

FAQ

Frequently asked questions

Driver-based planning builds financial forecasts from operational assumptions (drivers) rather than from prior-year numbers plus a growth percentage. Instead of saying "revenue will grow 20%", you say "we will have 534 customers at £658 ARPU." This is more transparent, testable, and flexible.

Build this in Grove FP in 10 minutes

No credit card required. Set up in minutes. 30-day money-back guarantee.