The 'We've Always Done It This Way' Tax

Every small business has a workflow that someone, somewhere, set up because it made sense at the time. Maybe the office manager who quit in 2019 built it. Maybe the accountant suggested it before the business had software. Maybe the owner did it that way the first week and nobody ever looked at it again.

The process is still there. It's still consuming time. And nobody can tell you why it works the way it does, only that it always has.

The Quiet Cost of Inertia

Most owners don't track what their habits are costing them, which is exactly why those habits survive. The cost shows up in places that don't have a line item: an hour of someone's Tuesday morning, a duplicate spreadsheet two people maintain because nobody trusts the other one's copy, a paper form that gets typed into the system by hand because that's how the previous bookkeeper liked it.

A Pegasystems study found employees lose nearly seven hours every week to complicated processes and fragmented tools. For a small business with three back-office staff, that's roughly a full extra paycheck a week that goes nowhere.

The cost of inertia isn't dramatic, which is why it's dangerous. You don't get a notice in the mail. You just notice you're tired on Friday and the work didn't get any smaller.

Why These Processes Survive

Legacy workflows have a kind of gravity. They look load-bearing even when they aren't. A few reasons they tend to stick around long past their usefulness:

• They were never written down. Nobody knows the whole flow. Each person knows their part, which makes the whole thing untouchable because changing any one piece feels risky.
• They're tied to a person, not a job. "Linda does the invoices a certain way" is not a process, it's tribal knowledge. When Linda's out, the process limps.
• They produce something the owner trusts. The report looks right. The numbers reconcile. Nobody wants to break a thing that produces a correct answer, even if it takes four hours to produce.
• Changing them feels like criticism. The person running the process has been running it for years. Suggesting it's outdated can feel personal.

A Freshworks survey found 20% of software budgets are wasted on unnecessary business complexity. One in five dollars going to systems and processes that nobody has audited recently.

What an Outdated Process Actually Looks Like

You can usually spot one without a consultant. The signs are practical and easy to check:

• Two people maintain the same list in two different places.
• A spreadsheet gets exported, edited, then imported into another system.
• A form gets printed, filled out by hand, then typed back into the computer.
• The same data gets entered three times for one customer interaction.
• The process has a step that exists because "the system won't let us skip it," and nobody has tested that claim in two years.
• A report gets emailed every Monday morning and only one person opens it.

If any of those sound familiar, the process is probably older than it should be. None of them are scandals. All of them are taxes.

How to Decide What to Keep

The "we've always done it this way" tax is real, but the answer isn't to burn every old workflow to the ground. Some legacy processes are load-bearing for a reason. The question is which ones are paying their rent.

Three useful tests when looking at an old process:

• The new-hire test. If a new employee asked why this step exists, could anyone give them a real answer? If the answer is "that's just how we do it," the step is suspicious.
• The customer test. Does this process produce anything the customer notices? If it's purely internal and only one person sees the output, it's a strong candidate for change.
• The cost test. Multiply the time it takes by the hourly cost of the people doing it, times 52 weeks. Write that number down. If it surprises you, the process needs a second look.

Unit4's 2025 research found 84% of finance and IT leaders said their teams spend too much time on manual processes, and 92% believed time and money would be saved if those processes were rebuilt. The honest read of that data is that almost every business knows it has a tax problem. Fixing it is a separate decision.

What to Do About It

Replacing a legacy workflow doesn't have to be a project with a binder. The most useful first move is usually small, specific, and aimed at one process you've been quietly resenting.

Three small actions that tend to pay back fast:

1. Pick one workflow that hasn't been reviewed in three years. Just one. Write down every step from input to output.
2. Calculate the annual cost of running it. Time per cycle, times frequency, times the wage of the person doing it. The number is usually higher than expected.
3. Decide if you'd build it that way today. If the answer is no, it's a candidate for change. If the answer is yes, it's a process worth defending.

Old workflows aren't bad because they're old. They're bad because they keep collecting cost long after anyone remembers why they exist. The fastest revenue leak to fix is usually the one you've stopped noticing. CoreAgentic's free AI Readiness Assessment will help you spot which of your habits is quietly taxing you the most, and which workflows would pay back the fastest if you replaced them.