Quick answer: Driver-based forecasting builds a sale projection from the operating inputs that produce revenue and cost, such as units shipped, net price, billable utilization, headcount and customer retention, rather than applying a growth percentage to last year. Each driver is tied to history and to evidence, so a buyer can test one assumption at a time. A disagreement then becomes a discussion of a specific input and not a verdict on the whole forecast.
Key points
- A driver is an operating quantity that sits in the company’s own records, has a history and converts to dollars by arithmetic.
- Running last year’s actual drivers through the model and matching reported revenue and gross profit is the first test of whether the model deserves trust.
- Drivers interlock, because volume needs capacity and growth needs people and working capital, so a driver model can check itself in a way a growth percentage cannot.
- A buyer’s case is usually built by changing a few drivers in the seller’s model, so the seller with evidence behind each driver controls the argument.
What a driver is, and what only looks like one
A driver is an operating quantity that appears in the company’s own records, has a history and converts to dollars by arithmetic. Units shipped, net price per unit, billable hours, headcount and the share of customers who renew all qualify. “Revenue grows at a steady rate” does not, because it names a result and gives no cause. A buyer cannot test a result. It can test whether a named customer will order more units, whether a price increase was accepted or whether new hires will become billable.
A real driver passes four tests. It can be measured in the company’s records, it has a history, a named person answers for it, and it turns into a financial line without a leap. A driver that fails a test is not ruled out, but it needs another kind of proof, such as a signed order where a history is missing.
The table shows the substitutions that matter most when a growth-percentage forecast is rebuilt around drivers.
| Percentage assumption | Why a buyer cannot test it | Drivers that replace it |
|---|---|---|
| Revenue grows at a set rate each year | It states an outcome with no cause, so the buyer can only accept or reject it | Units by product line or customer program, multiplied by net price after rebates and returns |
| Gross margin improves each year | It does not say whether price, material cost, yield or mix is changing | Material cost per unit from supplier quotes, labor content per unit, scrap rate, price realization |
| Payroll grows with revenue | It assumes productivity stays fixed and hides the hiring decisions | Headcount plan by role and start date, billable hours or revenue per person |
| Market share rises | No record shows who will buy more, or when | Named accounts, open proposals and the historical win rate |
A manufacturer’s driver tree
A manufacturer’s tree starts with units and net price by product line and runs down through cost per unit to gross profit. Capacity sits beside it as a check on volume. The guide to projecting margins, capital spending and working capital continues below gross profit.
Illustrative example: Driver tree for a two-line manufacturer
A manufacturer sells two product lines. Revenue is units multiplied by net price, and gross profit is revenue less material, direct labor and freight for each unit. Line A volume rises because a distributor has agreed in writing to add a region. Line B is held flat because no new orders are in hand. Supplier prices are fixed by contract through the forecast year, so unit costs do not change.
| Driver | Last year | Forecast | What a buyer would test |
|---|---|---|---|
| Line A units shipped | 400,000 | 420,000 | Monthly shipments; the distributor’s written plan |
| Line A net price per unit | $30.00 | $30.60 | Invoices showing a $1.00 list increase accepted on 60 percent of volume |
| Line A cost per unit | $22.00 | $22.00 | Supplier contract; labor routing |
| Line B units, net price and cost per unit | 100,000; $60.00; $42.00 | Unchanged | No new orders in hand |
| Revenue | $18,000,000 | $18,852,000 | Units times price, by line |
| Gross profit | $5,000,000 | $5,412,000 | Units times margin per unit |
Revenue rises by $852,000, of which $600,000 comes from volume at last year’s price and $252,000 from price. Costs are unchanged, so the same $252,000 reaches gross profit and supplies most of the $412,000 increase. A buyer therefore asks early for the invoices behind price realization.
A capacity driver sits beside the tree. Line A can ship 450,000 units on current shifts, so 420,000 needs no added shift. If the new region supplied 60,000 units, volume of 460,000 would exceed capacity and a second shift would have to enter the model. All figures are invented to show the arithmetic and are not benchmarks.
A services firm’s driver tree
A services firm builds revenue from people, using the number of consultants, the hours available from each, the share of those hours that are billed and the rate actually collected. Cost follows from the same headcount, so hiring ahead of demand shows up at once in a driver model and stays hidden in a growth percentage.
Illustrative example: Driver tree for a consulting-style services firm
A services firm starts the year with 20 consultants. Revenue is available hours multiplied by utilization, the share of hours billed, and by the realized bill rate, the rate collected after write-downs. Two consultants join on July 1 and bill at a lower utilization while they ramp. Staff cost is loaded pay, meaning salary, benefits and payroll costs.
| Driver | Last year | Forecast | What a buyer would test |
|---|---|---|---|
| Consultants added July 1 | 0 | 2 | Signed offers; how fast earlier hires became billable |
| Available hours for each consultant | 2,000 | 2,000 | Attendance and leave records |
| Utilization, existing consultants | 75% | 75% | Timesheets by person by month |
| Utilization, new consultants | n/a | 50% | Ramp of earlier hires |
| Realized bill rate | $150 | $155 | Rate cards, invoices, write-downs |
| Billable hours | 30,000 | 31,000 | 20 x 2,000 x 75%, plus 2 x 1,000 x 50% |
| Revenue | $4,500,000 | $4,805,000 | Hours times bill rate |
| Staff cost | $2,400,000 | $2,580,000 | $123,000 for each existing consultant; $60,000 for each new hire in the half year |
| Revenue less staff cost | $2,100,000 | $2,225,000 | Difference of the two lines above |
Revenue rises by $305,000 but revenue less staff cost by only $125,000, because the new consultants are paid before they bill at the full rate. One point of utilization on the 20 existing consultants is 400 hours, or $62,000 at the forecast rate. They are already on payroll, so nearly all of it reaches profit, and buyers read timesheets before almost any other record. These numbers are invented for illustration and are not benchmarks.
Tying each driver to history
The build follows an order, and each step answers a question that a buyer’s accountants would otherwise ask first.
- Rebuild the driver history from source records such as shipments by product line, invoices by customer and timesheets by person. Buyers request the same figures as operating metrics.
- Back-cast the model. Run it on each historical period’s actual drivers. If it does not reproduce reported revenue and gross profit, the logic or the data is wrong, and a model that cannot describe the past gives a buyer no reason to trust its view of the future.
- Bridge the changes. Split each year’s change into volume, price, mix, new customers and lost customers, and use the same categories in the forecast. A forecast that leans on price when history shows little price contribution must say what changed.
- Label the basis of each forecast driver: run-rate, contracted, planned and funded, or dependent on winning new business. The revenue forecasting guide shows the evidence that supports each label.
- Check the interlocks. Test volume against capacity, headcount against volume, working capital against revenue and capital spending against all three.
- Rank the drivers. Move each by the same small amount, one at a time, and record the change in earnings. The few at the top deserve the heaviest proof.
- Assign owners and freeze a version. Each driver has a named owner and a source document, and the data room model matches the CIM and the management presentation.
What a buyer can do with a driver model
A buyer’s analyst usually ties the opening forecast months to the latest actual results first. The analyst then replaces the seller’s drivers with its own, one at a time, and records the effect on earnings, and finally asks for the cause of every break from historical trend. The guide to how buyers test projections covers the sequence.
The result is a buyer case built on the seller’s own structure, which serves the seller better than a case built from scratch because the disagreement narrows to named inputs. A buyer may accept every driver except volume in one product line and price realization, and each can be answered with a document. A growth percentage offers a single number to cut. A dispute over named drivers can also be settled with structure, as the guide to management case versus buyer case explains. A transactional valuation done before a sale can use the driver ranking to show which assumptions a buyer is likely to challenge.
Where driver models go wrong
- A result with a driver’s label. Revenue per customer, growth in existing accounts and market share restate the outcome and add no mechanism.
- Detail the records cannot support. A driver for every expense line, most with no history, produces false precision and slows the answers buyers wait for.
- Every input leans the same way. Price up, cost flat, utilization up, churn down. A buyer who finds nothing leaning against the seller concludes that the forecast was built backward from a target. The base, upside and downside cases show the inputs that could lean the other way.
- A model nobody inside can explain. The managers who own the drivers will be asked about them in meetings with buyers.
A driver model is the working core of a sale projection. The complete guide to building financial projections for a business sale shows how it fits with the cases, the cash flow schedules and the narrative buyers read.
Frequently asked questions
What is the difference between driver-based and top-down forecasting?
A top-down forecast starts from a total, such as last year’s revenue, and applies a growth rate. A driver-based forecast starts from the quantities that create the total, such as units, price, hours and renewals, and calculates the result. It takes more effort to build, and it lets a buyer test each input separately.
How many drivers should a sale forecast have?
Enough to cover the lines that move earnings, and no more than the company keeps records to support. A small group of revenue drivers and a small group of cost drivers often explain most of the result. Extra drivers add precision the data cannot defend and make the model slower to explain.
Should the projection be monthly or annual?
Monthly for the first forecast year and annual afterward is a workable pattern. Buyers compare the opening months with actual results as they arrive, and monthly columns show seasonality and the timing of hires and contract starts. Later years rarely have the records to justify them.
What if a driver has no history, such as a new product?
Label it as planned and support it with the best evidence available, such as purchase orders, pilot results, supplier quotes and the ramp of earlier launches. Buyers give little weight to an unproven driver, so keep it separable in the model. That lets the buyer exclude it, or lets the parties tie it to an earnout.
Preparing a company for sale or a buyer's diligence?
The Impetus Group offers fractional investment banking support, including earnings normalization, financial projections, CIM preparation and help navigating buyer diligence, with an engagement scoped to what the business needs.
Related guides
- How Buyers Test Your Projections in Diligence, Test by Test: How buyers evaluate financial projections in a sale: the bridge from LTM, forecast accuracy, backlog and pipeline checks, customer calls, capacity and sensitivities.
- Revenue Forecasting for a Sale: Backlog, Pipeline, Recurring and Cohort Methods: How to forecast revenue for a sale: backlog conversion, pipeline weighting, recurring revenue and churn, and cohorts, with the evidence buyers accept.
- Transactional Valuation: What It Is and How It Works: A transactional valuation estimates what a strategic or financial buyer would pay for a business. Learn what goes into one and how it differs from an appraisal.
- Base, Upside and Downside Cases: Scenario Analysis for Sale Projections: Scenario analysis for a sale: what moves between base, upside and downside cases, how to label assumptions and how lenders and buyers use the downside.
- Projecting Margins, Capital Spending and Working Capital for a Sale: How to forecast gross margin, operating expenses, capital spending and working capital in a sale model so a buyer can follow the path from EBITDA to free cash flow.
- Management Case vs Buyer Case: How Buyers Adjust Your Projections: How a buyer turns a management case into its own case: the adjustments it makes, a reconciliation of the gap, and how sellers defend assumptions with evidence.
This guide is general education. It is not a valuation opinion, appraisal, investment advice, or legal or tax advice. How these guides are made.