New: Odoo and Dynamics 365 cost calculators.Estimate your costs

How to write an ERP RFP: template, questions and scoring sheet

An ERP RFP for a company of 25 to 100 people has eight sections: company overview, project scope, functional requirements, technical requirements, implementation approach, pricing, vendor…

FlecticUpdated 19 min read

An ERP RFP for a company of 25 to 100 people has eight sections: company overview, project scope, functional requirements, technical requirements, implementation approach, pricing, vendor information and submission logistics (ERP Research, September 2026). Keep it under 25 pages with 40 to 60 requirements, as Softabase advises, or accept 200 to 400 prioritized lines on ERP Research's model; the publishers disagree on volume and agree on ranking every line. Send the document to 4 to 6 vendors, keep 2 to 3 for demos, and score software and implementation partner on separate sheets with the weights locked before replies arrive.

When the product decision is made and the open question is who implements it, a ranked requirements list plus a partner RFQ (request for quotation) against a fixed scope answers it. The full template, both scoring sheets, the demo script and the quote format are below, with nothing behind a form. If Odoo and Microsoft Dynamics 365 are both still on the table, Flectic's ERP selection service compares them on your workflows and recommends one in writing before any RFP goes out.

What goes in an ERP RFP, and when a company your size can skip it

The eight sections, one job each:

  1. Company overview: who you are, what you run today, and why now.
  2. Project scope: the processes in and out, the sites involved, and the constraints.
  3. Functional requirements: what the system has to do, ranked by priority.
  4. Technical requirements: hosting, integrations, data volumes and security questions.
  5. Implementation approach: how each respondent would deliver, staff and support the project.
  6. Pricing: in a format you prescribe, so the replies compare.
  7. Vendor information: company facts, named team, references.
  8. Submission logistics: deadline, format, contacts, and the rule that every answer goes to every bidder.

The full document pays for itself when two or more products are still live candidates and several departments will live with the choice. Once your team has settled on Dynamics 365 Business Central or Odoo, the remaining decision is usually the partner, and that decision needs a shorter document: the same requirements list, a fixed first-phase scope, and a scorecard for team, method and price. A company with one warehouse, one country and a finance lead who can name the three most painful processes can often go straight to that partner conversation with the requirements list in hand.

Several of the templates that rank for an ERP RFP sit behind a lead form. The template and the weights below are a synthesis of the published guides, credited inline, and the scoring math is shown in full on this page.

Software RFP or partner RFQ: which document are you writing

Rand Group's selection guide (September 2026) draws the line cleanly: score the functional and technical fit of the product on one sheet, and score the team, methodology, migration approach and commercial terms of the implementing firm on a second (source). Send one document that asks vendors to bid software and services as a single number, and the reply hides which partner would sit in your project meetings.

The two documents share a skeleton and diverge in emphasis:

  • Central question (Software RFP: Which product fits our processes? · Partner RFQ: Which firm can deliver it here?)
  • Core attachment (Software RFP: The ranked requirements table · Partner RFQ: The same table, now the fixed scope)
  • Scored on (Software RFP: Functional fit, technical fit, total cost of ownership · Partner RFQ: Team, method, migration plan, price)

Whatever the product decision produced becomes an input: the requirements list you already wrote is the scope document partners price against. For the full path from long list to signed contract, see the ERP vendor selection guide. When the partner decision is the open one, our checklist for choosing an ERP implementation partner covers the interview and reference work.

What to write in each section of the template

Work through the skeleton top to bottom. Softabase's 25-page ceiling (source) is a useful discipline: it forces every section to carry weight.

1. Company overview

TechTarget's requirements guide (June 2026) starts the checklist with a project overview: company size, market, locations, project leaders, timeline and goals (source). Five sentences do the job. For a distributor:

We are a 45-person wholesale distributor running QuickBooks and spreadsheet-based inventory across warehouses in Columbus, Ohio and Hamilton, Ontario. We ship about 300 orders a day. Month-end close takes eight working days. The project owner is our CFO, the decision date is March 31, and the goal is visible stock and a three-day close.

2. Project scope

List the processes in scope with the pain in one line each, and name what stays out. For the distributor above, the scope block reads:

In scope: order to cash, purchasing, inventory, financials. Out of scope: payroll, which stays with ADP. Constraint: no cutover between November 15 and January 15.

3. Functional requirements

The format and the worked tables live in the next section. One rule holds here: every line carries a priority before it enters the document.

4. Technical requirements

Name each integration with direction and frequency: ecommerce platform to ERP (orders, hourly), third-party logistics provider to ERP (inventory, nightly), bank feeds, shipping rates. State data volumes: active SKUs, orders per day, journal lines per month. State where you need the production database to live; Canadian entities get a dedicated question list in the privacy section below.

