A new client. Mid seven-figure cloud spend. No FinOps practice. This is not a hypothetical or a constructed case study. It is a real engagement starting in the next few weeks, and I am going to write about it as it unfolds.

The premise is straightforward. A company reached the point where the cloud bill became impossible to ignore, and a CIO asked a simple question: we should probably have a FinOps practice, right? That question made its way to an IT Director, who is now responsible for figuring out what that actually means in practice. The Director does not have the bandwidth to build it alone. That gap is why I am involved.

The environment itself is not unusual once you look past the industry narrative. This is a private company in a traditional industry with a traditional IT organization. They have a meaningful on-prem footprint that is not going anywhere, alongside a mid seven-figure annual public cloud spend. What they do not have is everything typically associated with FinOps. There is no tagging strategy, no allocation model, no tooling, no reporting cadence, and no clear owner of cloud cost.

The engagement will run for six months. The first phase focuses on understanding the environment, establishing baseline reporting, and introducing the initial structure around tagging and ownership. The second phase moves into optimization, tooling decisions, and the beginnings of a governance model that can persist beyond the engagement. Six months is the entire window to go from zero to something that can stand up to a CFO-level question.

I am going to share what I see, where assumptions break, and what actually works. Not on a fixed schedule, but when there is something worth saying.

There is a gap between how the FinOps industry talks about maturity and what actually exists in the market. And I fell into this gap.

If you follow conferences, vendor briefings, or most published content in 2026, the assumption is that the early-adopter phase is over. The conversation has shifted toward more advanced topics. AI cost, unit economics, and the relationship between engineering decisions and gross margin dominate the discussion. Those are real and important problems.

They are just not universal problems.

A company with a mid seven-figure cloud spend and no FinOps practice is not supposed to exist according to that narrative. Yet it does, and it is not an isolated case. These environments are more common than the industry acknowledges, particularly in traditional sectors where cloud adoption outpaced organizational change. The bill grew, but the operating model did not.

FinOps maturity is not a smooth progression across the market. It is bimodal. One group of companies started early and built the necessary discipline over time. They are now dealing with second-order challenges. The other group is still at the starting line, often because cost only recently became visible enough to demand attention.

The market for new FinOps programs is still there. It is simply less visible than the conversations happening at the leading edge, so it receives less attention.

The instinct at this stage is to buy a tool. A dashboard feels like progress. It creates the appearance of movement and gives stakeholders something tangible to look at. Vendors are structured to support that instinct.

It is also the wrong starting point.

The first 90 days are not about tooling. They are about establishing ownership and creating the conditions for the organization to care about cost in a meaningful way.

That starts with basic questions that are often unanswered. Who owns cloud cost? Not in theory, but in practice. What language will be used when discussing cost across engineering, finance, and IT? Where does the data currently live, who can access it, and who has the authority to act on it? Do the teams closest to the spend have any incentive to change their behavior?

Frameworks can provide guidance, and they will be useful here. But handing a framework to a team that has never operated this way produces activity without control. The same is true for tools. Both assume a level of organizational readiness that does not yet exist.

If this phase is successful, the output is not a dashboard. It is a working system. That includes a defined set of owners tied to specific areas of spend, a tagging approach that has been agreed upon by the teams responsible for implementation, and an initial reporting cycle that reflects how the business thinks about its technology, not just how the billing data is structured.

Only after that foundation exists does tooling become valuable.

The first few weeks will provide more signal than most people expect.

One of the first questions is how fragmented the cloud spend is across the organization, and whether anyone can answer even basic questions without generating a new report. In many cases, the data exists but has never been used to inform decisions.

Another area to watch is how the organization thinks about on-prem and cloud costs. In traditional environments, on-prem infrastructure typically has a clear owner and an established mental model. Cloud often does not. That imbalance creates confusion around accountability and leads to inconsistent decision-making.

The nature of executive sponsorship also becomes clear quickly. The CIO’s request initiated this effort, but the strength of that sponsorship will be measured through follow-through. Prioritization, participation, and willingness to enforce change will determine whether the program gains traction.

Finally, there is the human dynamic. Some individuals will be engaged and interested in solving the problem. Others will be skeptical or indifferent. A few will expect the effort to fail. All of these perspectives are useful signals. Ignoring the resistance is where many early-stage efforts break down.

For organizations with mature FinOps practices, this will provide a reference point for what the early stages actually look like in 2026. Some of the processes that feel essential in a mature environment will appear unnecessary at this stage, while others will stand out as foundational in a way that is easy to forget over time.

