elevate techConsulting Group

Independent ERP and system selection

How do you write ERP requirements and an RFP?

Write ERP requirements by walking through how the business actually runs, area by area, and stating each need as a testable sentence. Score every item must, should or could. Then turn the list into a weighted selection criteria matrix and an RFP that asks vendors to show, not claim. Good requirements are the cheapest protection against a wrong ERP decision.

Why do requirements matter more than the vendor list?

Most failed ERP projects did not pick a bad product. They picked a product against a vague idea of the business. When a vendor writes your requirements, they describe what the vendor does well. When you write them, you describe what you need. That difference decides the demos, the pricing and the contract. For the larger decision, see how to choose an ERP and our independent ERP selection page.

What should an ERP requirements checklist cover?

Use these areas as headings. Under each, write the specific things your company does. Delete areas that do not apply.

Finance

Order to cash

Procure to pay

Inventory and warehouse

Manufacturing (if relevant)

Reporting

Integrations

Security

Data migration

How do you write a good requirement?

A good requirement is one sentence, in plain language, that a vendor can demonstrate. Compare these two:

The strong version can be scripted for a demo and scored. Include the real exceptions too: the odd customer, the split shipment, the intercompany sale. Exceptions are where systems fail.

On one multi-brand distributor engagement, the team wrote 240 business requirements and scored every platform considered against them. The list was long because the business was complicated, not because length was the goal. See the distributor case study.

How do you score requirements as must, should or could?

LevelMeaningHow to use it
MustThe business cannot run, or breaks a legal or customer commitment, without itA "no" disqualifies the vendor or requires a funded workaround
ShouldStrong value, and a workaround existsWeighted heavily in scoring
CouldNice to have, or a later phaseTiebreaker only

Keep must-haves under about a fifth of the list. If the share is higher, you are describing today's habits, not needs. Ask for each one: what happens if we cannot do this on day one?

Before you write requirements, find out which of your current systems are already doing the job.

Take the Systems Check

What does a selection criteria matrix look like?

Group the requirements into categories, assign each a weight that totals 100, score each vendor from 0 to 5 per category from the scripted demo, and multiply. Here is a simple version:

CriteriaWeightVendor A (0 to 5)Vendor B (0 to 5)Vendor C (0 to 5)
Functional fit: finance and order to cash25
Functional fit: inventory, warehouse, manufacturing20
Reporting and analytics10
Integrations10
Security and compliance5
Implementation partner and approach10
Total cost over five years15
Vendor stability and references5
Weighted total100

Score as a group, but have each person score alone first, then compare. Big disagreements show where a requirement was unclear. Do not skip the cost line: see ERP costs not in the quote.

What goes in the ERP RFP?

  1. Company overview. Size, locations, entities, industries, growth plans.
  2. Scope and goals. What problems this project must solve, and what is out of scope.
  3. Requirements. The scored list, with a response column: standard, configuration, customization, third party, or not available.
  4. Demo scripts. Real scenarios from your business that vendors must run live with your sample data.
  5. Implementation approach. Who does the work, the team, phases, timeline and what you must supply.
  6. Pricing in a fixed format. Subscription or license, implementation, data migration, integrations, training, support, and renewal increases, so vendors are comparable.
  7. References. Customers of your size and type that you can call.
  8. Contract terms. Data ownership, exit, service levels, price caps.
  9. Process and dates. Questions, submission deadline, demo window, decision date.

Send it to three or four vendors, not ten. Our list of questions to ask ERP vendors makes a good addendum.

What mistakes spoil an ERP requirements list?

Common questions

How many ERP requirements should we write?

Enough to describe how your business really runs, and no more. Many mid-size companies land between 100 and 250. One distributor we cite wrote 240. Quality matters more than count: each requirement should be testable in a demo.

Should every ERP requirement be a must-have?

No. If everything is a must, nothing is. Reserve must-have for what the business cannot run without, such as a legal or customer-contract need. Most requirements should be should-have or could-have.

Do we need a formal RFP to choose an ERP?

Not always. A shortlist of three or four vendors, a written requirements list and scripted demos can work as well. A formal RFP helps when the board, lender or sponsor expects a documented process, or when you need comparable written pricing.

Who should write the requirements?

The people who do the work, led by someone who owns the outcome. Finance, operations, sales and warehouse leads each write their own area. An independent lead keeps the list consistent and keeps vendors from writing it for you.

Not sure where to start?

Take a free three-minute score. If a conversation makes sense, it will offer one.