Custom ERP vs off-the-shelf: a decision guide for SMEs
Off-the-shelf ERP, customized ERP or custom software? A plain decision guide for SMEs: when each option pays off and what to ask before you decide.
When orders, stock and invoices are spread across several spreadsheets and programs, sooner or later a company starts looking at ERP. The question that follows is not really what ERP means. It is whether to buy an off-the-shelf ERP system, have an existing product customized to fit, or build custom software around the way you work. This guide walks through the three options, when each one pays off, and the questions worth asking before you decide.
Build vs buy ERP: what are you actually choosing?
ERP stands for Enterprise Resource Planning: software that keeps the data behind your daily operations in one place, from orders and stock to purchasing, invoicing and management reports. What an integrated ERP system covers, and its benefits and drawbacks, is explained in our ERP system guide.
This article is about the next step: how you get that system. There are three routes.
Three routes: off-the-shelf ERP, customized ERP, custom software
Off-the-shelf ERP
A ready-made product written for many companies, which you use more or less as it is. You usually pay a monthly or annual fee, typically per user, and the vendor develops the product further. You can be up and running soon if your processes are standard. In return, your company adapts to the software.
Customized ERP
An off-the-shelf ERP system that the vendor or a partner reworks for your company: new fields, your own documents, extra approval steps or reports. For small changes this is a good middle ground. The more that has to be rewritten, the more it costs, and the more trouble it can cause when the vendor releases a new version, because the customized parts then need checking and often fixing.
Custom software
Software designed and built specifically for your company. It contains the screens, steps and rules your team actually works with, and nothing else. The finished system, the source code and the documentation belong to you, and you do not have to wait for a vendor to add what you need. It does take more work at the start: first we need to understand how your company works, then design the system.
| Aspect | Off-the-shelf ERP | Customized ERP | Custom software |
|---|---|---|---|
| Fit | Your company adapts to the software | The software adapts in a few places, you adapt in the rest | The software adapts to your company |
| Getting started | Can be running soon | The customization has to be designed and built first | Needs discovery and design first, together typically 1–4 weeks for a small or medium project |
| Cost | Usually a monthly or annual fee that grows with users | Monthly or annual fee plus the cost of customization | One-off development fee with a fixed-price quote after discovery, then running costs |
| New versions | The vendor decides what goes in | Customized parts need checking with every new version | Extended when your company needs it |
| Ownership | You rent the software | You rent the software, and the customization often ties you to the vendor | You own the source code and documentation |
When is off-the-shelf ERP enough?
Honestly, for many SMEs it is. If these apply to you, you probably do not need custom development:
- your processes look like those of most companies in your industry;
- you mainly trade or provide services, without special rules for pricing, production or stock;
- the way you handle orders or stock is not what sets you apart;
- you are willing to adjust a little to the software in return for getting started soon.
In that case custom software is not worth it. Choose a good off-the-shelf product and, before you sign, test it with your own data and a few cases that come up every day. What to look for when you compare products is covered in the relevant section of our ERP system guide.
When does ERP customization make sense?
Customization is a good choice when the off-the-shelf product covers most of your work well and only needs adjusting in a few places. For example, you need your own document layout, an extra approval step or a report management asks for.
These are signs the customization will be too big:
- in the vendor's offer, customization costs close to or more than the product itself;
- your team still has to keep a spreadsheet next to the system because the important part does not fit;
- the vendor says the feature you need will come in a later version but cannot say when;
- your most important workflow only works in the system through workarounds.
At that point, reshaping an off-the-shelf product is often more expensive than a well designed custom system, and new versions keep causing trouble for years.
When is custom software worth it?
Custom development pays off when the way you work differs from the norm and that difference is your strength. Typical situations:
- Your own pricing: a quote is built from many factors, and that know-how took years to build. Today it lives in a big Excel file and in one or two people's heads.
- Custom manufacturing: every order is a little different, so the production steps, material needs and lead time have to be worked out order by order. Software for custom manufacturing calculates this by your rules, not by those of an average manufacturer.
- Special rules: for example, in contract manufacturing the customer's material has to be tracked separately, a construction company has to track materials and labour hours project by project, or driver and vehicle scheduling follows rules of your own.
- Many tools, manual copying: you use several programs and spreadsheets, and hours a day go into retyping data from one into another.
- An outgrown legacy system: you have an old program nobody can develop further, but the knowledge built into it still matters.
- Independence: you want to own the system, rather than let a vendor's pricing and roadmap decide what it can do.
Custom software does not mean replacing everything. A common setup keeps invoicing and accounting in the existing program, and a custom system handles only the part where your company differs. For many companies getting stock under control is the right first step, which we cover in our article on inventory management software.
How a custom project works in practice and what drives the price is covered in our guide to custom software development.
What to check before you decide
The question is not which route is better in general, but which one fits your company. These steps help:
- Write down how your company works today. How an order comes in, who does what with it, and where work gets stuck. That shows what the system has to do.
- Think about how you differ from your competitors. If that part fits into an off-the-shelf product, the off-the-shelf or customized route will probably do. If it does not, consider custom software.
- Collect three real cases that cause trouble today, and ask the vendor or developer to show their solution on those.
- Work out the total cost over several years. For off-the-shelf: the monthly fee, customization, implementation and training. For custom: the development fee and running costs. We explain how much an ERP system costs and what drives the price in a separate article.
- Ask who will own the system and the data. Can you export all your data if you switch later? With custom software, who owns the source code?
- Ask the people who will use it. Warehouse staff, administrators and whoever does the invoicing know exactly where it hurts. If they are left out of the decision, they will struggle to accept the new system.
Whichever route you choose, implementation matters as much as the software itself: moving the data, training the team and planning the switchover.
How we work when custom is the right route
We start with a free initial consultation. Based on it, we design the system at a fixed price, step by step, so from the very beginning you see on a live prototype how it will work. After that, in a separate offer, we give a fixed price for development that covers everything we recorded during design.
1. Free initial consultation
A one-hour online conversation. You tell us how your company works today, which programs and spreadsheets you use, and where it hurts most. Together we work out which route is realistic: off-the-shelf ERP, customizing an existing system or custom software. If it turns out an off-the-shelf product is enough, we will tell you.
2. Discovery and system design with a live prototype
Discovery and design typically take 1–4 weeks together for a small or medium project, and the fee is agreed in advance. We go through your processes and spreadsheets, then build a clickable prototype, a working model of the system you can try in the browser. Live prototype: before development starts, you already see your whole system working, and you can change it step by step during this phase. If you continue with us after design, the system design fee is credited against the development price.
3. Fixed-price quote for development
After discovery we give you a fixed-price quote: based on the approved prototype, we list what you get and what it costs, covering everything we recorded during design. We agree the development schedule at the same time.
4. Development with automated tests
Based on industry experience, a small or medium internal system used to need a development team of typically 3–4 people, and comprehensive automated testing, which keeps the system stable and easy to extend for years, pushed that cost even higher. Today, with the right methods, every project is led end to end by one lead developer, supported by a complete AI team, including a large suite of automated tests.
Automated tests are written for every part of the system, and the full test suite runs before every new release, whether the system runs with us or at your site. So after a later fix or extension you can check that everything that worked before still works. You get a weekly update during development.
5. Go-live, operation and support
Before go-live we load your existing data and train your team. After that there are two separate questions. The first is operation, meaning where the system runs: in Microsoft Azure, operated by us, or on your own servers. If we operate it, there is a separate test and production environment, and changes go live only after approval. The second is support, meaning who fixes and develops the system further. You can sign a separate support contract with us even if the system runs at your site. We write documentation for every system, covering development and how to run the tests, so someone else can take over if needed. The source code and documentation belong to you.
To see what kinds of business systems we build, take a look at the services section on our homepage.
In short
If your processes look like most companies' in your industry, choose a good off-the-shelf ERP system and test it with your own data before you sign. If you differ in only a few places, a small customization can be a good middle ground. But if your strength is exactly what an off-the-shelf product cannot follow, it is worth finding out what custom software that works the way your company does would cost.