5 Red Flags in ERP Vendor Demos (And What to Ask Instead)

Quick answer: Five red flags repeat across nearly every ERP vendor demo: a pre-cached demo environment that won't touch live data, the "yes to everything" response on customisation, the senior bait-and-switch (senior on demo, juniors on delivery), the happy-path-only demonstration that never shows error handling, and the roadmap hand-wave for missing capability. Each one is a specific signal of risk — and each has a specific counter-question that exposes the truth.

Most ERP vendor demos are theatre. The slides are polished. The presenter is confident. The system always works. And ninety days into the implementation, you discover that the system you bought is not the system you saw.

The disconnect is not because vendors lie. It is because demos are optimised to show capability under perfect conditions — and your business does not operate under perfect conditions. The buyers who avoid expensive selection mistakes are the ones who break the demo on purpose. They probe the gaps that polished presentations are designed to hide.

This guide covers the five red flags that repeat across nearly every ERP vendor demo — and the specific questions that expose them. Save this for your next vendor call. You can also pair it with our ERP selection checklist of 17 questions for a complete pre-purchase due-diligence pack.

Red Flag 1: The Pre-Cached Demo Environment

What to watch for: The vendor logs into a sparkling demo tenant with clean master data, perfectly matched transactions, and no error states. Every screen loads instantly. Every search returns the expected record. The bank reconciliation matches 100% on the first pass. Nothing ever breaks.

Why it's a red flag: That demo environment has been curated over years. It is not a representation of your business — it is a representation of the vendor's marketing team's idea of your business. The real system, populated with your real data, will not behave that way. Performance will be different. Edge cases will surface. Configurations that look one-click in the demo will turn out to require development.

What to ask instead:

"Can you load 50 of our actual customer records and 100 of our actual products into this demo session right now? We have a CSV ready."
"Can you run a bank reconciliation against our last statement export, with the real volume of unmatched transactions we typically have?"
"Can we have read-only access to this demo environment for the next 48 hours so we can explore it ourselves?"

What a good response looks like: A confident vendor will accept the live-data challenge. They may need 15 minutes to import, or they may schedule a second session, but they will agree in principle. A vendor who refuses, deflects, or insists on running through their script-only demo is signalling that the system performs differently outside the controlled environment.

This is doubly important for platforms with widely documented data-handling limitations. The patterns are covered in our data migration guide, and they routinely surprise buyers who have only seen pre-built demo tenants.

Red Flag 2: The "Yes to Everything" Answer on Customisation

What to watch for: You raise a requirement that does not appear in the standard product. The vendor smiles and says "yes, we can configure that". You raise a second, more unusual requirement. Same answer. By the third, you realise no requirement has triggered a "that would require custom development" or "that is genuinely outside the platform" response.

Why it's a red flag: Every ERP has limitations. A vendor who never acknowledges them is either (a) glossing over the line between configuration and development, or (b) selling you a future of heavy customisation. Both end the same way: an implementation that runs 50% over budget, an upgrade path that becomes increasingly fragile, and a system that costs more to maintain every year.

The implementation partners who say yes to everything are the ones who build technical debt rather than sustainable systems. Our guide on ERP customisation and how much is advisable covers why this matters so much for 5-year TCO.

What to ask instead:

"What exactly is the difference between configuration and development in your platform? Where is the line?"
"Show me the specific configuration you would use for this requirement, live. If it requires development, tell me now — that is a different cost category and a different upgrade risk."
"Can you give me an example of a customer requirement that you have refused, or strongly pushed back on, in the last 12 months?"

What a good response looks like: A credible vendor (or partner) will articulate the boundary clearly. Configuration changes settings within the platform's intended flexibility; customisation writes code. They should be able to name a recent example where they pushed back on a customer request — because over-customisation creates risk for the vendor's reputation, not just the buyer's TCO.

A "yes to everything" vendor is selling you a maintenance liability dressed up as flexibility. The questions in our partner vs vendor-direct guide are designed to expose exactly this.

Red Flag 3: The Senior Bait-and-Switch

What to watch for: The demo is presented by the senior partner, the practice lead, or the sales engineer with twenty years of experience. They are excellent. They answer every question crisply. Halfway through, you realise you have not been told who will actually staff your implementation if you sign.

Why it's a red flag: This is one of the most common, and most expensive, patterns in ERP procurement. The senior consultants you meet in the sales process are not the consultants who will deliver your project. The delivery team will be more junior, less experienced on your specific platform version, and possibly based in a different country and timezone. The implementation quality you priced in your evaluation is not the quality you will receive.

