The ERP demo is theater. Here’s what to demand instead.

Every ERP demo follows the same script because it’s built to do the same thing. Close the deal.

You sit through three of them and they blur together. Same friendly sales engineer. Same polished sandbox. Same five screens that walk you through the order-to-cash story you sketched on the discovery call. The demos look identical because they’re optimized for the same outcome, and that outcome is not your decision quality.

The system probably can do most of what you saw. The problem is that what you saw is the smallest possible slice of what you’re actually evaluating.

What the demo hides

Demos run on data that was hand-curated to look right. Customer records have full addresses. SKUs have proper categories. Inventory matches the bin. Yours doesn’t.

Demos skip the parts of the system that break. The two-day batch job that quietly fails on the first of the month. The custom field that doesn’t replicate to the BI tool. The integration that handles 10,000 records but chokes at 50,000. None of that is on the screen during a 90-minute presentation.

Demos show features in isolation. A demo of inventory management is not a demo of inventory management plus the integration to your warehouse management system plus the EDI feed to your three biggest customers. Each piece works on its own. Together they may not.

And demos are run by people whose job is to close. Not by the implementation team that’s actually going to deliver. The relationship you build during a demo is with someone you’ll never see again.

What to demand instead

The demo as a deciding event is broken. The demo as a screening event is fine. Use it to disqualify obviously wrong fits, then move to the part that actually tells you something.

What you actually want is harder to ask for, which is why most companies don’t.

Bring your own dirty data. Export a slice of your real customer master, real inventory file, real chart of accounts. Anonymize it if you have to. Send it ahead and ask the vendor to load it into the sandbox before the next session. If they push back on this, that’s your answer.

Ask them to do the ugly part. The demo always shows the happy path. Ask for a closing process. A year-end roll. A handover from sales to operations. The kind of multi-step process that touches three modules and three teams. The cracks show up at the seams.

Watch them break something. Ask them to skip a required field, enter a duplicate, post a journal to a closed period. How does the system tell the user? How does the user recover? You learn more from one error message than from the rest of the demo combined.

Get a sandbox login for two weeks. Real evaluation needs hands on the keyboard, not eyes on a screen. Two of your power users, two weeks, no babysitting. They’ll find more in a week than you’ll find in three demos.

Ask the implementation team to demo. Not the AE, not the sales engineer. The person who’s going to be on your project. They demo differently. They use language that matches your actual deployment, not the marketing deck.

How to read references properly

Every vendor will hand you three references. Every reference will say nice things. The trick is asking the questions that get past the script.

Don’t ask “how do you like the system?” They liked it enough to take the call. Ask:

• What have you customized? How many things? Why?
• What do you hate about it? Be specific.
• What would you do differently if you were selecting again today?
• How did the implementation differ from what was scoped at the SOW?
• Who was your partner? Are you still happy with them?
• How long until you actually trusted the reports coming out of the system?

The good references will answer all of these honestly. The bad references will hedge. Both signals are useful.

The walk-away signal

Any vendor who refuses to demo with your data is hiding something. It might be that the system genuinely can’t handle messy real-world data without significant configuration. It might be that the AE doesn’t want to risk an unscripted demo. Either way, you’re looking at a problem you’ll inherit on day one of implementation.

The vendors who say yes to a real evaluation are showing you something about how they treat customers. The ones who say no are also showing you something.

A 90-minute demo decides nothing. A two-week sandbox with your own data decides almost everything.