Your website or app is aging, buggy, or hard to change — so should you keep patching it, or rebuild from scratch? Rebuilding feels tempting, but it's expensive and risky. Here's a practical framework to decide.
Signs you can maintain (and shouldn't rebuild)
- The core works and users are happy — it just needs fixes and new features.
- It's built on a solid, current framework (e.g. a recent Laravel or WordPress version).
- Problems are specific (a slow page, a broken flow), not systemic.
- You need to move fast and budget is limited.
In these cases, targeted maintenance — bug fixes, refactoring the worst parts, adding features — gives you far more value per rupee than starting over.
Signs a rebuild is worth it
- It's on outdated, unsupported technology that's a security and hiring risk.
- Every small change is slow, painful or breaks something else.
- You can't add the features your business now needs.
- Performance or security problems are baked into the architecture.
The middle path most people miss
It's rarely all-or-nothing. Often the best move is a staged modernisation: stabilise and secure what you have, upgrade the framework, then rebuild the worst parts piece by piece — so you keep running (and earning) the whole time, instead of a risky big-bang rewrite.
Don't rebuild just because a new developer says so
"Let's rebuild it" is sometimes the honest answer — and sometimes just easier for the developer than understanding your existing code. A good engineer will read your codebase first and give you an honest, cost-aware recommendation.
That's exactly what I do under Existing Project Support — I take over, stabilise, secure and improve apps I didn't build. Send me your project details and I'll tell you honestly whether to maintain or rebuild.