Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

What drives the cost of an ERP rollout for a mid-size company

The cost of an ERP rollout at a mid-size company is driven mostly by process fit, data migration, the integrations around the ERP, the number of sites and users, testing and cutover, and the time staff spend learning it, not by the licence. Netbase sizes these drivers in discovery so the rollout can be quoted at a fixed price.

Book a solution review See the cloud ERP solution

By Huy Nguyen (David), Founder & CEO · Updated · 11 min read

star

This guide is for a CFO, COO or IT lead budgeting an ERP rollout or comparing proposals. It publishes no price, rate or range; it gives a sizing matrix to fill in before any quote. For the commercial models, read how Netbase engagement models work; for the build itself, see custom software development.

In this guide

Why do two ERP proposals for the same company differ so much?

Two ERP proposals can differ widely because each prices different assumptions. One assumes that the package is used as it comes, that two years of clean data move across and that the store keeps its own stock figures. Another assumes custom approval flows, ten years of messy history and a live stock sync with the store and the warehouse. The licence line looks similar in both; the work does not.

Most of the effort in a rollout sits in services and in the client's own time, not in the software. The LeverX guide to ERP implementation budgets lists the categories that are most often missed: internal staff time and backfill, data cleansing and migration, integrations, customization and process redesign, testing, training and change management, temporary productivity loss, reporting, cutover and hypercare, and contingency for scope changes.

Most Netbase projects are delivered on fixed-price contracts, with milestone-based, monthly team retainer and KPI-linked models also offered. A fixed price is only fair when the drivers below are sized first, which is the job of discovery, the first step of Netbase's six-step delivery lifecycle.

Which cost drivers matter most, and how do you size them?

The matrix below is the core of this guide. Score each driver for your rollout; the drivers you cannot answer are the ones discovery must settle before a fixed price is credible.

Driver The question that sizes it Small when, large when Discovery output that settles it
Process fit and customization How far do your processes differ from what the package does? Small: standard purchasing, sales and accounting. Large: custom quoting, production scheduling, approval chains the package lacks A fit-gap list per process: configure, extend, build or change the process
Data migration How much history moves, from how many systems, and how clean is it? Small: one source, open balances and active records only. Large: several sources, years of history, duplicates and no owner A data inventory with an owner per entity and a trial load
Integrations Which systems exchange records with the ERP, and which one owns each record? Small: one or two systems with documented APIs. Large: store, CRM, warehouse, bank and carriers, some without APIs An integration map: system, direction, record owner, API quality
Sites, entities and users How many legal entities, warehouses, currencies and user roles go live? Small: one entity, one site, a few roles. Large: several entities, intercompany flows, many roles A rollout map: which entity and site go live in which phase
Testing and cutover How will both sides prove the system works, and how will you switch over? Small: agreed test scripts, a quiet cutover window. Large: no scripts, cutover in peak season, parallel running Test scripts per process and a cutover plan with a rollback rule
Training and internal time Who on your side tests, decides and trains, and is their day job covered? Small: named key users with time set aside. Large: decisions by committee, nobody backfilled A responsibility list with named key users and their available time
Run and upgrade Who supports the system after go-live, and how often does it change? Small: stable processes, few extensions, a named owner. Large: frequent changes, many extensions to retest at each upgrade A support plan: owner, change process and upgrade testing

Two patterns follow from the matrix. First, process fit and data move a proposal more than the choice of ERP product, because every gap becomes configuration, an extension or a process change, and every unowned data source becomes clean-up nobody priced. Second, testing and internal time are cheap to plan and expensive to skip: without agreed test scripts and key users with time, go-live slips and a fixed-price project turns into open-ended rework.

How do you contain the cost before asking for a fixed price?

  1. Map the processes before you pick features

    Write down how orders, purchasing, stock and invoicing really run today, then mark which steps are standard. The guide to process change before software shows how far to redesign before the ERP starts.

  2. Decide what history moves

    Open balances and active records are usually enough for go-live; older history can stay in a read-only archive. Every year of history you migrate is more cleaning and more test loads.

  3. Name the owner of every record

    Customers, products, stock and prices each need one system of record. The ERP, CRM and e-commerce integration architecture guide sets the owners flow by flow.

  4. Phase the rollout

    Start with one entity or site and the core finance and inventory processes; add sites and modules once the first phase is stable. A phase is a smaller, separately tested change.

  5. Agree test scripts and the cutover rule before the build price

    Write the scripts from real transactions, including the awkward ones, and decide when you would roll back.

  6. Book your key users' time

    Name them, set aside their hours and plan how their usual work is covered during testing and training.

A discovery phase that produces these outputs is what product discovery and roadmapping delivers before a build is quoted. If an old system is being replaced, assess it first with the legacy system assessment checklist.

Where does AI help in an ERP rollout?

