The lineage
A short history of knowing what things cost.
The methodology behind CostCtrl isn't new. It's a proven idea whose rigour was always sound. What changed is the cost of putting it to work.
The ABC movement, and why it stalled.
Activity-based costing arrived in the late 1980s and dominated the cost-accounting conversation through the 1990s. The premise was simple: allocate costs by the activities that drive them, not by a flat % of revenue. The implementations were not. Models took years to build and broke within a quarter. By the 2000s, most companies had quietly given up.
TDABC: the evolution of ABC.
Time-Driven Activity-Based Costing, developed by Kaplan and Anderson, evolved ABC into something more powerful and more scalable, modelling cost through the time activities actually consume. A real step forward, but a more demanding one: it asks more of a company's data, its systems, and the maturity of the team running it. For most businesses, that demand was exactly what kept a rigorous model out of reach.
Enterprise cost platforms calcified.
A handful of enterprise platforms made cost modelling tractable for very large companies. They required six-figure implementations, dedicated consultant teams, and year-plus deployments. The mid-market couldn't afford them.
What changed, and why companies are coming onboard now.
This is where CostCtrl comes in. We paired the proven methodology with our own allocation engine and an AI layer that work in concert: the engine computes every number, the AI builds and reads the model alongside your team. Work that used to take months, schema generation, data integration, driver inference, insight synthesis, now takes weeks. Companies already know they need this clarity. What changed is that reaching it is finally fast and affordable, which is why they are adopting it now.