Skip to content
Start a Project
tech@softlixx.com
+92 347 0970 627

Custom ERPsBy Softlixx TeamPublished Updated 8 min read

Ready-made or custom ERP: how do you decide?

I read a survey of ERP projects, peer-reviewed studies on customizing ERP software and a 2026 paper on buying versus building.

On this page

The short answer

It depends on how unusual your process is, and on who will keep the code working. The studies I read say some customization is typical, especially for small companies whose edge is doing something unique, but each customization has to be weighed against its maintenance. A 2026 paper finds regulated and mission-critical systems stay mostly in the buy column. I found no independent data comparing the cost or speed of a ready-made ERP with a custom build. That is what I found after reading the sources below.

Key takeaways

  • There are three routes: a ready-made ERP as it comes, a ready-made ERP with custom code, and a fully custom ERP.
  • A peer-reviewed study found some customization is typically required, and each one needs weighing against its impact on future maintenance.
  • Small companies customize more often than large-enterprise advice suggests, and one study says they may avoid standardization to protect what makes them unique.
  • Panorama's 2026 survey of 170 organizations found more than a quarter of ERP projects over budget, most often because of an unexpected need for additional technology.
  • Panorama says a SaaS ERP shifts maintenance and upgrades to the vendor, but makes internal governance more important.
  • I found no independent data comparing the cost or speed of a ready-made ERP with a custom build.

What are the three routes?

Use a ready-made ERP as it comes, add custom code to it, or build a custom ERP. Each puts a different share of the code, and its upkeep, in your hands.

By a ready-made ERP as it comes I mean configuring standard modules. Adding custom code to a ready-made ERP is the second route, and a custom ERP is software written for one business from the start. Softlixx sells ready-made ERP implementations and custom builds, so I have a stake in this topic, and I have kept in the evidence that cuts against customizing.

Three routes, and what the research says about each
RouteWhat it meansWhat the research I read says
Ready-made as it comesConfigure the standard modules.Most organizations reengineer their processes in line with the software, to keep the vendor's support (Light, 2001).
Ready-made with custom codeAdd code that extends the standard modules.Some customization is typically required, and each needs weighing against future maintenance (Light, 2001).
Fully customSoftware written for one business from the start.Regulated and mission-critical systems remain mostly in the buy domain (Klotz, 2026). No independent cost or speed data found.

Sources: QUT ePrints, arXiv.

Is customizing an ERP a good idea?

Not by default. The research I read says some customization is normal, but each one has to earn its upkeep.

A peer-reviewed study by Ben Light, published in 2001, looked at two ERP projects where customizations were made. It says that to avoid invalidating maintenance and development support from the vendor, most organizations reengineer their business processes in line with those implicit within the software. Regardless, some customization is typically required.

While customizations can give true organizational benefits, careful consideration is required to determine whether a customization is viable given its potential impact upon future maintenance.

Ben Light, researcher, writing in the Journal of Software Maintenance and Evolution in 2001. Read the source

Small companies may differ. In a 2011 conference paper by Ondrej Zach and Bjørn Erik Munkvold of the University of Agder, the authors say conventional wisdom, founded on studies from large enterprises, holds that ERP systems should be implemented without customization. However, studies of ERP implementations in small and medium-sized enterprises indicate that customization is more common there. Their case study of four SMEs found reasons specific to the SME context, including unique business processes, ownership type and organizational maturity.

My readingBoth studies are old and small: one is from 2001, and the other covers four companies. I take them as a reminder to ask what each customization is for and who will maintain it, not as a rule against customizing.

Does company size change the answer?

Often, yes. Small companies tend to sit on the awkward side of both routes. I read three studies on small and mid-size businesses, from 2020 to 2023.

A 2021 preprint by Issam Jebreen and colleagues says small and medium-sized businesses generally thrive because they have done something unique within a niche market. For that reason, they may seek to protect their competitive advantage by avoiding any standardization that packaged software encourages. The challenge is how to respond to misfits between the software's functions and each business's needs.

A 2023 paper by Lukas Böhme and colleagues, based on 15 interviews with industry experts, says existing ERP systems are unsuitable for startups and small and medium-sized enterprises that grow quickly and need adaptable solutions with low barriers to entry. It describes high entry barriers, high costs of implementing implicit processes, and insufficient interoperability with tools already in use.

A second Jebreen preprint, from 2020, studied how software companies judge the feasibility of implementing packaged software. The criteria they use to estimate the effort and time needed are new features, level of customization, software output and technical needs.

My readingThese are small qualitative studies: one built on 15 interviews and two on ethnographic work inside software companies. I read them as signals about where misfits arise, not as measurements of how often.

Who looks after upgrades and maintenance?

A SaaS ERP shifts some of that work to the vendor, but customizations bring maintenance back.

Panorama Consulting Group's 2026 ERP Report covers the ready-made side. It adds a warning: SaaS ERP increases the importance of internal governance, because frequent updates and evolving functionality need clear ownership and oversight.

SaaS ERP shifts responsibility for system maintenance and upgrades to vendors, reducing customers' infrastructure and upgrade burden.

Panorama Consulting Group, ERP consultancy, in its 2026 ERP Report. Read the source

Customization is where the upkeep comes back. Light's study is titled for the maintenance implications of customizing ERP software, and Panorama says a project's timeline depends on factors such as the number of modules implemented and the degree of software customization.

A 2026 preprint by David Klotz re-examines the buy-or-build decision for enterprise software in the age of AI coding tools. It is a conceptual paper, not a test. It finds that the “SaaSocalypse” claim, that AI will make most software cheap to build in-house, is overstated for most enterprise application categories. Building is most compelling for commodity utilities and differentiating custom applications, while regulated and mission-critical systems remain predominantly in the buy domain.