AI shortens parts of the rollout work, but it does not replace the people who sign off data and processes. In Netbase delivery, AI-assisted work runs under human control, and Netbase works with the major commercial and open-source AI tools and models, chosen per project.

AI can group duplicate customers and products in a legacy export, draft field mappings between the old and the new data model, and propose test cases from real transaction samples. The engineers still check every mapping against the business owner's rules, every merge of records against the source data and every test case against the agreed process. The result is a cleaner trial load and a test set both sides can re-run after every change, not an unreviewed migration.

What delivery record exists, and what does not?

The clearest public view of how an ERP is sequenced is the multi-tenant cloud ERP that Netbase has built as offshore development partner for a US client that is not named. It is delivered in phases: the first covers CRM, real-time messaging, HR management, a knowledge base, custom fields and workflows, work and project management and API integrations; a planned second phase for retail adds point of sale, inventory, purchasing, e-commerce integrations, financial management, reporting and multi-store management. The phasing mirrors the matrix above: sites, modules and integrations are named stages, not a hidden part of "build the ERP".

Netbase's wider ERP work covers consultancy and customization of Odoo with a Vietnamese Odoo implementation partner for retail chains, manufacturers, distributors and other clients that are not named, a Vtiger CRM to ERP upgrade, and finance, inventory, sales, HRM and CRM modules. The method runs from project preparation and a business blueprint through realization and final preparation to go-live, support and maintenance. Productized modules such as Smart ERP Light are licensed, not transferred, while the client owns the IP created for it in custom development.

What does not exist: Netbase publishes no budget, price, duration, overrun, saving or other result for any ERP project. The sizing matrix is a framework for scoping, not a benchmark of Netbase outcomes.

Alternatives: which rollout route keeps the cost in check?

Option Strength Risk Choose it when
Package used as it comes Fastest start, vendor keeps up with rule changes Staff work around gaps by hand Your processes are close to standard practice
Package with extensions Keeps the package core, fits the processes that set you apart Each extension is retested at every vendor upgrade A few processes differ and the package has documented APIs
Custom modules beside a package core Strategic processes fit exactly, utility processes stay standard Needs an integration layer and a long-term owner Quoting, production or B2B processes set you apart
Phased rollout Smaller, tested steps; cost spread across phases Old and new systems run side by side for a while Several entities or sites, or data that needs cleaning first
Wait No rollout cost yet Manual work and the old system continue Nobody owns the data, or no key users can be freed

Selection criteria: choose the route whose weakest driver you can live with. Martin Fowler's strangler fig pattern describes the phased route: new parts are built beside the old system and behaviour moves across step by step. The BDC comparison of custom and off-the-shelf ERP warns that customization can be expensive and its long-term cost hard to estimate. The custom ERP vs off-the-shelf ERP guide covers that route choice in depth.

Netbase leads with consulting, solutions, custom development and AI-enabled transformation; dedicated teams and outsourcing are secondary delivery options. For the ERP engagement itself, see ERP and CRM development and the module-based cloud ERP starting point. For the same method applied to a different system, read what drives the cost of an AI agent project.

What are the limits of this guide?

  • It publishes no price, rate or range, and no third-party price figure is used; vendor cost guides differ widely and rest on assumptions they do not always state.
  • The seven drivers are not weighted; their relative size depends on your processes and data, which is why discovery comes before the quote.

Plan the next step with a Netbase consultant

Frequently asked questions

Usually not. Fitting the system to your processes, migrating and cleaning data, building integrations, testing, cutover and the time your own staff spend on the project tend to carry more of the work than the licence, which is why proposals that size those drivers differently look so different.

Yes, once discovery has sized the drivers: a fit-gap list, a data inventory, an integration map, a rollout map, test scripts and named key users. Most Netbase projects are delivered on fixed-price contracts, and Netbase also offers milestone-based, retainer and KPI-linked models where the scope cannot yet be fixed fairly.

Mostly because scope that nobody priced appears during the project: data that needs more cleaning than expected, an integration nobody listed, a process the package does not support, or key users who have no time to test. Sizing each driver in discovery moves these surprises before the price.

Keep standard processes standard, migrate open balances and active records rather than all history, give every record one owner, phase the rollout by entity or site and book your key users' time. Each choice removes scope from the first phase without blocking a later one.

Next step

Score your rollout against the seven drivers, then book a solution review to turn the open questions into a discovery plan and a fixed-price scope.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
AI-enabled ERP and CRM development connected to your commerce AI-enabled ERP and CRM development connected to your commerce

Netbase provides custom ERP and CRM development for growing companies to run sales, operations and finance in systems shaped to how they work, connected to their ecommerce channels and using AI for document capture, forecasting and sales follow-up. We build on proven modules, including Smart ERP Light and Cloodo Workspace, and work with Odoo or Salesforce where one fits.

Learn More
line
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system

A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase