A single cost model across four clouds is the difference between a managed multicloud estate and four separate bills no one can compare. The obstacle is that AWS, Azure, GCP, and OCI each name and structure billing data differently, so raw exports do not line up. The practical solution is the FOCUS specification, the FinOps Foundation open standard that defines a common schema, consistent columns for billed cost, effective cost, usage, and commitment discounts, that every provider now maps its data into. Build your model on that schema and a cross cloud total, allocation, and unit metric all become trustworthy. Without it, every cross cloud comparison rests on someone's spreadsheet assumptions about what each column means.
Here is why the problem is hard, how FOCUS solves the schema, and what a usable one cloud model should express in business terms.
Why is comparing four clouds so hard?
The clouds do not disagree about arithmetic, they disagree about vocabulary. AWS reports cost in the Cost and Usage Report with its own line item structure; Azure has its own cost export columns; GCP exports billing to BigQuery with a different shape; OCI produces its own cost and usage reports. The same concept, the cost after a commitment discount, has a different column name and sometimes a different calculation in each. Layer on the commitment instruments, Savings Plans and Reserved Instances on AWS, Reservations and the Azure Savings Plan, CUDs on GCP, Universal Credits on OCI, and a naive sum of four exports double counts some discounts and misses others. The result is that finance and engineering argue about the number instead of acting on it.
How does the FOCUS standard solve the schema?
FOCUS gives every provider a common target schema. Instead of reconciling four vocabularies by hand, you map each provider export into FOCUS columns once and maintain that mapping. Two columns do most of the work: billed cost, what appeared on the invoice, and effective cost, the amortised cost after commitments and discounts spread across their term. With those defined consistently, a cross cloud total is finally apples to apples. The standard also normalises usage and commitment fields, which makes coverage and utilisation comparable across clouds, so you can see, for example, that AWS commitment coverage is high while OCI Universal Credits are underused, all in one view rather than four consoles.
What should one cost model express in business terms?
A normalised total is the floor, not the ceiling. A model leaders will actually use carries three more things.
- Effective cost, not just billed. Amortise commitments so month to month comparison is meaningful and a large upfront payment does not distort one period.
- Allocation by team and product. Tag based allocation mapped through FOCUS lets you compare what a product costs regardless of which cloud it runs on.
- A unit metric. Cost per customer or per transaction converts an absolute total into an efficiency measure that survives growth and travels across clouds.
With these in place the model answers the questions a board asks: what do we spend in total, on what, per unit of value, and is it getting more efficient.
A worked example
A Fortune 500 retailer ran AWS, Azure, and GCP and reported each separately, so leadership never had a single spend figure and could not tell which cloud was most efficient per unit of traffic. We mapped all three billing exports into FOCUS columns, reconciled effective cost after Savings Plans, Reservations, and CUDs, and allocated spend to products by tag. The single model revealed that one cloud carried far lower commitment coverage than the others, a quick win, and that a workload split across two clouds cost markedly more per transaction on one of them, informing a placement decision. The model became the one number every quarterly review now starts from. Figures are verified against billing data and anonymised.
Frequently asked questions
Why is one cost model across clouds so hard?
What is the FOCUS billing standard?
What should the model express in business terms?
Build one model across your clouds
Our playbook walks through standing up a single FOCUS based cost model across AWS, Azure, GCP, and OCI, independent of any provider and taking zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the guide, then read the cross cloud cost optimization guide for the full approach.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.