TL;DR
- ERP vendor demos are designed to impress, not to expose weaknesses. Structured evaluation questions do the job demos cannot.
- The 12 questions in this guide cover: total cost transparency, implementation quality, UK compliance, data ownership, reference customers, support responsiveness, product roadmap, scalability, customisation risk, integration capability, go-live approach, and exit terms.
- The implementation partner is as important as the software. A well-implemented mid-tier system will outperform a poorly implemented premium one every time.
- Never evaluate on the demo alone. Send your requirements document in advance, run scenario-based demonstrations, and speak directly to reference customers who have gone live in the last 12 months.
- If a vendor struggles to answer any of these questions clearly, that difficulty is itself useful information.
You have done the research. You have a shortlist of three or four ERP vendors. You have sat through the demos and they all looked reasonably impressive, which is exactly what they were designed to do.
Here is the problem: ERP demos are rehearsed. The vendor controls the data, the workflow, and the sequence of what you see. They show you the system at its best, on scenarios they have practised hundreds of times, using a configuration that has been polished specifically for the demo environment. You are not seeing the rough edges. You are not seeing what happens when something goes wrong, or when your specific business process does not map cleanly to the system’s assumptions.
That is why evaluation questions matter. The right questions shift the conversation from “look what we can do” to “show me specifically how you handle our situation.” They expose capability gaps that polished demos hide. And the way a vendor responds to hard questions tells you a great deal about what the relationship will be like after you sign the contract.
Here are the 12 questions every IT Manager and CFO should ask before committing to an ERP vendor.
1. Can you give me a written quote that covers everything, not just the licence?
This is where you find out whether a vendor is being straight with you.
Ask for a written cost breakdown that includes: the software subscription or licence for years one, two, and three; implementation fees broken down by workstream; data migration as a separate line item; training; integrations with the specific systems you use; and ongoing support. Then ask explicitly: what is not included in this quote?
A vendor who cannot or will not produce a detailed written cost breakdown before contract signature is not a vendor you should trust with a multi-year ERP commitment. You need to know what you are buying before you buy it, and “pricing depends on your requirements” is an acceptable answer during early conversations, not during final evaluation.
Watch for annual price escalation clauses buried in the contract. A 7% annual increase on a £25,000 subscription adds up to more than £9,000 of additional spend over five years, above the original commitment. Know what you are signing.
2. Who will actually deliver our implementation, and can we meet them?
The sales team is not the implementation team. This is one of the most important distinctions in ERP procurement, and businesses that fail to make it often find themselves surprised after contract signature.
Ask to meet the consultant or project manager who will lead your implementation. Ask about their background: how many similar projects have they delivered? In your sector? In the last 12 months? Ask what happens if that person leaves the vendor or partner during your project. What is the continuity plan?
Some ERP vendors sell the software and then subcontract implementation to a partner network of varying quality. That is not inherently wrong, but you need to know who is doing the work and evaluate them directly, not just the software company.
A confident, credible implementation team will welcome this conversation. A vendor who deflects it or cannot name the people who will work on your project is worth treating with caution.
3. Show us how you handle our specific process, not your demo data.
This is less a question and more an instruction, but it belongs in every evaluation.
Before any demonstration, send the vendor a set of three to five scenarios drawn from your actual business. Be specific. Not “show us the purchase order workflow” but “show us how a purchase order for goods in USD from a US supplier is raised, approved by two signatories above £10,000, received into our Birmingham warehouse, and matched to the invoice with a three-way match.”
That level of specificity exposes whether the system genuinely handles your process or whether the demo is papering over gaps. If the vendor asks to use their own data instead of yours, ask why.
The scenarios you choose should reflect the processes that are most critical, most complex, or most likely to differ between systems. Routine tasks will work in almost any ERP. The edge cases and industry-specific workflows are where systems diverge.
4. Is your system Making Tax Digital compliant, and what does that actually mean?
For any UK business, MTD compliance is a hard requirement, not a differentiator. Your ERP must be able to submit VAT returns digitally to HMRC without a manual workaround or a third-party bridging tool.
But ask beyond the headline. MTD for VAT has been mandatory for most UK businesses since 2022. MTD for Income Tax (MTD ITSA) is rolling out from April 2026 for self-employed individuals and landlords with income above £50,000, with broader expansion to follow. Ask the vendor whether their system is built for the full MTD journey or whether it currently covers VAT only.
Also ask: is the system listed as MTD-compatible software on HMRC’s own recognised software list? Any legitimate UK ERP vendor should be able to confirm this. If they describe MTD compatibility as a feature rather than a basic compliance requirement, that is worth noting.
5. Who owns our data, and what happens to it if we leave?
This question makes some vendors uncomfortable, which is precisely why you should ask it.
Your data is one of your most valuable business assets. Customer records, transaction history, financial data, employee records. You need absolute clarity on three things: where it is hosted (UK, EEA, or elsewhere, and what the data sovereignty implications are for UK GDPR), who has access to it, and what happens to it if you terminate the contract.
A vendor should be able to confirm that you own your data, that you can export it in a usable format (not a proprietary file type that only their system can read), and that it will be deleted from their servers after a reasonable period following contract termination. If the answer to any of these is vague, treat it as a red flag.
Data portability is also a practical question. If you ever need to switch ERP systems, a clean data export in a standard format (CSV, XML, or equivalent) is the difference between a manageable migration and a painful one. Ask to see a sample data export from a live customer environment.
6. Can we speak to three reference customers who went live in the last 12 months?
Not case studies. Not testimonials on the website. Actual reference customers you can call and ask direct questions.
Specifically, ask for references from businesses of similar size to yours, in a similar sector, who have implemented the same or similar modules. A reference customer from a very different industry or a much larger business is not going to tell you what you need to know about your specific situation.
When you speak to references, ask them: did the implementation come in on time and on budget? Were there capability gaps discovered after go-live that were not flagged during the sales process? How quickly does the support team respond when something goes wrong? If they were choosing again, would they choose the same vendor and the same implementation partner?
A vendor who cannot provide reference customers, who provides references that do not match your profile, or who tries to redirect you to written case studies instead of live conversations is not inspiring confidence. References are the closest thing you will get to an unfiltered view of the reality behind the demo.
7. What does your support model look like after go-live, specifically?
“We offer comprehensive post-go-live support” is not an answer. Push for specifics.
What are the support hours? Is support available Monday to Friday during UK business hours only, or is there weekend cover? What is the target response time for a critical issue that is blocking operations? What is the escalation path if your first-line contact cannot resolve the problem?
Ask whether the support team is based in the UK or offshore. Ask whether your implementation consultant remains available for questions in the months after go-live or whether you are handed off to a generic helpdesk. Ask how the vendor handles bugs or system issues discovered after go-live: are they fixed in a patch, queued for the next release, or classified as configuration issues that fall outside the support scope?
Support quality is very difficult to assess before you need it. The questions above will not give you a guarantee, but they will help you compare vendors on something more concrete than a promise.
8. How does the system handle our specific industry requirements?
Generic ERP systems can be configured to approximate almost anything. But there is a significant difference between a system that natively supports your industry’s processes and one that has been heavily configured to work around gaps.
If you are a UK food manufacturer, ask specifically about batch traceability, expiry date management, allergen declaration workflows, and recipe management. If you are a construction business, ask about quantity surveying, job costing, subcontractor management, and CIS (Construction Industry Scheme) tax handling. If you are a distribution business, ask about multi-site warehouse management, route planning, and automated replenishment.
Ask the vendor to show you, not tell you, how they handle these requirements. Ask whether the functionality is native to the platform or delivered through a third-party add-on. Add-ons have their own update cycles, their own support teams, and their own pricing. A system that requires multiple add-ons to handle your core workflows is a system with a higher long-term maintenance cost and more points of failure.
9. What does your product roadmap look like, and how do customer requirements influence it?
You are not just buying software for today. You are entering a relationship with a vendor whose product decisions will affect your business for the next five to ten years.
Ask what major developments are planned in the next 12 to 24 months. Ask whether the roadmap is publicly available or shared with customers. Ask how the vendor decides what to build: is it driven by a small number of large enterprise customers, or is there a mechanism for SMBs and mid-market businesses to influence the product direction?
Also ask what happens to your configuration and your data when the vendor releases a major update. For cloud ERP, updates should be automatic and backward-compatible. If a major update requires significant reconfiguration or breaks existing integrations, that is a significant hidden cost. Ask whether this has happened before and how the vendor handled it.
10. What integrations do you have pre-built, and what does custom integration cost?
Almost every UK business needs their ERP to connect to something else: their bank, their e-commerce platform, their payroll bureau, their CRM, their shipping carrier, or their sector-specific tools.
Ask the vendor for a complete list of pre-built integrations and confirm that the specific systems you use are on it. Pre-built integrations are maintained by the vendor and included in the subscription. Custom integrations need to be built, tested, and maintained, and they carry a cost every time either system updates.
For your most critical integrations, ask to see them demonstrated in the evaluation. An integration that exists on paper but has not been tested recently with the current version of both systems is not a reliable integration.
Also ask: what is the API access model? If you need to build a custom integration in the future, can you do it using documented, stable APIs, or does every integration require vendor involvement at a day rate?
11. How do you approach go-live, and what is your rollback plan if something goes wrong?
A vendor’s go-live methodology tells you a lot about how much they have learned from previous projects.
Ask whether they recommend a phased go-live (module by module or department by department) or a big bang approach (everything live simultaneously). Ask how they have handled go-live failures in the past and what support is available in the first few weeks after launch.
Ask specifically: what is the rollback plan if a critical issue emerges after go-live? Is it possible to revert to the previous system, and if so, for how long and under what conditions? Not every vendor has a clear answer to this, but asking it reveals how thoroughly they have thought through the risk.
Also ask about parallel running: the practice of operating both the old and the new system simultaneously for a period after go-live, comparing outputs for accuracy before fully committing to the new system. For finance and payroll, this is standard practice. A vendor who discourages it without a good reason is prioritising a clean sign-off over your risk management.
12. What are the contract exit terms, and what notice period do you require?
Read this before you sign anything, not after. But also ask about it during evaluation, because the answer tells you something about how the vendor thinks about the relationship.
A vendor confident in the quality of their product and implementation will offer reasonable exit terms. A vendor who requires very long notice periods, charges significant exit fees, or makes data export difficult is building lock-in into the contract rather than earning renewal through service quality.
Ask specifically: what is the minimum contract term? What notice is required to terminate? What is the cost of early termination? What happens to your data within 30 days of contract end? Is data export included in the offboarding process at no additional charge?
These questions are not about planning to leave. They are about understanding what you are committing to, which is exactly what any CFO should know before signing a multi-year contract.
How to Score Your Vendor Evaluation
With 12 areas to assess, you need a consistent way to compare your shortlisted vendors. A simple scoring approach works well.
For each question or area, score the vendor from 1 (poor response, concern raised) to 5 (strong response, confident). Weight the areas that matter most to your business more heavily. UK compliance, data ownership, and implementation quality are rarely less than critical. Product roadmap and integration capability matter more for some businesses than others.
Total the weighted scores across all 12 areas. The vendor with the highest score is not automatically the right choice, but it gives you an objective basis for the decision that you can present to your board without it looking like a gut feeling.
Combine the scoring with direct reference conversations and a written cost breakdown from each vendor. If one vendor scores significantly lower on the evaluation but significantly cheaper on cost, you have a conversation worth having with your CFO about whether the gap is worth the saving.
How Blue Lotus 360 Approaches Vendor Evaluation
We do not shy away from these questions. Every one of them.
Blue Lotus 360 is an AI-powered cloud ERP platform built for UK SMBs and mid-market businesses across manufacturing, distribution, construction, services, retail, and more. The platform covers Finance and Accounting, Procurement, Inventory and Warehouse Management, Manufacturing, HR and Payroll (PAYE, RTI, auto-enrolment), Sales Force Automation, POS, and Project Management from a single integrated system.
For UK compliance: MTD-compatible, listed on HMRC’s recognised software list, with GDPR-compliant data hosting and a clear data portability policy. For implementation: dedicated project leads, scenario-based demonstrations, and reference customers available for direct conversations. For support: UK-based team with clear SLAs and post-go-live continuity built into every engagement.
Book a free consultation at bluelotus360.com/uk/ and bring your hardest questions. That is what the conversation is for.
Frequently Asked Questions
What is the most important question to ask an ERP vendor?
If you can only ask one, ask to speak to three reference customers who went live in the last 12 months in a similar business to yours. Reference conversations give you unfiltered access to the reality behind the demo and the sales pitch. Nothing else comes close for revealing the gap between what a vendor promises and what they actually deliver.
How do you evaluate ERP vendors fairly when they all look similar in demos?
Run scenario-based demonstrations using your own business processes, not vendor demo data. Send your requirements document in advance and ask the vendor to respond in writing before the demo. Score each vendor against the same criteria using a weighted matrix. This removes the bias of recency (whichever demo you saw last), presentation style, and the charm of the sales team, and replaces it with something you can actually compare.
What is an ERP RFP and do I need one?
An RFP (Request for Proposal) is a formal document sent to vendors asking them to respond to your requirements and provide a detailed proposal including pricing, implementation approach, and references. For larger, more complex ERP projects, a formal RFP process is valuable because it forces vendors to respond to the same set of criteria, making comparison easier. For smaller businesses evaluating two or three vendors, a structured requirements document and the evaluation questions in this guide can serve a similar purpose with less administrative overhead.
How long should an ERP vendor evaluation take?
For a thorough evaluation of three to four vendors, allow six to ten weeks. This covers: two to three weeks for requirements documentation and initial research; two to three weeks for demonstrations and written responses; two weeks for reference conversations, cost comparison, and contract review. Compressing this process to save time almost always results in a decision made on incomplete information, which is one of the primary causes of ERP implementation problems.
Should we use an independent ERP consultant to help with vendor evaluation?
For mid-market and larger businesses evaluating complex or high-value projects, an independent ERP consultant can add real value. They bring market knowledge, evaluation experience, and no stake in which vendor you choose. For smaller businesses, the structured evaluation approach in this guide, combined with direct reference conversations, is usually sufficient. If you do use an independent consultant, confirm that they do not receive referral fees from the vendors they recommend, because that independence is the whole point.
