And why the mismatch is quietly costing you more every quarter
By Steele Consulting
Your business is twice the size it was three years ago. Different customers. Different team shape. Different workflow. Different problems.
Your core systems — the ones that run the business — are mostly the same.
You haven’t noticed, exactly. The systems work. They’ve always worked. What you’ve noticed is a quieter thing: that work has gotten harder for reasons you can’t quite name. Reports take longer. Decisions require three tools instead of one. New hires take longer to onboard than they used to, and nobody can quite say why.
In our 24 years at Steele Consulting building custom software, we’ve watched this exact pattern crystallize in dozens of growing businesses. The software didn’t get worse. The company changed. And the mismatch between the two is quietly becoming the brake on where you’re trying to go.
This post is about how to recognize that mismatch — and what to do about it when you see it.
Why this happens
Software and companies evolve on different timescales.
A system you built or bought when the company was 30 people, one product, one geography was designed around assumptions that fit the business at the time: specific volume, specific team structure, specific workflow, specific customer type. Those assumptions got baked in — not just into the code, but into the data model, the integrations, the processes wrapped around it, the way people operate it.
Then the company kept growing. More people. New products. New markets. Changed strategy. Changed team composition. The assumptions underneath the software stopped matching the reality on top of it. Nobody noticed the mismatch happen because it happened gradually — a workaround here, a bolted-on spreadsheet there, a report that someone just regenerates by hand each month.
By the time the mismatch is big enough to feel like a problem, it has usually been expensive for a year or two.
The 5 signs your software is built for your old company
Five symptoms show up reliably. Any one of them means the question is worth asking. Three or more means the answer is already yes.
1. Your workarounds have workarounds
The system doesn’t handle your new reality cleanly, so people built workarounds. The workarounds didn’t handle the next evolution of your reality cleanly, so people built workarounds for the workarounds. By now, the manual processes layered on top of the system are a system of their own — and the one in the box is really just a data store with some reports on top.
2. Different departments disagree about what the system is for
Sales uses it as a pipeline tracker. Ops uses it as an inventory system. Finance uses it as a reporting source. All three groups are using it for things it wasn’t originally designed for, and all three are frustrated for different reasons. They’re not wrong. The system is being asked to be three different things to three different audiences — and it was built to be one.
3. New hires can’t make sense of it
Documentation is sparse because the system reflects a company that existed before the current team got here. The weird naming conventions, the unused fields, the modules that are only used by one person — all of these are historical artifacts the new hire has to decode before they can operate the system. Onboarding time keeps creeping up and nobody can quite explain why.
4. The system assumes constraints that no longer apply
The system was built for a smaller volume, a single location, one product line, one currency, a specific team shape. Then the business grew out of those constraints. Now the system has quiet assumptions — low row counts, a single tax jurisdiction, one legal entity — that are being quietly violated. Reports look right until you look closely. Edge cases that used to be exceptions are now the norm.
5. The business plan requires things the system can’t do
The most important sign. Growth plans assume capabilities the current software doesn’t support. New products are being delayed because integrating them with the current stack is too hard. The business is being quietly shaped around what the systems can do, not what the strategy needs.
If the system is actively limiting the business’s forward motion, the system isn’t a tool anymore — it’s a constraint.
Why you didn’t notice this happening
Three structural reasons the mismatch stays invisible longer than it should.
The team adapts
Humans are extraordinarily good at building workflows around broken tools. By the time the mismatch is severe, your best people have made it operable through workarounds that have become their jobs. The friction stops looking like friction. It starts looking like “how we do things here.”
No single decision looks like the problem
Every workaround was a small, rational choice. Every manual process was faster to implement than fixing the underlying system. The sum of them is expensive. The individual decisions all looked cheap.
You remember when the system worked
You know this system was fine three years ago, because you were there. That memory makes it hard to see that the system isn’t fine now — because the company isn’t the same company it was.
What to do about it
The question isn’t “is the software broken?” — the software isn’t broken. The question is “does the shape of this software still match the shape of this business?”
If the answer is no, three paths exist, which we covered in detail in Build, Buy, or Bend:
- Rebuild. Keep the system; fit it to the current company. Major refactor, data model updates, process realignment. Right when the underlying system is still the right one, but needs to grow with the business.
- Replace with something new. Buy a better-fit tool, migrate the data, retire the old system. Right when the mismatch is fundamental — the current system was built around assumptions that will keep breaking as the business grows.
- Rebuild as custom. Replace with purpose-built software designed around the business as it actually is now. Right when the workflow is genuinely specific to your business and off-the-shelf alternatives won’t fit either.
Each option has a cost. The one that’s always more expensive than it looks is doing nothing — because the gap keeps widening, and every year of delay makes the eventual change bigger.
When to leave it alone
Not every system that was built for the old company needs updating. The honest version of the question includes a specific “no” case: sometimes the mismatch is small enough that the workarounds are the right answer, at least for now.
Leave the system alone when: the mismatch is bounded (one department, one process, not growing); the workarounds are stable (not expanding, not compounding); the business is unlikely to grow much more in the dimensions that are stressing the system; and the capital that would go to fixing it has a better use elsewhere.
Leave it alone, in other words, when you’ve looked at it honestly and decided the gap isn’t worth closing yet. That’s a real decision. The failure mode isn’t choosing to wait — it’s not making the choice at all.
How this connects to the other decisions you’re making
The “built for the old company” diagnosis sits upstream of several of our frameworks. It’s often what triggers the Build, Buy, or Bend decision — the mismatch is the “why now?” of the conversation. The DRIFT framework quantifies what the mismatch is costing you across five categories. And When a Spreadsheet Becomes a System often starts as a workaround for a system that no longer fits — one specific symptom of the broader pattern this post describes.
Read in sequence: this post diagnoses the shape mismatch; DRIFT quantifies its cost; Build, Buy, or Bend decides what to do about it; and the spreadsheet post names one of the specific places the mismatch tends to show up first.
Book a call
Twenty-four years of building custom software. Both sides of the table on more decisions than we can count. And a track record of telling clients honestly when the answer is us and when it isn’t.
If you’re sitting in the middle of this decision right now, that’s the conversation we’re built for. Book a 30-minute call and we’ll walk through it with your specific situation. No pitch. No pressure. You’ll leave with a clearer picture of what to do — whether you work with us or not.