For those who are at or near zero, this offers a view into the part of the journey that is rarely documented. Most content focuses on outcomes rather than starting conditions. Seeing the initial steps, and the friction involved, is often more useful than another description of an end state.

For vendors and service providers, this highlights where the buying conversation actually begins. It does not start with a tool evaluation. It starts with a lack of clarity around ownership, data, and decision-making. Entering too late in that process limits the ability to influence meaningful change.

The engagement begins soon, and the starting point is clear. A company with real spend, no system, and a mandate that has only recently become urgent. I’m excited for the possibilities.

Starting from zero is more common than the industry suggests. It is simply less visible. This is an opportunity to make that visible, and to share what it actually takes to build something that works.

Structural Trend Quick Takeaway

Pick any line of your cloud bill. Ask two questions. Which team is on the hook for this spend? Which specific person on that team will answer the phone when it moves the wrong way? If both answers come back without a pause, the line is covered. If either answer is "I will get back to you," it is not.

The signal is the percentage of total cloud spend, weighted by dollars, where both questions answer cleanly.

A team without an individual produces diffusion. The budget envelope sits on a group, and when overspend happens, everyone agrees it is a problem and nobody agrees whose problem it is.

An individual without a team produces a hero or a martyr. One person carries the weight, the rest of the team treats the spend as someone else's job, and the program collapses the moment that person changes scope or leaves.

Both layers matter for different reasons. Team ownership sets the envelope and creates peer accountability. Individual ownership creates a clear escalation path and a single name that finance can call when the number moves. A FinOps program without both layers is the kind of program that produces dashboards nobody reads.

This signal is also the cleanest way to test whether the change-management work in the first 90 days is actually landing. Tag coverage is easy to fake by running a script. Reporting cadences are easy to fake by sending the email. Named ownership is hard to fake because it requires someone to say yes to something in a meeting where their name gets written down.

You do not need a tool. Open the bill.

Sample the 20 largest cost lines. In most environments, those 20 lines cover 70 to 80% of total spend. For each line, write two columns. Team owner. Individual owner. Fill the columns by walking the org and having the conversation, not by guessing from a tag.

The dollars covered, divided by the total spend in your sample, is your starting number.

Do this once with no preparation. The result is your honest baseline. Most greenfield programs come in under 20%. Some come in at zero. Then do it again 90 days later, after the change-management work has run. The delta is the signal.

Below 30%. The program is pre-baseline. Any tooling investment at this stage compounds the gap because the tool will surface cost to a layer that has no one to act on it.

30 to 60%. The program is in motion. The named owners are usually concentrated in the workloads that already had attention. The gap is everywhere else.

Above 80%. The program has structure. The remaining gap is usually shared infrastructure that genuinely belongs to a platform team. That is fine, as long as the platform team has both layers covered for its own scope.

100% is not the goal. A 100% number usually means someone wrote a name into a spreadsheet without negotiating it. A 75% number negotiated in real conversations is worth more than a 100% number generated by a tagging policy.

A tool can tell you what a tag says. A tool cannot tell you whether the person on the tag will pick up the phone, or whether they have the authority to make a decision when they do. Those are organizational questions. They get answered in rooms, not in dashboards.

The reason this is the signal for a greenfield engagement is the same reason it is the signal for any new program at any size. The work of FinOps is putting names on things. Everything after that is execution.

News or Market Updates for Engineering, IT, or FinOps leaders.

Summary: Relatively slow period from the hyperscalers, with one useful AI cost primitive from Google. Yet, layoffs kept moving, with Cloudflare and Meta on the May calendar and US tech cuts past 113,000 year to date. FinOps X is three weeks out.

FinOps X 2026, June 8-11, San Diego. Three weeks out. This year's theme is AI Value, token economics, agentic FinOps, and executive alignment (agenda). The State of FinOps 2026 numbers driving the framing (98% manage AI spend, 90% SaaS, 78% report to CTO/CIO) describe the top of the curve. The greenfield programs starting this year, including the one in this issue's lead, are not in that data.

FinOps Best Practices That Turn Cloud Cost Into Action (Hyperglance, May 12). Walks the move from visibility to action and lands on the same point this issue's FinOps Signal makes: teams stall at the dashboard because nobody owns what the dashboard shows.

Cloudflare, May 7-8. 1,100 layoffs (20% of staff) announced alongside earnings, with CEO Matthew Prince citing AI efficiency and AI usage up 600% in three months. Stock dropped 24% on the same call (CNBC).