My readingI read this as a reason to settle upkeep before you settle the route. I did not find a source that puts a figure on the upkeep of either one.

How do ERP projects usually go?

Often over budget or late, and mostly for reasons that come before any code. I read a 2026 survey from an ERP consultancy.

Panorama's report covers 170 respondents between January 2025 and January 2026, 56.5% of them multinational, with a median annual revenue of $200.5 million and a median project timeline of 9 months. More than a quarter of organizations reported that their project was over budget, and almost a quarter reported that it was over schedule.

Of those over budget, the most common reason was the unexpected need for additional technology. Of those over schedule, it was organizational issues, such as governance, resistance to change and process redesign.

Organizations discover fatal misfits late in the project, so they turn to additional technology, scope expansion, and custom builds.

Panorama Consulting Group, ERP consultancy, in its 2026 ERP Report. Read the source
The sources, and the limit of each
SourceWhat it foundLimit to keep in mind
Panorama 2026 reportMore than a quarter of projects over budget, almost a quarter over schedule.A consultancy that sells ERP services. 170 organizations with a median revenue of $200.5 million.
Light, 2001Some customization is typically required, and each needs weighing against future maintenance.Two case studies, 25 years old.
Zach and Munkvold, 2011SMEs customize more often than the large-company wisdom suggests.A case study of four SMEs.
Jebreen and colleagues, 2021SMEs may avoid standardization to protect what makes them unique.Ethnographic work in two software companies. A preprint.
Böhme and colleagues, 2023Existing ERP systems are unsuitable for fast-growing SMEs.Based on 15 expert interviews.
Klotz, 2026Regulated and mission-critical systems stay mostly in the buy domain.A conceptual paper and a preprint, not a test.

Sources: Panorama Consulting Group, QUT ePrints, PACIS 2011 Proceedings, arXiv (2021 preprint), arXiv, arXiv.

My readingPanorama sells ERP selection and implementation services, and says it has no financial ties to software vendors. Its sample is 170 organizations with a median revenue of $200.5 million, so it may not describe a small business. To me, it is evidence that a poor fit is expensive whichever route you take.

What should I ask before choosing a route?

Ask who keeps the code working, who owns it, and whether a fit check has been done. The sources point to these three.

The U.S. Copyright Office says the person who creates an original work is its author and owner. Work made for hire covers employees and certain types of commissioned works, and ownership can also come from contracts like assignments.

Three questions to put to any ERP supplier
AskWhyWhere it comes from
Who maintains each customization through upgrades?Customization has maintenance implications, and a SaaS ERP shifts upgrades to the vendor.Light, 2001, and Panorama, 2026
Who owns the code?Ownership follows the author, an employment or commissioning arrangement, or a contract.U.S. Copyright Office
Has a fit check been done?Unexpected technology needs are often a result of poor system selection.Panorama, 2026

Sources: QUT ePrints, Panorama Consulting Group, U.S. Copyright Office.

My readingI would put all three answers in the contract: who maintains each customization through upgrades, who owns the code, and what the fit check found. I am not a lawyer, and the ownership source is a US one, so ask a lawyer before signing.

What should a business do first?

If I were starting today, I would work in this order: map the process, test a ready-made ERP against it, customize only what earns its upkeep, and put maintenance and ownership in writing. It is my reading of the sources above.

  • Map how the business really worksThe Agder authors found unique business processes are one reason SMEs customize. Know whether yours really is unique.
  • Test a ready-made ERP firstPanorama says misfits found late drive extra technology and custom builds.
  • List each customization and its reasonLight says each one needs weighing against its impact on future maintenance.
  • Name who maintains every customizationPanorama says a SaaS ERP shifts upgrades to the vendor. Ask who covers the parts you add.
  • Get code ownership in writingThe U.S. Copyright Office says ownership can come from contracts like assignments.
  • Give someone ownership of governancePanorama says a SaaS ERP makes internal governance more important.
  • Ask for proof of cost claimsI found no independent data comparing ready-made and custom ERPs on cost or speed.

Questions people ask

What is the difference between a ready-made and a custom ERP?

A ready-made ERP is standard software you configure. A custom ERP is written for one business from the start. In between, you can add custom code to a ready-made ERP. Ben Light's study says most organizations reengineer their processes to fit the software so they keep the vendor's support, while a study of four SMEs found customization is more common in small companies.

Is a custom ERP better than a ready-made one?

Not by default. I found no independent data comparing them on cost or speed. The studies I read say some customization is typical but has to be weighed against future maintenance, and Panorama says poor system selection often leads to extra technology and custom builds. What fits depends on how unusual your process really is.

Who looks after upgrades and maintenance?

Panorama says a SaaS ERP shifts responsibility for maintenance and upgrades to the vendor, but makes internal governance more important. Customizations carry maintenance implications of their own, according to Light's study. For a custom build, I read the upkeep as yours to plan and arrange.

Who owns the code of a custom ERP?

It depends on the contract. The U.S. Copyright Office says the person who creates an original work is its author and owner. Work made for hire covers employees and certain types of commissioned works, and ownership can also come from contracts like assignments. So get ownership and source code terms in writing.

Sources

How I checked this. I opened every source linked here and checked each figure and each quotation against the source page, most recently on 3 October 2026. Anything in a box marked “My reading” is my own interpretation, not a finding of the studies. Studies change and new ones appear, so I will update this piece and change its dates when the evidence does.

KEEP READING

See all research