5. Implementation approach

Ask each respondent to describe the phases, the named people per phase, the decision cadence, what they need from your team each week, and how they price a scope change found mid-phase. A partner that skips the question will improvise on your budget later.

6. Pricing

Prescribe the quote format from the pricing section below and require software and services as separate totals. That split is what lets you keep a product and change the partner.

7. Vendor information

Ask for years in business, headcount by role, the count of customers live on the current major version, and three references of similar size and industry. Require short CVs for the named team, including who leads data migration and who runs training.

8. Submission logistics

Set the deadline with a time zone, name one point of contact, open a written Q&A window, and share every answer with all bidders. State that you will score against published weights applied to the requirements table. Vendors who know the scoring is systematic write tighter replies.

How to write requirements a vendor can answer and you can score

Give every line a priority and write the business need beside it, as TechTarget advises (source). The labels and their scoring weight come from ERP Research: mark each line must have, should have or nice to have, and the label multiplies the fit value in the scoring section below. On volume, the two published guides disagree: Softabase (April 2026) keeps 40 to 60 lines in an RFP under 25 pages, while ERP Research (September 2026) advises 200 to 400 prioritized requirements and warns that past 1,000, vendors skim. Whichever count you follow, rank every line as you write it: marking all 60 lines must have throws away the 3, 2 and 1 spread, so the fit values do all the separating, and a list with no priorities cannot be scored on this model at all.

Then force a structured answer. ERP Research's fit scale replaces yes and no with four values: Standard (4 points), Configuration (3), Customization (1) and Not available (0). Multiply each by the priority you set: must have 3, should have 2, nice to have 1. A vendor that answers Customization on a must have is telling you the price of that line belongs in the quote, so require it there.

Sample requirements for a distributor (ERP for wholesale distribution):

  • Print the customer PO number on the order acknowledgment (Priority: Must have · Business need: Customers refuse invoices without it)
  • Track lot numbers and expiry dates by warehouse (Priority: Must have · Business need: Recall traceability for food-safe lines)
  • Price by customer contract with volume breaks (Priority: Should have · Business need: Quote accuracy without re-keying)
  • Rate-shop carriers at ship confirm (Priority: Nice to have · Business need: Freight spend visibility)
  • Customer portal for reorder and invoice history (Priority: Nice to have · Business need: Fewer order-status calls)

The vendor adds two columns: the fit value (Standard, Configuration, Customization or Not available) and a demo reference for every should have and must have.

Sample requirements for a manufacturer (ERP for manufacturing):

  • Explode a multi-level bill of materials with phantom assemblies (Priority: Must have · Business need: Costing accuracy on subassemblies)
  • Capture actual labor and machine time per operation (Priority: Must have · Business need: Job costing that survives an audit)
  • Backflush components at work order completion (Priority: Should have · Business need: Floor speed over minute-by-minute tracking)
  • Schedule work centers on finite capacity (Priority: Should have · Business need: Promises backed by a real schedule)
  • Record quality checks at receipt and before shipment (Priority: Should have · Business need: Fewer returns traced to intake)

Both tables are starting points: replace lines with your own processes and keep the priority and business-need columns.

Questions that separate strong replies from weak ones

Written replies show how a vendor thinks before the first demo. These sort the field fast.

For the software vendor

  • How many customers run live on the current major version, and what did the last upgrade round involve?
  • Which of our must haves ship as standard, and which need configuration?
  • What happens to customizations at the next upgrade: rework, retest, or retirement?
  • Which integrations on our list are prebuilt, and which are partner-built?

For the implementation partner

  • Who would sit on our project, what does each person own, and what share of their week goes to us during go-live?
  • How many projects have you delivered for companies our size in our industry, and can we call two references this month?
  • What does your discovery produce in writing, and is it a paid engagement?
  • How do you price a scope change discovered in month two of phase one?
  • Who owns data migration, and how many mock loads run before cutover?
  • What do you need from our team each week, in hours?

Privacy and data questions for Canadian buyers

Put these in the RFP and require written answers. The statutes set the duties; your lawyer reviews the replies.

  • Where will the production database physically reside, and in which country?
  • Which subprocessors process our data, and where are they located?
  • Does a SOC 2 report exist, for which audit period, and will you share it under NDA? SOC 2 is a voluntary audit report, so ask for the period and read the exceptions.
  • How would you support a PIPEDA access request that touches employee or customer data (PIPEDA overview)?
  • What changes for a Quebec entity under Law 25?
  • If you send commercial email to our team, how do you comply with CASL?

A weighted scoring sheet you can copy

