Custom software or an off-the-shelf solution? Almost every company that has outgrown spreadsheets, email and a handful of disconnected tools faces this question. The answer rarely depends on technology. It depends on how specific the process you are digitising is to your business, and what it costs you when the system and the work don't match.
In this article we go through the criteria management and IT use to make the call: when an off-the-shelf system is the better choice, when custom development pays off, how to compare total cost of ownership and which risks are most often overlooked.
It's a business question, not a technical one
Off-the-shelf products (SaaS, ERP, CRM) are built for the average user in an industry. That is their strength: they roll out quickly, the vendor maintains them and good practice is built in. The same thing becomes a weakness when your process isn't average.A good rule: buy for what you do like everyone else, build for what sets you apart. Accounting, payroll and email are rarely a competitive advantage. The way you plan production, process orders or manage key accounts very often is.
When off-the-shelf is the better choice
- The process is standard and defined by law or common practice, such as accounting, payroll or tax reporting.
- You need a fast rollout, and the system covers most requirements without major customisation.
- You have no one to own the system internally: someone who decides on development, priorities and maintenance.
- The changes would be cosmetic. If you need a different report layout rather than a different process, an existing system is enough.
When custom development pays off
- The process is your advantage and you don't want to change it to fit someone else's software.
- Existing systems need too many workarounds: spreadsheets alongside the system, manual re-entry, extra tools filling the gaps.
- You need to connect several systems (ERP, webshop, warehouse, a mobile app for field staff) that don't talk to each other.
- Licences scale with headcount, and you plan to grow or need access for partners, customers or field teams.
- Data and logic must stay yours, for regulatory or security reasons, or because they are the core of the business.
Total cost of ownership, not the licence fee
The most common mistake is putting a monthly subscription next to a development quote. A realistic comparison looks at total cost of ownership over several years and includes everything the system actually requires.
| Off-the-shelf | Custom development | |
|---|---|---|
| Upfront investment | Lower: rollout, configuration, data migration | Higher: analysis, design, development, testing |
| Licences and subscriptions | Ongoing, usually per user or module | No licences for the system itself |
| Customisation | Limited to what the vendor allows | The system is built around your process |
| Integrations | Depend on available connectors and the API | Planned from the start |
| Maintenance and upgrades | Included, on the vendor's schedule | Maintenance contract, on your priorities |
| Ownership of code and data | Code stays with the vendor, data export depends on the system | Agreed in the contract |
| Leaving the system | Can be slow and expensive | Depends on documentation and code handover |
Compare over the same period, for example five years, and for the same number of users.
Add the costs that never show up on an invoice: staff time spent moving data between systems by hand, errors from double entry and processes you bent to fit the software instead of the other way round.
The risks that get less attention
Both options carry risk. The difference is who manages it.
- Vendor lock-in. Price changes, a discontinued feature or an acquisition change how you work without you having a say.
- A roadmap you didn't write. The feature you need may arrive in two years, or never.
- Dependence on the team that built your custom system. Reduced by documentation, access to the source code and a clear maintenance contract.
- An overloaded first release. Custom projects most often miss deadlines when everything is squeezed into version one. A smaller first step followed by upgrades carries less risk.
Custom software development
Web, mobile and desktop applications for processes that off-the-shelf systems don't cover, with a written fixed-price quote.
The hybrid approach: a standard core, custom edges
The decision rarely has to be all or nothing. A common and sound architecture is an off-the-shelf system for standard processes (ERP, accounting) with custom applications at the edges: a customer and partner portal, a mobile app for the field team, an internal planning tool or an integration layer connecting systems that otherwise don't talk.You keep the advantages of the standard system and build only what sets you apart.
Five questions before you decide
- 1
How specific is the process?
Would a competitor describe it the same way? If so, an off-the-shelf system is probably enough.
- 2
What does the mismatch cost today?
Estimate the hours of manual work, the errors and the workarounds that exist because the system doesn't follow the process.
- 3
What does the system have to connect to?
List the systems, the direction of data and how often it has to be in sync.
- 4
Who will own the system?
Someone in the company has to set priorities, whichever option you choose.
- 5
What if you want to leave in three years?
Check data export, code ownership and documentation before you sign, not after.
How we approach this decision
In the first consultation, which is free, we go through the process, the systems you already have and what must not be interrupted. If there is an off-the-shelf product that covers your needs, we'll tell you. If development makes sense, you get a written quote with the scope of work and a fixed price, and you review how the system will look before it is built. Before go-live we test it with you, on real cases from your business.
Let's talk about your system
Describe the process and the systems you work with. We'll come back with a proposal and next steps.


