FinOps Consulting
What to Do When Your Cloud Bill Is Already Optimized: Cloud Cost Optimization, Egress and Moving Steady Workloads
Most FinOps work stops at the edge of the cloud. Ours starts there. Send us the shape of your bill for a Free Cloud Bill Review: a first read within 24 hours on whether there is a saving worth modeling beyond what FinOps has already found.
Get My Free Cloud Bill ReviewFinOps inside the cloud is the right first step, and for many companies it is enough. But it runs out. Once commitments cover the steady baseline, instances are right-sized and batch work runs on spot, each further round finds less, and waste has a way of coming back: wasted cloud spend rose to 29 percent in 2026, the first increase in five years, as AI workloads arrived. This guide is written by an advisory practice that prices the options on both sides of that line, in the cloud and out of it, and does not resell cloud capacity or FinOps software.
Sources: Flexera 2026 State of the Cloud (first three); major cloud provider price lists (egress). As of October 2026.
Annual cloud spend, which cloud or clouds, the main workloads, and roughly what your outbound data looks like.
A first read on whether there is a saving worth modeling beyond what your FinOps work has found, and roughly how large it could be.
If FinOps inside the cloud is the right answer for your bill, we will tell you so, and it will have cost you one email.
The first read is free. A full analysis is a fixed fee only if you choose it, and placement is paid by the provider.
Or email the shape of your bill to contact@metrocoloadvisory.com
Why Our FinOps Consulting Services Go Further
Most FinOps engagements finish where ours begins. Four things set the work apart, and each one is there to get you a larger, better-supported number than a standard engagement would.
We price the lever other FinOps work leaves out.
For every workload steady enough to move, we build the cost of running it on bare metal and on owned hardware in colocation, line by line, and set it against your optimized cloud cost, not your list price. Comparing against list is how repatriation cases get overstated.
We start where your team finished.
We do not redo rightsizing or sell you a tagging project. We take your billing export and allocation data as they stand, credit the savings already achieved, and model only what is left.
We know what the alternatives cost.
Published pricing for bare metal and colocation is a rate card; what providers sign at volume is a different number, and we are in that market continuously. Data Center Knowledge used the practice as its source in August 2026.
The fee is fixed, and the answer is not.
We do not resell cloud capacity or FinOps software, so we have no stake in keeping you where you are. If the answer is that FinOps inside the cloud is enough, that is the answer you get.
Press: Data Center Knowledge, August 2026, on the gap between the space operators advertise and what they can deliver.
What a FinOps Engagement Produces, and What It Costs
| Deliverable | What it contains |
|---|---|
| A workload map | Every material workload sorted into steady, variable or mixed, with its egress profile, its dependence on managed services, and any data residency or compliance limits. This produces the movable list and the stay list, confirmed with your engineers before anything is priced. |
| An in-cloud baseline | Your optimized cloud cost today and the FinOps headroom still left inside the cloud, crediting what your team has already achieved. |
| A dedicated cost build | The movable list costed on bare metal and on owned hardware in colocation: servers, facility, interconnect, bandwidth, operations, the platform layer that replaces managed services, and migration. |
| A scenario model | Optimized cloud, bare metal, colocation and hybrid, as a P&L over three to five years, with cash timing separate from EBITDA and egress broken out. A working model your finance team keeps. |
| A recommendation | Which scenario, which workloads, in what order, the risk attached to each, and what has to be true for each move to work. |
The engagement starts with one thing: your billing export. From there the movable list is in writing inside two weeks. Placement, if you decide to move, is separate and costs you nothing.
Cloud Cost in 2026: The Numbers
| Figure | Number | Source |
|---|---|---|
| Wasted cloud spend | 29 percent of infrastructure and platform spend, up from 27 percent and the first rise in five years | Flexera 2026 |
| Large enterprises spending more than $5 million a month on cloud | 76 percent | Flexera 2026 |
| Organizations with an established FinOps team | 63 percent | Flexera 2026 |
| Managing cloud spend cited as a top challenge | 85 percent | Flexera 2026 |
| Generative AI as a public cloud service | 58 percent of organizations | Flexera 2026 |
| Internet egress from the major clouds at volume | Roughly 5 to 9 cents per gigabyte, not discounted by commitments | Provider price lists |
| Free data transfer when leaving a cloud | Google (January 2024), AWS and Microsoft (March 2024), for full departures | Provider announcements |
| Typical saving moving steady workloads to bare metal or colocation | 30 to 50 percent against optimized cloud cost; varies by workload | Metro Colo Advisory market read, consistent with a16z, which put repatriated workloads at one-third to one-half the cost of equivalent cloud |
Sources: Flexera 2026 State of the Cloud, a survey of 753 cloud decision-makers; provider price lists and announcements. Checked October 2026.
What Does FinOps Consulting Actually Do?
FinOps, short for financial operations and also called cloud financial management, is the practice of making engineering, finance and the business jointly accountable for cloud spend. The FinOps Foundation organizes it into three phases, and most FinOps services map onto them.
Inform
Making spend visible and attributable: tagging, cost allocation, showback and chargeback, so every dollar has an owner and a unit cost can be calculated. On its own it saves nothing, but nothing else works without it.
Optimize
Reducing the rate and the usage: commitment discounts, rightsizing, spot capacity, storage tiering, newer instance families and cleaning up idle resources. This is where most cloud cost optimization services earn their fee.
Operate
Keeping it that way: budgets, anomaly alerts, cloud cost governance and a regular cadence between engineering and finance. This is where FinOps tools and FinOps as a service tend to live.
What all three phases share is an assumption: the workload stays where it is. FinOps makes the cloud cheaper. It does not usually price leaving it, and for a company whose steady workloads have outgrown per-hour and per-gigabyte pricing, that is where the larger number sits.
Where Does Cloud Cost Optimization Run Out?
Every cloud cost reduction program works through roughly the same levers. The first seven make the cloud cheaper. The eighth asks whether a workload belongs in it.
| Lever | What it does | Where it stops |
|---|---|---|
| 1. Visibility and allocation | Shows who spends what, and what a unit of product costs | Saves nothing directly; it is the foundation |
| 2. Idle and waste cleanup | Removes unused and forgotten resources | A one-time gain; waste returns with every new workload, as AI has shown |
| 3. Rightsizing | Matches instance size to actual load | Once instances fit, there is little left |
| 4. Commitment discounts | Savings Plans, Reserved Instances, Azure reservations, Google committed use discounts | Still cloud pricing, discounted; locks in one to three years |
| 5. Spot and preemptible capacity | Deep discounts for interruptible capacity | Only for work that tolerates interruption; mature teams already use it |
| 6. Newer instance families | Better price-performance, including Arm | A step change you take once |
| 7. Negotiated private pricing | Enterprise discount at large committed spend | Discounts the rate; egress is still billed per gigabyte |
| 8. Placement: bare metal or colocation | Moves steady workloads off per-hour and per-gigabyte pricing | Needs migration and operations; wrong for spiky or deeply managed workloads |
Most companies are right to work down that list in order. The problem is that many stop at seven, and for a steady, egress-heavy workload the eighth is usually worth more than the rest combined. It is also the only one that comes with a migration, which is why it deserves a model rather than a hunch.
A Worked Example: FinOps Done, Now What?
The figures below are illustrative, built for a company spending about $24 million a year on one hyperscaler with a mature FinOps practice: commitments cover the steady baseline, batch work runs on spot, and the fleet has moved to newer instance families. They show the shape of the analysis, not any client’s numbers.
Illustrative example, not client data. Free to cite with a link to this page.
| Line | Annual |
|---|---|
| Cloud spend today, already optimized | $24.0 million |
| Further savings still available inside the cloud | about $1.2 million |
| Steady, egress-heavy workloads identified as movable | $9.6 million |
| The same workloads on bare metal, including operations and bandwidth | $6.7 million |
| Recurring saving from placement | $2.9 million |
| One-time migration cost | $1.2 million, paid back in about five months |
The in-cloud headroom is small. After years of good FinOps, another round of optimization finds around 5 percent. That is worth taking, and it is not the main event.
The placement saving is larger, and it recurs. About 30 percent on the movable share, and most of it comes from bandwidth and the managed-services layer rather than compute. The bare metal guide walks through why egress is usually the biggest line.
It is an EBITDA number, not just a cost number. $2.9 million of recurring saving is $2.9 million of EBITDA. At an illustrative 12 times multiple, that is roughly $35 million of enterprise value, which is why companies preparing to raise or list look at this question at all.
If your numbers look anything like that, send us the shape of your bill. You’ll hear back within 24 hours, at no cost.
Get My Free Cloud Bill ReviewWhy Does Egress Decide So Many FinOps Cases?
Egress, the charge for data leaving the cloud, is the line FinOps can do least about. AWS, Azure and Google Cloud all bill internet egress per gigabyte, roughly 5 to 9 cents at volume, and commitments do not discount it. Bare metal and colocation providers sell bandwidth as a port with a commit, so for a business that serves traffic at scale, the same outbound volume costs a fraction as much. Even for workloads that stay in the cloud, a private link cuts the rate: AWS charges about 2 cents per gigabyte over Direct Connect in the US, as the data center connectivity guide sets out.
Exit costs have changed too. Google, AWS and Microsoft introduced free data transfer for customers leaving in early 2024, following the EU Data Act. The catch for most FinOps cases is scope: the waivers are built for full departures, with conditions such as a 60-day window and closing or emptying the account. A hybrid move, where steady workloads leave and the rest stays, generally has to budget its migration transfer. The cloud repatriation guide covers the full exit strategy.
FinOps Tools or FinOps Consulting?
Both, usually, for different jobs. FinOps tools, from native consoles to dedicated cloud cost management software, handle the operate phase: dashboards, allocation, anomaly alerts and commitment automation, running every day. A consultancy handles the decisions a tool cannot make: which commitments to buy, how to restructure allocation, and whether a workload should move. What no tool does is price the alternative. Every dashboard reports your cloud spend against your cloud spend, which is why our engagements sit alongside your FinOps tooling rather than replacing it.
How Cost Optimization Differs Across AWS, Azure and Google Cloud
AWS cost optimization
Centers on Savings Plans and Reserved Instances for commitments, Spot Instances for interruptible work, and Graviton for price-performance.
Azure cost optimization
Uses reservations and the savings plan for compute, spot virtual machines, and the Azure Hybrid Benefit for existing Windows Server and SQL Server licenses.
Google Cloud cost optimization
Relies on committed use discounts, sustained use discounts applied automatically on some machine types, and Spot VMs.
All three bill egress per gigabyte, and all three offer exit waivers for full departures. The placement analysis runs the same way whichever you are on, and multi-cloud estates are modeled provider by provider.
When Is FinOps Inside the Cloud the Right Answer?
More often than repatriation advocates admit. If your workloads spike ten times against their baseline, depend heavily on proprietary managed services, need to run in many regions at once, or total less than a few hundred thousand dollars a year, a move rarely pays for its migration and operations. In those cases the right engagement is good FinOps, and we will tell you so rather than sell you a model you do not need. The cloud versus colocation calculator gives a free first read before any engagement.
How the Practice Works on Cloud Cost
Consulting, paid by you. The FinOps and repatriation analysis described above, at a fixed fee agreed before work starts, delivered in writing with the working model.
Placement, paid by the provider. If you decide to move, we take the specification to providers and operators, run the process so the responses are comparable, and negotiate the terms that matter. The provider you choose pays us through its channel program, so you pay nothing and are under no obligation to use us for it. See how placement works.
The two are separate. The consulting fee does not depend on the placement, and the placement does not depend on having done the consulting. The data center consulting page covers the wider practice.
Frequently Asked Questions
What is FinOps?
FinOps, short for financial operations, is the practice of managing cloud spend as a shared responsibility between engineering, finance and the business, so every dollar of cloud cost has an owner and a purpose. The FinOps Foundation organizes it into three phases: inform, optimize and operate.
What is FinOps consulting?
FinOps consulting is outside expertise in cloud financial management: making cloud spend visible, reducing waste and buying capacity at the lowest available rate. Most engagements cover allocation, commitment strategy, rightsizing and an operating cadence. The better ones also ask whether steady workloads belong in the cloud at all.
What does a FinOps consultant do?
A FinOps consultant diagnoses where cloud money goes and sets up the practices that keep it under control: tagging and allocation, commitment purchasing, rightsizing, anomaly monitoring and governance. At larger scale they also model structural options, such as negotiated pricing or moving workloads to dedicated infrastructure.
How much does FinOps consulting cost?
It depends on the pricing model: some firms charge a percentage of savings, some sell a subscription bundled with software, and some charge a fixed fee. Our engagements are fixed-fee, typically $50,000 to $195,000 over four to six weeks, and include the scenario model for moving steady workloads off the cloud. The first read on your bill is free.
What is the difference between FinOps tools and FinOps consulting?
FinOps tools run continuously: dashboards, allocation, alerts and automated commitment purchasing. FinOps consulting makes the decisions a tool cannot, such as restructuring commitments or deciding whether a workload should move. Most companies above seven figures of spend use both.
How much can cloud cost optimization save?
It depends on how mature your practice already is. Companies starting from nothing often find large savings in waste and commitments; Flexera’s 2026 report put wasted cloud spend at 29 percent across the industry. Companies with mature FinOps usually find little headroom left inside the cloud, and the larger saving is placement: steady workloads on bare metal or colocation typically cost 30 to 50 percent less.
When does FinOps stop saving money?
Usually once commitments cover the steady baseline, instances are right-sized and interruptible work runs on spot. After that each round finds less, and egress, the largest line for many traffic-heavy businesses, barely moves because it is billed per gigabyte regardless of commitments.
Is cloud repatriation part of FinOps?
It is the part most FinOps programs leave out. FinOps asks how to buy cloud more efficiently; repatriation asks whether a workload should be in the cloud. A sound analysis models the two against each other, which is what our engagements do.
How do you reduce cloud costs when commitments and rightsizing are already done?
Look at placement and egress. Steady workloads with heavy outbound traffic often cost 30 to 50 percent less on bare metal or colocation, mostly because bandwidth is sold as a port rather than per gigabyte. Hybrid designs keep the elastic and managed parts in the cloud and move the steady core.
Does it matter whether we are on AWS, Azure or Google Cloud?
For in-cloud optimization, yes: the commitment instruments, spot programs and licensing benefits differ. For the placement question, much less, because all three bill egress per gigabyte and the dedicated alternatives are priced the same way whichever cloud you leave. Multi-cloud estates are modeled provider by provider.
How do egress fees affect cloud cost optimization?
Egress is often the line that decides the case. The major clouds bill outbound data per gigabyte, roughly 5 to 9 cents at volume, and commitments do not discount it, while bare metal and colocation providers price bandwidth as a port. Exit waivers introduced in 2024 cover full departures but generally not a partial, hybrid move.
What is a Free Cloud Bill Review?
Send us your annual cloud spend, which clouds, the main workloads and roughly what your outbound data looks like. Within 24 hours you get a first read on whether there is a saving worth modeling beyond what FinOps has found, and roughly how large. It costs nothing, and if FinOps inside the cloud is the right answer, we will say so.
Get Your Free Cloud Bill Review
Annual spend, which cloud or clouds, the main workloads, and roughly what your outbound data looks like. That is enough for a first read on whether there is a saving worth modeling beyond what FinOps has already found, and you’ll hear back within 24 hours. If FinOps inside the cloud is the right answer, we will tell you that.
We do not resell cloud capacity or FinOps software, and placement, if you move, is paid by the provider.
The decision after FinOps: cloud repatriation, the cloud versus colocation calculator and hybrid cloud.
Where steady workloads go: private cloud, bare metal, wholesale colocation and the colocation pricing guide.
Costs and contracts: data center cost, the data center lease guide, data center connectivity and the provider comparison.
Specific workloads: AI and GPU colocation, GPU rental, disaster recovery, compliance and VMware alternatives.
The wider practice: data center consulting, data center due diligence, data center migration and why use a broker.