Value drivers in a valuation conversation: making assumptions traceable

Separate the record of performance from the drivers behind it

Historical financial statements and management accounts show what happened. A valuation conversation often also needs an explanation of why it happened and which conditions may continue, change or disappear. The useful distinction is between an observed result, the operating driver management believes produced it, and the evidence that supports that belief.

For example, revenue growth might be linked to a new customer segment, price changes, renewals, capacity added, a one-time project or a combination of factors. Stating the connection does not prove the forecast; it gives the reader a clear question to test rather than an unexplained percentage in a model.

Use a value-driver register for material assumptions

A concise value-driver register can make the operating story much easier to review. For each material driver, record the historical measure, the forward assumption, the owner, the evidence source, the period covered and the circumstances that could change the result. Keep it proportionate: the aim is to explain the assumptions that could materially affect the decision, not to document every operating metric.

The register can sit beside a forecast, board pack or diligence workstream. It should distinguish confirmed information from management judgement and flag evidence that is unavailable, incomplete or still being validated.

• Revenue: customer retention, pipeline conversion, pricing, volume and customer concentration
• Margins: mix, supplier costs, labour, utilisation, pricing discipline and one-off items
• Cash and capital: working-capital cycle, capital expenditure, debt, owner funding and contingent commitments
• Risk and resilience: contract terms, key-person dependency, systems, regulatory exposure and customer churn
• Growth plan: new markets, product launches, hiring, capacity and the evidence behind each milestone

Make normalisation and forecast bridges explainable

When management discusses non-recurring costs, owner compensation, start-up spend, unusual contracts or a change in accounting treatment, document the underlying event and supporting records before describing any potential adjustment. A label such as "one-off" is not a substitute for an explanation of what occurred, whether it has ended and why the treatment may matter.

For forecasts, create a bridge from the latest historical period to the projected period. The bridge should show the main levers—such as volume, price, mix, headcount, delivery capacity and cash needs—and identify the assumptions that do the most work. This enables a productive challenge process without implying that every forecast outcome is certain.

Test sensitivity before it becomes a surprise

A small number of scenarios is often more useful than one highly precise-looking forecast. Identify the assumptions most likely to change the operating result and show how the analysis responds when those assumptions move. Examples may include a delayed customer renewal, lower utilisation, a higher cost base, slower hiring or a longer cash-conversion cycle.

Sensitivity analysis is a decision tool, not a promise or a valuation conclusion. It helps leadership identify what information is most valuable to obtain, which risks need active management and where an outside reader may reasonably ask further questions.

Keep the scope of any valuation engagement clear

A value-driver register and forecast bridge are preparation tools. They do not determine a standard of value, valuation methodology, conclusion, report scope, intended use or reliance. Those matters depend on the purpose, entity, ownership interest, valuation date, evidence and the terms of an appropriately scoped engagement.

This article is general information, not a valuation opinion, investment recommendation, legal advice or tax advice. Obtain advice based on the relevant facts before relying on a business value or taking action.