This is so common that it is the single biggest reason for the gap between vendor-quoted timelines and the realistic timelines covered in our implementation timeline guide. The senior on the demo could deliver in 6 months; the delivery team they staff with will need 10–12.

What to ask instead:

"Who specifically will be on our project? Names, roles, individual implementation counts on this platform."
"Can we meet that team — not just the partner who presented today — before contract signing?"
"What is your policy if a named team member rolls off the project mid-implementation? Replacement timeline? Knowledge transfer?"
"Get the named delivery team in writing as a schedule to the SOW."

What a good response looks like: A credible partner names the actual project lead, senior consultant, and core team. They put the names in the SOW. They agree to a meet-and-greet before signing. They have a clear policy on team continuity — and they are willing to commit to it contractually.

If the answer is "we will assign the best available team at the time of kickoff", you are buying a project at a quality you cannot verify. Walk away or insist on contractual minimums for consultant experience.

Red Flag 4: The Happy-Path-Only Demo

What to watch for: The demo flows beautifully. Sales order is created. Inventory is reserved. Invoice is issued. Payment is reconciled. The month closes. Every transaction works on the first attempt. Nothing fails. No user gets a permission error. No integration times out. No data validation rejects a record.

Why it's a red flag: Real businesses do not run on happy paths. Real businesses run on a thousand small exceptions per month: customers who change their order after the invoice goes out, suppliers who send three lines instead of the seven on the PO, bank statements that import with corrupted character encoding, eCommerce orders that fail to sync because a SKU was renamed yesterday. The quality of an ERP is determined entirely by how well it handles exceptions, not how smoothly it handles the happy path.

A demo that never shows an exception is a demo that hides where the system is weakest. Our guide on why ERP implementations fail covers how often this exception-handling gap becomes the post-go-live crisis that nobody anticipated.

What to ask instead:

"Show me a bank reconciliation with 50 unmatched transactions. How does the system suggest matches? What does the manual workflow look like?"
"Show me what happens when an EDI order arrives with a SKU that does not exist in our catalogue."
"Show me what happens when an inventory transaction posts in a closed accounting period."
"Show me the audit trail of a transaction that has been amended four times. Who changed what, and when?"
"Show me what a user sees when they hit a permission denied error mid-workflow."

What a good response looks like: A capable system has explicit, designed-in workflows for exceptions. The vendor can walk you through the matching engine, the exception queue, the supervisor review screen, the override audit log. A weak system silently fails or requires database-level intervention to recover. You want to see the exception handling before you sign, because that is where you will live after go-live.

This is also the area where the implementation traps documented per vendor most often live — every platform has specific patterns of "what fails first" that you should know before you commit.

Red Flag 5: The Roadmap Hand-Wave

What to watch for: You raise a capability gap. The vendor's first answer is "that is on our roadmap for the next major release". You ask for specifics. The answer becomes vaguer: "we expect to deliver in the H2 release", "it is in development now", "our product team has prioritised it". No date you can rely on, no commercial commitment, no specifics on which features will land first.

Why it's a red flag: ERP vendor roadmaps are aspirational. Some features ship as promised; many slip; some get deprioritised entirely when a larger customer requests something else. Buying an ERP on the strength of roadmap promises is buying a future capability that may never arrive — and you have no contractual recourse if it does not. The capability gap you are trying to close today is still going to be a gap in 18 months, just with sunk implementation cost on top.

This is especially common with platforms in transition (legacy products being sunsetted in favour of cloud successors, products being repositioned for a new market segment, products that are catching up to a competitor on a specific capability). Roadmap claims accelerate when the vendor is losing deals on the gap.

What to ask instead:

"Is this capability available today, or am I being asked to buy on roadmap commitments?"
"Can you commit contractually to a delivery date, with remedies if the capability does not land on time?"
"Can I speak to a beta customer who is already using this capability?"
"If we sign today and this capability slips by 12 months, what is your remediation? Credits? Refund? Free professional services?"
"What is the historical roadmap-slip rate for this product line? How many features delivered on the originally announced date in the last 24 months?"

What a good response looks like: A confident vendor will either show you the capability today, point you to a beta customer using it, or offer a contractual remedy if it slips. They will be transparent about roadmap risk. They will tell you which features are firm commitments versus aspirational targets. They will not ask you to bet your implementation on the marketing slide.

