Calculator
How much time do you get back?
Move the sliders. The calculation deducts review time honestly, because a person reviews everything.
1 h
1 h
1 h
1 h
1 h
1 h
How we calculate
The formula, with no hidden tricks.
- Postponed work per week is the number of developers multiplied by the hours each of them loses per week to maintenance, small bugs, testing and documentation.
- Work taken over is the share of that an agent can carry out. How much that is depends on your code and your tasks. By default we assume half.
- Review time is the time your team needs to review the proposals. We deduct it.
- Per year we assume 46 working weeks (52 weeks minus 20 days of holiday and 10 public holidays) and a working day of 7.6 hours (38 hours per week). [24, 23, 22]
- The cost of an hour is set to €65 by default: our own calculation based on Belgian salary data, employer contributions and benefits. [26, 25, 27]
The default of 8 hours of postponed work is deliberately cautious. Developers themselves estimate that they spend an average of 17.3 hours per week on maintenance. [5] All assumptions and sources are on our page with calculation assumptions.
This is an estimate, not a promise. Your real figures depend on your code, your team and the kind of work. In the free scan we run the calculation with your data.
Want the real figures?
In a free online call we run the calculation with your code, your team and your task list.