The ERP demo is the moment when buyers are most vulnerable. The vendor is on home turf, the demonstration has been designed to impress, and the account executive has rehearsed every transition. Most buying teams approach this moment without any structured preparation. The result: you end up selecting the vendor with the best salesperson, not the one whose product best fits your actual requirements. This guide gives you the tools to flip that power dynamic.
This article follows on from our guide on ERP RFPs and the 50 questions to ask vendors. If you are still in the shortlisting phase, start there.
Before the Demo: Building the Buyer Scenario
Demand a Business Scenario, Not a Product Tour
An ERP vendor’s default demo is a guided tour of its best features. The product is shown in ideal conditions, with fictitious data chosen by the sales team. You will never see the rough edges.
The only way to objectively evaluate an ERP is to put your reality in front of it.
Send every vendor, at least two weeks before the demo:
- A representative data set from your operations (a fictional customer order with a partial backorder, a multi-line purchase order, a month-end close with subscription accruals)
- The 3 to 5 business-critical processes you want to see executed live — not commented on in a slide
- The expected format: “We want to watch the operator perform the action in front of us, inside your production interface”
This scenario must be identical for every vendor in the running. That is the prerequisite for fair comparison. A vendor that refuses to work from your scenario, or asks to modify the data, is already sending you a signal.
Sample scenarios to provide:
| Process | Concrete test case |
|---|---|
| Customer order | Partial backorder: 80 units available out of 120 ordered |
| Vendor invoice | Three-line delivery note, invoice with price discrepancy on line 2, two-level approval workflow |
| Month-end close | Subscription accrual re-entry across three entities |
| CFO reporting | Consolidated J+1 dashboard with drill-down by profit centre |
Assembling the Evaluation Team
The ideal demo committee includes:
- The CIO or IT director, who chairs the session
- One key user per process being evaluated (head of accounting, head of procurement, etc.)
- The CFO if the finance module is in scope
- A technical representative (enterprise architect or project manager)
Hard rule: no more than 8 people. Beyond that, the session becomes hard to facilitate, side conversations multiply, and questions get lost. Everyone else receives the meeting notes.
Each participant scores independently during the demo. Discussion before scores are consolidated is prohibited — the conformity bias it creates will systematically skew results toward whatever the most senior person says first.
The Structure of a Well-Run ERP Demo
A productive demo runs three hours. Beyond that, decision fatigue sets in and the last vendor benefits from a contrast effect that distorts judgment.
Recommended structure:
| Block | Duration | Content |
|---|---|---|
| Company presentation | 15 min | The vendor introduces itself. You listen — no questions. |
| Business scenario | 2h | Your scenario, executed live. You ask the questions. |
| Architecture and integrations | 30 min | Technical questions: API, security, hosting |
| Commercial and next steps | 15 min | Timeline, indicative pricing, next step |
The business scenario block is sacrosanct. If the vendor tries to skip or compress it, redirect firmly.
What You Must Never Accept During a Demo
Slides instead of a live demo. The phrase “in the next release, you’ll have…” is a warning signal. If a feature is not available today in the version you would be purchasing, it does not exist for your project.
A last-minute scenario change. “We’d prefer to show you the standard interface first” generally means your scenario exposed a limitation. Hold the line.
The absence of the consultant who will implement the product. If only the account executive is present, you will never see the technical nuances. Insist that a senior certified consultant attends the demo — not just as an observer.
A demo in an overly polished “sandbox.” Ask to see the product in the exact version you will receive, not a cloud-hosted demo environment with a custom configuration staged by the vendor.
The Scoring Grid: 5 Dimensions for Objective Evaluation
After each demo, each committee member scores the vendor on five dimensions. The score is individual, on a scale of 1 to 5, then multiplied by the weighting coefficient.
| Dimension | Weighting | What is being evaluated |
|---|---|---|
| Functional coverage of the scenario | 35% | Did the product execute your scenario without workarounds? |
| Usability and ease of use | 20% | Did key users navigate without assistance? |
| Integration and API capabilities | 20% | How does it connect to your existing systems? |
| Performance and scalability | 15% | Response times, volumes, multi-site support |
| Vendor roadmap and vision | 10% | Development plan over 18–24 months |
Composite score = sum of (score × weighting) × 20 (to scale to 100)
Example: coverage 4/5 × 35% + usability 3/5 × 20% + API 4/5 × 20% + performance 4/5 × 15% + roadmap 3/5 × 10% = (1.40 + 0.60 + 0.80 + 0.60 + 0.30) × 20 = 74/100
Common trap to avoid: do not create an informal “sales rep enthusiasm” criterion. It is the most frequent bias in committees that do not use a formal grid. If the CIO or CFO takes a position publicly before scores are consolidated, everyone else’s scores drift toward theirs.
The 15 Questions to Ask During the Demo
Distribute these questions among committee members before the session. Each person owns their area and records the answers.
Functional Questions
- “Show me how you handle a customer order with a partial backorder. What happens automatically?”
- “How do you configure a two-level approval workflow with automatic delegation when the approver is absent?”
- “What is the process for correcting an invoice that has already been posted? Who can do it, and what audit trail does it leave?”
- “How do you manage a multi-currency entity with monthly close, with closing rate vs. historical rate?”
- “Show me the CFO dashboard at month-end. What is the data lag?”
Technical Questions
- “What API is available to connect our CRM? REST or SOAP? Do you have a native connector for Salesforce or HubSpot?”
- “How are roles and access rights managed by entity, with segregation-of-duties matrices?”
- “What are the RPO/RTO figures in the event of an outage? Do you have a documented BCP?”
- “How often are updates released? Can we defer an update if it falls during our year-end close?”
- “Where is our data hosted? What security certifications do you hold (ISO 27001, SOC 2, or sector-specific equivalents)?”
Questions Designed to Reveal Hidden Limitations
These are not trick questions — they reveal how mature a vendor really is on the issues that cause projects to derail.
- “Show me a client of our size and industry that has been using this feature in production for more than 12 months.”
- “In your recent projects, what percentage is standard configuration vs. custom development?”
- “If we want to switch ERP systems in three years, how do we extract our data, in what format, and on what timeline?”
- “What is your average resolution time for a critical (P1) ticket? Do you offer contractual SLAs?”
- “Can you give me three references in our sector that I can call this week — not through your sales team?”
The answers to these five questions often reveal more than two hours of demo.
After the Demo: Locking in the Comparison Before Memory Fades
The 24 Hours That Make the Difference
Memory is selective and emotional. A polished sales close can erase 90 minutes of functional limitations in the collective recollection. That is why every committee member must submit their individual scores within 24 hours of each demo, through a shared tool (spreadsheet, Notion form, or Confluence page).
The rule: no collective discussion between demos. If you are evaluating four vendors, you consolidate only after seeing the last one. Premature synthesis creates anchoring bias that contaminates subsequent evaluations.
The Synthesis Meeting
The synthesis meeting takes place after the final demo. It follows this framework:
- Each member presents their individual scores without initial justification
- Calculate composite scores by vendor
- Discuss significant divergences (individual score more than 1.5 points above or below the median)
- Review red flags (see below)
- Issue a recommendation to the steering committee
How to Handle Disagreements
In a committee of six, disagreements are normal and healthy. If the head of accounting rates functional coverage 2/5 while the CIO rates it 4/5, you need to understand the gap before blindly averaging.
Expertise-weighted voting: on functional criteria, the key user’s score counts double. On technical criteria, the technical lead’s score counts double.
The 3 Disqualifying Red Flags
Regardless of the overall score, these three situations should lead to immediate elimination of a vendor:
Red flag 1: Unable to demonstrate live a feature presented as standard. If the vendor lists a feature in its RFP response but cannot show it live during the demo, it is not available in the production release. “It is in development,” “that is a specific configuration,” “our consultant can set that up” — these answers disqualify the feature.
Red flag 2: No verifiable references in your sector. A vendor that cannot give you the name and direct phone number of two or three comparable clients you can call independently has not built the sector expertise it claims. Written testimonials on the vendor website are not a substitute for a 20-minute call with a CIO who lived through the implementation.
Red flag 3: Excessive commercial pressure or an artificially compressed timeline. “This offer is only valid until the end of the month,” “we have another prospect looking at your go-live slot” — this type of pressure is a sales technique that signals either a weak pipeline or a deliberate attempt to short-circuit your decision process. In either case, this is not a partner for an 18-month project.
Conclusion
The ERP demo is not a show — it is an evaluation tool. If you have prepared the business scenario, assembled the right committee, used the scoring grid, and asked the 15 structured questions, you emerge from this process with a documented, defensible decision. The final selection must rest on concrete evidence, not on a sense of confidence generated by a talented salesperson.
The next step is contract negotiation: 15 clauses to check before signing your ERP contract. To go deeper on selecting the implementation partner who will deliver the chosen product: How to choose an ERP integrator: scoring framework across 10 criteria.
