Custom ERP vs off-the-shelf ERP: how to choose, and when to extend instead

This guide is for owners, finance and operations leaders and IT managers of growing companies whose spreadsheets or first package no longer keep up. It compares the routes, the cost of owning each one and the questions that decide it. Connecting whichever ERP you choose to your store and CRM is covered in our enterprise systems integration guide.

In this guide

• Four routes, not two
• The routes compared
• Where custom pays off, and where it does not
• Cost of ownership over the life of the system
• Six questions that decide it
• Integration decides as much as the ERP
• AI and the ERP decision
• How Netbase approaches the choice
• What delivery record exists, and what does not
• Limits of this guide
• Frequently asked questions
• Next step

Four routes, not two

The question is usually framed as build or buy, but four routes are on the table.

• A package used as it is. You configure an ERP product and change your processes to match it. Upgrades come from the vendor.
• An extended package. You keep the package core and add custom modules, reports and integrations through its extension points, as many companies do with Odoo or a similar suite.
• Custom on reusable modules. A partner starts from ready modules for orders, inventory, projects or billing and builds only what is specific to you, so the system fits without starting from zero.
• Fully custom. Every module is designed and built for your business, and you own the whole system.

A fifth pattern is common in practice: a package for the utility work, such as the ledger and payroll, with custom applications around it for the work that differs, connected through APIs.

The routes compared

BDC, the Business Development Bank of Canada, sums up both sides: off-the-shelf systems "offer proven, pretested functionality that can often be implemented with fewer surprises and less risk", while "a custom system that appears affordable at first may end up costing significantly more over its lifetime".

Where custom pays off, and where it does not

Martin Fowler's utility vs strategic dichotomy gives the most useful test. For a utility function, "you buy the package and adjust your business process to match the software"; strategic functions, the ones that set you apart, are where bespoke software earns its cost.

• Usually utility: general ledger, payroll, tax reporting and standard purchasing. A package does these well and keeps up with rule changes.
• Often strategic: how you quote and price, configure products, schedule production, serve B2B accounts or run projects. These are where packages force workarounds and where a custom module pays off.

Apply the test process by process. Most companies find a few strategic processes and many utility ones, which points to an extended package or custom modules around a package core rather than a wholesale choice.

Cost of ownership over the life of the system

Compare routes over the years you expect to run the system, not on the first invoice.

• Package costs are licences or subscriptions per user or module, implementation, training, and the workarounds staff do by hand where the product does not fit.
• Extension costs add building the extensions and retesting them at every vendor upgrade; heavy customization can make upgrades the largest recurring cost.
• Custom costs are the build, then hosting, maintenance, security updates and the team that knows the code.
• Integration and data migration cost money on every route and are often underestimated.

No single ratio holds between these: it depends on users, processes, data and how long the system lives. Price each route on your own numbers.

Integration decides as much as the ERP

An ERP rarely stands alone. The store, the CRM, payment providers and carriers all exchange orders, stock, customers and invoices with it, and a route that fits on paper can fail on integration. Before choosing, map those flows and their owners with ERP, CRM and e-commerce integration architecture. A package with documented APIs, or a custom ERP built API-first, keeps later changes cheap; Netbase's systems and API integration service builds that layer whichever route you choose.

How Netbase approaches the choice

Netbase's ERP work starts with consultancy: process mapping, a fit-gap analysis and a build, buy or extend recommendation. It has consulted on and customized Odoo in Vietnam with a local Odoo implementation partner, upgraded a client from Vtiger CRM to a full ERP, and built cloud ERP platforms. Its productized module library includes a CRM and B2B sales engine, a workflow automation toolkit and Smart ERP Light, and Cloodo, a Netbase Business Division, combines CRM, HRM, Cloud ERP and AI modules in one workspace. Productized modules are licensed, not transferred, while the client owns the IP created for it in custom development. Most Netbase projects are delivered on fixed-price contracts agreed after discovery; see dedicated team vs fixed price. The ERP and CRM development service describes the engagement, and cloud ERP is the module-based starting point.

What delivery record exists, and what does not

• What exists. The cloud ERP record describes a multi-tenant cloud ERP that Netbase has built as offshore development and managing partner for a US client (not named) since 2020, with CRM, work management and API integrations in its first phase and a retail extension planned. The Cloodo record describes Netbase's own digital workplace. The Odoo projects and the Vtiger upgrade are described by scope only, and their clients are not named.
• What does not. None of these records publishes a cost comparison, implementation time, licence saving or business result, and none is offered as proof that one route is cheaper. The Odoo work was delivered with a partner, and no Odoo vendor status is claimed.

Limits of this guide

• The routes and costs are described qualitatively; published cost ratios vary by source and method, and none is used as a Netbase figure.
• The BDC and Martin Fowler pages are cited for what they say on the access date.
• Accounting, tax and legal requirements differ by country and are outside this guide.

Next step

Share the processes that set you apart, the systems your ERP must connect to and where today's tools fall short, and we will book a solution review to run a fit-gap and compare the routes with you. You can also see ERP and CRM development or more Netbase insights.

Related services and solutions