Question 1

What does an ERP rescue engagement involve?

Accepted Answer

An ERP rescue engagement starts with an independent diagnostic of the programme: where it genuinely stands, what is recoverable and the three things that must change immediately. That is followed by a governance reset, scope control, integrator accountability and a replanned path to go-live with risks named and owned. The engagement runs through to a controlled go-live and handover. Each phase is owned by a single named executive, not a committee.

Question 2

How quickly can an ERP rescue start?

Accepted Answer

Typically within two weeks of the first conversation. A failing programme cannot afford a long mobilisation and the diagnostic phase is deliberately short. The goal is to have an honest, independent view of the programme in the hands of the board within the first fortnight.

Question 3

How long does an ERP rescue take?

Accepted Answer

The diagnostic phase runs in the first two weeks. Stabilisation and replanning typically take four to eight weeks depending on how far the programme has drifted and the complexity of the integrator relationship. Recovery and delivery to go-live depends on the scope of the remaining programme. A 4 million pound ERP programme was recovered and delivered within four months.

Question 4

What is the difference between an ERP rescue and a standard ERP implementation?

Accepted Answer

A standard ERP implementation starts from a defined scope, a contracted integrator and a plan the business believes in. An ERP rescue starts from a programme that has lost confidence, a scope that has drifted, a budget forecast to overrun and a go-live date nobody can honestly defend. The rescue work is diagnostic, political and commercial as much as it is technical. The integrator relationship has to be reset, governance rebuilt and a realistic, resourced plan agreed with the board before delivery can recommence.

Question 5

Which ERP platforms do you rescue?

Accepted Answer

NetSuite, Microsoft Dynamics 365, SAP S/4HANA, Oracle Fusion Cloud, Epicor (E8, E9 and Kinetics), Sage 200 and Sage SaaS, and Infor. The rescue methodology is the same across platforms: independent diagnostic, governance reset, replanning and hands-on delivery leadership through to a controlled go-live.

Question 6

What does the first 30 days of an ERP rescue look like?

Accepted Answer

The first two weeks are a rapid, independent diagnostic: an honest assessment of where the programme actually is, what is recoverable, what the integrator relationship looks like from the outside and the three things that must change immediately. By week four, a governance reset is underway, scope is being controlled and a replanned path to go-live is being drafted for board sign-off. The board has a written view of the programme and named accountability for recovery by the end of the first month.

Question 7

What does an ERP rescue engagement cost?

Accepted Answer

ERP recovery is complex work and is priced in the complex band: GBP 1,500 to GBP 2,000 per day, equivalent to approximately GBP 6,500 to GBP 8,500 per month at one day per week. The scope, day commitment and total cost are defined in the engagement letter before any work begins. There are no open-ended retainers: each phase is scoped and agreed in writing.

ERP Implementation Rescue & Recovery