Custom ERP: when it beats an off-the-shelf one

More and more SMEs already running a standard ERP — SAP Business One, Odoo, Holded, Sage — come to Evicron with the same frustration: the tool handles accounting, invoicing and basic inventory well, but the moment the business has a process of its own — pricing that depends on several variables, an approval flow with several steps, an integration with machinery or suppliers that isn’t in the connector catalogue — it starts running on third-party add-ons, parallel spreadsheets and patches nobody documents. At Evicron, an AI and custom software studio based in Barcelona with 200+ projects delivered across 12 sectors since 2019, this guide covers when a custom ERP genuinely beats an off-the-shelf one, what it costs, how long it takes, and what to ask before commissioning one.

What a custom ERP actually is

A standard ERP is generic software built to fit as many companies as possible: predefined modules for accounting, purchasing, inventory and invoicing, with configuration up to a point and an ecosystem of third-party integrations. It’s fast to roll out and has a known upfront cost, but the real price shows up later: per-seat or per-module licences, implementation consulting to bend your process into its structure, and a customisation ceiling you eventually hit.

A custom ERP flips that logic: it’s built to mirror the company’s actual process — how a quote is really priced, how a production order actually flows, who approves what and in what order — instead of forcing that process into generic modules. No per-seat licence, no module caps, and the codebase belongs to the company.

When a custom ERP pays off

It’s worth considering when two or more of these apply:

• Your operating process is your competitive edge and doesn’t fit standard modules: pricing logic that’s genuinely yours, a production flow with steps no generic ERP accounts for, sector-specific approval rules.
• You’re already juggling several systems that don’t talk to each other — the ERP for invoicing, a spreadsheet for whatever it doesn’t cover, a third system for the warehouse — and someone on the team spends hours a week moving data between them by hand.
• Licence and add-on module costs are growing faster than the business and already sit as a meaningful fixed cost, without the standard ERP covering the essentials without extra charges.
• You need the system tied into applied AI — an assistant that checks order status, OCR that digitises delivery notes or supplier invoices, automatic stock alerts — and the standard ERP only offers that through third-party modules that don’t quite fit the rest of the system.

When it’s not worth it yet

If a standard ERP covers most of the operation and the exceptions are one-off, there’s no reason to replace it: most SMEs with conventional buy-sell-and-inventory processes are better off with Odoo, Holded or similar than funding a build of their own. It’s also not worth it if the process is still changing every month — building custom software around something that hasn’t settled ends up costing twice — or if the company doesn’t yet know, in detail, what its actual process is: that mapping has to exist before a single line of code gets written.

What it costs and how long it takes

At Evicron, a custom ERP falls under custom software development: platforms with genuine business logic start at €12,000, typically taking 3 to 6 months depending on how many modules and integrations it needs to cover. The process runs through 4 phases — discovery, weekly development sprints, a clickable demo by week 2, and delivery with your own code, no lock-in — with the quote fixed after a free discovery session. We’ve already covered what actually moves the price of a custom software project in more detail: on an ERP, what drives the cost up is almost always integrations with existing systems — a payment gateway, a logistics provider, a payroll system — not the interface.

What to ask before commissioning a custom ERP

1. Who owns the code once it’s done? The right answer is “you, no exceptions.” If it means depending on the vendor for any future change, that’s a red flag.
2. How does data from the current ERP get migrated? A serious project includes a migration plan for accounting, inventory and invoicing history, not just the new screen.
3. What happens to the modules that already work well today? You don’t need to replace the whole system: it’s often better to integrate a custom ERP with the standard accounting module that already works than to rebuild that too.
4. Who maintains it once the project wraps? An ERP grows with the business: it needs someone to maintain and extend it, not a sealed deliverable.

The decision, in one line

If your operating process is the same one any company your size and sector has, a well-configured standard ERP is cheaper and faster. If that process is precisely what sets you apart — and you’re already running it on patches and parallel spreadsheets — a custom ERP stops being a technical indulgence and becomes the investment that removes those patches.

At Evicron we assess your specific case in a free, no-obligation discovery session, and tell you honestly whether a custom ERP is worth it or whether you just need to configure the one you already have better. We apply the same process — weekly sprints, a demo by week 2 — as on projects like Hipteca. Get in touch: we reply within 24 hours.