2.1 — What FOCUS is
To execute FinOps Capabilities you need data. Organisations generate enormous volumes of billing data from many providers, in many formats, at many granularities. Ingesting, normalising, and analysing it is hard because of that variability.
FOCUS™ — the FinOps Open Cost & Usage Specification — provides a unified approach. It enables vendors and organisations to produce billing and usage reports that are normalised across cloud, SaaS, PaaS, and other consumption-based services.
FOCUS is maintained as an open-source specification by FinOps Practitioners, vendors, and Cloud Service Providers themselves. Because it’s open source, it benefits from transparency, agility, and continuous improvement.
How the spec is built
- Convene the working group — practitioners, data generators, and vendors define dimensions, metrics, and attributes.
- Iterate on releases — the working group and broader community shape each cycle through feedback and prioritisation.
- Drive adoption — collaborate with cloud providers, SaaS/PaaS vendors, and data-centre platforms to implement FOCUS natively.
Practical benefits for practitioners
- Cleaner data — less time reconciling schemas, more time on actual FinOps work.
- Faster analysis — query patterns and mental models work across all data generators.
- Portable skills — what you learn about FOCUS data carries across providers, tools, and even employers.
- Apples-to-apples comparisons across providers.
- Better engineering and product decisions because the data underneath is trusted.
2.2 — FOCUS and FinOps: the connection
FinOps is an operational framework that creates financial accountability through collaboration between Engineering, Finance, and business teams. The framework defines Capabilities — the functional areas of activity that support the practice (Reporting & Analytics, Forecasting, Budgeting, Allocation, Anomaly Management, Workload Optimisation, …).
Each Capability needs data to function effectively. The core insight: time spent reformatting billing data is time taken away from positively influencing the FinOps practice. FOCUS feeds normalised data directly into FinOps Capabilities so that practitioners can spend their time analysing, not reformatting.
How much of your FinOps team’s resources go toward reconciling billing data and language across sources before you can even report or visualise spend?
2.3 — Simplifying with a common language
Without normalisation, the same column name can mean different things to different teams. Two Product teams both use a “Cost” column for Planning & Estimating work:
- Team A assumes “Cost” excludes any reduced rates or discounts.
- Team B assumes “Cost” reflects discounted rates.
Each produces materially different forecasts and presents them to the CTO. Confusion, extra analysis cycles, delayed decisions. FOCUS prevents this by providing normalised values with clear, unambiguous definitions.
The three cost fields you must know
| Column | Definition | When to use |
|---|---|---|
| Billed Cost | The charge that serves as the basis for invoicing. Includes all reduced rates and discounts. Excludes amortisation of prepaid purchases. | Cash-basis FinOps work — allocation, budgeting, invoice reconciliation. |
| Effective Cost | Amortised cost after applying all reduced rates, discounts, and the applicable portion of relevant prepaid purchases. The original prepaid charge itself becomes 0. | Tracking and analysing real spending trends and unit economics. |
| List Cost | List Unit Price × Pricing Quantity. No discounts applied. | Calculating savings — compare against Contracted, Billed, or Effective Cost. |
Cash basis vs. accrual basis
- Cash basis — when money is paid (matches Billed Cost).
- Accrual basis — when cost is incurred or consumed (matches Effective Cost).
2.4 — Putting billing data in the path
FinOps doesn’t succeed with just a FinOps team doing FinOps. It succeeds when every Persona in the organisation is doing FinOps as part of their normal job. FOCUS enables that culture to take root.
A common language enables collaboration, but the work of FinOps requires actual billing data in the path of decision-makers. Get it to engineers early and often — ideally before they deploy infrastructure.
Persona notes
- Engineering — FinOps shouldn’t replace DevOps or become a separate task; it works best when it’s part of DevOps.
- Finance — standardised FOCUS data should flow into Finance systems so existing reporting and audit processes can handle cloud spend.
- Leadership — reports should integrate FOCUS data with business metrics like KPIs and unit economics. Isolated FinOps dashboards reinforce the false perception that cost is separate from business outcomes.
Knowledge check
Q. Finance asks for a monthly cost report that should reconcile exactly to the cloud provider’s invoice for that period. Engineering separately asks for a report that shows the true economic cost of each running resource, with prepaid commitments spread evenly across the months they cover. Which two FOCUS columns do the two reports rely on?