ERP Consulting · Project Rescue

ERP Consulting for Project Rescue

An ERP project rescue is an independent assessment of a troubled ERP implementation — schedule, budget, scope and acceptance — that gives management a costed basis to continue the project in full, continue it in part or stop it. The review is carried out by consultants with no stake in the original implementation.
THREE OPTIONS, ALL OF THEM PRICED THE ORIGINAL PLAN THE PROJECT DELAYS OVER BUDGET RECOVERY AUDIT Continue in full Costed in the audit Continue in part Costed in the audit Stop the project Costed in the audit

Continue, cut back or stop — the audit prices all three before anyone decides.

The starting point

Successful ERP projects require a high level of commitment right from the start

Most ERP projects that get into difficulty show the same early signs: delays against the original project plan, budgets exceeding what was approved, and the growing sense that the original project goals can hardly be achieved.

At that point the worst move is to keep adding resources without an independent view of where the project actually stands. More people and a later go-live date do not answer the question management is facing, and they raise the cost of every option that follows.

A rescue review sits alongside the work we do in ERP project management and it always ends in numbers: what continuing costs from here, what stopping costs and where the ERP cost exposure actually sits.

Reviewed by

Dr. Harald Dreher

CEO, Founder / ERP / Digital, Dreher Consulting

About the author
Decision summary

Is a rescue review the right step for your project?

A quick read before you spend a meeting on it. If most of this matches your situation, a recovery audit is worth scoping — if it does not, we will say so.

When a rescue fits

The plan has slipped, and the slippage is compounding

  • The project is behind the original plan and the delays are compounding

  • The approved budget is exceeded or forecast to be

  • Confidence inside the team that the original goals will be met is falling

  • The implementation partner is reviewing its own work

What we need from you

The people, the documentation and a few days

  • Access to your stakeholders and project staff for the fact check

  • The project documentation as it stands

  • A few days of commitment from your side

  • Openness to all three outcomes — including a stop

See what you get from the audit

THE QUESTIONS THAT DECIDE IT

What can be done if an ERP project experiences difficulties?

Eight questions decide whether a project continues, continues in part or stops. Each one has to be answered with evidence rather than opinion.

01 Should the project be stopped?
02 Could the project be stopped, or is it part of a larger business initiative?
03 Are there possibilities to save the project as a whole or in parts?
04 What costs will still be incurred if continued?
05 What costs will result from discontinuation?
06 What acceptance does the project retain among participants?
07 What measures must be taken to continue and achieve the original goal?
08 Which project planning promises success?

These are the questions the recovery audit answers — with your stakeholders, not about them.

Why this approach is different

A review with no preferred outcome

A typical rescue attempt
The Dreher approach
Who reviews the project
The implementation partner reviews its own work
An independent consultancy with no stake in the original implementation
First move
Add resources and extend the timeline
An independent fact check with stakeholders and project staff
The stop option
Rarely costed, so never seriously compared
Continue, partial continuation and full stop are all priced
Acceptance
Assumed
User acceptance is assessed as part of the audit
Output
A revised plan from the same assumptions
A decision basis for management, then a roadmap for the chosen path
Our take

Someone has to be able to say stop.

Dreher is not the implementation partner and does not resell software, so the audit has no preferred outcome. We are not defending earlier decisions, and we do not earn more if the project continues. That matters, because the honest answer is sometimes to stop — and that answer only exists in practice if someone has priced it.

Management gets three costed scenarios and a recommendation that follows from them, rather than a revised plan built on the assumptions that produced the problem.

How we work

The recovery audit

An independent fact check with you, your stakeholders and your project staff — in a commitment of a few days.

Stage 01

Independent fact check

Where the project actually stands: progress against plan, budget consumed, scope delivered, and what the people in the project say when someone independent asks.

Output · status picture
Stage 02

Scenario assessment

Three scenarios are worked through and priced: continuing with the complete project scope, partial continuation of project parts and a complete project stop.

Output · three costed scenarios
Stage 03

Decision basis

Management receives a clear recommendation with risk statements — a foundation to decide on recovery or termination, not a plan that assumes continuation.

