ERPPricingBudgetCustom software
Custom ERP development cost: what drives the budget, line by line, and how to keep it under control
10 min read
What a custom ERP costs depends first on what you mean by "ERP". Two or three modules wired into the accounting software you already use, a core system for orders, inventory and invoicing, or a full multi-entity platform: these projects share a name and nothing else. Public sources give an order of magnitude, the cost lines explain the spread, and yearly maintenance often decides the five-year bill.
Most pages ranking for this question are agency price lists with ranges that run from a few thousand dollars to several million, with no source. This one uses only published figures, says where they come from, and shows you how to read a quote. Whether to build or buy at all is covered in our guide to custom ERP vs off-the-shelf ERP.
What the published numbers say
Few independent sources publish real ERP budgets. Two are worth knowing, read with their limits.
| Source | What it says | How to read it |
|---|---|---|
| Cegid, a French ERP vendor (article updated 6 November 2026) | EUR 150,000 to 800,000 for the first build of a fully bespoke ERP at a small or mid-sized company, EUR 300,000 to 2 million for a larger mid-market firm, 9 to 18 months from scoping to go-live | A packaged-ERP vendor has every reason to show that bespoke is expensive; the range targets a complete ERP, not a few modules |
| Clutch, a B2B review platform (updated 21 September 2026) | Software development projects: average cost of $132,480, most common budget band $10,000 to $49,999, average duration around 13 months | All software types and all countries; the average is pulled up by large projects |
Both point the same way: a complete ERP is a heavy project, but most real software projects are much smaller than a complete ERP. So the useful question is not "what does a custom ERP cost" but "which ERP do you actually need".
Three different projects behind one word
| Project | Typical scope | Biggest cost driver |
|---|---|---|
| Modules around what you have | Two or three modules (quoting, order tracking, scheduling) connected to your accounting software and any packaged ERP you keep | Connectors and data migration |
| Core operations system | Customers, products, orders, inventory, purchasing, invoicing, with an accounting export | Pricing, stock and invoicing rules |
| Full ERP | The core plus manufacturing, multi-entity, multi-currency, quality, asset maintenance, finance | Number of modules and how they depend on each other |
For a small or mid-sized business, the first case is by far the most common and usually the best return: keep packaged software for what it does well, and build only what is specific to you. Our article on integrating a custom application with an ERP covers how that hybrid works in practice.
The cost lines, one by one
A serious custom ERP quote breaks down at least these lines. If one is missing, ask where it went.
| Cost line | What it covers | What pushes it up |
|---|---|---|
| Discovery | Interviews, process mapping, written business rules | Processes that differ between sites or departments |
| Design | User journeys, screens, data model, permissions | Many user roles with different rights |
| Module development | Screens and, above all, the rules behind them | Exceptions per customer, site or period |
| Integrations | Accounting, banking, e-commerce, carriers, e-invoicing | Legacy systems without a documented API |
| Data migration | Products, customers, stock, history, cleaning and checks | Data scattered across several spreadsheets |
| Acceptance testing | User testing and fixes | Testing squeezed into the last week |
| Training and rollout | Team onboarding, cutover | Several sites, no period of parallel running |
| Hosting and operations | Servers, backups, monitoring | High availability requirements |
| Maintenance and changes | Fixes, security patches, upgrades, adjustments | Poorly documented code, a single developer with no backup |
Screen count appears nowhere in that table, on purpose. ERP cost follows the number of business rules, not the visible surface: an order entry screen that checks stock, applies the customer's price list and reserves goods is worth far more than a read-only screen that looks identical in a mockup. Our breakdown of custom business application cost goes deeper on this.
The modules that drive the price
Not all modules are equal. The expensive ones share a trait: many special cases, and mistakes that cost real money.
- Production planning. Bills of materials, routings, machine capacity, work orders and the daily disruptions around them. Often the single most complex module in a manufacturing ERP.
- Advanced inventory. Multiple warehouses and bins, lots, expiry dates, serial numbers, cycle counts.
- Multi-entity and multi-currency. Intercompany flows, recharges, consolidation, exchange rates.
- Pricing. Customer-specific discounts, volume breaks, contract prices, promotions, freight terms. A good pricing engine is a project in its own right.
- E-invoicing and tax compliance. Several European countries now require structured electronic invoices between businesses, usually through certified platforms or networks. A custom ERP should connect to one rather than reinvent the chain, and budget the connector and its testing as a line of its own.
By contrast, an order-tracking module, a management dashboard or a read-only customer portal stays a modest line, provided the data is clean.
What not to build
The surest way to cut the cost of a custom ERP is to not rebuild what already exists, standardised and proven:
- general ledger accounting, charts of accounts and tax filings;
- payroll, whose rules change constantly;
- e-signature, online payments and transactional email, which specialist services expose through APIs;
- the e-invoicing platform itself.
A custom ERP that posts clean entries to your accounting software and sends invoices through a certified network costs less and ages better than one that tries to do everything.
Five-year total cost: a simple formula
Comparing a build quote with a monthly licence fee makes no sense. Put both on the same timeline. Call B the cost of the first build, and use Cegid's published maintenance ratio of 15 to 25 percent of B per year.
Over five years, a custom ERP then lands between B + 5 × 15% of B = 1.75 × B and B + 5 × 25% of B = 2.25 × B, before any major new features you decide to add along the way.
On the packaged side, start with licences. Our custom vs off-the-shelf ERP guide works through Microsoft's public US price list for Business Central: $144,000 in licences over five years for 30 users, before any implementation services (checked on 6 November 2026). For Odoo, our Odoo vs custom software comparison lists licences, implementation packs and hosting.
Two lessons follow without inventing a number:
- The more users you have, the better custom compares, because its cost barely depends on the number of accounts while licences multiply with every seat.
- The more standard your processes, the more packaged software wins, because implementation shrinks to configuration.
The exact crossover depends on your case. Run the calculation with real quotes, over five years, maintenance included on both sides.
Timelines are a cost too
Cegid quotes 9 to 18 months for a fully bespoke ERP, and Clutch an average of around 13 months for a software project. A long project costs more than its invoice: months of double data entry, staff pulled off their jobs, decisions put on hold.
The answer is delivery by module. The first module in production earns its keep and funds the next; the second benefits from what the first taught everyone. An ERP delivered in one block after fifteen months puts all the risk on a single date.
Fixed price, time and materials or subscription
| Model | How the price is set | Who carries an overrun |
|---|---|---|
| Fixed price | Fixed per module, agreed on a visible scope | The provider, within the agreed scope |
| Time and materials | Hours or days actually worked | You, entirely |
| Subscription | Monthly fee covering build, hosting, maintenance and changes | The provider, who stays publisher and operator |
For an ERP, uncapped time and materials is the riskiest model for the buyer: scope is wide and rules surface as you go. Fixed price per module, on a scope made visible by a prototype, is safer. A subscription removes the upfront investment; in return, rights to the code are defined case by case in the contract. Our comparison of fixed price vs time and materials goes through the trade-offs.
Mistakes that blow up the budget
- Copying the old system screen by screen, workarounds included.
- Leaving data migration to the end, when it is the step that exposes inconsistent rules.
- Letting every department add requests without one decision-maker to arbitrate.
- Underestimating connectors to legacy software with no API or documentation.
- Leaving maintenance out of the budget, then discovering it at the first security patch.
- Picking the lowest quote, which often hides a vague scope followed by change orders.
A checklist for reading a custom ERP quote
- Is the scope described by process and rule, not only by screen?
- Are connectors listed one by one, with the direction of each data flow?
- Is data migration priced, and who signs it off?
- Do testing, training and cutover each have a line?
- Are hosting and yearly maintenance priced?
- Can you stop after the first module without losing what you paid for?
- Are rights to the code, data and documentation written down, case by case in the contract?
When not to build a custom ERP
Stay with packaged software if your processes are close to your industry standard, if you have few users, or if nobody on your side can give time to scoping and testing. A custom ERP without an available decision-maker on the client side almost always ends late and over budget, whoever builds it.
Where to start
- List your processes and, for each, the tool that runs it today, spreadsheets included.
- Find the double entry and the errors it causes: that is where the return on investment sits.
- Pick a first module that is useful on its own.
- Make it visible before you price it.
For that first module, we build a free visual prototype and present it on a video call within 5 working days: your team sees the screens and the rules, and the quote rests on what they saw. The approach is explained in see your software before you pay.