# ERP Go-Live Delay Cost Calculator > Source: https://netray.co/tools/erp-go-live-delay-cost-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer What-if tool showing the true cost of postponing an ERP go-live: extended project team, legacy licences still running and benefits you do not yet earn. ## Category erp-migration ## Audience - ERP project manager - Steering committee - CFO ## Tool **Kind:** calculator **Currency:** EUR **Inputs:** #### Delay **Key:** delay **Type:** slider **Default:** 3 **Min:** 0 **Max:** 12 **Step:** 0.5 **Unit:** months #### Project team cost per month **Key:** team_cost **Type:** number **Default:** 52000 **Min:** 0 **Step:** 1000 **Unit:** EUR **Help:** Partner consultants plus internal staff at loaded cost. #### Legacy system run cost per month **Key:** legacy **Type:** number **Default:** 9000 **Min:** 0 **Step:** 500 **Unit:** EUR **Help:** Maintenance, hosting and support you only avoid after cutover. #### New ERP subscription already payable per month **Key:** new_sub **Type:** number **Default:** 11000 **Min:** 0 **Step:** 500 **Unit:** EUR **Help:** Many contracts start billing at signature, not at go-live. #### Expected monthly benefit after go-live **Key:** benefit **Type:** number **Default:** 28000 **Min:** 0 **Step:** 1000 **Unit:** EUR **Help:** Savings or margin gains from your business case. #### Extra risk premium on remaining budget **Key:** risk_pct **Type:** number **Default:** 5 **Min:** 0 **Max:** 40 **Step:** 1 **Unit:** % **Help:** Allowance for re-testing and key user fatigue after a slip. **Outputs:** #### Extra project team cost **Key:** team_total **Expr:** delay * team_cost * (1 + risk_pct / 100) **Format:** currency #### Legacy still running **Key:** legacy_total **Expr:** delay * legacy **Format:** currency #### Subscription paid but unused **Key:** sub_total **Expr:** delay * new_sub **Format:** currency #### Deferred benefits **Key:** benefit_total **Expr:** delay * benefit **Format:** currency #### Total cost of the delay **Key:** total **Expr:** team_total + legacy_total + sub_total + benefit_total **Format:** currency **Primary:** true #### Cost per week of delay **Key:** per_week **Expr:** if(gt(delay,0), total / (delay * 4.345), (team_cost * (1 + risk_pct / 100) + legacy + new_sub + benefit) / 4.345) **Format:** currency **Primary:** true **Chart:** #### Cost of delay vs months postponed **Type:** line **X:** delay **From:** 0 **To:** 12 **Steps:** 24 **Series:** - total **Disclaimer:** Deferred benefits are opportunity cost, not cash out. Show them separately to the steering committee if finance does not accept them as cost. ## Content **Intro:** Go-live dates slip for good reasons: incomplete data, weak testing, a key user leaving. But the steering committee needs a number. This calculator converts a proposed postponement into euros per week so the trade-off between risk and delay is explicit. **Sections:** #### How to use it **Body:** Enter the month-by-month burn rate of the project team, the legacy costs you cannot stop until cutover and any new subscription already running. Add the monthly benefit from your business case. Then drag the slider to the delay under discussion, typically one, two or three months. Export the result to PDF for the steering committee pack. **Bullets:** - Include internal staff in the team cost - Check when the new subscription actually starts billing - Use a conservative benefit, not the sales case - Test slips of 1, 3 and 6 months #### The cost components **Body:** Total cost equals extended team cost with a risk premium, legacy run cost, new subscription paid but not used, and the benefits you push out. The first three are real cash. The fourth is opportunity cost and depends on the quality of the business case. The per-week figure is handy when debating a cutover weekend versus waiting for the next period close. #### Using it in decisions **Body:** Compare the cost of delay with the cost of going live with known defects. If a two-month slip costs about the same as a one-month support surge after launch, other factors such as quarter-end timing, audit cycles or the summer shutdown should decide. In many European plants the August and December shutdowns narrow the cutover window, so a short slip can become a long one. #### Common mistakes **Body:** Teams leave out the subscription already running and the legacy support renewal that falls due during the slip. Another is using the sales-promised benefit. Also remember that a delay rarely stops at the first estimate, so view the 6 month point on the chart as a stress test, not a worst case. **Cta:** If the delay comes from data or interface issues, Netray can help build automated checks on migrated data so retests are faster. **Faq:** #### Should deferred benefits count as cost? **Answer:** Show them as a separate line. Finance may treat them as opportunity cost, but they explain why waiting is not free. If your case has weak benefit estimates, lower the figure or set it to zero. #### What risk premium is sensible? **Answer:** Five to fifteen percent is a common planning allowance for retesting and loss of momentum. Set it higher if the delay involves key staff turnover. #### How do I handle a phased go-live? **Answer:** Run the calculator for the wave that slips and enter only that wave's team cost, legacy modules and benefits. Repeat for each wave. #### Does it include penalty clauses? **Answer:** No. Add penalties or contract change fees to the result manually if your agreement contains them. ## Search terms erp go live delay cost, cost of delaying erp implementation, erp project overrun cost, erp postponement business case, erp go live date decision, erp delay calculator --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json