Output · decision basis
Stage 04

The chosen path

For a continuation: a clear roadmap, milestone-focused project management and user-acceptance measures. For a stop: an orderly wind-down that protects what has been built.

Output · roadmap or wind-down
What do you get from us?

Six deliverables — including the cost of stopping.

Project status assessment

Independent ERP consulting to establish where the project really stands.

Performance evaluation

Progress measured against the implementation plan, not the mood in the steering committee.

Decision basis

Recovery or termination, with the costs of both.

Clear roadmap

For continuation or for an orderly termination.

Risk management statements

What can still go wrong on the chosen path.

User acceptance analysis

Whether the people who must work with the system still stand behind the project.

From our project work

A decision basis, not a revised plan.

What management receives

One decision basis, three costed scenarios

The recovery audit ends in a document your management team can act on. Each scenario is priced before anyone argues for it.

Continue in fullThe remaining cost of reaching the original goal, the risks that stay on the table and the measures the plan now depends on.

Continue in partWhich parts of the project can be saved, what each is worth to the business and what an orderly reduction in scope costs.

StopThe cost of discontinuation, what has been built that is worth keeping and how a wind-down protects it.

Read the ERP project rescue reference
Stalled ERP project · Supply & Production W. Ruhsi — the project was stalled, the investment was secured
For 15 years we have been working with Dreher Consulting on various tasks in the context of process optimisation. We have achieved all our goals

Bernd Kullmann · Managing Director, Deuter

What managing directors ask when an ERP project is in trouble.

Honest answers about what a recovery audit assesses, how long it takes and what happens when the answer is to stop.

Answers by:

Dr. Harald Dreher

Founder · Dreher Consulting

Since 1992 he has reviewed ERP projects in difficulty for Mittelstand companies — independent of the implementation partner, with no software revenue behind the recommendation.

1. What is an ERP project rescue?

An ERP project rescue is an independent assessment of a troubled ERP implementation. Schedule, budget, scope and acceptance are reviewed by consultants with no stake in the original implementation, and three scenarios are priced: continuing with the complete project scope, partial continuation, or a complete stop. The output is a costed decision basis for management, not a revised plan.

2. When should we bring in an independent consultant to a troubled ERP project?

When the project is behind the original plan and the delays are compounding, the approved budget is exceeded or forecast to be, and confidence inside the team that the original goals will be met is falling. The clearest signal is the reflex to add resources without an independent view of where the project actually stands.

3. How long does a recovery audit take?

A few days of fact-finding with your stakeholders and project staff. The review establishes progress against the implementation plan, budget consumed and scope delivered, then prices the three scenarios. The commitment is deliberately short, because management needs a decision basis before more money follows the original assumptions.

4. Can a failing ERP project be saved in parts?

Yes. Partial continuation is one of the three scenarios the audit prices. Some project parts carry enough value and enough acceptance to be worth finishing, while others cost more to complete than they return. Naming which is which, and costing both, is the substance of the scenario assessment.

5. What does the recovery audit actually assess?
Progress against the implementation plan, budget consumed, scope delivered, and the acceptance the project retains among the people who must work with the system. The measures required to continue and reach the original goal are assessed alongside the costs of discontinuation, so all three outcomes can be compared on the same basis.
6. Does a rescue always mean continuing the project?
No. A complete stop is one of the three priced scenarios, and it is sometimes the honest answer. Because Dreher is not the implementation partner and does not resell software, the audit has no preferred outcome — the stop scenario is costed properly rather than assumed away.
Start the conversation

Get an independent view of your ERP project

A costed basis to continue, cut back or stop — from consultants with no stake in the original implementation.

High commitment

45-minute independent strategy call

The full initial consultation with Dr Harald Dreher or the senior partner managing the account. Aim: to clarify the decision-making situation — not to recommend a system.

Book the call
Medium commitment

15-minute orientation call

Whether taking on the mandate makes sense. If we're not the right people for the job, we'll say so.

Book a short call
Low commitment

Prefer to email?

Where you stand. Next step — not a sales pitch.

Email us