Software development
Digitization in the middle class: How to measure your success
Digitization is no longer a trend for medium-sized enterprises, but a need to remain competitive. But how to measure the success of Digitalisie...
Technical Debt Costs: Refactoring and Modernization
What reducing technical debt costs: refactoring, modernization and sustainable prioritization.
In brief
Score from 0 to 100
The tech-debt score runs from 0 to 100. Below 35 the risk is low, from 35 to below 65 it is medium, and from 65 it is high.
Read the tech-debt score
Tech debt calculator
How high is your technical debt?
Analyze the state of your software
Step 1 of 425%
How old is the software?
How the tech-debt score is built
The calculation follows six visible stages. All figures remain planning values until scope and assumptions have been reviewed.
1. Capture inputs
The calculator records the visible project, volume, complexity and operating parameters selected on this page.
2. Add fixed components
One-off investment and recurring operating components are added separately.
3. Apply multipliers
Volumes, time values and rates are multiplied where the model converts effort or incidents into monetary effects.
4. Create the range
The calculator applies its documented lower and upper uncertainty factors to the base result; ROI views keep investment and savings visible separately.
5. Round and calibrate
Monetary result fields are rounded to the nearest whole euro. Public project-cost components are calibrated with the centrally maintained display factor.
6. Classify the result
The result is shown as non-binding guidance. A binding quote requires scope, data, integrations, risks and acceptance criteria to be reviewed.
Included
- Inputs shown in the calculator
- Calculator-specific base values and factors
- Displayed one-off and recurring result components
Not included
- Requirements not selected in the calculator
- Unknown data migration and third-party licence costs
- Taxes, legal advice and a binding delivery commitment
Efficiency or discount factor: A central display factor of 0.7 is applied to public project-cost components to keep all calculators aligned with the currently reviewed pricing basis. It is not a customer-specific discount; customer-entered wages, revenues and existing operating costs are not reduced.
Why this is not a binding quote: The calculator cannot verify complete requirements, third-party dependencies, data quality, legal constraints or acceptance criteria.
Technical responsibility and review
- Technical owner
- Björn Groenewold
- Role
- Managing Director and software engineer
- Expertise
- Software development and software estimation
- First published
- Last technical review
- Price basis
- September 2026
Sample calculations & scenarios
Concrete project profiles with assumptions and indicative budgets—useful for internal alignment alongside the calculator.
Technical debt: typical effort and costs
Paying down technical debt is often billed as part of ongoing development or as dedicated refactoring phases. Costs depend on codebase size, test coverage and target quality.
The score runs from 0 to 100: below 35 the risk is low, from 35 to below 65 it is medium, and from 65 it is high. The catalogue span EUR 1,470 – 699,930 excl. VAT is the investment frame for the whole effort, not a monthly rate and not a yearly saving.
We help you prioritize which debt hurts most and plan incremental improvement so that new features remain possible while debt is reduced. The path is the same as legacy modernization, and the annual pain figure sits in the software pain calculator.
What drives technical debt costs?
Technical debt accumulates when code is written for speed rather than maintainability, when tests are missing or when architecture no longer fits how the system is used. Paying it down requires an honest assessment: which parts slow down change, cause bugs or block scaling? We run a structured audit, produce a prioritised list and estimate effort per area. Refactoring can then be scheduled in sprints alongside new features so you do not have to freeze development. In many cases a mix of quick wins and deeper modernization works best – we help you choose.
Ongoing costs depend on how much debt you tackle and whether you combine it with new functionality. We recommend starting with the most painful areas and establishing better practices (tests, code reviews, documentation) so new code does not add more debt. Use the calculator above to score your technical debt. Terms for the idea itself are in the glossary entry on technical debt. For a tailored prioritization workshop, get in touch. We outline options without turning the catalogue span into a monthly rate.
Request a quoteFAQ
Technical Debt Costs
Assessment & Refactoring
How much does it cost to reduce technical debt?
The tech-debt score runs from 0 to 100.
Below 35 the risk is low, from 35 to below 65 it is medium, and from 65 it is high. An audit ranks the debt; the catalogue span on this page is the investment frame for the clean-up, not a yearly saving.
The work then proceeds module by module or sprint by sprint.
What drives technical debt costs?
The effort scales with how large the codebase is, how well it is tested and the quality level you aim for.
Debt builds up when code favours speed over maintainability or when the architecture no longer matches the product. A structured audit turns that into a prioritised list with effort per area.
Do we have to freeze development while paying down debt?
No.
Refactoring can be scheduled in sprints alongside new features. A mix of quick wins and deeper modernisation often works best – we help you choose.
How do we prevent new technical debt?
We recommend establishing better practices (tests, code reviews, documentation) so new code does not add more debt.
We can integrate this into your next project or maintenance contract.
Inputs in the tech-debt score
How to read the tech-debt score
Four checks: age and symptoms, the 35 and 65 thresholds, yearly excess cost, and the investment frame of a renewal.
1. Build a score from 0 to 100
Age, change effort, and dependencies produce a number, not a euro amount.
2. Do not move the thresholds
Below 35 is low, from 35 is medium, from 65 is high. There is no second scale in between.
3. Show excess cost separately
Yearly excess cost sits beside the score. It does not replace it.
4. Use the catalog price only as a frame
Audit, refactoring, and architecture do not share one figure. The catalog price is the investment frame.
Typical pricing models (overview)
| Model | When it fits | Budget & flexibility | Typical risks |
|---|---|---|---|
| Fixed price (fixed scope) | Clearly defined scope, stable requirements, repeatable delivery. | Predictable total cost; little room for change without a change order. | Scope creep leads to change orders or quality trade-offs. |
| Time & Material | Discovery, legacy, evolving requirements, or close collaboration. | Maximum flexibility; budget transparent via hourly or daily rates. | Without prioritisation, effort can grow—backlog and reviews matter. |
| Retainer / maintenance package | Ongoing operations, updates, small features, and support. | Agreed capacity per month; predictable follow-on cost. | Large changes may still need a separate estimate. |
| Hybrid (milestone + T&M) | MVP or phased releases with clear go-lives, then iterate. | Core delivery fixed price; extensions on a time-and-materials basis. | Define contractually what is in scope vs. extra work. |
Calculators on this page provide indicative ranges; we choose the right model with you based on risk, scope, and planning horizon.
What determines the costs, and what comes next?
The ranges shown are indicative. For a binding quote we discuss scope, priorities and funding options in a free intro call. Many digitalization projects qualify for grants – try our funding calculator.
Browse all cost calculators, explore services and typical solutions. Questions about Tech-Debt-Score? Contact us.
After using the Tech-Debt-Score calculator, validate assumptions in a short intro call.
What we align in the call
- Scope, risks, and funding options
- Milestones and documented exclusions
- Transparent quote without hidden line items
Costs for Tech-Debt-Score in context
- Scope, risk, and quality expectations drive the range
- Include operations, maintenance, and grants
- Dedicated contacts and short paths from East Frisia
Browse all cost calculators in the costs overview.