What it is
The ERP Requirements Gathering Workbook is a weighted scoring spreadsheet that lets you evaluate two shortlisted ERP vendors, requirement by requirement, across the modules that matter. You list each requirement, rate its Priority from 1 to 5, mark hard dealbreakers as must-haves, and score how well each vendor meets it from 1 to 5 — and the workbook converts those numbers into weighted points, module sub-totals, and a single rolled-up recommendation.
It is organized around six modules — Financials/GL, Order-to-Cash, Procure-to-Pay, Inventory & SCM, Manufacturing/MRP, and Reporting & BI — with a Scorecard tab where you do the rating and a Summary tab that explains how to read the result. Each requirement's weighted score is simply Priority multiplied by Vendor score, so the requirements you care about most carry the most weight in the final ranking.
Because it is a calculator, the workbook does the math for you: every module sub-totals automatically, the Scorecard rolls everything into a total weighted fit percentage, and the Summary tab interprets it — a viable mid-market ERP usually scores 70 percent or more overall, and if two vendors land within about five points, the tie is broken by must-have coverage, total cost of ownership, and implementation risk rather than by raw score alone.
What it's used for
Buying teams use the workbook to replace a gut-feel vendor comparison with a structured, weighted, auditable one. It forces the organization to agree on what it actually needs and how much each need matters before scoring vendors, which is far harder to argue with than a sales-led demo impression.
- ✓ Cataloguing requirements across all six modules so nothing important — multi-entity consolidation, three-way matching, lot traceability, MRP — gets forgotten in the comparison.
- ✓ Weighting each requirement by Priority (1 to 5) so mission-critical needs drive the outcome and nice-to-haves do not inflate a vendor that happens to be strong in irrelevant areas.
- ✓ Flagging hard dealbreakers with the must-have column, so a vendor that fails a non-negotiable is visible even if its overall weighted score looks healthy.
- ✓ Scoring two shortlisted vendors side by side (1 to 5 per requirement) and letting the workbook compute weighted points and module sub-totals automatically.
- ✓ Producing a single rolled-up weighted fit percentage and a computed recommendation, giving the steering committee an objective starting point for the decision.
- ✓ Interpreting close races — when two vendors land within about five points — by escalating to must-have coverage, total cost of ownership, and implementation risk rather than relying on the raw number.
- ✓ Creating an auditable record of the evaluation that can be revisited if a decision is challenged or a new requirement surfaces late in the process.
Who uses it
The workbook is filled in collaboratively by the people who own each module's requirements and reviewed by the team making the buying decision. Each contributor scores the areas they understand best, which keeps the ratings grounded.
Context & good to know
ERP selection is notoriously vulnerable to recency and charisma bias — the last demo you saw, or the slickest salesperson, can swing a decision that should be driven by fit to your actual requirements. A weighted workbook counters that by making the team commit to priorities up front and then scoring against them, so a vendor cannot win on polish if it misses the requirements you weighted heavily.
The weighting mechanic is what makes the tool more than a feature checklist. Because each score is Priority times Vendor score, a vendor that nails every nice-to-have but stumbles on a mission-critical requirement will not float to the top. Pairing that with an explicit must-have column means a hard dealbreaker stays visible even when a vendor's overall percentage looks competitive — the number and the non-negotiables are read together.
The Summary tab's guidance reflects how real selections resolve. A viable mid-market ERP — whether NetSuite, Acumatica, SAP Business One, or Epicor — typically clears 70 percent weighted fit, so a low score is a genuine warning. And when the top two land within about five points, the workbook deliberately hands the decision off to must-have coverage, total cost of ownership, and implementation risk, because at that margin the spreadsheet has done its job and judgment takes over. This is exactly why the workbook pairs naturally with the TCO & ROI Calculator and the Fit-Gap Analysis.
The workbook also creates a durable record that outlives the selection itself. Months into an implementation, when someone asks why a particular platform was chosen or why a requirement was rated mission-critical, the scored workbook answers definitively. That auditability matters in regulated industries and in any organization where a major software decision must be defensible to a board or an auditor — the weighted requirements, the must-have flags, and the module sub-totals together form a transparent rationale that a slide deck of demo impressions never could.