Custom ERP vs. off-the-shelf ERP: which suits an SME?

When a small business ends up keeping orders in Excel, stock on paper and customers in the owner’s phone, the question inevitably comes up: should we get an ERP? Straight after it comes the second one: do we buy a ready-made, “off-the-shelf” one, or build a custom ERP, designed around our own processes?

There is no answer that works for everyone. There are, however, a few clear criteria you can use to decide without relying on sales promises. Below you will find the real differences between the two options, the costs most people overlook, a five-step decision process and the mistakes we see most often in SMEs.

What off-the-shelf ERP and custom ERP actually mean

Off-the-shelf ERP is a standard product, sold as a licence or subscription, with predefined modules: invoicing, stock, purchasing, sometimes HR and accounting. You configure it, but you don’t change it in any depth. The workflows are designed for the “average business” in the industry it was built for.

Custom ERP is an application built for your business. The screens, fields, order statuses and reports start from the way you work, not the other way round. Technically, it is built on modern components (a database, a web interface that also works on your phone, automations), but the business logic belongs to you.

There is also a hybrid option: you keep a standard package for what is genuinely standard (accounting, for example) and build custom only the part that sets you apart, such as orders, production or appointments, with automatic links between the systems.

When off-the-shelf ERP is the right choice

• Your processes are standard for your industry: you buy, store, sell and invoice, with no unusual steps.
• You need something working quickly and you accept adapting to the software.
• Your team can work “the way the software wants”, and that doesn’t damage your customer relationships.
• Your initial budget is very small and you prefer a predictable monthly subscription.
• You don’t need links to your telephony, WhatsApp or website.

If every point applies to you, a well-chosen standard product is probably the most sensible decision. There is no point paying for development of something that already exists and fits you.

When a custom ERP makes sense

The signs that you have outgrown a standard product show up in day-to-day operations, not in strategy meetings:

• You have steps that don’t exist in any software: orders with unique specifications, samples approved by the customer, batches with different requirements, appointments tied to a specific member of staff.
• Your team keeps a parallel spreadsheet or WhatsApp group, because the software doesn’t cover what actually happens.
• You pay for modules you don’t use, but you are missing exactly the one you need.
• You want the phone, WhatsApp, website and ERP to be a single system, so that an order taken by an AI agent over the phone appears straight in production.
• You have several locations or sales channels and nobody sees the full picture.

An example from our projects: a chain of patisseries in Sibiu was losing orders because the phone rang exactly when everyone was busy. We built an AI voice agent that takes the calls and a custom ERP that the orders go straight into, with every production detail. Around 20 calls a day that used to be lost orders are now recovered. A standard package would have had nowhere to connect the agent, and it wouldn’t have followed the specific workflow of a patisserie either.

Head-to-head: custom ERP vs. off-the-shelf ERP

The costs you don’t see in the quote

With off-the-shelf ERP, the advertised price is rarely the real price. Write down:

• the cost per user multiplied by the number of people you will have in two or three years, not today;
• the “premium” modules your workflow can’t function without;
• hours of configuration, data import and training, billed separately;
• time your team loses on workarounds: parallel spreadsheets, data entered twice;
• the cost of leaving: how easily you can export your data if you walk away.

With a custom ERP, the questions are different:

• what the implementation includes and which deliverables you get at each stage;
• who maintains it and what infrastructure and maintenance cost each month (this depends on volume, so ask for an estimate based on your real data);
• whether you get documentation and access to the database;
• how later changes are made and how quickly.

For reference, at Neurotech a custom ERP or CRM starts from €2,500 (implementation, excluding VAT), paid in instalments tied to deliverables. Monthly costs depend on usage volume, so we work them out for your specific case, not from a price list.

How to decide in 5 steps

1. Map the real workflow, not the ideal one. Take a typical order and follow it from first contact to payment. Note every person, every piece of software and every sheet of paper it passes through.
2. Mark what is standard and what is specific. Invoicing is standard. The way you schedule production or look after loyal customers probably isn’t.
3. Test two or three off-the-shelf packages on your own workflow, not on the vendor’s demo. Ask for a trial period and enter real orders.
4. Work out the total cost over three years for both options, including your team’s time and the cost of mistakes.
5. Choose the option that removes the most workarounds. If you still need the parallel spreadsheet after the trial, the software isn’t right for you.

Common SME mistakes

Buying on number of features

An ERP with forty modules is no better than one with five if you only use three. Unused features clutter the interface and make training harder.

Wanting everything custom from day one

A custom ERP doesn’t have to do everything from the start. Begin with the workflow that hurts most, usually orders, and add modules as the system proves its worth.

Ignoring your existing data

Moving customers, products and order history across is a separate stage. Plan it from the outset, or your team will spend months working in two systems.

Not asking the people who use the software

The owner signs, but the order handler works in the software eight hours a day. If you don’t involve them, you only find the problems after launch.

Not clarifying who owns the data

Whichever option you choose, make sure the data is yours and can be exported. With a custom system, ask for database access and technical documentation.

The hybrid option, which we often recommend

In practice, many SMEs end up with a combination. Accounting stays with the accountant, in their own software. Orders, customers, production and communication move into a custom application. Between them, automations send the data where it needs to go, with no manual copying.

We build systems like this on a Supabase database hosted on servers in the EU, with automations in n8n and, where it makes sense, AI agents based on Claude that take orders by phone or on WhatsApp. You can read how we protect data on our data security page, and see the kinds of applications we build under custom applications.

Another example: a beauty salon reached roughly 40% more revenue from upselling after moving to a custom app and a new website. The difference came from the system being built around the salon’s services, not a generic template.

In short

• Choose off-the-shelf ERP if your processes are standard and you can work the way the software wants.
• Choose custom ERP if you have specific workflows, lots of spreadsheet workarounds, or you want your phone, WhatsApp and website linked to the same system.
• Consider the hybrid option if you want to keep accounting in your accountant’s software and customise only the operational side.

If you are not sure which category you fall into, we can look at your order workflow together and tell you honestly whether you need something built or whether a standard package will do. Book a free 30-minute call.