B2B SaaS / European SaaS platform
From runaway spend to accountable cloud unit economics
How a scaling SaaS platform connected infrastructure spend to product demand, recovered waste, and made cost ownership part of engineering delivery.
The operating constraint
Growth had outpaced the company’s ability to explain its cloud bill. Monthly spend was visible at account level, but product leaders could not connect cost to a customer, feature, or transaction. Engineering teams saw optimisation as a periodic finance request rather than a design constraint.
The result was predictable: oversized workloads, forgotten environments, inconsistent tagging, and forecasts that moved after every release. The company needed savings, but it could not trade away the capacity supporting growth.
The intervention
Detakai created a cost-and-usage model around the company’s actual product architecture. Shared infrastructure was allocated using consumption drivers, while directly attributable services were mapped to products and environments.
We then combined four workstreams:
- Rightsizing based on sustained utilisation, not peak snapshots.
- Automated schedules for development and test environments.
- Commitment planning after variable demand had been separated from the stable base load.
- Ownership policies embedded into infrastructure pull requests.
Every recommendation carried an owner, expected return, implementation effort, and service-risk assessment. This turned a large cloud bill into a sequenced engineering backlog.
What changed
Within twelve weeks, 31% of idle and structurally inefficient spend had been removed. Allocation coverage rose from 38% to 94%, giving product teams a reliable cost-per-account and cost-per-transaction view.
The more important shift was behavioural. Cost variance became part of release review, and teams could see whether a technical decision improved or weakened product margin. Finance stopped chasing explanations after month-end; engineers received useful cost signals while decisions were still reversible.
The durable system
The company now runs a monthly unit-economics review supported by automated anomaly routing. New services inherit ownership, budget, and lifecycle metadata by default. Savings are not treated as a one-time programme: the controls continually identify drift as products and demand change.
The system protects both sides of the equation—financial efficiency and the capacity required for growth.