Every growing business reaches a point where spreadsheets, a basic accounting package and a collection of disconnected tools no longer hold the operation together. Orders are re-typed, stock figures disagree, production plans live in someone's head, and month-end takes a week. The usual answer is an ERP — enterprise resource planning — system that brings sales, purchasing, inventory, production, service and finance into one place.
The next question is harder: should you adopt a packaged ERP product, or build a custom one around your business? Vendors of packaged ERPs and builders of custom software each have strong views. This guide tries to give an honest comparison, including the cases where custom is the wrong answer.
What an ERP actually needs to do
Strip away the marketing and an ERP does three things:
- Records transactions once — an order, a purchase, a goods receipt, a production booking, an invoice — and lets every department use the same record.
- Applies business rules — pricing, approvals, stock allocation, planning, costing, tax — consistently.
- Gives visibility — what is happening now, what is late, what is profitable.
The modules vary by business: a distributor needs strong sales, purchasing and inventory; a manufacturer adds BOMs, production planning, shop-floor tracking and quality; a service company needs contracts, jobs, technicians and spares. Before comparing options, list which of these areas matter most to your business and where your current pain is greatest.
The case for packaged ERP
Packaged ERPs have real strengths:
- Breadth. They cover many functions out of the box, including complex areas like multi-currency accounting, consolidation and tax.
- Proven processes. Standard processes embody common practice and can bring discipline to a business that lacks it.
- Speed for standard needs. If your processes are typical, configuration can be faster than building.
- Ecosystem. Partners, consultants, trained users and add-ons are available.
- Vendor maintenance. Updates, security and regulatory changes are the vendor's responsibility.
For a business whose processes are close to industry standard, with no strong reason to differ, a well-chosen and well-implemented package is often the right answer.
Where packaged ERP struggles
- Fit. Packages are designed around average processes. Businesses with distinctive ways of quoting, producing, servicing or pricing either change how they work — sometimes losing an advantage — or customise.
- Customisation trap. Heavy customisation of a package makes upgrades difficult and expensive. Within a few years, the business may be stuck on an old version — a legacy system with a famous name.
- Usability. Packages serve many industries, so screens are often generic and dense. Shop-floor workers, technicians and occasional users find them hard to use, leading to workarounds and poor data.
- Cost structure. Licence or subscription fees per user grow with the business, often including users who need only one screen.
- Implementation risk. ERP implementations are notorious for overruns — not because the software is bad, but because the business must adapt to it all at once.
The case for custom ERP
- Fit to your processes. The system is designed around how your business actually works — including the parts that make you competitive.
- Usability by role. Each role gets screens designed for its tasks: a tablet screen for operators, a mobile app for technicians, a dense desk screen for planners.
- Phased delivery. You build the most valuable areas first and expand, instead of implementing everything at once.
- Ownership. You own the software; there are no per-user licence fees for the custom parts, and you decide what changes and when.
- Integration on your terms. The system is designed to connect with the tools you choose to keep.
Where custom ERP struggles
- Breadth takes time. Everything must be built. A custom system will not have every feature of a mature package on day one.
- Regulated functions. Statutory accounting, payroll and tax filing change frequently and are well served by packages. Rebuilding them is rarely wise.
- Dependence on your partner. You need a development team — in-house or external — for the long term.
- Requires product ownership. Someone in your business must define and prioritise what the system does.
Comparison at a glance
| Factor | Packaged ERP | Custom ERP |
|---|---|---|
| Fit to distinctive processes | Limited without customisation | High |
| Breadth on day one | High | Grows by phase |
| Usability for non-office users | Often weak | Designed per role |
| Statutory accounting and tax | Strong | Better integrated than rebuilt |
| Implementation style | Often large and simultaneous | Phased by value |
| Licensing | Per user or subscription | Owned; hosting and support costs |
| Upgrades | Vendor-driven; customisations complicate them | Under your control |
| Long-term dependence | On vendor and implementation partner | On your development team |
The hybrid architecture most growing businesses end up with
In practice, the best answer for many growing businesses is neither pure package nor pure custom, but a deliberate combination:
- A proven accounting package for the general ledger, statutory reporting, tax and payroll.
- A custom operational system for the processes that define the business — quoting, order management, production, service, field operations, dealer management — designed for the people who use them.
- Integration between them, so invoices, receipts, payments and costs flow automatically.
- Specialist tools where they are clearly best — for example, a dedicated e-commerce platform or a payment gateway.
This approach keeps regulated, standard functions in mature products while giving the business full control over the processes where it competes. It also allows phased delivery: the custom operational system can start with the most painful area and grow.
Decision criteria
Score each of these honestly for your business:
- How distinctive are your core processes? If your quoting, production or service model is a reason customers choose you, protect it.
- How many users are outside the office? Technicians, operators, drivers and salespeople need tailored mobile and tablet screens.
- How painful is your current situation, and where? Concentrated pain in one or two areas favours a phased custom approach; broad, standard pain may favour a package.
- How fast is the business changing? Fast-changing businesses benefit from software they can change quickly.
- Do you have product ownership? Custom systems need someone who owns priorities.
- What will the cost look like over five to ten years? Compare subscriptions, implementation, customisation and upgrades for a package with build, hosting, support and enhancement for custom.
Total cost of ownership: what to include
Comparisons that look only at the first year are misleading. Over a realistic horizon, include:
- Packaged: licences or subscriptions for all users over the period, implementation partner fees, customisation, integrations, upgrades (including re-applying customisations), training, internal staff time and add-ons.
- Custom: discovery and development by phase, hosting, third-party services, support and maintenance, enhancements, training and internal staff time.
Also weigh costs that are hard to quantify: workarounds and lost productivity from poor fit, the value of processes that differentiate you, and the risk of a failed implementation.
How to start a custom ERP without a big-bang project
- Map the value chain — from enquiry to cash — and mark where time, money and errors are lost.
- Choose the first module with the biggest pain and clear boundaries — often order management, production tracking, or field service.
- Integrate with what stays — accounting, existing inventory, spreadsheets that will be retired later.
- Go live, learn and expand module by module, each with its own discovery and acceptance.
- Retire old tools as each module takes over.
Within a year or two, the business has a coherent operational system built around its processes, implemented without a single risky switch-over.
Two examples
A distributor that chose a package. A distributor of standard electrical products, with typical buying, stocking and selling processes and most users in the office, evaluated both paths. Its processes matched common practice closely, and its main need was reliable inventory and accounting. A packaged system, implemented with minimal customisation, was the right choice. The company added a small custom dealer ordering portal later, integrated with the package.
A manufacturer that chose custom operations. A manufacturer of engineered-to-order equipment quoted every job individually, with complex configuration, long production cycles, site installation and years of service. Packaged ERPs required heavy customisation for quoting, project-based production and service. The company kept its accounting package and built a custom operational system in phases: quoting and orders first, then production planning and shop-floor tracking, then installation and service with a technician app. Each phase delivered value within months, and the integrated system eventually replaced a dozen spreadsheets.
Common mistakes
- Choosing a package by feature checklist without testing it against your real processes and data.
- Customising a package until upgrades become impossible.
- Building a custom system that tries to do everything in the first release.
- Rebuilding statutory accounting instead of integrating with a proven package.
- Ignoring non-office users when evaluating usability.
- Comparing only first-year costs.
Summary
Packaged ERP suits businesses with standard processes, mostly office users and a willingness to adapt to the software. Custom ERP suits businesses whose processes are distinctive, whose users work beyond the office, and who want to own and evolve their system. For many growing businesses, the best answer is a hybrid: a proven accounting package for statutory functions, a custom operational system for the processes that define the business, integration between them, and phased delivery that brings value early and limits risk.
How to evaluate a packaged ERP properly
Vendor demonstrations are designed to impress, and they usually show the product's strongest flows with tidy sample data. Ask instead for a scripted demonstration: give each shortlisted vendor three or four of your real scenarios — a typical order with your pricing rules, a production job with your routing, a return, a month-end report you rely on — together with sample data, and ask them to show those scenarios in the product. Watch how many steps each takes, which parts need customisation, and how the product handles your exceptions. Invite the people who will use the system daily, not only managers.
Also ask to speak with two or three customers in a similar industry and size, preferably ones who have been live for more than two years. Ask them how much was customised, how upgrades went, how long implementation really took and what they would do differently.
Questions to ask a custom ERP builder
- Which comparable business systems have you built, and can we speak with those clients?
- How will you learn our processes before proposing a design?
- How will you split delivery into phases, and what will the first phase include?
- How will the system integrate with our accounting package and other tools we keep?
- Who will own the code, and how will we access it during the project?
- How will reporting work — fixed reports, flexible queries, dashboards?
- What does support look like after launch, and how are improvements planned?
The answers reveal whether the builder thinks in terms of your business or only in terms of features and technology.
Frequently asked questions
Is custom ERP only for large companies?
No. Small and mid-sized businesses with distinctive processes often benefit most, because packaged ERPs are designed around average processes and their customisation can be expensive. The key is building in phases, starting with the areas that matter most.
Can a custom ERP handle accounting and statutory compliance?
It can, but many businesses choose to keep a proven accounting package for statutory books and integrate it with a custom operational system. This avoids rebuilding well-solved, heavily regulated functions.
What is the biggest risk with packaged ERP?
Forcing the business to fit the software — or customising the package so heavily that upgrades become difficult and costly, recreating the problems of legacy software.
What is the biggest risk with custom ERP?
Trying to build everything at once, or choosing a development partner who lacks experience with business systems. Phased delivery and strong product ownership reduce this risk.
Do we own a custom ERP?
With the right contract, yes — the code and intellectual property for what is built for you belong to you, with no per-user licence fees for the custom parts. Hosting and third-party services remain separate costs.