Meta, effective May 20. 8,000 cuts and 6,000 cancelled open roles as Meta raises 2026 capex guidance to $115-145B against $56.3B in quarterly revenue. Teams reorganized into AI-focused pods under Alexandr Wang.

TechTimes, May 18. US tech layoffs past 113,000 across 179 events year to date, a 33% increase over the same period in 2025 and the worst pace since 2023.

If you would like your company included in the Spotlight, contact the CloudXray AI Team

Company: CloudXray AI

Category: Managed Services & Consulting

What They Do: FinOps Consulting & Advisory Services; Owners & maintainers of the single largest FinOps company directory (finops.cloudxray.ai)

Why It Matters: Companies still need guidance on implementing FinOps and understanding the landscape of companies that exist

Practical guide for leaders and practitioners

If you have nothing in place today and the CIO just asked you to start, this is the work. No tools. No framework rollout. No maturity assessment. Just the moves that need to land in the first month before any of the heavier lifting works. The lead essay in this issue framed the first 90 days as change management. This is the first 30 of those 90.

The CIO said “FinOps.” That word is overloaded, and if you do not pin it down early, the program will drift. Before you build anything, get your sponsor on a call and force clarity in three areas.

Start with the problem. What are they actually trying to solve? Is it cost growing faster than revenue, surprise quarterly bills, lack of visibility for the CFO, or pressure to reduce spend without adding headcount? There are many valid answers, but you need one primary driver.

Next is the definition of success. What does “working” look like in six months? Is it a repeatable report, a budget process, a measurable reduction in spend, or clear ownership across workloads? Again, you are not looking for a list. You are looking for a shape.

Finally, understand what they are willing to back you on. This is the most important part. Are they willing to enforce tagging, assign ownership, change accountability structures, or push back on new spend? These are the moments where the program will either move or stall.

Write the answers down. If they stay vague, everything that follows will be as well.

Before introducing any tooling, you need a direct understanding of where the money goes.

Take the most recent month’s bill in whatever form it exists today. Spreadsheet, console view, billing export. It does not matter. What matters is that you work from raw data. Identify the top 20 cost lines. In most environments, those lines will account for 70 to 80 percent of total spend.

For each one, document three things. What the cost represents, what business function or workload it supports, and the approximate monthly value.

This exercise should take a few hours. The output is a single-page view of your spend concentration. That page becomes the foundation for everything else. Without it, you are operating abstractly.

Once you understand where the money is going, the next step is to attach accountability.

For each of the top cost lines, identify both the responsible team and a specific individual who can speak to the number. Not in theory, but in practice. Someone who will respond when the number moves.

This is not a tagging exercise. It is a conversation exercise. You need to walk the organization and ask directly. Some answers will be clear. Others will not exist yet.

That absence is important. It tells you where the system is broken.

At the end of this step, calculate your baseline coverage. What percentage of total spend has a named owner, weighted by dollars? Most greenfield environments land below 20 percent.

That is your starting line.

With a baseline established, focus on what can realistically move in the first month.

Where a team exists but no individual is accountable, assign one. This is usually a short conversation with the team’s manager. Most will agree, especially if ownership comes with visibility and influence over the number.

Where no team owns the workload at all, do not attempt to solve it immediately. These are typically shared services or legacy systems that require broader organizational decisions. Capture them, but do not let them stall progress.

The goal in this step is measurable movement. Shifting ownership coverage from 20 percent to 40 percent in 30 days is meaningful progress and creates momentum for the rest of the program.

Most teams make the mistake of waiting until they have a polished report before scheduling any reviews.

That delay kills momentum.

Instead, schedule the first monthly cost review immediately. Put it on the calendar. Invite your sponsor and the owners identified in the previous steps.

The first meeting should run off the simple top-20 view you created earlier. No dashboards. No polished slides.

The purpose of the meeting is not to present. It is to observe. Who shows up, who engages, where the questions come from, and where resistance appears. Those signals will tell you what the eventual reporting needs to support.

If you wait for the perfect artifact, the meeting never happens.

At the end of the first month, return to your sponsor with a clear picture of what has changed and what remains unresolved.

Start with ownership. Show where coverage began, where it is now, and which workloads drove the improvement.

Then highlight the gaps. Specifically, the areas where no team owns the spend and where resolution requires executive-level decisions.

Finally, outline the next 30 days of work, including the specific people and decisions you will need support for.

This conversation is the first real test of sponsorship.

If your sponsor is willing to back you on ownership and accountability, you have the foundation of a program. If not, what you have is an initiative without authority.

It is better to learn that on day 30 than on day 90.