Cost allocation without the headache
A simple tagging strategy that teams actually follow, and what to do with the costs tags can't reach.
Every FinOps conversation eventually lands on the same question: who owns this cost? Until you can answer it, savings stay theoretical. Nobody fixes waste they don’t own.
Cost allocation is how you answer that question. It sounds like an accounting exercise, but done well it changes how teams behave. Here’s how to get there without a six-month project.
Start from the business, not the bill
The most common mistake is designing allocation around how the cloud provider structures its bill. Instead, start with how your business thinks about money:
- Which teams or business units should see their costs?
- Which products or customers do you want to understand the cost of?
- Which environments matter: production, staging, development?
Write this down as a short list. That list is your allocation model. Everything else is just implementation.
Use as few tags as possible
Tags (labels in some clouds) are the main tool for linking resources to owners. The temptation is to define twenty of them. Don’t. Teams follow three or four tags. They ignore twenty.
A good starting set:
- owner: the team responsible
- product: the product or service it supports
- environment: production, staging or development
- cost-centre: only if finance needs it for reporting
Agree on exact spellings and allowed values. “Prod”, “production” and “PRD” are three different tags to a report.
Use structure before tags
Tags aren’t the only way to allocate. Often the easiest win is structural: separate accounts, subscriptions or projects per team or product. Everything inside them is allocated automatically, with no tagging discipline required.
A practical rule: use accounts and projects for big boundaries (teams, products, environments) and tags for the details inside them.
Decide what to do with shared costs
Some costs can’t be tagged to one owner: shared networking, security tools, support plans, a database used by several products. Ignoring them makes every team look cheaper than it really is.
Pick a simple, transparent rule and stick to it:
- Proportional: split by each team’s share of direct spend
- Even: split equally across teams
- Usage-based: split by a measurable driver, such as requests or storage used
The best rule is the one everyone understands and accepts. Precision matters less than consistency.
Make it stick
Allocation decays without maintenance. Three habits keep it healthy:
- Enforce tags at creation. Most clouds let you require tags through policies, so untagged resources can’t be created in the first place.
- Report on the gaps. Show the share of unallocated spend every month. When it’s visible, it shrinks.
- Share the results. Send each owner their own cost report. Allocation only creates value when the people who own the costs actually see them.
How far to go
Aim for about 80% of spend allocated in the first month or two. That’s enough for teams to recognise their costs and start acting. Chasing the last few percent can wait.
If you’d like a second pair of eyes on your current setup, a FinOps assessment measures how much of your spend is allocated today and what it would take to close the gap.