If the answer to "can we have a contractual commitment" is no, you are buying current capability, not future capability. Price the deal on what exists today.

A Short Note on Sales Pressure

There is a sixth pattern worth flagging briefly, because it sits underneath all five above: end-of-quarter discount pressure. The "this pricing expires Friday", "we only have one implementation slot left this quarter", "our finance team needs the contract by month-end" — all of these are sales mechanics, not commercial reality. ERP vendors will negotiate at any time of year. Discounts are deeper at quarter-end because quotas are real, but the offer does not actually expire. A vendor who manufactures urgency is signalling that they are more interested in closing your deal than in fitting your business.

Take the time. Do the demo properly. Use the questions in this guide. Cross-reference with our vendor due-diligence checklist and the partner evaluation guide. The deal will still be there in 30 days. The mistakes you avoid will save you 30 months.

Frequently Asked Questions

What are the most common red flags in ERP demos?

Five patterns repeat across nearly every vendor demo: pre-cached demo environments that won't touch live data, "yes to everything" responses on customisation, senior consultants on demos with junior teams on delivery, happy-path-only demonstrations that never show error handling, and roadmap promises for missing capability. Each is a specific signal of risk. Each has a counter-question that exposes whether the system is actually fit for the buyer's situation.

How do I evaluate an ERP demo properly?

Bring your own data, your own scenarios, and your own exception cases. Insist on a live load of sample records, a side-by-side comparison of your real workflow against the system's standard workflow, and explicit demonstration of exception handling and error recovery. Get the named delivery team in writing before you sign. Ask for a contractual commitment on any capability that is not already in the live product.

What questions should I ask in an ERP demo?

The most diagnostic questions are: (1) Show me the system handling 50 unmatched bank transactions; (2) Show me what happens when a transaction posts to a closed period; (3) Who specifically will be on our project, and can we meet them today; (4) What is the difference between configuration and development in this platform, and where is the line; (5) Can you give me a recent example where you refused a customer customisation request. These five expose more about real fit than any list of feature questions.

Should I bring my own data to an ERP demo?

Yes — and prepare it in advance. A CSV of 50 customer records, 100 products, and a recent bank statement export is enough. A vendor who refuses to load it is hiding something about how the system actually performs at your scale. A vendor who accepts the challenge is showing confidence in the product. The willingness alone is one of the strongest signals you will get during the evaluation.

How long should an ERP demo last?

The first demo, scoped to your specific scenarios with your own data, should run 90–120 minutes. A second session covering exception handling, integrations, and the delivery team meet-and-greet adds another 60–90 minutes. Anything shorter than 90 minutes for an initial demo is a marketing pitch dressed up as a demonstration — useful for shortlisting at most, not for procurement decisions.

Why do ERP vendors avoid showing error handling?

Because error handling is where most ERPs are weakest, and the gap between platforms is widest. Happy-path flows look broadly similar across NetSuite, Business Central, Acumatica, Odoo, and SAP. Exception handling, audit trails, override workflows, and recovery from integration failures are where the differentiation lives — and where the implementation pain hides. A vendor who avoids showing this is a vendor who knows the comparison would not flatter them.

Can I get a free trial of an ERP before buying?

For some platforms, yes. Odoo, Zoho, Xero, and QuickBooks Online all offer free trials with limited functionality. For mid-market platforms (NetSuite, Business Central, Acumatica, Sage Intacct) a trial is rare; instead, ask for a 48-hour read-only access pass to the demo tenant so you can explore the system yourself. Enterprise platforms (SAP S/4HANA, Oracle Fusion) do not offer trials — the equivalent is a paid Proof-of-Concept engagement.

How ERPLenz Can Help

The questions in this guide will expose vendor weaknesses, but they will not tell you which vendors are worth demoing in the first place. That work — translating your business profile into a calibrated shortlist with risk-flagged candidates — is what the ERPLenz assessment does.

Walking into a demo with a vendor-agnostic shortlist that already knows which platforms fit your operational profile, your budget, and your industry changes the dynamic entirely. You stop being a prospect being sold to. You start being a buyer running a structured evaluation.

Get your free ERP shortlist before your next vendor call →

This guide is the floor of your demo evaluation, not the ceiling. Which red flags will hit your specific deployment depends on your industry, scale, and integration profile — exactly the variables a calibrated assessment surfaces.