On this page8 sections
Three options, not two
Most build-or-buy ERP decisions are really a choice between three options. Packaged ERP is software you subscribe to or license and use largely as designed. Configured and extended ERP is a packaged product set up with your own fields, workflows and reports, sometimes with add-ons or custom code. Custom ERP is built around your workflow and connected to the tools you already use.
| Aspect | Packaged | Configured and extended | Custom |
|---|---|---|---|
| Starting point | You adopt the vendor’s standard processes | You adjust the product within its limits | The system is designed around your process |
| Time to first use | Often quick for standard processes | Depends on configuration and add-on work | Depends on scope; faster one module at a time |
| Unusual workflows | Handled with workarounds outside the system | Fine if the settings stretch far enough | Close fit, including your terms and exceptions |
| Upgrades | Delivered by the vendor | Settings usually carry over; custom code must be retested | Your builder maintains and changes it |
| Main risk | Changing how you work to suit the software | Customisations that make upgrades costly | Dependence on the builder and the quality of the build |
When off-the-shelf is the better choice
Off-the-shelf ERP is usually the better choice when your processes are close to how most businesses in your industry work. You get software many users have tested, upgrades and security fixes from the vendor, and more consultants who know the product.
BDC, the Business Development Bank of Canada, makes the same point: most small and mid-sized businesses are better off with an off-the-shelf system that meets their needs, and should avoid customising it wherever possible. That advice deserves to be taken seriously. Off-the-shelf tends to fit when:
- Your sales, purchasing and stock processes are standard, and you are happy to follow the product’s way of doing them.
- The main needs are accounting, payroll and tax reporting, which mature products already handle well.
- Nobody in the business has time to own a custom system or work with a developer.
When custom ERP earns its place
Custom ERP earns its place when the way you work is genuinely different and that difference matters to customers. Common examples are quoting with many options and rules, products made or engineered to each order, a business that mixes manufacturing, distribution and service, or approval and quality rules that packaged products only handle with spreadsheets on the side.
Be honest about which differences matter. A quoting method that wins work is an advantage; a habit that a standard process would improve is not.
Custom does not have to mean replacing everything. Often the best result is to keep the accounting software, CRM or online store that works and build only the missing piece, connected through APIs (application programming interfaces).
Total effort over time
The purchase or build price is only the first line. The Australian Government’s business.gov.au advises working out the total cost of ownership of any digital tool: the upfront cost plus running costs over its life. For ERP, compare these areas over several years:
- Implementation: process mapping, configuration or development, data migration, testing and training.
- Licences or subscriptions: often per user or per module for packaged products, growing with the business. Custom systems swap these for development and hosting costs.
- Customisation upkeep: every custom field, report or add-on must be maintained and retested when things around it change.
- Upgrades: BDC notes that in a highly customised system, even one that started off the shelf, each upgrade typically means redoing the customisations. A custom system changes only when you decide, so someone must keep it secure and current.
- Dependence on the builder: heavy customisation ties you to the partner who configured it, and custom code to the team that wrote it. Owning the code and data, with good documentation, reduces this risk.
A decision table
Treat this as a starting point, not a verdict.
| Your situation | Lean towards | Watch out for |
|---|---|---|
| Processes are close to industry standard | Packaged ERP | Customising it later, one small change at a time |
| Standard core, with some fields, approvals or reports that differ | Configured ERP with minimal custom code | Custom code that complicates upgrades |
| Accounting works; the gap is quoting, production or jobs | Keep the accounting software and add one module | Unclear which system is the master for each record |
| The workflow is unusual and part of how you win work | Custom ERP, built in stages | Building around habits rather than real advantages |
| Nobody can own the system or work with a builder | Packaged ERP with vendor support | Paying for modules you will not use |
Questions to ask before choosing
Ask these questions of every option, including any custom builder.
- How standard is our process?Map the workflow, including exceptions, and mark which steps are a real advantage and which are habit.
- Who will own the system?Name the person who will decide, approve changes and support colleagues after go-live.
- What happens at upgrade time?Ask how customisations and integrations are retested, and who pays for that work.
- Who owns the data and the code?Get it in writing, with how to export your data in a standard format, and check how the Australian Privacy Principles apply to any personal information it holds.
- How does it connect to what we keep?Check the integration with your accounting software, CRM and online store, and which system is the master for customers, products and prices.
- Can we try it with our own data?business.gov.au advises trialling digital tools before buying. A demo with your products and a real order shows more than a feature list.
How a module-by-module approach reduces risk
The biggest risk in any ERP project is a long build that goes live all at once and turns out not to fit. Delivering one module at a time on one set of data reduces that risk.
- Each module solves one real problem and is accepted before the next begins, so problems surface while they are small.
- You can stop, change direction or switch to a packaged product without losing the modules already in use.
- Data is cleaned once and reused, because every module shares the same customer, product and order records.
Our how we work page compares traditional ERP with custom ERP side by side, and ERP for small business covers which module to start with. If custom looks right, our custom ERP service builds around your workflow and connects the tools you keep.
At Optivise AI, a custom ERP module typically takes about a week to build, plus testing, and each module is accepted before the next starts. You can try a demo ERP with your own test or anonymised data first. Scope and fees are agreed in each proposal.
Questions
Is custom ERP better than off-the-shelf ERP?
Neither is better in general. Off-the-shelf ERP suits businesses with processes close to industry standard, because it is tested, upgraded by the vendor and widely supported. Custom ERP suits businesses whose workflow is genuinely different and matters to customers, provided someone will maintain it. Compare both on fit, total effort over several years and who you will depend on.
What is the difference between configuring and customising an ERP?
Configuring uses settings the product already provides, such as fields, workflows, approval rules and report layouts, and normally carries over when the product is upgraded. Customising changes or adds code beyond those settings. It can fit your process more closely, but each upgrade may require customisations to be retested or rebuilt, which adds ongoing effort.
Should a small business build or buy an ERP?
Most small businesses should first look at off-the-shelf or configured options, especially for standard needs such as accounting, payroll and basic inventory. Building makes sense when a core workflow, such as quoting, production or job tracking, does not fit packaged products without heavy workarounds. A middle path is to keep the tools that work and build only the missing piece.
How much does custom ERP development cost?
It depends on scope rather than a fixed price. The main drivers are the number of modules, the state of your existing data, how many systems must be connected, and how much training and support you need. Starting with one module is a much smaller commitment than a full system, so ask for scope and fees module by module. Custom ERP
What happens if the developer of a custom ERP is no longer available?
This is the main risk of custom software, so plan for it before the build starts. Agree in writing who owns the code and the data, ask for documentation and a way to export data in standard formats, and check that the system uses common technology another developer could maintain. These protections matter as much as the build price.
Sources