Freeze the model early. ERP Research's mistake list says to lock the weights before the RFP goes out and not to rescore after replies arrive. A model that changes once you have seen the bids cannot be defended.

Layer 1: score each requirement line

Use ERP Research's fit values times your priorities. A must have answered Standard earns 4 × 3 = 12 points; the same line answered Customization earns 1 × 3 = 3. A worked total: assume 50 requirements, of which 20 are must have, 20 should have and 10 nice to have. The maximum is 20 × 12 + 20 × 8 + 10 × 4 = 440 points, and a vendor that totals 330 of 440 on ERP Research's requirement-line score is 110 points off the ceiling; the lines where those points went are the first ones to spot-check in the demo. Total every vendor the same way and the ranking survives questioning.

Layer 2: weight the categories

Three published weight sets, each an example from its publisher:

  • Functional and industry fit (Rand Group: 30% · Softabase: 35% · ERP Research: 40%)
  • Technical, integration and data (Rand Group: 15% · Softabase: 15% · ERP Research: 20%)
  • Reporting, automation and AI (Rand Group: 10% · Softabase: n/a · ERP Research: n/a)
  • User experience (Rand Group: 10% · Softabase: n/a · ERP Research: n/a)
  • Security and compliance (Rand Group: 10% · Softabase: n/a · ERP Research: n/a)
  • Scalability and roadmap (Rand Group: 10% · Softabase: n/a · ERP Research: n/a)
  • Total cost of ownership (Rand Group: 15% · Softabase: 25% · ERP Research: 15%)
  • Vendor viability (Rand Group: n/a · Softabase: 15% · ERP Research: 15%)
  • Implementation (Rand Group: n/a · Softabase: 10% · ERP Research: 10%)

Rand Group and ERP Research score each category 1 to 5; ERP Research publishes its category weights on its selection criteria page. The three columns are alternative models, and the job is to pick one and freeze it before the RFP goes out, then score every vendor on the same sheet. Price is the smaller category in all three, 15, 25 and 15 percent against functional weights of 30, 35 and 40, and it can still offset a modest functional gap. The weights alone never make a missed must have an automatic loss; if you want that bar, state it as your own rule and compare prices only among vendors that cleared it.

The partner sheet

Rand Group's example partner weights:

  • Platform experience: 20%
  • Industry and process experience: 20%
  • Proposed team: 15%
  • Methodology and project management: 15%
  • Data migration, integration and customization: 10%
  • Training, change management and support: 10%
  • References, transparency and commercial terms: 10%

Score each category 1 to 5, divide by 5, multiply by the weight, and the totals land on a 100-point scale. Team and methodology carry 15 percent each on this sheet, so two partners quoting similar prices still separate on them.

How to run demos on scripts of your own workflows

Softabase's funnel sends the RFP to 4 to 6 vendors and demos 2 to 3; ECOSIRE advises 5 to 8 recipients rather than 15 or more (source). Demos go only to the shortlist, and every vendor gets the same script.

Write two or three scripts from your live workflows. The distributor script: enter a contract-priced order, ship it partial, backorder the balance, then run the month-end inventory report finance already uses. The manufacturer script: raise a work order with scrap and rework, close it, and pull the job cost. Every vendor demonstrates on your items, your prices and your tax setup.

Run every session in the same shape: the script first, then spot checks on three requirement lines named that morning, then questions. The spot checks are where fit values meet reality: a Standard answer shows in three clicks or it does not exist. Score in the room, and debrief right after each demo while the panel's notes still disagree in useful ways; TechTarget (June 2026) suggests meeting after each demo to review differences in the feedback (source). Waiting a week turns five sets of notes into one fuzzy impression.

A pricing format that forces comparable quotes

A single-number bid hides the work behind it. In an r/Odoo thread, one buyer describes a quotation with just one line item and no task breakdown (thread); in a thread on custom module pricing, a buyer treats a missing audit or discovery package as a red flag (thread). Prescribe the lines, and every bid becomes comparable:

  • Subscription or licenses: Per user type, per month, contract term, list price and the discount you get
  • Discovery: Fixed fee and the written findings it produces
  • Implementation, by phase: Fixed fee or capped hours per phase, with named deliverables
  • Data migration: Which records, how many mock loads, price per entity or per hour
  • Integrations: Each interface on its own line with its price
  • Reporting: Standard reports included, custom builds priced
  • Training: Hours by role, remote or on site
  • Support after go-live: Included hours, response times, renewal price
  • Years 2 and 3: Assumed subscription uplift, support renewal, expected custom work
  • Expenses and taxes: Travel policy and tax treatment for US and Canadian entities

Require software and services as separate totals so you can keep a product and change the partner, which is the split Rand Group builds its model around. Ask every bidder how long the prices hold, and put the answer in the award letter.

