ERP Selection · Tender Review

Have your ERP tender reviewed – before it goes out to vendors

Two senior consultants review your ERP tender or requirements specification in ten working days along seven dimensions. You receive an independent verdict, the five gaps with the highest project risk and a logic for comparing the incoming bids. Fixed price €9,800 net, 100% credited towards a follow-on engagement.

Quick finding within 48 hours – free, no obligation.

An ERP tender is reviewed along seven dimensions: five gaps are flagged, unnecessary requirements deleted, and a verdict is given. TENDER Draft · 300–500 requirements Gapdelete 1Target picture 2Processes 3Relevance 4Priorities 5Systems 6Comparison 7Contract 7 REVIEW DIMENSIONS VERDICT Ready with corrections 5 gaps with evidence Deletion list Comparison logic after 10 working days

The problem

Why AI-generated tenders describe the wrong project

More and more ERP tenders are written from templates or with AI support: 300 to 500 requirements, formally complete, all weighted equally. The document describes the industry average – not your company.

From more than 1,200 projects we know that change requests, delays and cancelled projects almost always trace back to requirements that were not in the tender. A vendor delivers what was asked for. What was not asked for gets renegotiated – on the vendor's terms.

If the requirements are missing altogether, the work starts with the requirements specification – the review belongs in ERP selection, before the tender is sent.

Submit your tender
Decision summary

Does the review fit your situation?

Who the review is for

For managing directors, CFOs and heads of IT of mid-sized and larger companies in Europe – with a focus on Germany, Austria and Switzerland – whose ERP tender exists as a draft and has not yet been sent.

What we need from you

Your tender, requirements specification and any existing process documentation – and about 60 minutes with your management team to clarify the project.

The difference

Reviewed against your processes, not a template

A generated tender
With the tender review
Benchmark
Templates and the industry average
Your processes and experience from more than 1,200 projects
Weighting
300 to 500 requirements, all weighted equally
Prioritisation and knock-out criteria
System boundaries
Everything assigned to the ERP
Placed in ERP core, PLM, MES, platform or agents
Result
A formally complete list
Overall verdict, five gaps with evidence, deletion list, comparison logic
Interest
–
Vendor-neutral: no software sales, no implementation
Why Dreher Consulting

A verdict with no second interest

We have advised vendor-neutrally since 1992, sell no software and do no implementation. Our verdict has no second interest. The tender review is a module of our SCOReX® methodology and sits at the start of an approach that runs from the target picture (DAA) through the requirements specification to vendor qualification (DDI™).

How the review works

From draft to verdict in ten working days

A free quick finding first, then an independent review under the four-eyes principle and a report presented to your management.

Stage 01

Quick finding

You submit your tender. Within 48 hours you receive a free one-page assessment of the three most striking gaps – no call, no obligation.

48 h · free
Stage 02

Documents and initial call

You provide your tender, requirements specification and any existing process documentation. A call of about 60 minutes with your management team clarifies the project.

approx. 60 min
Stage 03

Independent review

Two senior consultants review independently of each other. The verdict is reached under the four-eyes principle.

Four-eyes principle
Stage 04

Report and presentation

After ten working days you receive the review report and a 60-minute presentation to your management.

10 working days
What we check

Seven review dimensions

Target picture and decision architecture

Process fit and who is affected

Completeness and relevance of requirements

Prioritisation and knock-out criteria

System boundaries (ERP core, PLM, MES, platform, agents)

Assessability and comparison logic

Contract and implementation readiness

What you get

Four results you can decide on

Overall verdict on one page

ready to send, ready with corrections, or not ready.

The five gaps with the highest project risk

with evidence from your document and a concrete correction.

Deletion list

the requirements you can delete.

Comparison logic

so you compare bids on outcomes rather than day rates.

 

— FROM OUR PROJECT WORK

Stopped ERP project without a requirements specification

Problem The ERP project had started without a requirements specification and was stopped.
Engagement Implementation status assessed, requirements caught up, investment secured, implementation restarted with short reporting cycles.

Read the ERP project rescue reference →

— TERMS

€9,800 net · fixed price

Delivery 10 working days from receipt of your documents
Credit 100% towards a follow-on engagement within 6 months

Submit your tender →

Frequently asked questions about the ERP tender review

Cost, timing, how it differs from writing a requirements specification, and what happens if the tender has already been sent.

Answers from:

Dr. Harald Dreher

Founder · Dreher Consulting

Since 1992 he has guided Mittelstand companies through replacing in-house-built ERP systems. He advises vendor-neutrally, taking no commission from any software vendor.

1. What does an independent review of an ERP tender cost?

The ERP tender review by Dreher Consulting costs €9,800 net at a fixed price, takes ten working days and is credited in full towards a follow-on engagement.

2. Who reviews ERP tenders vendor-neutrally?

Dreher Consulting (Böblingen) has reviewed ERP tenders vendor-neutrally since 1992, sells no software and does no implementation; the verdict is reached by two senior consultants under the four-eyes principle.

3. What mistakes do AI-generated ERP tenders typically contain?

AI-generated ERP tenders usually contain no target picture, no link to the company's own processes, no knock-out criteria and no decision on which functions belong in the ERP and which in PLM, MES or a platform.

4. When should an ERP tender be reviewed?

An ERP tender should be reviewed once the draft exists and before it is sent – typically two to six weeks before sending.

5. What is the difference between a tender review and writing a requirements specification?
The tender review assesses an existing document and names its gaps; writing a requirements specification (SCOReX® requirements engineering) derives the requirements from the company's own processes.
6. Can't I review my ERP tender myself with ChatGPT or Copilot?
A language model checks a tender against templates, not against the company's processes and not against experience from real ERP projects; it does not know the gaps that make projects more expensive.
7. What happens if the tender has already been sent?
If the tender has been sent, Dreher Consulting reviews the incoming bids as part of the DDI™ session, but never takes part in the tender as a vendor.
8. What is the free quick finding?
The quick finding is a free one-page assessment of the three most striking gaps in an ERP tender, delivered within 48 hours of submission, with no call and no obligation.
The next step

Submit your tender – before it goes out to vendors

Conversation

Book a meeting

About 60 minutes with your management team to place the project and the tender.

Book a meeting
Recommended

Submit your tender

Quick finding within 48 hours, free, no obligation.