What does a small business ERP need?

It should cover the processes creating the most errors or repeated work, share data across the teams that need it, support clear permissions and offer a workable data migration path. Test these flows with real examples rather than comparing feature counts alone.

Should I choose an all-in-one or a modular ERP?

It depends on your initial scope. If several teams need shared data immediately, assess the whole integration. If budget and implementation capacity are limited, a modular system may let you start with one process and add others later, provided the modules share data and permissions.

How should I compare ERP prices?

Calculate first-year total cost: subscription, extra users, implementation, migration, training, integrations and support. Ask each vendor to list included modules and limits. Monthly subscription alone does not show the full cost.

How to choose an ERP for a small business: a checklist

Choose a small business ERP by testing the workflow you need to improve, not by counting features. Write down where information enters, who uses it, what decision follows and where someone retypes it today. Then ask every vendor to demonstrate that same case. A useful demo should follow the data from start to finish and show what happens when something goes wrong.

This checklist helps you compare systems on evidence instead of a long list of unchecked claims.

1. Map the work before looking at software

Pick two or three journeys your team repeats often. For example, an opportunity becomes a customer and invoice; a sale changes stock; a purchase affects budget and cash. Record the current tools, the people involved and every point where information is copied.

Turn each journey into a demo question:

Workflow	Demo question	What to verify
Sale to payment	What happens to the customer and invoice when a sale closes?	The same data carries forward and unpaid balance is visible.
Stock to purchase	How is low stock detected?	There is a traceable movement and a replenishment decision.
Project to margin	Where do time, costs and billing meet?	You can see the project result without joining files.

Ask to see a case like yours on screen, including a correction or cancellation. This reveals whether the process is connected or merely shown across separate screens.

2. Set a realistic starting scope

You do not have to implement every area at once. Rank problems by impact, frequency and difficulty of change. Work repeated every day by several people may deserve attention before a report prepared once a quarter.

Separate your needs into phases:

Day one: users, roles, core records and the first workflow to fix.
Next phase: teams that need to reuse those records, such as Finance after Sales.
Later: automation and reporting that depend on reliable data.

If you are considering a modular ERP, ask what happens when you add a module. Do customers, products and permissions remain the same, or must they be migrated again? Zentral’s CORE and modules share a base, and the pricing page shows the cost of your selected combination.

3. Compare total cost, not only subscription price

Ask each vendor for a quote covering the same period, such as the first twelve months. Include:

Subscription, included users and extra user charges.
Implementation, configuration and data migration.
Required integrations, training and support.
Terms for adding modules, increasing users and exporting your data.

Keep exclusions next to the headline price. A cheaper quote that leaves out migration or support may cost more in practice. Also ask who does the internal work: cleaning duplicate customers and agreeing on process owners can take time from your own team.

4. Test migration and permissions

Bring a small, anonymised sample of customers, products or projects to the demo. Include awkward cases such as duplicate records and missing fields. Ask how the system imports them, validates them and corrects errors before the data goes live.

Then test specific permissions. A sales colleague may need to view an invoice’s payment status without changing accounting records. A “roles” screen is not enough: ask to see two users with different access and a record of changes.

5. Test AI with a verifiable task

If the product advertises AI, prepare a question about your own data and define the expected answer in advance. Check where each number comes from, which period it covers and whether the user is allowed to see it. A fluent answer is not the same as a verifiable one.

Also ask what happens when the data is incomplete. A useful system should explain the limitation or ask for context instead of inventing a number. In a Zentral demo, you can test a question about the modules you are assessing and see what data is available to that user.

Decision checklist

Before signing, make sure you can answer these questions with evidence:

Did the demo complete a real workflow from start to finish?
Which data is shared between teams, and what still needs an integration?
How much time and internal work will migration require?
What can each role view and change?
What is the full first-year cost, and what is excluded?
How can you export data if you change systems?
Who helps when a configuration or integration fails?

The right choice solves your first problem, makes the cost clear and gives you room to expand without starting over. Use the same checklist with every vendor so the decision rests on comparable evidence.