GUIDE

Choose an ERP for the business you will be in three years.

A step-by-step method for shortlisting, testing and choosing an ERP: the processes to map, the questions to ask every vendor, the costs people forget and the red flags to walk away from.

SUNDIAL / GUIDE

The ERP buyer’s guide for 2026.

Guide 01

What this guide covers.

Nine steps, from writing down what is broken today to signing with confidence. Each step ends with something you can hand to your team. The method works whichever vendor you choose, including if it is not us.

By the Sundial team. Free to use, copy and adapt for your own business.

Try the demo   Talk to us

1. Start with what is broken

Most ERP projects start with a feature list. Start with a list of problems instead. Ask each team lead to write down the five things that waste their week and the decisions they cannot make because the numbers are late or wrong.

  • Orders confirmed without knowing whether stock is available.
  • Invoices raised days after delivery because the dispatch note sits in another system.
  • Month-end close that depends on one person’s spreadsheet.
  • Purchase orders approved on chat, with no record of who agreed to the price.
  • Stock counts that never match the books, so nobody trusts reorder levels.

For each problem, note who owns it, how often it happens and what it costs in hours or missed revenue. This list becomes your evaluation script and, later, the way you measure whether the project worked.

2. Map your processes end to end

An ERP is valuable because one transaction flows through every team without retyping. Map the flows, not the departments. For each one, write the steps, the documents created and the hand-offs between people.

  • Quote to cash: lead, quotation, sales order, delivery, invoice, payment, reconciliation.
  • Procure to pay: request, RFQ, supplier quotation, purchase order, receipt, inspection, supplier invoice, payment.
  • Plan to produce: forecast or order, bill of materials, work order, job cards, material issue, finished goods, costing.
  • Record to report: journals, bank reconciliation, depreciation, accruals, close, statements.
  • Service and support: issue, SLA, visit, warranty claim, repair, billing.

Mark every hand-off that happens on paper, email or chat today. Those are the places an ERP saves the most time and where a weak one will hurt the most.

3. Write requirements that separate systems

Every ERP has invoicing. Write requirements that only some systems meet, phrased so a vendor can show them on screen in minutes.

  • One ledger: a delivery, receipt or work order posts to accounts automatically, with no batch export.
  • Inventory valuation you understand (FIFO or moving average) and stock that can never silently go negative.
  • Batches and serial numbers traced from supplier to customer, if you sell anything regulated, perishable or under warranty.
  • Multi-company and multi-currency, if you have or plan more than one legal entity.
  • Roles and permissions down to the document and field, so people see what they need and nothing more.
  • A full audit trail: who changed what, when, and the value before and after.
  • Reports your team can build and save without a developer.
  • Works properly on a phone for approvals, stock lookups and sales visits.
  • Your data can be exported in full, in an open format, at any time, and there is a documented API.
  • Daily backups, a named place where your data lives and a clear answer to who can access it.

4. Ask every vendor the same questions

Send the same written questions to every shortlisted vendor and compare the answers side by side. Vague answers are an answer.

  • Which of our problems from step 1 can you show solved in your standard product, without customization?
  • What will we need customized, who builds it, and what happens to it when you release an upgrade?
  • Who implements: you, a partner, or us? Who is accountable if the go-live date slips?
  • How do upgrades work, how often, and can we postpone one?
  • If we leave, how do we get every record out, and in what format?
  • Is the database ours alone (single-tenant) or shared with other customers?
  • Which AI capabilities are shipped today and which are on the roadmap? Show the shipped ones live.
  • What does support look like in our time zone, and how do we reach a person?

5. Run a scripted demo with your own data

Do not accept a vendor’s standard demo. Send a script two weeks in advance built from your process map and a small set of your real items, customers and suppliers.

  • Give the vendor ten real items, five customers, five suppliers and one bill of materials, if you manufacture.
  • Ask them to run one full quote-to-cash and one full procure-to-pay flow live, including a partial delivery and a return.
  • Have the people who will use the system every day drive it for part of the session, not only watch.
  • Ask for one report you need today, built in front of you.
  • Score each step immediately after the demo while it is fresh, using the scorecard in step 9.

If a vendor offers a self-serve demo workspace, use it before the call. You will ask better questions.

6. Count the total cost, not the license

The subscription is usually not the largest cost of an ERP. List every line below for each vendor, over three years, and ask them to fill in what they can.

  • Subscription or licenses, and how they grow with users, companies or modules.
  • Implementation: configuration, workshops, project management.
  • Data migration: cleaning, mapping, trial loads, reconciliation.
  • Customization and integrations, and the cost of keeping them working through upgrades.
  • Hosting, backups and security, if not included.
  • Training, and the hours your team spends away from their day job.
  • Support after go-live and any premium support tier.
  • The cost of running old and new systems in parallel during cutover.

Then add the cost of doing nothing: the hours your team loses each month to the problems in step 1.

7. Judge AI claims carefully

In 2026 every ERP vendor talks about AI. The useful questions are about control and evidence, not about how impressive a chat window looks.

  • Does the AI act through the same roles and permissions as the person using it?
  • Does it draft and wait for approval, or can it post transactions on its own? Can you choose?
  • Does it show which records it used, so a person can check the answer?
  • Does your data stay inside your instance, and is it used to train anyone else’s model?
  • Which capabilities are shipped, which are in preview and which are roadmap?

Sundial is designed for AI agents to work alongside the team: ask the business a question in plain language, or let an agent draft a purchase order and wait for your approval. We label each capability as shipped, in preview or coming, and we expect every vendor you evaluate to do the same.

8. Know the red flags

  • The vendor cannot show your process without “we will configure that later”.
  • Every requirement is answered with customization.
  • There is no clear way to export all of your data.
  • Pricing changes the moment you mention a second company or warehouse.
  • The implementation plan has no data migration trial runs.
  • References are only offered for a different industry or company size.
  • AI features are demonstrated on slides instead of in the product.

9. Decide with a weighted scorecard

Score each vendor from 1 to 5 against weighted criteria, then multiply. Agree the weights before the first demo so nobody adjusts them to fit a favorite.

Example weights (illustrative only, set your own):

  • Fit to your mapped processes without customization: 30%
  • Ease of use for the people who will use it daily: 20%
  • Total cost over three years: 15%
  • Data ownership, export and APIs: 10%
  • Implementation plan and support: 15%
  • Reporting and AI, shipped today: 10%

A scorecard does not make the decision for you, but it makes the reasons visible and stops the loudest voice in the room from winning by default.

Next: plan the move with the ERP migration checklist.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us