Repair
Keep most of the system when its foundations are understandable and focused fixes can control risk.
Solution
Should we fix the existing application or rebuild it?
Keeping an unstable system forever and rebuilding everything by default can both waste time and money. The responsible choice depends on what still works, what the business must preserve, and the cost and risk of changing each part.
Request a Technical AssessmentWhy the decision is difficult
The application contains valuable working behavior but fails unpredictably.
Repeated patches create new problems.
Tests and documentation do not explain business-critical behavior.
Dependencies or frameworks may be old or unsupported.
The data model and integrations are difficult to replace safely.
Nobody can estimate repair work with confidence.
The answer comes from evidence
A reliable build, understandable architecture, dependency health, tests, data design, configuration, deployment, platform age, duplication, and documentation all influence the decision.
A weak layer does not necessarily condemn the entire application. Likewise, visible working screens do not prove the foundations are worth preserving.
Avoid two default decisions
- Do not rebuild everything solely because the code is unfamiliar.
- Do not keep patching solely because a rebuild feels disruptive.
- Do not use a simplistic completion percentage as the decision rule.
Evaluate before choosing scope
- 1
Capture required business behavior and valuable working components.
- 2
Establish whether the application builds and runs repeatably.
- 3
Review architecture, data, dependencies, tests, configuration, and deployment.
- 4
Identify risks that can be isolated from risks spread throughout the system.
- 5
Compare repair, partial replacement, and rebuild paths.
- 6
Choose staged work with clear verification points.
Three legitimate outcomes
Partial replacement
Retain useful components while replacing specific fragile interfaces, data paths, or platform layers.
Rebuild
Replace the system when preserving it creates greater cost or risk than rebuilding the required behavior.
Relevant HerbDev services
Make the repair-or-rebuild decision after understanding the system.
A Technical Assessment creates a practical comparison of what can be retained, what must change, and what should happen next.
Request a Technical Assessment