How to Run ERP Vendor Demos So Staff Actually Help Pick (2026 Guide)
Run ERP vendor demos your staff can trust in 2026: scripted day-in-the-life scenarios, a staff scoring panel, an anchored scorecard and a gap log for contracts.
On this page
To run ERP vendor demos that staff actually help pick, your team writes the script, not the vendor. Build it from day-in-the-life scenarios, send the same script to every finalist, and seat a scoring panel of the people who do the work. Then score each scenario live on a locked scale, and log every “that’s on the roadmap” answer as a gap.
Do that in 2026 and the demo stops being a sales show. It becomes evidence.
Key takeaways
Write the demo script yourself, from your own pain points and real transactions.
Put the people who do the work on the scoring panel, not in the audience.
Lock an anchored scorecard before the first vendor walks in.
Treat anything not shown live as a gap, and carry the gap log into the contract.
Staff who scored the demo become your strongest advocates at go-live.
A polished vendor tour shows you the best presenter. A scripted demo shows whether payroll can handle a retro step increase for your largest union without a side spreadsheet.
Many demo guides are written for manufacturers and skip fund accounting, union pay rules and procurement no-contact rules. This guide lays out a seven-step process for cities, counties, school districts and utilities. It draws on 2024 and 2025 government RFPs, a county board presentation and a 2026 state audit, so your government ERP selection rests on evidence your staff produced.
If you’re still narrowing the field, read how to shortlist ERP vendors for a city or county first.
What is a scripted ERP vendor demo?
A scripted ERP vendor demo is a session where each finalist runs the same buyer-written scenarios, in the same order and time box, often with the buyer’s own sample data. A staff panel scores every scenario. You control the agenda, the vendor drives the keyboard, and the software has to prove it handles your real work.
Government buyers already write the vendor demonstration script into their public sector ERP RFPs:
The idea isn’t new. In August 1999, GFOA’s journal Government Finance Review advised governments to set expectations early so they lead the demonstration, not the vendor, and to have vendors show only software “currently available and in production.”
Your move: if your RFP doesn’t already reserve the right to a scripted demonstration of finalists, add that clause before release.
Why vendor-controlled ERP demos mislead your team
A vendor-run demo shows the happy path with clean data. The hard days, like retro pay, grant cost transfers, reopening a closed period or union step progressions, rarely appear. Staff leave impressed, with nothing to score.
Even a vendor says the checkbox approach falls short. In a Workday blog post, the company’s vice president for government writes that demos often rely on long scripted lists focused on “checking the box” for features.
He argues instead for a day-in-the-life view and testing by the people who will use the software. KCT agrees: scripts should follow your processes, not a feature checklist.
Swipe to see all columns →
| Element | Vendor-controlled demo | Scripted by your team |
|---|---|---|
| Who sets the agenda | Vendor sales team | Your facilitator, in writing, weeks ahead |
| Data used | Vendor’s clean demo data | Your sanitized sample data |
| Order and time per scenario | Whatever shows best | Fixed order, fixed time box, same for every finalist |
| Who is in the room | Managers and IT | Staff who do the work, plus observers |
| How gaps surface | They don’t: hard scenarios get skipped | A gap logger records every skip, workaround and roadmap answer |
| What the score means | Overall impression of the presenter | How well each scenario fits your process |
Your move: tell finalists in writing that unscripted feature tours will not be scored.
Known gaps don’t go away after selection
Gaps turn into workarounds. A February 2026 Minnesota Office of the Legislative Auditor report found that calculating faculty payroll was not built into Minnesota State’s Workday system.
According to the auditor, the limitation “was known during the request for proposals process.” Minnesota State went ahead because Workday met many other requirements, and it still uses its legacy ISRS system to calculate faculty pay.
The audit does not blame any demo. The lesson is narrower: a gap known at selection carries a long-term cost, so log it and price it.
How to run ERP vendor demos in 2026: 7 steps
To run ERP vendor demos well, give your staff the script, the scorecard and the final say. The seven steps below take your ERP evaluation team from naming a scoring panel to writing every demo gap into the contract.
Build a staff scoring panel before you write the script.
Write day-in-the-life scenarios from your own pain points.
Send the same script and sample data to every finalist.
Lock an anchored scorecard before the first demo.
Run demo day as a facilitator, not an audience.
Give staff a hands-on test drive of the finalists’ software.
Debrief, reconcile scores and carry the gap log into the contract.
Step 1: Build a staff scoring panel before you write the script
The panel scores. Observers watch and give input. Leadership either attends whole sessions or stays out of scoring.
Your scorers should be the clerks, accountants, payroll specialists and billing staff who will live in the system every day. Managers and IT belong on the panel too, but not on their own.
Cochise County, AZ is a good model. Its April 2024 board presentation shows an evaluation team of seven super users (two from IT, two from HR, three from Finance), with scoring facilitated by Procurement.
A separate observation team from Courts, the Sheriff’s Office, the Treasurer’s Office and the Budget Office reviewed the script, attended the demos and gave group feedback.
Smaller agencies use the same pattern. When Superior, WI replaced its finance and HR software, GovTech reported in December 2025 that six staff from finance, payroll, HR and IT evaluated 10 proposals and then watched three vendors demo over three days.
Swipe to see all columns →
| Role | Who | What they do | Scores? |
|---|---|---|---|
| Scenario scorers | Super users for each module (AP, payroll, utility billing, budget) | Score the scenarios they own, for every vendor | Yes |
| Observers | Departments that touch the system lightly: courts, public safety, treasurer, utility field staff | Review the script, watch, flag concerns in the debrief | No |
| Facilitator and timekeeper | Project lead or selection advisor | Owns the clock, the script and the parking lot | No |
| Gap logger | One named person, every session | Records every skip, workaround and roadmap answer | No |
| Technical reviewer | IT | Covers security, integrations and hosting | Yes, technical scenarios only |
| Executive sponsor | Finance director, city or county manager | Attends full sessions or none | Optional |
Three ground rules make the panel credible (KCT rule of thumb):
Your move: name the panel and send calendar holds now, before finalists are known.
Step 2: Write day-in-the-life scenarios from your own pain points
A scenario is a real task, start to finish, under your rules. “Show us accounts payable” is a feature request. “Take this invoice from receipt to payment against a grant-funded PO, with a budget check, and show the audit trail” is a scenario.
Write scenarios with your panel, starting from your worst days. Cochise County built its script from county requirements and the pain points of its current systems, which its presentation says involved 60% manual process steps.
Boston went further and published its demo use cases inside the RFP itself. Vendors were asked to show:
Step progressions across BPHC’s 8 unions with limited manual work
A retroactive payroll costing adjustment
A cost transfer posted to a grant
Adjustments after a period is closed
Here are KCT example scenarios to adapt, not a standard:
Swipe to see all columns →
| Department | Scenario | What a pass looks like |
|---|---|---|
| Payroll | Retro pay for a union step increase across two pay periods | Calculated by the system, correct costing, no side spreadsheet |
| Finance | Post a grant cost transfer | Correct fund and grant coding, full audit trail, approval shown |
| Finance | Adjust after period close | Clear rules on who can reopen or adjust, and a log of who did |
| Purchasing | Requisition to PO to encumbrance to invoice | Budget check fires, encumbrance releases correctly |
| Utility billing | Meter read import, a mid-cycle rate change and a disputed bill | Reads kept at full precision, prorated rate, dispute tracked to resolution |
| HR | Hire into a union position | Step, pay and benefits eligibility set by rule, not by hand |
| Budget | Mid-year budget amendment | Approval chain visible, amended budget flows to department reports |
Edge cases matter more than they look. At Farmers Branch, TX, KCT pinpointed where single-gallon water-usage precision was lost (storage, calculation or export mapping), delivered an interim fix and is leading the city and its vendors toward a durable one. A good utility billing scenario makes the vendor show that export live, at the precision you need.
Your move: keep scenario counts manageable, roughly 5 to 8 per major module (KCT rule of thumb), and rank them so the must-haves get demoed first.
Step 3: Send the same ERP demo script and sample data to every finalist
Every finalist gets the identical script, in the identical order, with the same time box and the same advance notice. Include sanitized sample data so no vendor can fall back on its own polished demo data.
A useful sample set includes:
A few chart of accounts segments
Some employees with union codes
A vendor file
A handful of utility accounts
Plan the calendar early: the gap between proposals and demos is short. Boston’s RFP planned one to two days of demos per vendor, and here is how three agencies scheduled theirs:
Swipe to see all columns →
| Agency | Proposals due | Demos | Format |
|---|---|---|---|
| Ellensburg, WA | August 12, 2025 | October 2025 (planned) | Onsite |
| Sammamish, WA | October 25, 2024 | November 2024 (planned) | Virtual |
| Boston Public Health Commission | March 21, 2025 | April 21 to May 2, 2025 (planned) | Virtual |
Write the script before proposals arrive. Either format works:
Record sessions if procurement rules allow, so scorers can rewatch disputed scenarios. Buying through a cooperative contract or piggyback? First check other agencies, the state and associations for existing contracts, then still run scripted demos with your own panel before you commit.
Your move: send the script with at least a few weeks of prep time (KCT rule of thumb). Require each vendor to confirm in writing that what it shows is generally available today.
Step 4: Lock an anchored ERP demo scorecard before the first demo
Score each scenario, not each vendor’s overall impression. Use an anchored demo scoring rubric so a “3” means the same thing to payroll as it does to IT, and lock it before demo one.
Cochise County weighted its scripted demonstration at 15% of the total score, labelled “Ease of Use & Process Fit.” Boston’s evaluation criteria also name User Experience & Usability and User Training.
Only staff can judge ease of use. For the full weighting matrix, see our shortlisting guide.
Here’s the ERP demo scorecard KCT uses as a starting point.
Swipe to see all columns →
| Score | Label | What the panel saw | Log as gap? |
|---|---|---|---|
| 4 | Out of the box | Shown live, standard, matched our process | No |
| 3 | Configured | Shown live, with configuration the vendor showed or described specifically | No |
| 2 | Workaround | Shown, but with an extra manual step or side process | Yes |
| 1 | Described only | Talked through but not shown, or needs a third-party product | Yes |
| 0 | Not available | Not offered, or “on the roadmap” | Yes |
Each scorer’s sheet should capture the same fields for every scenario:
Scenario ID and vendor
Score from 0 to 4
Ease-of-use note in plain words (“six clicks to approve,” “had to leave the screen”)
Gap yes or no
Follow-up question for the vendor
Your move: hold a 30-minute calibration session where scorers rate a sample scenario together before demo week. If scores split widely, fix the anchors now.
Step 5: Run demo day as a facilitator, not an audience
Your facilitator owns the clock and the script. The vendor drives the keyboard. Staff score.
Procurement rules shape the day too. Ellensburg’s RFP instructs proposers not to contact any other city personnel between proposal submittal and award, and warns that breaking this rule may get a proposal rejected.
Route every vendor question through procurement. Tell panel members to decline side conversations, lunch invitations and follow-up sales calls.
House rules for demo day (KCT rule of thumb):
Open with the agenda and the scoring rules. No slide decks past 10 minutes.
Keep scenario order fixed. If a vendor jumps ahead, the facilitator pulls them back.
Park off-script questions and come back to them at the end.
The gap logger writes down every “we can do that in the next release.”
Scorers fill in their sheets during or right after each scenario, while it’s fresh.
No group discussion until every individual score is in.
Your move: print a one-page run sheet for the facilitator with times, scenario IDs and the scorers assigned to each.
Scripting, training a panel and facilitating three vendors is a lot for a finance team that’s also closing the month. KCT’s ERP Consulting & Selection Advisory team writes scenarios with your staff, runs demo days and keeps vendors on script. KCT is not a Tyler partner or reseller and takes no referral fees from Tyler.
Step 6: Give staff a hands-on test drive of the finalists’ software
Watching isn’t using. For your last two finalists, give panel members a sandbox or a supervised hands-on session so they can run two or three of their own scenarios.
The same Workday blog post recommends a hands-on test drive by the people who will actually use the software, and suggests reserving it for the final vendors before selection.
Your move: request sandbox access in the RFP or the finalist letter, and score the test drive on the same 0 to 4 scale.
Step 7: Debrief, reconcile scores and carry the gap log into the contract
Collect individual scores first, then discuss the outliers. A 4 and a 1 on the same scenario means someone saw something the others missed. Document the reasoning for your council or board.
Then treat the gap log as contract material. The Minnesota OLA audit shows how long a known gap can last: Workday went live for finance and HR/payroll in July 2024, and as of the February 2026 report, the legacy system was still calculating faculty pay.
The same report says Minnesota State is still weighing options to close that gap, including buying a separate product or building a new internal system. Every one of those options costs money the original contract didn’t cover.
So every gap should land in writing: what will be configured, by whom, by when and at what price. Our guides on avoiding hidden costs in an ERP vendor contract and writing a public sector ERP implementation SOW show how to turn demo promises into enforceable deliverables.
Your move: turn every score of 0 to 2 into a line item with one of three outcomes:
Accept the gap and document the workaround.
Require the fix in the SOW.
Price it as a change order before you sign.
Common ERP demo mistakes to avoid
The most common ERP demo mistakes hand control back to the vendor: letting it set the agenda, scoring impressions instead of scenarios, and accepting roadmap answers.
Swipe to see all columns →
| Mistake | Why it hurts | Fix |
|---|---|---|
| Letting the vendor set the agenda | You see strengths, never weaknesses | Send your own script and score only scripted scenarios |
| Managers score while end users watch | Ease of use gets judged by people who won’t use it daily | Make super users the scorers |
| Scoring overall impressions | The best presenter wins | Score each scenario on an anchored scale |
| Accepting roadmap answers | Future features become your workaround | Score roadmap items 0 and log them |
| Skipping the debrief and gap log | Gaps never reach the contract | Reconcile scores and turn gaps into SOW lines |
| Talking to vendors outside procurement | Can breach no-contact rules like Ellensburg’s | Route every question through procurement |
How staff-led ERP vendor demos pay off after go-live
Staff-led ERP vendor demos pay off because panel members and observers become your future champions. They already know why the system was picked, what it does well and where the gaps are.
Cochise County made that link explicit: its board presentation lists starting the people change process as an outcome of involving observers in the demos.
Adoption still takes work after launch. Our guide on managing staff resistance to new ERP software covers how to build digital champions once the system is live.
Your move: invite panel members to become super users and trainers during implementation, and share a summary of the final scorecard with all staff.
FAQ
What is a scripted demo in ERP selection?
A scripted demo is a vendor presentation that follows a buyer-written script of real business scenarios instead of the vendor’s standard tour. Every finalist runs the same scenarios, in the same order, ideally with the buyer’s sample data. Staff score each scenario, so the result reflects process fit rather than presentation skill.
How long should an ERP vendor demo be?
ERP vendor demos for a full finance and HR system can take one to two days per vendor. Boston’s 2025 RFP planned one to two days. Smaller scopes can fit into one day, so scale the time to your modules and scenarios (KCT rule of thumb).
Who should attend ERP vendor demos?
ERP vendor demo attendees should include scoring super users from each module, observers from departments that touch the system lightly, a facilitator, a gap logger and IT for technical scenarios. The same scorers should attend every vendor’s session for their scenarios. Executives should attend whole sessions or stay out of scoring.
How many vendors should you invite to an ERP demo?
Two to three finalists is a common range. Boston planned to demo its top two to three vendors, Cochise County demoed two and Superior, WI demoed three. More than three tends to wear out your panel (KCT rule of thumb).
Should you give ERP vendors your own data for the demo?
Your own sanitized sample data is the best way to see real fit, so yes, give it to vendors. Send a small set with the script, and never include personal data such as Social Security numbers or real bank details.
How do you score an ERP vendor demo?
An ERP vendor demo is scored scenario by scenario on an anchored 0 to 4 scale, where 4 means shown live out of the box and 0 means unavailable or on the roadmap. Scorers rate individually before any group discussion. The demo score then rolls into the total, as with Cochise County’s 15% weight.
How do you tell real ERP functionality from roadmap promises?
Real functionality is shown live, in a version that is generally available today. Anything described but not shown, or promised for a future release, is a gap. Ask vendors to confirm in writing that what they demoed is generally available, and log every roadmap answer so it reaches the contract.
Let your staff pick the system they will run
The demo is the one moment when the people who’ll run the system for a decade get to test it before you sign. Script it well and they decide on evidence, not charm.
Don’t wait for proposals: name your panel and start writing scenarios now.
If you’d like help, KCT’s ERP Consulting & Selection Advisory team writes scenarios with your staff, facilitates demo days and turns the gap log into contract language. KCT is both an advisor and an implementer, so we can support you at any point, from the first scenario to go-live.
Scope depends on your modules, departments and stakeholders, so most agencies start with an assessment. Contact KCT to talk through your selection.