Xavier Thompson had a rule about numbers he couldn’t explain.
If a number appeared on a report, a statement, or an invoice and nobody in the building could account for it — not partially, not approximately, not with a reasonable guess — that number was not a finance problem. It was a systems problem. And systems problems, in his experience, had a way of being significantly larger than the number that first surfaced them.
He had learned this lesson at a previous company, in a different context, long before he’d ever heard the word ransomware used in reference to his own file server.
He was about to learn it again, this time in the form of a cloud infrastructure invoice that arrived in his inbox on the first Monday of February, flagged by Sandra with a single comment in the subject line:
“Can you explain this?”
He could not.
The Number
Meridian Group’s monthly cloud infrastructure spend had, over the preceding three months, increased from approximately eight thousand dollars to just under twenty-four thousand dollars.
The services were all legitimate. The charges were all real. The platforms generating the invoices were all ones Meridian actually used — or had used at some point, or had intended to use, or had used for a project that was technically still open in someone’s task management system even though the actual work had concluded in September.
That last category, as it turned out, was doing a significant amount of the heavy lifting on the invoice.
Sandra had flagged it during a quarterly spend review. She brought it to Xavier because, in her words, “the number is real but the justification isn’t, and I don’t know enough about cloud infrastructure to tell the difference between a legitimate cost increase and something we should be concerned about.”
Xavier appreciated the honesty. He called Xpert.
The Audit
What the Xpert team found when they mapped Meridian’s cloud environment was, in a different way but with a familiar feeling, another archaeological dig.
In the absence of any centralized governance or visibility over cloud resource provisioning, individual departments at Meridian had been independently making cloud decisions for years — spinning up virtual machines, storage buckets, development environments, and software subscriptions as their needs arose, with IT neither approving nor tracking what was being created.
The audit surfaced the following:
Forgotten development environments. Meridian’s engineering team had spun up three separate cloud development environments over the past eighteen months for various project phases. Two of them had been superseded by subsequent environments and were no longer actively used. They were, however, still running — consuming compute resources around the clock for no operational purpose. Combined, they accounted for roughly four thousand dollars per month in charges that were generating exactly zero business value.
Duplicate tools across departments. Four separate departments had independently procured cloud-based project management tools — different platforms, different pricing tiers, different contracts. None of them were aware the others existed. Meridian was paying for four solutions to the same problem, with employees split across platforms that didn’t communicate with each other, creating exactly the kind of fragmentation that made collaboration harder rather than easier.
Abandoned storage. Three storage buckets in Meridian’s cloud environment contained a combined total of several terabytes of data — backups, project archives, exported reports — that had been created, uploaded, and never revisited. Some of it dated back four years. None of it was being used. All of it was being charged for.
Over-provisioned resources. Several cloud virtual machines had been sized for peak workloads during an infrastructure migration eighteen months earlier and never scaled down after the migration was complete. They were running at a fraction of their capacity, paying for compute power that was sitting idle the majority of every day.
Unlicensed seat accumulation. Across Meridian’s SaaS platforms — the cloud-hosted software tools used by the business — a pattern had emerged that Xpert had seen in post-ransomware vendor access work: licenses accumulating for employees who had left, roles that had changed, and projects that had concluded. Nobody was removing seats when people or projects departed. The billing continued regardless.
The shadow IT cloud dimension. Three department heads, when interviewed as part of the audit, mentioned tools or services they were using that did not appear in any IT-managed inventory. Two of them were surprised to learn that IT wasn’t already aware of these services. One of them was surprised to learn that IT had an inventory at all.
Xavier reviewed the full audit report on a Thursday afternoon, methodically, from beginning to end.
When he finished, he looked up at the Xpert team representative sitting across from him and asked the question that had been forming since page two:
“Does every company look like this?”
The answer was honest: most growing companies, yes. The specifics vary. The pattern doesn’t.
What It Cost — And What It Was Supposed to Cost
The financial picture, once Xpert had mapped it fully, broke down into three categories.
Recoverable waste: Cloud resources that could be immediately decommissioned or right-sized without any operational impact. Forgotten development environments, abandoned storage, over-provisioned machines, duplicate tool subscriptions that could be consolidated to a single platform. This category represented approximately eleven thousand dollars per month in spend that was generating no business value and could be eliminated without a single employee noticing a meaningful change in their workday.
Optimizable spend: Resources that were legitimately needed but improperly configured — over-sized for their workload, on the wrong pricing tier, or running on schedules that didn’t align with actual usage patterns. With proper configuration, this category could be reduced by an estimated forty percent without impacting performance.
Legitimate growth spend: A portion of the increase was, in fact, entirely appropriate — reflecting genuine growth in Meridian’s operations and the legitimate expansion of cloud usage as the business scaled. This was the part Sandra had expected. It was also the smallest of the three categories.
The math was uncomfortable in its simplicity: of the sixteen-thousand-dollar monthly increase that had triggered Sandra’s flag, approximately twelve thousand dollars per month was either wasteful or avoidable. Annualized, Meridian had been on a path to spend over a hundred and forty thousand dollars in cloud resources that ranged from unnecessary to actively counterproductive.
Sandra’s expression when Xavier shared the annualized figure suggested she had several thoughts about it, none of which she chose to express in that particular meeting.
How Xpert Fixed It
The remediation operated on two levels simultaneously — immediate cleanup and structural governance to prevent the same accumulation from happening again.
Immediate decommissioning. The forgotten development environments were shut down. The abandoned storage was reviewed, archived where appropriate, and eliminated where not. The over-provisioned virtual machines were right-sized to match their actual workloads. Combined, these actions reduced the monthly cloud bill by over eight thousand dollars within the first two weeks.
Tool consolidation. The four duplicate project management platforms were consolidated to a single, company-wide solution under IT management. The transition was handled with minimal disruption — Xpert mapped the existing workflows in each platform and built a migration plan that preserved the data and habits people had developed without requiring them to start from scratch.
Cloud spend governance. Going forward, any new cloud resource provisioning above a defined threshold required a documented request through IT, with a named business owner, a stated purpose, and a defined lifecycle — including a review date at which the resource would be evaluated for continued need. No more resources spinning up invisibly and running indefinitely because nobody was watching.
A monthly cloud spend report. Xpert implemented automated cost monitoring across Meridian’s cloud environment, with a monthly report delivered to Xavier and Sandra that broke down spend by department, resource, and trend. Anomalies — unexpected spikes, resources approaching waste thresholds — were flagged automatically before they accumulated into an invoice that required a “can you explain this?” email.
SaaS license management. The seat accumulation issue was addressed as an extension of the offboarding workflow Xpert had already implemented after the HR incident — when an employee departed or changed roles, license review was now a standard step in the process. Seats were reclaimed. Billing adjusted. The invisible accumulation had a circuit breaker.
The following month’s cloud invoice came in just under ten thousand dollars.
Sandra sent Xavier a one-line email when it arrived.
“This is what it should have looked like all along.”
The Broader Pattern
Xavier had a conversation with the Xpert team after the cloud audit that he found himself returning to in the weeks that followed.
He’d asked them — genuinely curious, not rhetorically — why this kind of thing was so common. Why did growing companies end up with cloud environments that looked like Meridian’s? These weren’t careless organizations. The people making the decisions were competent, motivated professionals solving real problems.
The answer, as Xpert framed it, was structural rather than personal. Cloud infrastructure is designed to be frictionless. Spinning up a new resource takes minutes. The cost is distributed across a monthly invoice that nobody scrutinizes until the number is large enough to require explanation. And in a growing company, where everyone is focused on moving fast and solving immediate problems, the governance conversation rarely keeps pace with the provisioning decisions.
It’s not that nobody noticed. It’s that the environment was designed in a way that made not noticing the default.
Changing the default required someone to build visibility into the environment and accountability into the process. That’s not something a busy department head can do on the side. It’s something an IT partner does deliberately, as part of a broader mandate to make technology work for the business rather than against it.
Xpert did it. Sandra got her explanation. Xavier updated his rule about numbers he couldn’t explain.
The new version: if you can’t explain a number, call Xpert before Sandra does.
Coming up in the next installment of The Xavier Chronicles: A disgruntled employee resigns without notice and is out the door before IT knows anything has happened. What they take with them — and how it could have been prevented — becomes the story of why HR and IT need to be speaking the same language.
Meridian Group is a fictional company. Cloud waste and ungoverned SaaS spend are among the fastest-growing and least-visible costs for mid-sized businesses, with industry research consistently showing that organizations waste between 30–35% of their total cloud spend on unused or underutilized resources. Xpert Technologies helps growing companies in Metro Detroit build cloud environments that are properly governed, continuously monitored, and aligned with what the business actually needs.
Not sure what your cloud environment is costing you — or why? Maybe it’s time to chat with an Xpert.
#CloudComputing #ITCostOptimization #SaaSManagement #CloudGovernance #DigitalTransformation #MetroDetroit #XpertTechnologies
