Mon – Sat: 9:00 AM – 7:00 PM IST
ERP Basics

ERP RFP checklist

The questions that produce different answers from different vendors — and the ones that do not.

In short

An ERP request for proposal should establish scope, ask scenario-based functional questions, and require specifics on implementation approach, team, data migration, integration, support and commercials. The useful questions are the ones a vendor cannot answer yes to without committing to something checkable.

Why It Matters

Why this matters in practice

Most RFPs are long and produce near-identical responses, because they ask closed questions that invite a yes. A question like "does your system support batch traceability" discriminates between nobody. "Describe how a user traces every customer who received a specific raw material lot, and how long that takes" produces answers you can compare.

Scenario questions produce comparable, checkable answers
Named team commitments prevent substitution after signing
Assumptions stated in writing make change control possible
Reference customers in your sector are the strongest signal
How It Works

How it works in practice

Scope and context

Your business, volumes, sites, users and the processes that are genuinely distinctive. Vendors cannot price what they cannot see.

Functional scenarios

Ten to fifteen real cases, each asking how the product handles it and whether in standard configuration.

Implementation approach

Phases, duration, what they need from you, and what happens when something slips.

Team and continuity

Who specifically will run it, their experience, and whether they are committed or indicative.

Commercials and assumptions

Price with its assumptions stated, change-request rates, and what the support agreement covers after go-live.

Worked example

A worked example: why 600 requirements produce no information

An RFP lists 612 requirements, each to be answered standard, configurable, customisation or not supported. All three vendors return over 95 percent in the first two categories.

The responses are worthless for discrimination, and predictably so. 'Configurable' covers everything from a checkbox to three weeks of work. Requirements phrased as features invite feature answers. And no vendor responding competitively will mark anything 'not supported' if any reading of the question allows otherwise.

A better instrument asks fewer questions that are harder to answer evasively: weighted requirements with the genuinely essential ones marked; scripted scenarios the vendor must demonstrate with your data; a request for the named implementation team with their relevant experience; references of your choosing rather than theirs; and total cost over five years on a template you supply so the figures are comparable. Thirty well-chosen questions separate vendors. Six hundred do not.

Key terms

The vocabulary, briefly

Term What it means
RFI Request for information — an early, lighter enquiry to build a longlist.
RFP Request for proposal — the detailed requirement and commercial request.
Scoring matrix Weighted criteria applied consistently across responses.
Scripted scenario A business case the vendor must demonstrate with your data.
Evaluation panel The group scoring responses, which should include the people who will use the system.
What Goes Wrong

Common mistakes worth avoiding

Hundreds of yes/no requirements

Every vendor answers yes. The matrix produces no discrimination and consumes weeks.

No question about standard versus custom

A capability delivered by development costs differently from one delivered by configuration. Ask explicitly.

Accepting indicative teams

The people in the proposal should be the people on the project, or the proposal is not about them.

No assumptions in the pricing

A price without stated assumptions cannot be defended against a change request later.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Requirements marked essential Should be a minority. If most are essential, prioritisation has not happened.
Scoring variance across the panel Wide variance means the criteria are ambiguous, not that the panel disagrees.
Scenario completion in demonstration The hardest evidence available in a selection, and the least gameable.
Cost comparability Whether responses can actually be compared, which requires supplying the template.
FAQ

Questions we are asked about this

Short enough that vendors answer it properly. Fifteen good scenario questions produce more discrimination than three hundred checkbox requirements.
Three to five seriously evaluated beats ten superficially. Each proper evaluation costs you time as well as them, and thin evaluation is how selections end up decided on price.
Weighted requirements with essentials identified; scripted scenarios to be demonstrated on your data; the named implementation team with sector experience; a five-year cost breakdown on your template; references you may choose from their customer base; and the contractual position on code ownership, data extraction and exit. Most of the discriminating information comes from the last four, which are also the ones most often omitted.
Four to six at RFP, narrowed to two or three for scripted demonstrations and references. More than six produces a volume of responses nobody reads properly, and it wastes the time of vendors who had no realistic chance. A longlist built through lighter RFI enquiries is the efficient way to reach that number without excluding options prematurely.
Opinions differ and disclosing a range is usually more productive than concealing it. A range lets vendors propose a realistic scope rather than guessing, and it avoids three months spent evaluating a proposal that was never affordable. The risk is anchoring, which is managed by giving a range rather than a figure and by holding the scope constant across responses.
The people who will use the system daily, a finance representative, someone technical, and an executive sponsor with authority to decide. The common failure is a panel of managers and IT with no daily users, which produces a selection that scores well on capability and poorly on usability — and usability is what determines whether the system is actually adopted after go-live.
Related

Where to read next

How to choose an ERP

Read more

ERP total cost of ownership

Read more

ERP implementation phases

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.