Legacy Systems · the warning signs
// legacy systems
Gradually, then suddenly.
The signs show up in conversations that happen every week: "We can't do that in the current system." "That change will take six weeks." "I'm the only one who knows how this part works."
Here are the signs we see consistently - the ones that say it's time to have the replacement conversation, even if you're not ready to make the decision yet.
// the 8 signs
Small changes require touching many interconnected systems, and estimates seem absurdly high for the scope. It's an architecture problem, not a team-performance one - and it gets worse, not better, without intervention.
Built on technology newer engineers don't know and increasingly don't want to learn. When the one or two people who hold the architecture in their heads leave, you find out how serious the risk really was.
"Ask Marcus how that part works" is a warning sign. Critical knowledge living in individual contributors rather than code or docs is a fragility that's easy to overlook - until it breaks.
Brittle integrations that break when either side changes, manual data exports, and data silos are symptoms of a system past its integration window - you're building expensive bridges or making decisions the system allows, not the ones the business needs.
End-of-life software stops getting security patches; GDPR, SOC 2, and HIPAA need increasingly creative workarounds; auditors ask harder questions. At some point it's a liability, not an inconvenience.
Add up engineering time, the drag on new-feature delivery, manual workarounds, and opportunity cost. When that number approaches what a replacement would cost to build and run, you've hit an inflection point.
A system built for 50 employees may be wrong for 500; one built for a single product line may not support five. When "the system can't support that" becomes a strategic constraint, you've outgrown the design.
Rising unplanned downtime, or maintenance windows that are longer and more frequent, means the system is running at the edge of its reliability envelope - and damaging your credibility every time.
Three or more sound familiar? It's time for the conversation ↓
// the conversation to have
If three or more of these apply, it's worth having the modernize-vs-replace conversation - not as a commitment, but as a planning exercise.
The goal is to understand the actual options, the actual costs, and the actual timeline before you're in a crisis situation where the only choice is the fast one.
ready when you are
Three or more signs sound familiar? Let's map your options, costs, and timeline before it becomes a crisis - assessment first, no commitment.