From First Contact to a Live, Trusted Profitability Model

Most profitability work fails not because the arithmetic is wrong but because the engagement has no shape. A consultant arrives, builds a heroic spreadsheet, presents a striking slide, and leaves. Three months later the numbers are stale, no one can refresh them, and the insight that was supposed to change pricing has quietly decayed into a file nobody opens. The problem was never the method; it was the absence of a path from question to living model.

A defined journey fixes that by making each stage produce an artefact the next stage depends on, and by making the client an owner rather than an audience. The diagnostic produces a scoped question and a data inventory. The design produces a documented cost model. The build produces a pipeline your team can run. Validation produces a reconciliation that ties to the cent. Go-live produces decisions. Governance keeps all of it true. Nothing is hand-waved, and nothing leaves with the consultant.

This is also how trust is earned rather than asserted. A board does not trust a number because a consultant is confident; it trusts a number it has watched survive a reconciliation gate and a challenge session. The journey below is built so that by the time management acts on the whale curve, they have already seen the model defend itself. That is the difference between a margin story and a margin fact.

This is the stage where experience separates a durable model from a fragile one, and it is where our years of hands-on time-driven activity-based costing implementation earn their place. Robert Kaplan and Steven Anderson's TDABC reduces the whole problem to two numbers per activity: the capacity cost rate, an annual cost of a resource pool divided by its practical capacity, and a time equation that says how many minutes each transaction consumes. Get those two right and the model allocates itself from the transaction data.

The design work is deciding what the resource pools are, how they map from the accounting cost centres, and how the time equations should flex with real complexity rather than a flat average. Cost centres were built for budgeting and responsibility, not causality, so the crosswalk from accounting structure to cost model is rarely one-to-one and is the single most important design artefact in the engagement. We set practical capacity honestly, at roughly 80 to 85 percent of theoretical, so that idle capacity shows up as a visible number rather than being smeared across output and making healthy products look expensive.

Two judgements decide whether a model ages well, and both come from having built many of them.

The output of this stage is a documented model design: the pools, the rates, the time equations and the mapping table, all in a form the client can read and challenge before a line of pipeline is built.

No number leaves this stage until it has survived two gates. The first is the reconciliation gate: the sum of every cost loaded into the model must equal the audited trial balance to the cent. If the extracted cost does not tie back to the accounts, nothing downstream is credible, and we automate this check rather than eyeballing it so that it runs on every refresh, not just at launch. A costing model that disagrees with the trial balance is almost always an ETL problem, a missed ledger or an inconsistently handled accrual, and the gate is where that gets caught.

The second gate is a challenge session with the people who know the business. We take the model to the operations and commercial teams and test its results against their intuition. When the model says a flagship account is unprofitable, the question is whether that is a real cost-to-serve finding or a broken driver quietly redistributing profit between customers. A driver that does not truly cause a cost is the most dangerous error in costing because the model still balances; it is simply wrong in a way no reconciliation catches. Walking the results past the people closest to the work is how we find those before a decision rests on them. The model that emerges is decision-grade and defensible under scrutiny from a CFO, a lender or a buyer's diligence team.

A live model is not a finished one. The last stage is governance: the routines that keep the model true as the business changes, so that the trust earned at validation does not erode over the following year. A model that was right at launch and never touched again is a slow return to the stale spreadsheet the whole journey was meant to escape.

Governance is mostly a handful of standing habits. The monthly refresh runs the automated pipeline and re-clears the reconciliation gate, so drift is caught the month it appears rather than at year end. The mapping table and the time equations are version-controlled and carry sign-off, so a change in the org structure or a new product line updates the model deliberately rather than by accident. Ownership sits with the client's finance team, with us on hand for the periodic review, so the model does not depend on any one person's memory. The same governed inputs then extend naturally into activity-based management and profitability KPIs, so the recaptured margin stays visible on the board dashboard and the gains show up in the numbers quarter after quarter. The costing stays rigorous; the model stays yours.