Size sets the starting point
A connected multi-workflow product takes longer to understand and verify than a single-path application.
Resource 08 · Remediation planning
Cost to fix calculator
Turn product size, critical findings, integrations, and release maturity into a transparent remediation range and delivery band.
Your evidence
Estimate the repair envelope.
Planning estimateCount the work before naming a price.
This produces a directional range, not a proposal. Nothing is submitted or stored.
Estimated envelope
Repair range
- Base review and repair hours
- Risk and integration hours
- Migration allowance
- Likely engineering hours
- Low planning range
- Likely planning figure
- High planning range
- Indicative delivery time
The model assumes 30 productive engineering hours per delivery week and adds uncertainty around the calculated work. A code review can materially change the range.
How the model works
Transparent arithmetic, editable assumptions.
The model converts visible complexity into engineering hours, multiplies by your editable blended rate, then applies an uncertainty range of 80–130%.
Risk creates test work
Critical findings, money flows, integrations, and migrations require repair plus evidence that the repair holds.
A range is more honest
Until the repository is reviewed, a precise quote would hide uncertainty rather than remove it.
Choose the next useful step
Replace the estimate with an evidence-based scope.
A senior review identifies what is actually broken, what can remain, and which work belongs in the first milestone.