Off-the-shelf vs custom: why ready-made often costs more.

I'll start with something most developers won't admit: off-the-shelf software is sometimes the right answer. If you need standard accounting, email or word processing, you should absolutely buy the established product — nobody should pay to have Xero or Gmail rebuilt. So this isn't "custom good, packaged bad." It's about the specific, operational parts of your business where a generic tool starts to chafe — and where the sticker price hides the real cost.

The price you see isn't the price you pay

A packaged system advertises a small monthly number and that's what sticks in your mind. But the real cost is the small number, plus the time your team wastes working around it, plus the per-user fees as you grow, plus the second and third tools you buy to fill the gaps, plus the cost of one day having to move off it. Let's walk through where that adds up.

1. You bend your business to fit the software

Packaged software is built for the average of thousands of companies, which means it fits none of them exactly. So your team adapts: they skip the fields that don't fit, keep a "real" version in a spreadsheet on the side, and invent workarounds for the steps the software gets wrong. Every one of those workarounds is a small daily tax on your team — and a place where mistakes creep in. A custom system flips this: the software bends to your process, so there's nothing to work around.

2. Per-user fees punish you for growing

Most off-the-shelf tools charge per user, per month, forever. It feels harmless at five people. At twenty-five it's a serious line item that grows every time you hire — you're effectively paying a tax on your own success, indefinitely, and you never own anything at the end of it.

25 staff at, say, R350 per user per month is R8,750 a month — over R100,000 a year, every year, with nothing owned at the end.

A custom system is priced on the system, not per login. As your team grows, your people cost you nothing extra to add. For a growing business, that difference compounds dramatically over a few years.

3. The feature you need is always "on the roadmap"

The day you need the software to do something specific to your business, you hit a wall. You log a request, and it joins a queue behind thousands of other customers. Maybe it ships next year; maybe never. You don't get a vote, because the product isn't built for you. With a custom system, the thing you need is the roadmap — you ask, and it gets built, because it's your software.

4. Your data lives on someone else's platform

With most SaaS, your data sits on the vendor's servers, often outside South Africa, under their terms. That raises real POPIA questions about where personal information lives and who controls it. And the day you want to leave, you discover how hard they've made it to get your data out cleanly — that friction is a deliberate part of the business model. A custom system keeps your data in a place you control, exportable any time, which is both safer and a lot less stressful.

5. The Frankenstein stack

Because no single packaged tool does everything, you end up with five of them — one for quotes, one for stock, one for the CRM, one for jobs — none of which talk to each other. So your team re-types the same information into each, and you stitch reports together by hand. The monthly fees stack up, and so does the wasted time. A custom system can hold the pieces that matter to you in one place, with everything connected, so data flows instead of being re-entered.

When off-the-shelf genuinely wins

To keep this honest, here's when you should not call me and should just buy the product: when the job is completely standard (accounting, payroll basics, email), when you need it live this afternoon, or when the volume is so small that a spreadsheet is genuinely fine for now. Good software decisions are about matching the tool to the job — not buying custom for the sake of it.

The honest comparison

For the operational core of your business — the work that makes you different from your competitors — a custom system usually wins on the things that matter over time: it fits exactly how you work, there are no per-user fees, your data stays yours, changes happen on your say-so, and you deal with the person who built it. Packaged software wins on speed-to-start and on truly standard tasks. The mistake is using a generic tool for the part of your business that isn't generic at all — and paying for that mismatch every single day.

If you're currently wrestling a packaged tool into doing something it was never meant to do, it's worth a 20-minute chat to work out, honestly, whether custom would actually cost you less over the next three years. Sometimes the answer is no — and I'll tell you so.

Work out what's cheaper for you