We build custom software, so treat what follows with appropriate scepticism. But recommending a custom build to every business that asks would be bad advice, and it tends to produce unhappy clients.
Here is how we actually think about it.
Off-the-shelf is usually right when
Your process is standard. Accounting, payroll, and email are solved problems. The rules come from regulation and convention, not from anything unique to your business. Buying is almost always correct here.
You need it working next week. Packaged software is available immediately. Custom development takes months.
The budget is genuinely tight. A monthly subscription spreads cost in a way a build cannot. If capital is constrained, that matters more than a better long-term fit.
Nobody internally can specify what you need. If the requirements are vague, a custom build will discover that expensively. Use a package first, learn what does not fit, then reconsider.
Custom is usually right when
Your process is your advantage. If the way you handle production scheduling or pricing is part of why you win business, packaged software will force you to abandon it or work around it.
You are paying for workarounds. Count the spreadsheets, the re-keying, the manual reconciliation that exists purely because the software does not fit. That labour is a recurring cost, and it often exceeds the build cost within a couple of years.
Per-seat licensing scales against you. Some packages cost more precisely as you grow. A build is a fixed cost that does not penalise success.
Integration is the actual requirement. When the real need is making four existing systems talk to each other, no package solves that — that work is custom regardless.
The comparison people get wrong
The usual mistake is comparing the licence fee to the build quote. The honest comparison includes:
- Licence or subscription over five years, at your expected headcount
- Staff hours spent on workarounds, at real salary cost
- Customisation and consultant fees to make the package fit
- The cost of migrating away if the vendor changes direction
Against the build, count development, hosting, and ongoing maintenance — because custom software does need maintenance, and pretending otherwise is how projects sour.
The middle path
Most businesses land somewhere in between: buy accounting, build the operational system that runs your specific workflow, and integrate the two. That is a perfectly good answer and often the cheapest overall.
What we would ask you
Before quoting anything: what does the current process cost you in hours, and which part of it would you refuse to change even if the software demanded it? The answers usually make the decision obvious.
If you want that conversation without a sales pitch attached, get in touch. Sometimes our advice is that a package will serve you better.
