Custom software or off-the-shelf: how to decide
· 7 min read
Most businesses asking this should buy. Off-the-shelf products are cheaper, faster, maintained by somebody else, and improve without you paying for it. Anyone who tells you otherwise as a general rule is selling development.
The interesting question is where that stops being true.
Buy when the process is normal
Accounting, payroll, email, scheduling, basic CRM — these are solved. Your version of them is not special, however it feels internally, and building your own means paying to reach a standard that a subscription already exceeds.
A useful test: if you can describe the process to another business in your industry and they nod, buy it.
Build when the process is the business
Sometimes the way you do a thing is the reason customers choose you. A pricing model nobody else runs, a workflow that lets you turn work around faster, a way of handling a job that competitors cannot copy easily.
Force that into a product built for the standard approach and you either lose the advantage or spend years fighting the software. That is when building is not indulgence.
The middle case, which is most cases
Usually the answer is neither. You buy the standard components and build the small piece that joins them in your particular way — the layer that moves a booking into the job system, applies your pricing rules, and writes the invoice.
That integration layer is often a fraction of a full build, and it captures most of the value people imagine they need a bespoke system for.
Questions that decide it
- Could a competitor buy the same product and get the same result? If yes, buy it.
- Are you working around the product more than with it? That is the signal to build.
- Is the workaround a spreadsheet somebody maintains by hand? That is a build waiting to be scoped.
- Would this still matter in three years, or is it this year’s problem?
What building actually commits you to
The build is the smaller half. Custom software needs hosting, updating, securing, and someone who understands it when something breaks. Budget for that at the start, or you will discover it later at a worse moment.
Two things to insist on if you do build. You own the code, in your own repository, with documentation — anything else is a hostage arrangement. And it should be written so somebody other than the original developer can maintain it, because eventually somebody else will.
The honest summary
Buy the boring parts. Build the part that is genuinely yours. Be suspicious of anyone whose recommendation happens to match the largest thing they sell — including us.
Common questions
Quick answers.
Is custom software more expensive than a subscription?
Almost always upfront, and not always over several years — subscriptions scale with seats and usage while a build is mostly a fixed cost plus maintenance. The comparison worth doing is total cost over three years including the hours people currently spend working around the product.
Do we own custom software you build?
You should own any custom software anyone builds you — the code, in your repository, with documentation and tests. If a supplier is vague about this, that is the answer to a different and more important question.
What is the middle option between buying and building?
Buying the standard components and building only the layer that connects them in the way your business actually works. It is usually a fraction of a full build and captures most of the value.
Next step
Ready to put this into practice?
Book a consultation and we will map where this applies to your business — and you keep the findings either way.