Demo: replace the web shop, retain the ERP — the case
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
build the case for one concrete pair of decisions.
Draft outline details
Step by step
- State the outcomes: faster promotion changes, mobile support, stable finance.
- Describe three options for the web shop: keep, refactor, replace with SaaS or suite; "retain" for the ERP with an API wrapper.
- Estimate costs and benefits for five years with ranges; include dual running and migration.
- Show the coexistence plan: strangler routing, product and order data sync, ERP stays finance master.
- Planned mistake: the benefit line counts all future online growth as caused by the new shop. Fix: attribute only the growth tied to specific capabilities and show a conservative range.
- Present risks, triggers to revisit, and the recommendation.
Check your understanding
Why retain the ERP in this case?
Show answer
Low change demand, finance dependence, and high replacement risk relative to benefit.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.