This Isn't an Excel Problem. It's an EBITDA Leak.
If your COO spends Monday morning manually stitching together five reports from five systems into one spreadsheet, you don't have a tools problem. You have an EBITDA Leak: a hidden, recurring operational cost that never makes it onto a board slide, because nobody calls it that.
An EBITDA Leak is the sum of hours, decisions, and money a company loses because its people have to establish the truth before they can act. In service and operational businesses with 150+ employees, this leak rarely shows up in one place — which is exactly why boards ignore it, even though over a year it can cost more than most strategic initiatives combined.
This article breaks down where this cost actually comes from, why most companies measure it wrong (or not at all), and what concretely changes in the P&L once data stops being a battleground and becomes a foundation.
Why Boards Don't See It (The "It's Just Excel" Myth)
Most Founders and COOs I talk to believe their data problem is a tooling problem — "we'll buy a better system, and it'll be fine." It's a convenient belief, because it shifts responsibility onto IT and a licensing budget.
The less convenient truth: Excel isn't the problem. Excel is the symptom. It's a symptom of the absence of one consistent source of data — what data architecture calls a Single Source of Truth (SSOT).
Single Source of Truth (SSOT) means one automated data source that every department treats as authoritative — no manual re-typing, no "draft versions" floating around in email, no guessing which file is current.
Without an SSOT, every additional system (PMS, ERP, CRM, inventory spreadsheets) becomes another version of the truth. And every extra version of the truth is another hour of your most expensive team's time spent not on decisions, but on verification.
Where This Cost Actually Comes From — Three Mechanisms
This isn't one big problem. It's three smaller ones that compound week after week until they become an organizational habit.
1. Verification instead of decisions. A manager isn't asking "what do we do?" — they're asking "which report do I trust?" Half an hour, sometimes more, just to establish a starting point for a conversation that hasn't even begun yet.
2. Fixing instead of working. Someone overwrote a formula. Someone renamed a column. Nobody knows when the data actually broke, so someone has to roll back several versions and check manually. This is work that creates zero value — it only restores the state that existed before the error.
3. Waiting instead of acting. A strategic decision — on pricing, staffing, expansion — waits, because "the report will be ready tomorrow." In a service business where margin depends on how fast you react to occupancy or turnover, a one-day delay isn't a minor inconvenience. It's an opportunity cost nobody books in the ledger, but one that quietly eats into the bottom line.
Does data chaos actually affect EBITDA, or is it just an operational annoyance? It affects it directly, through two channels: labor cost (hours from highly-paid people spent on administrative tasks instead of strategic ones) and decision cost (delayed or wrong decisions made on outdated data). In companies with 150+ employees, these two channels combined can account for several percentage points of annual operating costs.
What This Actually Costs — Order of Magnitude, Not Guesswork
It's worth being honest here: without an audit of your specific company, nobody can give you an exact number for your organization. But market estimates for operational businesses at the 150+ employee scale paint a fairly consistent picture:
- Management teams operating in a "manual" model typically spend somewhere in the range of ten to twenty hours per week, combined, on assembling, verifying, and correcting reports instead of interpreting them.
- Moving to an automated data layer (centralization + validation + self-service BI) typically translates into an operating cost reduction of a few percentage points in the first year — not because data itself generates savings, but because it stops consuming the time of people who should be doing something else.
- The decision cycle — the time from a board's question to a trustworthy answer — typically shrinks from "once a week" to essentially real-time.
These are estimated ranges, not a guaranteed outcome. But even the low end of these estimates, in a company with dozens of mid- and senior-level managers, shows up in the income statement — not just in team morale.
[LINK: case study on data centralization in a service business]
What Separates Order from Chaos — Not at the Tool Level, at the Decision Level
The difference between a company that "gets by" with Excel and one that has real order in its data isn't the number of licenses purchased. It comes down to three architectural decisions:
- Centralization — all operational data (bookings, sales, logistics, CRM) flows into one secure place instead of living in silos that don't talk to each other.
- Automated validation — the system flags inconsistencies on its own, before a manager builds a board presentation on top of one. That's the difference between "someone will notice eventually" and "the system caught it before it went out the door."
- Self-service BI — dashboards that don't need a translator. Leadership logs in, sees the KPIs, makes the call — without asking an analyst for "just one more cut of the data."
This is exactly the difference between a manager as a spreadsheet gatekeeper and a manager as a strategist. You're paying for the second one. Data chaos gives you the first.
In practice, what does "order in your data" actually require — replacing all your systems? No. Centralization doesn't mean ripping out your PMS, ERP, or CRM — it means adding a layer that automatically collects and organizes data from those systems, instead of forcing people to do it manually every week. It's a change to the information flow layer, not a replacement of the tools your team already relies on.
What This Means for Your Calendar and Your P&L
This is where most Founders and COOs start doing the math — and rightly so. Because the effect of putting your data in order isn't "soft." It has two sides:
The hard side: fewer hours lost to verification and fixing means your fixed cost (management salaries) starts generating more value per hour. That flows directly into operating costs, and indirectly, into margin.
The soft side, which is just as real: decisions made faster and on more reliable data mean less "strategic hesitation" — the state where leadership waits because it doesn't trust the numbers. In service businesses, where the window to react to demand or occupancy shifts can be short, that speed has both a cost of inaction and a reward for acting.
Your best manager shouldn't be the most expensive data analyst in the building.
What to Do Differently — A First Step, Not a Full Project
You don't need to start by replacing your entire infrastructure. You need to start by answering one question: where, specifically, in your organization does managers' time turn into verification instead of decisions?
That question can be answered in a 15-minute conversation — no slides, no commitments, no hard sell. Sometimes the answer is "you're actually in good shape, the problem lies elsewhere." That's valuable information too, and worth hearing before you invest in something you don't need.
If reading this made you think of a specific Monday, a specific report, or a specific manager — that's not a coincidence. It's a pattern that repeats across most operational businesses at this scale.
Book a 15-minute diagnostic — we'll pinpoint together where your company is losing time to searching for the truth instead of growth.