Logix Gridnode.
Implementation

How to Write an ERP RFP: Requirement Sections, Demo Scripts and a Weighted Scoring Model

Most ERP RFPs balloon into 900-line spreadsheets that every vendor answers "yes" to. This playbook covers the sections worth keeping, demo scripts run on your own data, and a scoring model your board can defend.

Logix Gridnode editorial team · November 2026 · 9 min read

Start With the Decision You Need to Defend, Not a Downloaded ERP RFP Template

Your steering committee will eventually sign off on a multi-year, likely seven-figure commitment, and someone will ask why Vendor B beat Vendor A. A generic ERP RFP template won't help you answer. Templates are built to be thorough, so they produce hundreds of requirement lines, vendors mark nearly all of them "fully supported," and the shortlist gets decided by price and whichever demo felt smoothest.

A useful RFP does three things. It gives vendors and implementation partners enough information to propose a realistic scope. It makes them commit, in writing, on the 15 to 30 processes that actually separate one product from another. And it produces comparable data that drops straight into a scoring model you agreed on before any proposal arrived.

Advertisement

So begin with a one-page decision brief, not the requirements. Cover the business outcomes you need (say, closing the month in five days instead of twelve, or running three legal entities on one chart of accounts), the hard constraints (go-live window, budget ceiling, countries in scope), and who scores what. Everything in the RFP should trace back to that page. If a section feeds neither a score nor a contract clause, cut it.

Requirement Sections to Keep, and the Ones That Only Add Noise

Effective mid-market and enterprise RFPs share a skeleton. Weak ones share padding: generic capability lists any modern cloud ERP covers, and boilerplate questions vendors answer by pasting marketing copy.

SectionKeep or cutWhy
Company profile, entities, countries, volumesKeepVendors can't size licenses or implementation without transaction volumes, user counts by role, and entity structure
Priority process requirements (15 to 30 scenarios)KeepThis is where vendors actually differ, and it feeds the demo script
Regional compliance and taxKeepE-invoicing, statutory reporting and data residency vary by country and can rule a product out
Integration inventoryKeepWMS, TMS, EDI, banks, e-commerce and payroll interfaces drive cost and risk
Data migration scopeKeepOpen items only, or history too? The answer moves the cost considerably
Implementation approach, team and rate cardKeepPartner quality often predicts project outcome better than software features do
Commercials: pricing schedule, renewal caps, exit termsKeepYour TCO comparison depends on a standard pricing template
Generic feature checklists ("supports multi-currency")CutEvery vendor says yes, and you learn nothing
Long vendor history and philosophy questionsCutAsk for two pages of financials and viability data instead
Long security questionnairesMoveSend to finalists only, alongside their SOC 2 or ISO 27001 reports

As a rough guide, a focused RFP for a company with a few hundred employees runs 25 to 40 pages plus a requirements workbook of 150 to 300 lines. If yours is heading toward 1,000 lines, you're writing an implementation specification, and nobody can price it accurately at this stage.

Writing an ERP Requirements Checklist Vendors Can't Answer With a Blanket Yes

Vendors aren't necessarily lying. "Supported" can mean standard functionality, a configuration setting, a partner add-on, a custom extension, or something on next year's roadmap. Your ERP requirements checklist has to make them say which.

Use fixed response codes, one per line:

  • S: standard, in the current general release with no configuration beyond setup
  • C: configuration (workflows, fields, rules) done without code
  • A: third-party add-on, vendor named and priced separately
  • X: custom extension, with estimated hours
  • R: roadmap, with target release (not binding unless you make it so)
  • N: not supported

Then write requirements as outcomes with conditions, not feature names. "Supports lot tracking" tells you nothing. Compare: "Trace a finished-goods lot back to every supplier lot and receipt in one query, across two plants, for a recall response." Tag each line Must, Should or Could, and reserve Must for requirements that would genuinely end a bid. If most of your lines are Must, the tag has stopped meaning anything.

Finally, state in the RFP that response codes will be attached to the contract as representations. That clause alone tends to turn a lot of S answers into C or A.

Turning Priority Processes Into an ERP Demo Script Run on Your Data

An unscripted demo shows you how good the vendor's presales team is. A scripted one shows you the software. Your ERP demo script should take the 15 to 30 priority scenarios from the RFP and string them into end-to-end flows that each finalist runs in the same order.

Build each scenario from five elements:

  1. Starting condition: for example, "Customer has a credit hold, two open orders and a contract price that expires mid-month."
  2. Your data: a sample of real item masters, customers, suppliers and price lists (anonymized if needed), sent a couple of weeks before the demo.
  3. Steps to perform live: who does what, in which role.
  4. Expected outcome: the document, posting or report that should come out the other end.
  5. Scoring prompts: what evaluators should watch for, such as screen count, manual workarounds, or signs the flow was built just for the demo.

Include at least one scenario per region you operate in. For example: issue a tax invoice that clears through a government portal in a country with mandatory e-invoicing (India, Saudi Arabia, Mexico or Poland, say), process intercompany stock transfers between two entities with different functional currencies, then run the consolidated close.

Keep one unscripted hour at the end where process owners can say "show me what happens if...". Budget roughly a day per finalist for a single-entity distributor and more for multi-country manufacturing. If a vendor won't use your data, that tells you something about the vendor.

