What does connecting operations to finance mean?

It means building an explicit, maintained link between the operational drivers that describe how the business runs — volumes, headcount, utilisation, conversion, lead times — and the financial statements that describe its results. When the link exists, a change in an operational assumption flows through to revenue, cost and cash automatically. When it does not, finance and operations plan separately and reconcile afterwards, usually by argument.

Why do operational and financial plans diverge?

Because they are built in different places on different assumptions and reconciled only at set-piece moments. Operations plans in units and capacity; finance plans in currency, and translates the operational view through a set of rates that are rarely revisited. Once those rates go stale, the two plans describe different businesses — and the divergence is usually discovered during a variance discussion rather than in advance.

What is a driver model?

A driver model expresses financial outcomes as the arithmetic consequence of operational quantities and rates — revenue as volume multiplied by price, cost as headcount multiplied by fully loaded rate, and so on down the P&L. Its advantage over a line-item forecast is that it re-runs: when the business changes, you change the driver rather than rebuilding the model, and the consequence is visible immediately.

Connecting Operations to Finance

You own the forecast. Can you trace it back to what the business is actually doing?

When the plan and the operation run on separate models, the forecast drifts — and nobody can say exactly why. Connecting the two gives you an independent, company-level view of what’s really happening, not just what was budgeted.

The plan and the operation slowly stop describing the same company

The financial plan is a model of intent — what the business committed to at a point in time. The operation is what then happens: volumes move, a team is slow to hire, utilisation slips, a pipeline converts late. Each of those is a fact about the business. Most never make it into the financial model except as a downstream number, after the quarter, with the cause already lost.

So the forecast drifts — not because the finance team is wrong, but because it’s reasoning from outputs rather than drivers. By the time the variance shows up in the P&L, the operational event that caused it is weeks gone. You can describe the gap. You can’t yet trace it.

Driver-based thinking is the bridge between the two

A driver-based model derives the financial outcome from the operational levers that actually produce it: volume, price, headcount, utilisation, pipeline. Revenue isn’t a number someone types in — it’s what falls out when you state the volume and the price. Cost isn’t a target — it’s what headcount and utilisation imply. The money becomes a consequence of the operation, expressed in the same model.

That single change is what closes the loop. When a driver moves, the financial picture moves with it — automatically, and in a way you can explain. A forecast stops being a quarterly negotiation and becomes a live readout of operational reality. And when the board asks why margin moved, the answer is already in the model: it traces to the driver, not to a reconciliation exercise that starts after the meeting.

This is the logic behind driver-based planning and driver-based forecasting — and it’s why we treat them as the core discipline rather than a feature.

The independent view

Above consolidation: one independent, company-level view

There’s an important boundary to be clear about. Pulling the entities together into a true and fair set of group accounts — the consolidation — is heavy, technical work, and it stays where it belongs: on the finance side. We’re not trying to relocate it. Consolidation produces the authoritative financial record. That job is finance’s, and it’s done well by finance.

What’s usually missing is the layer above it: an independent, company-level view that takes the consolidated financial position and connects it to the operational drivers underneath — so leadership can see not just the consolidated result but what’s producing it, across the whole business, in one place. That view is independent by design. It doesn’t belong to any one function’s system or any one team’s spreadsheet, which is exactly why everyone can trust it as the same truth.

The result is a shift in what the numbers are for. Instead of a record of what the business did, you get a working model of how it behaves — the same picture for the board, for finance, and for the operating teams who move the drivers in the first place.

Trace your forecast back to reality

Start with a free diagnostic. We’ll look at how — or whether — your operational drivers connect to your financial plan today, and what it would take to give you one independent, company-level view. No pitch, no commitment.

You own the forecast. Can you trace it back to what the business is actually doing?

The plan and the operation slowly stop describing the same company

Driver-based thinking is the bridge between the two

Above consolidation: one independent, company-level view

Inputs on the left, operations on the right — connected through one model

Go deeper

Trace your forecast back to reality

Check your inbox

We'll be in touch