- If you work like everyone else, buy off-the-shelf. Custom software pays off when your operations don’t fit one without patches.
- Compare over three to five years: per-user fees, patches, hours copying data and the cost of changes.
- It’s not all or nothing: the usual route is keeping what works, connecting it and building only what’s missing.
The short answer
If you work like everyone else, buy off-the-shelf and keep your money. If your operations don’t fit one without patches, go custom. The hard part is knowing which of the two you are.
Custom and off-the-shelf, side by side
| Off-the-shelf | Custom | |
|---|---|---|
| At the start | Fast, with little investment. | More time and initial investment. |
| Each month | A fee, usually per user. | Hosting and maintenance. |
| Way of working | You adapt to the software. | The software adapts to you. |
| If you change something | You depend on what it allows. | It gets changed, and you pay for that change. |
| Who owns it | The vendor. You rent it. | You, if it’s in writing. |
| Main risk | It goes up in price or disappears. | Choosing the wrong people to build it. |
Five questions to decide
- Does someone copy data between programs? It’s the clearest sign something doesn’t fit.
- Is what matters still in Excel or on paper, even though you pay for software?
- Have you seriously tried an off-the-shelf package? If not, start there.
- What do the patches cost you? Office hours, errors and people doing things by hand.
- Does your way of working give you an edge? If it’s what sets you apart, don’t squeeze it into someone else’s mould.
If you answer yes to several, it’s worth looking into.
What to really compare
Don’t compare the first month’s fee with the development quote. Compare over three to five years:
- Per-user fee multiplied by your users and all those months.
- Hours a month of people copying data or working around the software.
- What each change costs in one case and the other.
- What happens to your data if you want to leave one day.
We break it down in how much custom software costs.
The third option: connect
It’s not all or nothing. Often the best route is keeping what works, connecting it and building only what’s missing. You pay less and don’t change what your team already knows how to use.
A real case
A transport company needed to handle expenses, truck incidents, delivery notes and consignment notes in its office. We built it a custom system, organised the way they work and with AI agents that take the repetitive tasks. It builds on what we learned creating FleetyManager, our own software for transport companies.
It paid off because their operations didn’t fit an off-the-shelf package. That isn’t always the case.
If you go custom, insist on this
- That they understand your operations first.
- That the code, data and documentation are yours, in writing.
- Work in phases, with a first useful version within weeks.
- Knowing what happens after delivery.
More in custom software for businesses.