The FinOps tools market has grown rapidly. AWS Cost Explorer, Azure Cost Management, Google Cloud Billing, Spot.io, Apptio Cloudability, CloudHealth — there are dozens of platforms that promise to give you visibility into your cloud spend and help you optimise it.
Most organisations that buy one of these tools do not meaningfully reduce their cloud costs. The tool surfaces the data. The organisation does not have the processes, accountability, or culture to act on it. The tool becomes an expensive dashboard that finance looks at once a month and engineering ignores.
What FinOps Actually Requires
The FinOps Foundation defines three phases of FinOps maturity: Inform, Optimise, and Operate. Most organisations get stuck in the Inform phase — they can see their cloud spend, but they cannot explain it to the engineering teams generating it or hold those teams accountable for it.
Moving to the Optimise phase requires cost allocation that is accurate and meaningful. Every cloud resource must be tagged to a team, product, environment, and cost centre — and those tags must be enforced automatically, because humans do not tag resources consistently under time pressure. Without accurate allocation, you cannot have the cost accountability conversation with engineering teams, because nobody can agree on who owns what spend.
The Operate phase — where FinOps delivers its full value — requires scheduled commitment purchasing (reserved instances and savings plans), architectural decisions made with cost as an explicit design constraint, and a regular cadence of cost review that engineering and finance attend together.
The Reserved Instance Problem
The most consistent source of cloud waste we observe in practice is the failure to purchase reserved capacity. On-demand EC2, Azure VMs, and GCP Compute instances cost 40–70% more than equivalent reserved capacity. For workloads that run continuously — production databases, application servers, Kubernetes node groups — the business case for 1-year or 3-year reservations is usually overwhelming.
The reason organisations do not purchase them is governance, not economics. Reserved instance purchases require commitment — and commitment requires someone with the authority and confidence to make a multi-year infrastructure investment. In organisations where engineering and finance do not collaborate on cloud cost decisions, this decision falls through the gap between them.
What Building a FinOps Discipline Looks Like
A genuine FinOps discipline has four components. A tagging standard — enforced automatically — that allocates every cloud dollar to a specific team and workload. A committed spend strategy — reviewed and updated quarterly — that maintains appropriate reserved capacity coverage. A regular cost review cadence — monthly, with both engineering and finance present — that identifies anomalies, celebrates optimisation wins, and holds teams accountable for their spend. And an architectural review process that treats cost as a first-class design constraint alongside performance, reliability, and security.
None of this requires a specific tool. All of it requires organisational commitment and a clear owner. The FinOps function — whether staffed internally or delivered by a partner — is that owner.
Ready to apply this to your organisation?
Book a free 30-minute discovery call. No agenda except understanding your situation and telling you honestly what we'd recommend.