Weighting the ERP Vendor Scoring Matrix So the Steering Committee Can Defend It

Agree on weights and the scoring scale before any proposal is opened, and minute the decision. That's what makes the result hold up later, both against internal politics and against a losing vendor's complaint that the process was unfair.

Treat regional compliance as a gate first and a score second. If a product can't meet a mandatory e-invoicing or statutory reporting obligation in a country you operate in, through a supported, named method, it's out, however well it scores elsewhere. Products that pass are then scored on how well they handle compliance.

CriterionTypical weightEvidence source
Functional fit (scripted demo and requirement codes)35-40%Demo scores, weighted by Must/Should
Five-year total cost of ownership20-25%Standardized pricing template
Implementation partner capability15-20%Named team, references, methodology, rate card
Regional compliance and data residency (after gate)10-15%Country-by-country response, localization ownership
Technology, integration and vendor viabilityaround 10%API documentation, release cadence, financials

Weights are a starting point; adjust them to your decision brief, and make sure they total 100%. Score every criterion 0 to 5 with written anchors: 5 means standard and shown on your data, 3 means achievable with configuration, 1 means it needs a custom extension, 0 means not shown. Without anchors, one evaluator's 4 is another's 2.

Here's a hypothetical. A 300-person distributor with entities in the UK, the UAE and India scores Vendor A at 4.2 for fit, 3.0 for cost, 4.5 for partner and 4.0 for compliance. Vendor B scores 4.6, 3.8, 2.5 and 3.5. With weights of 40/25/20/15, Vendor A comes out at 4.0 and Vendor B at 3.8. B demos better and costs less, but its weak partner bench closes the gap. That's the trade-off the matrix should make visible, not hide.

Scoring Total Cost, Partner Strength and Compliance Without Fooling Yourself

Total cost. Make every bidder complete the same five-year template: subscription by user type, add-ons, implementation services, data migration, integrations, training, support tier, and partner rates for post-go-live work. As a typical 2026 market range, mid-market cloud ERP subscriptions run roughly $100 to $250 per full user per month, with limited or self-service users priced well below that. Implementation services commonly run one to three times first-year subscription. These figures vary widely by contract, region and scope, so confirm them with each vendor. The costliest surprises are usually renewal uplifts, forced edition upgrades and storage overages, so negotiate a renewal cap and price those items up front.

Partner capability. Score the named people, not the firm's logo. Ask for CVs of the project manager and solution architect, the share of time each will commit to your project, and two references from a similar industry and country mix that you can call without the partner on the line. A partner with strong European delivery may have no tax localization experience in Brazil or Indonesia.

Compliance. For each country, ask who owns the localization (vendor, certified partner or third-party add-on), how quickly it was updated after the last regulatory change, and where data is hosted. Data-protection regimes such as the EU GDPR, India's DPDP Act and Saudi Arabia's PDPL affect hosting and transfer decisions differently. Have qualified local tax and legal advisors confirm the obligations before you treat any vendor's answer as sufficient.

Running the ERP Selection Process: Timeline and Red Flags That Should End a Bid

A disciplined ERP selection process for a mid-market company typically takes three to five months from decision brief to signed contract. Rushed demos are how most bad selections happen.

PhaseTypical durationOutput
Decision brief and process mapping3-4 weeksPriority scenarios, weights agreed and minuted
Long list to shortlist (RFI)2-3 weeksFour to six vendors receive the RFP
RFP response window3-4 weeksCoded responses, pricing templates
Scripted demos with two or three finalists3-4 weeksDemo scores, reference calls
Negotiation and contract3-5 weeksSigned subscription and statement of work

Red flags that should drop a vendor or partner to the bottom of the list:

  • Refusing to put response codes or the named team in the contract
  • Demoing on its own sample data after receiving yours
  • Implementation estimates far below every other bid, with no scope explanation
  • Compliance answers that say "supported via partner" without naming the partner
  • References only from other countries or industries
  • Pressure to sign before quarter-end in exchange for a discount

Your next step: write the one-page decision brief this week and get the steering committee to approve the scoring weights before you send a single RFP. If they can't agree on weights now, they won't agree on a vendor later.

Common questions

How many vendors should receive our ERP RFP?

Usually four to six, narrowed from a longer list through a short RFI. Sending the full RFP to ten or more vendors multiplies your evaluation work and makes serious vendors less willing to invest in their responses. Take two or three finalists forward to scripted demos.

Should we use a vendor-supplied ERP RFP template?

Use it as a reference for structure, but don't send it as is. Templates from vendors or resellers tend to favor that product's strengths and are padded with generic feature lines everyone answers yes to. Build your requirements from your own priority processes and regional obligations.

Do we need a selection consultant?

Not always, but an independent advisor helps if you lack experience running ERP selections or operate across many countries. Choose one with no reseller or implementation relationship with the shortlisted vendors, and agree the fee up front. Fees vary widely by region and scope, so get several quotes.

How do we handle e-invoicing and tax requirements across several countries?

List every country in scope with its current and announced obligations, then treat mandatory items as pass/fail gates in the scoring model. Ask vendors who owns each localization and how updates are delivered after regulatory changes. Have local tax advisors validate the obligations, because rules and timelines change and differ significantly between countries.

Written by the Logix Gridnode editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.