A realistic timeline for a mid-size company, and the mistakes that weaken your position

ERP Research's clock for a full RFP runs eight to twelve weeks from drafting to award: requirements gathering 2 to 3 weeks, drafting 1 to 2, vendor response 3 to 4, scoring and shortlisting 1, demos and references 1 to 2 (source). Cross 300 requirements and ERP Research extends the response window from 3 to 4 weeks to 4 to 6 weeks, which turns the full clock into about 9 to 14 weeks. ECOSIRE's lighter version drafts in 1 to 2 weeks, distributes in 1, and gives vendors 2 to 3 weeks to reply (source).

No survey publishes a selection duration for a 25 to 100 user company as of October 2026, so treat both clocks as the publishers' estimates. The nearest large-sample datapoint measures implementation, and for a much bigger cohort: Panorama Consulting Group's 2026 ERP report covers 170 organizations, 56.5 percent of them multinational, with a median annual revenue of USD 200.5 million across the sample and a median implementation timeline of 9 months (report). Read the 9 months as delivery length for projects of that scale; it is not a selection timeline for a company of 25 to 100 people. More than a quarter of those projects ran over budget, most often because of unexpected technology needs, which the report ties to poor system selection. Scope discipline in the RFP is where that risk gets priced down.

The recurring mistakes are known and cheap to avoid:

  1. Sending 1,000 or more requirements. ERP Research: vendors skim and the document loses its point. Hold to 200 to 400 prioritized lines, or 40 to 60 on Softabase's shorter model.
  2. Setting weights after the demos. Lock the model before the RFP goes out and score replies against it.
  3. Scoring from memory a week later. Debrief right after each demo, while the panel's notes still disagree usefully.
  4. Letting one bid cover software and services. Two sheets, two totals, one award decision on each.
  5. Sending to 15 or more recipients. ECOSIRE advises 5 to 8; Softabase says 4 to 6.
  6. Pasting in a 40-page gated form. Trim to the processes in scope; the 25-page ceiling exists for a reason.

When the shortlist is down to partners and the requirements list is written, the remaining work is discovery, scoring support and delivery. Flectic's ERP implementation services cover that arc. Bring the draft RFP to the free discovery call; it shortens the path from requirements list to a fixed-scope proposal.

How Flectic can help

Flectic implements Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada. If the platform is still open, the ERP selection service compares Odoo and Dynamics 365 on your workflows and recommends one in writing. Flectic sends a written proposal with a fixed price for each phase before work starts. Before you issue the RFP, review the ERP implementation service and Book a free discovery call with Flectic.

Sources

Frequently asked questions

How do we weight functional fit against price without letting a cheap, unfit system win?

Hold price to the weight the published models give it: total cost of ownership carries 15 percent in Rand Group's sheet and ERP Research's, and 25 percent in Softabase's. Score functional fit first and set aside any vendor that rates one of your must-haves as Not available. Compare price only among vendors that cleared the fit bar.

How do we stop vendors from answering yes to every line?

Require a fit value on every requirement line: Standard, Configuration, Customization or Not available. A yes is not an allowed answer on the sheet, Standard scores 4 points and Customization scores 1, and those values separate vendors only when the answers are accurate. The demo spot-check is what catches a vendor who marked Standard on a line the product does not do out of the box: pick three must-haves per vendor and ask to see each one working in the system.

The template I downloaded is a 40-page form. What can we cut?

Softabase advises keeping the whole RFP under 25 pages, which happens when requirements stick to the processes in scope. Cut boilerplate vendor questions, cut lines for processes with no planned change, and move security and legal detail into a short attachment. Keep the commercial sheet to one page.

What do we attach for Canada: PIPEDA, Quebec Law 25, data location, SOC 2?

Attach a one-page list of questions the vendor answers in writing: where the production database resides, which subprocessors touch your data, whether a SOC 2 report exists and for which audit period, how a PIPEDA access request would be handled, and what changes for a Quebec entity under Law 25. PIPEDA governs personal information in the Canadian private sector, and Law 25 adds Quebec-specific duties. Have your lawyer review the replies.

Is a full RFP worth it, or is a requirements list plus two scripted demos enough?

When the product is chosen and only the partner decision is open, a requirements list, a fixed first-phase scope and an RFQ scored on team, method and price is enough. Run the full two-sheet RFP while two or more products are still live candidates. The requirements list you write for the light path becomes the spine of the full document anyway.

Should the software vendor and the implementation partner be scored on the same sheet?

Score them on separate sheets. Rand Group advises one weighted sheet for the product's functional and technical fit and a second for the partner's team, methodology, migration approach and commercial terms. A combined bid hides which firm would do the work and what their team looks like.