Test every shortlisted ERP against your own scenarios and data, check how you would leave it, and price the implementation and the people time, not just the license.
Write down your scenarios first
Before looking at any product, write ten to fifteen scenarios that describe how your business actually runs. Not features, but stories: "A customer orders 200 units, we have 120 in Chicago and 100 in Columbus, we ship partially and invoice what ships." "We buy steel in tons, issue it to production in kilograms, and sell finished parts by the piece." "A technician visits a site under warranty and uses two spare parts."
These scenarios become your test. Every vendor demo should walk through them, ideally using your own items and customers. A polished demo of the vendor's standard flow tells you very little about how the system handles your awkward cases.
Process fit before features
Feature lists make every ERP look complete. What matters is whether the system handles your processes without heavy customization. Look at the core flows end to end: quote to cash, purchase to pay, stock movement, production if you make things, and month-end close. Note every point where the vendor says "we would customize that". Each one adds cost, delay and upgrade risk.
Some customization is normal. A lot of it, early on, usually means the system was designed for a different kind of business.
Usability for the people who use it daily
The people who decide on an ERP are rarely the people who use it eight hours a day. Put the warehouse lead, an accounts executive and a salesperson in front of each shortlisted system and give them a task from the scenarios. Watch where they get stuck. A system that needs long training for routine tasks will be used reluctantly, and reluctant use produces bad data.
Check the phone experience too. Approvals, stock lookups and field updates increasingly happen away from desks.
Data ownership and the exit
Ask how you would leave. Can you export all transactional records, not just reports? Is the data model documented? Is API access included and complete? Where are backups held and can you get a copy? An ERP built on an open engine, as Sundial is on ERPNext, can answer these concretely. Treat vague answers as a warning.
Implementation and support
Ask who will implement the system, how many similar businesses they have set up, and what the plan for data migration, training and the first month-end close looks like. Ask what happens after go-live: who answers questions, how fast, and at what cost. Get the implementation scope in writing, including what is excluded.
Total cost, honestly counted
The license or subscription is usually the smallest part of the cost. Add implementation fees, data migration, customization, integrations, training, and above all the time your own staff will spend on the project. Then add ongoing costs: support, hosting if separate, upgrades and the cost of maintaining any customizations through those upgrades.
Compare options over several years, not the first year alone.
Watch how pricing scales. Some systems charge per user, which can penalise you for giving occasional users such as warehouse staff or approvers their own logins and push teams towards shared accounts. Others charge per module or by transaction volume. Model your expected growth over three to five years, including new users, branches and modules, and see how each option's cost changes as you grow.
Testing AI claims
Almost every ERP vendor now talks about AI. Separate what is shipped from what is planned by asking to see it working on data like yours, in the product you would actually buy. Ask how answers are checked, whether actions wait for approval, whether permissions apply, and whether everything is logged. Sundial is AI-native by design, and we frame our own agent capabilities as roadmap until they are in customers' hands; expect the same candour from anyone you evaluate.
The short checklist
- Did the system handle all our scenarios with our data?
- How much customization did it need, and where?
- Could our daily users complete routine tasks without help?
- Can we export everything and leave without the vendor's cooperation?
- Who implements it, and what is the written scope?
- What is the multi-year cost, including our own people's time?
- Which AI capabilities are shipped, and which are plans?
If you would like Sundial on your shortlist, try the demo or send us your scenarios and we will walk through them.





