5 Signs Your Operations Are Leaking Money
Most operational waste doesn’t show up on a P&L. It shows up in how long things take, how often things break, and what happens when a key person is out. The businesses that find it earliest are the ones that know what to look for.
1. Your team is manually moving data between systems
This is the most common one, and it’s often so normalized that nobody mentions it. Someone exports a CSV from one tool, opens a spreadsheet, pastes the data, reformats it, then uploads it somewhere else. Or they re-type information from an email into a CRM. Or they copy totals from one report into another.
Every one of those steps is a place where time gets spent and errors get introduced. The work itself produces nothing — it’s just moving information from one container to another. That’s almost always automatable, and when it is, you typically get both the hours back and a more accurate result.
The tell: ask your team what they do every Monday morning, or at the start of every month. If the answer involves “pulling” or “compiling” anything, you’re looking at a leak.
2. Approvals live in someone’s email inbox
When approvals — for invoices, contracts, hires, purchases, whatever — happen in email threads, you lose two things: visibility and momentum. Nobody can see what’s waiting without asking. Things stall because the right person is traveling or buried. And when something goes wrong, tracing it back through email threads is painful.
The cost isn’t just the hours spent chasing approvals. It’s the downstream delays — payments that go out late, vendors that get frustrated, deals that slow down because internal process is moving slower than the conversation outside.
The fix is usually simple: a lightweight structured workflow where requests have status, owners, and deadlines visible to everyone involved. It doesn’t need to be complex. It just needs to exist outside of someone’s inbox.
3. Reporting is built by hand every cycle
If someone spends two hours every week — or every month — pulling numbers from multiple places, pasting them into a spreadsheet, and formatting a report that looks roughly the same every time, that’s a process that should have been automated the first time it was repeated.
Beyond the time cost, manual reporting has a quality problem. Every step where a human touches the data is a step where a human can make an error. And because the report looks fine to anyone reading it, those errors often go undetected for a long time.
The more decision-critical the report, the more important it is to take the human steps out of building it. Your team’s time is better spent reading the report than constructing it.
4. Your processes depend on one person’s institutional knowledge
Every business has one. The person who knows how to handle the weird edge case. The one who knows which client needs a call before getting an invoice. The one whose two-week vacation creates three weeks of catch-up.
This is an operational risk that usually doesn’t feel urgent until it becomes one. When it does — when that person leaves, gets sick, or just takes a vacation at the wrong time — the cost is suddenly very visible.
The fix isn’t always software. Sometimes it’s documentation. Sometimes it’s a structured checklist. Sometimes it’s a system with guardrails that make the right path obvious. But the pattern to look for is: “only [name] knows how to do this.” Every instance of that phrase is a single point of failure.
5. You’re working around your tools instead of with them
Every tool has workarounds. That’s normal. But when the workarounds become the process — when your team has a standard “step 4 is to export this and fix it in Excel” that everyone just knows — you’re paying for a tool that isn’t actually doing its job.
Sometimes the fix is switching tools. More often, it’s configuring or integrating the one you have so the workaround is no longer necessary. Occasionally it means building something custom because your process genuinely doesn’t fit anything on the market.
The signal isn’t which tools you use. It’s whether your team has to compensate for them. If the compensation has become invisible — just part of how things work — it’s worth making it visible again.
What to do with this list
Go through these one by one and write down the first concrete example that comes to mind for each one. Not every business has all five — but most have at least three, and usually didn’t know what to call them until they saw them written out.
Some of what you find will be fixable without any outside help — a missing checklist, a process that just needs to be written down, a tool that needs to be configured properly. Start there. The things that are left after you’ve done what you can yourself are the things actually worth bringing to someone else.