As of: 19 June 2026 · Reading time: 4 min
Key takeaways
- Rescue or redesign software?
- Our data-based decision-making aid with cost-benefit analysis helps you with the right choice.
Rescue or redesign software? Our data-based decision-making aid with cost-benefit analysis helps you with the right choice.
“Proactive maintenance costs a fraction of what an unplanned outage causes.”
– Björn Groenewold, Managing Director, Groenewold IT Solutions
- *Your software project is in a deep crisis. ** Dates are torn, costs explode and quality is in the basement. You are facing a fundamental decision with far-reaching consequences: try to save the sinking ship or give it up and start with a complete new development? This decision should not be taken out of the abdomen. It requires a cool, data-based analysis.
The deceptive entanglement of the new beginning
Short: Executive answer: Your software project is in a deep crisis.
Executive answer: Your software project is in a deep crisis.
Decision-makers exploring Rescue or redesign software? Decision aid can use Cost Calculator: AI Development, Discover solutions, Software Maintenance sowie Cost Calculator: Software Maintenance as structured entry points.
The idea of a new development is often tempting. A green meadow where you can work with the latest technologies and without the old loads of the failed project.
But this path is paved with considerable risks, which are often underestimated.
[Software Recovery](/services/software recovery)
Low initial investment
Faster time-to-market
Consistent knowledge is preserved
Risk often more calculable
*40-60% cheaper *
New development
High initial investment
Longer development time
Risk of loss of knowledge
danger of repeating identical errors
chance of modern technology
The underestimated power of salvation
Short: A professional software review aims to maximize the investments already made.
A professional software review aims to maximize the investments already made. Industry analyses show that a rescue ** can save up to 40-60% of the cost of a new development**.
The focus is to consider the existing code as a valuable asset that can be saved and improved.
The rescue score: A quantitative decision-making aid
Short: To make a more objective decision, you can use the following checklist.
To make a more objective decision, you can use the following checklist. Rate each factor on a scale of 1 (does not apply) to 5 (does fully apply).
Review checklist
Short: FactorFr. Code qualityIs it stable, well written parts in the code? ArchitectureIs the basic architecture still viable? Domain knowledgeDoes complex business logic in the code?
FactorFr. Code qualityIs it stable, well written parts in the code? ArchitectureIs the basic architecture still viable? Domain knowledgeDoes complex business logic in the code?
Team knowledgeIs it team members with deep understanding? InvestitionWurde is already investing a lot of budget? Time-to-MarketIs a fast launch critical?
DataDoes it contain critical data whose migration is complex? **Is the software deeply integrated into other systems?
Score 30-40: A rescue is most likely the better option. Score 20-29: The decision is not clear. A detailed analysis is necessary.
Score 8-19: A new development could be the more sensible alternative.
Detailed cost comparison
Short: | Aspect | Software Recovery | New Development | |---------- ** Costen | Approx.
| Aspect | Software Recovery | New Development | |---------- ** Costen | Approx.
40-60% of new | twind100% (base) | ** Timeframe | 3-6 months to stabilise | ung12-24 months to launch | | Risiko | Medium (known problems) | High (unknown problems) | ** Knowledge maintenance | High Niedrig | to medium |
Conclusion: Courage for analysis instead of early demolition
The decision between rescue and
On the numbers: Survey and market figures without an inline footnote follow common public reports (e.g. Bitkom) and official statistics (Destatis). Practical examples: Groenewold IT internal data, 2026.
References and further reading
Short: The following independent references complement the topics in this article:
The following independent references complement the topics in this article:
- Bitkom – German digital industry association
- German Federal Office for Information Security (BSI)
- European Commission – Digital strategy
- MDN Web Docs (Mozilla)
- W3C – World Wide Web Consortium
"DevOps is less about tools and more about shared ownership of quality and release discipline."
— Björn Groenewold, Managing Director, Groenewold IT Solutions
Frequently Asked Questions (FAQ)
What is this article about: “Rescue or redesign software? Decision aid”?
Here we cover Rescue or redesign software? Decision aid — focused on architecture, process, and business outcomes. In short: Rescue or redesign software?
Our data-based decision-making aid with cost-benefit analysis helps you with the right choice.
Who benefits most from the content described here?
Typical readers are business and IT leaders in Software maintenance who want to secure quality, security, and maintainability over the long term.
How does this topic fit into an IT or digital strategy?
In a digital strategy, prioritize stable core processes first, then extensions. See also professional software development and consulting. For multi-system landscapes, IT consulting and architecture helps align vendors and internal teams.
What are sensible next steps if we need support?
If you need support with design, delivery, or modernization: schedule an appointment or outline your project via contact.
About the author

Managing Director of Groenewold IT Solutions GmbH and Hyperspace GmbH
Since 2009 Björn Groenewold has been developing software solutions for the mid-market. He is Managing Director of Groenewold IT Solutions GmbH (founded 2012) and Hyperspace GmbH. As founder of Groenewold IT Solutions he has successfully supported more than 250 projects – from legacy modernisation to AI integration.
Blog recommendations
Related articles
These posts might also interest you.

Code review: Detecting quality problems early
Learn how code reviews reveal quality problems early. Best practices, checklists and tools for effective code reviews.

Software Rescue: How to bring back failed IT projects
Not every software project runs according to plan. Budget surpasses, missed deadlines or technical dead endes can meet any company. The good news: Most projects can still be saved. This guide will…

Security in software maintenance: How to protect your...
Security is a critical aspect of software maintenance. We will show you the most important safety practices that cannot be missed in any maintenance process.
Free download
Checklist: 10 questions before software development
Key points before you start: budget, timeline, and requirements.
Get the checklist in a consultationRelevant next steps
Related services & solutions
Based on this article's topic, these pages are often the most useful next steps.
Related services
Related solutions
More on Software maintenance and next steps
This article is in the Software maintenance topic. In our blog overview you will find all articles; under category Software maintenance more posts on this subject.
For topics like Software maintenance we offer matching services – from app development and AI integration to legacy modernisation and maintenance. We describe typical use cases under solutions. Our cost calculators give initial estimates. Key terms are in the IT glossary. Books and long-form guides appear on the publications page; deeper articles live under topics.
If you have questions about this article or want a non-binding discussion about your project, you can book a consultation or reach us via contact. We usually respond within one working day.
