Sooner or later, most businesses hit a wall with their software. The tool you bought no longer fits how you work, or there is no tool out there that does what you need at all. That is the moment the question lands on the table: do we buy something off the shelf and adapt to it, or do we build something of our own that fits us exactly? It is one of the most expensive decisions a growing business makes, and it is often made on instinct.
Custom software is not better than off-the-shelf, and off-the-shelf is not cheaper than custom. Each is right in some situations and a costly mistake in others. The skill is knowing which situation you are actually in.
We sit on both sides of this. We build custom software, and we also help clients choose and set up off-the-shelf systems. So we have no reason to push you toward one or the other. What follows is the same reasoning we walk through with a client before a single line of code or a single licence is paid for.
Default to buying for the ordinary stuff
If thousands of other businesses need the same thing you do, someone has almost certainly built it already, and built it well. Accounting, email, payroll, basic stock control: these are solved problems. Building your own version is like opening a bakery and starting by inventing flour.
For these commodity needs, buying wins almost every time. You get something mature, supported, and tested by thousands of users who already found the bugs for you. You are not paying to discover problems that other people solved years ago.
There is a quieter benefit too. When you buy a well-established product, you also buy the community around it: the help articles, the forums, the accountants and bookkeepers who already know the package, the staff who arrive having used it at their last job. None of that exists for software only your business runs. It is real value that never shows up on the invoice, and it is easy to forget when a custom build is sounding exciting.
If your competitors could buy the exact same software off the shelf and run their business just as well, that software is not where you should be spending money to be different.
Build when it is genuinely your difference
There are two solid reasons to build. The first is that the thing in question is your real differentiator, the part of how you work that sets you apart from competitors. The clever way you route deliveries, price jobs, or manage a process nobody else does quite the same. Off-the-shelf software will flatten that into something generic, and your advantage disappears.
The second reason is simpler: nothing on the market actually does what you need. You have looked, you have demoed, and every option forces you to bend your business into an awkward shape it was never meant to take. At that point, building can be the cheaper path, not the expensive one.
The hidden costs nobody mentions
Both choices come with costs that are easy to ignore at the start and impossible to ignore later.
- Buying. The sticker price is rarely the real price. Heavy customisation to make an off-the-shelf tool fit can quietly cost more than building would have, and you are still locked into someone else's roadmap and price increases.
- Building. Custom software is never finished. Someone has to maintain it forever: fix bugs, keep it secure, update it when the world around it changes. If you cannot commit to that, do not build it.
The forever question
Before you build anything custom, ask: who looks after this in three years? If the honest answer is a shrug, you are not choosing between build and buy. You are choosing between a supported product and an orphan. Buy the product.
A short decision checklist
When a client is torn, we run through a handful of plain questions:
- Is this a common need or a unique one? Common leans buy, unique leans build.
- Does it set us apart from competitors? If yes, building protects that edge.
- Does anything on the market fit without heavy bending? If yes, buy it. If everything needs major surgery, building gets cheaper.
- Can we maintain it long term? No honest answer here means do not build.
- What is the total cost over five years, not five months? Run both numbers properly before deciding.
The path most people miss: do both
The choice is rarely all-or-nothing. The smartest setups we build are hybrids. You buy the core, a solid accounting package or a proven CRM, and you build only the edges: the small custom piece that connects those tools, or the unique workflow that nothing on the market handles.
This gives you the best of both. The boring, solved parts are handled by mature products someone else maintains. The part that makes you different is yours, built to fit, and small enough to look after. You are not reinventing flour, but you are still baking your own bread.
Think in years, not invoices
Whichever way you lean, do the maths over the full life of the thing. A licence at R2,000 a month is R120,000 over five years before any add-ons. A custom build might cost more upfront and less to run, or the other way around. The right answer is the one that costs less over years and fits how you actually work, not the one with the smaller first invoice.
Get that comparison honest, and the build-versus-buy decision stops being a gamble. It becomes what it should be: a clear-eyed business call about where your money does the most good.
