Every business has them. The processes that nobody designed on purpose. The workflows that started as a temporary fix three owners ago. The spreadsheets that exist because the last person who set them up has retired, but everyone is too nervous to touch them.
You can usually spot them in conversation. Someone asks, “Why do we do it that way?” and the answer is some version of: “That’s just how we do it.”
That phrase is one of the most expensive things in small business. And it’s expensive in a specific way that almost never shows up on a P&L.
The cost you don’t see on the income statement
Research commissioned by Ricoh and conducted across multiple regions found that employees lose 76 days of productive time per year to inefficient processes. That’s not 76 days of total downtime — that’s 76 days lost specifically to processes that could run faster, smoother, or more reliably but don’t, because nobody has gone back to redesign them.
The same body of research found that 38% of employers still rely on manual administrative processes, and roughly half of workers say better tools would meaningfully improve their productivity.
The point isn’t the specific number. The point is the structure: there’s a measurable chunk of every employee’s year that disappears into work that exists because nobody questioned it. For most small businesses, that chunk is large enough to fundamentally change the unit economics of the company.
Why owners stop seeing it
The hardest part isn’t fixing legacy workflows. It’s seeing them.
There’s a well-documented cognitive bias called status quo bias — humans systematically prefer keeping things as they are, even when change would clearly produce a better outcome. The bias gets stronger the longer the current arrangement has been in place, and stronger again when the current arrangement was set up by someone the team trusts (often: the owner themselves).
This is why the worst-designed process in the business is usually the one with the longest tenure. Time gives it legitimacy. Familiarity makes it invisible. New employees show up, see that “this is how it’s done,” and absorb it as the default. Three years later, they’re training the next hire on the same broken workflow, with the same matter-of-factness as if they’d designed it themselves.
The owner usually doesn’t see it because the owner is the most adapted person in the system. You’ve built workarounds for every quirk. You know which spreadsheet column is actually the source of truth and which is the historical one nobody deletes. You know that the report works as long as you copy-paste the data in that specific order. The process works for you — because you’ve spent years learning to compensate for its problems.
The compounding cost
The reason “the way we’ve always done it” is so expensive is that the cost compounds in three directions at once.
It compounds across time. A workflow that wastes 30 minutes per week per person, over a five-person team, over five years, is 650 hours. Roughly four months of full-time work — gone, paid for, with nothing to show.
It compounds across hiring. Every new employee has to learn the legacy workflow. They lose ramp-up time learning it, lose retention because the bad workflow is what they complain about, and eventually carry the bad workflow into their training of the next hire. The dysfunction self-propagates.
It compounds across opportunity. This is the most expensive layer. While your team is doing things the way they’ve always been done, your competitors are doing them faster. The customers waiting on a quote, the leads not getting followed up, the reports not being read because they take a week to produce — those are missed revenue, not just wasted time.
The processes most likely to be hiding it
A short checklist of the workflows that most often turn out to be legacy drag in service businesses:
- The handoff from sales to operations — the moment a sale becomes a job is almost always done with some combination of an email, a verbal conversation, and someone manually entering the same data into 2–3 systems.
- The weekly or monthly report — the data exists in real time, but nobody trusts the dashboard, so someone manually rebuilds the report from source systems every cycle.
- The end-of-month close — accounting, payroll, inventory adjustments, and reconciliation done in a sequence that was figured out before half the current team was hired.
- The lead-follow-up dance — a leads spreadsheet, a CRM, an email tool, and a salesperson who’s “going to get to it” all looking at the same lead and none of them taking the next step.
- The pricing/quoting process — a spreadsheet of prices that hasn’t been updated cleanly in years, with hidden formulas only one person understands.
- The onboarding of new clients — paperwork, account creation, intro emails, kickoff meetings, all coordinated by hand because “it’s only a few clients a month.”
None of these are unusual. All of them are usually fixable. None of them get touched until someone finally points at them and says, “wait — why is it like this?”
What it actually takes to see them again
You can’t fix what you can’t see, and as we noted, the people closest to the legacy workflow are the worst-positioned to spot it. A few practical ways to surface the hidden cost:
Ask the newest person. Whoever has been with the company least time still has the outsider’s view. Ask them, plainly: “What’s the one thing we do here that doesn’t make sense?” The answer is your starting point. They’ve usually been biting their tongue about it for months.
Track a single transaction end-to-end. Pick one type of work the business does — a quote, a job, an invoice, a hire — and walk through every step it takes from start to finish, with hands on a stopwatch. You will be uncomfortable with what you find. That discomfort is the data.
Count tools touched. For any given workflow, count how many separate systems someone has to touch to complete it. If the answer is more than three, you almost always have a redesign opportunity.
Run the “if I were starting fresh” exercise. For any process, ask: if I were building this business from zero today, with access to current tools, would I design it this way? If the answer is no — and it usually is — you’ve identified a workflow that’s running on inertia, not design.
Automation is one answer, but not the only one
Custom automation is often the right fix for legacy workflows — especially the ones that touch multiple systems, run frequently, and produce the most invisible drag. The 20-hour rule applies here: any of these legacy processes that consume more than 20 hours a month across the team are usually worth a serious automation conversation.
But “automate it” isn’t always the right answer. Sometimes the right answer is:
- Eliminate the workflow entirely. Some legacy reports get built every week and nobody reads them. The fix isn’t to automate the report — it’s to stop producing it.
- Consolidate the tools. Three systems doing overlapping jobs can sometimes become one system doing a better job, with no automation needed.
- Redesign before you build. Automating a bad process produces a fast bad process. The right move is to first redesign the workflow, then decide what to automate.
The trap to avoid is moving directly from “we’ve always done it this way” to “let’s automate the way we’ve always done it.” That just locks in the legacy decisions with code.
The reframe
The point of this post isn’t that legacy processes are bad. They’re not — most of them were the right answer when they were created. The point is that legacy processes silently stop being the right answer over time, and the cost of not noticing that they’ve stopped being right is enormous.
Every small business has a few legacy processes that have outlived their usefulness. The competitive advantage isn’t in being immune to them — it’s in noticing them earlier and being willing to redesign.
If you can’t remember the last time you questioned how a recurring process in your business actually works, that’s not a sign of stability. It’s a sign of accumulated drag you’ve stopped seeing.
If you’d like help running an outside-eyes audit of the legacy workflows in your business — looking at what they actually cost, and what would change if they ran differently — book a 30-minute call and we’ll walk through it.