Custom Software vs. Off-the-Shelf: How to Choose

Every few weeks someone asks us the same question: should we build custom software, or just buy something that already exists? It is the right question, and the honest answer is that it depends on something specific — not on which approach sounds more impressive.

Here is the framework we actually use.

Start with the problem, not the solution

Before comparing products, write down the problem in plain language. Not "we need a CRM" but "three people re-enter the same customer details in two different systems, and we find out about it a week late."

The second version tells you what to look for. The first one tells you what to search for in a vendor's brochure — and the two are usually not the same thing.

Off-the-shelf is the right answer when…

• Your process is genuinely standard for your industry.
• The vendor has many customers in South Africa doing something similar.
• You need it working properly in weeks, not months.
• Nobody has budgeted for ongoing maintenance.

Accounting packages, payroll systems, standard CRM and e-commerce platforms sit firmly in this column. Rebuilding any of these from scratch is almost always a bad investment — you would be spending years and a great deal of money reimplementing software that already exists and is properly tested.

If a well-supported platform already does 90% of what you need, that 10% is usually not worth a custom build.

Custom is the right answer when…

• Your process is specific enough that no product fits it.
• You need to integrate several systems that do not talk to each other.
• The software is a genuine competitive advantage, not just an operational tool.
• You have outgrown a platform's pricing model — per-seat costs are now larger than the problem they solve.
• Compliance, data residency or security requirements rule out hosted platforms.

This is where most of our work sits. Not because custom is better in the abstract, but because the businesses that come to us have outgrown a general-purpose tool.

The middle option most people ignore

There is a third path worth considering before committing either way: extend and integrate.

Keep the platform that already handles most of your work, and build only the specific thing it cannot do. Often that is a custom integration, a small internal tool, or a reporting layer that pulls from two systems and gives your team one clear answer.

This delivers most of the benefit at a fraction of the cost and risk of a full rebuild.

Questions to ask before you commit

1. What does this actually cost per year, including hosting, maintenance and support — not just the licence?
2. Who owns the data, and can we export all of it if we leave?
3. What happens to the system if the vendor stops trading or raises prices?
4. How many other South African businesses of our size and type use this?
5. Is there ongoing development cost, or is this a one-off build?

If a vendor cannot answer question three without flinching, that tells you something important about how the relationship will end.

The honest summary

Off-the-shelf software is usually the smarter commercial decision, and we will tell you so when that is the case — including when that means you do not need us.

Custom development earns its place when your process is the differentiator, or when the systems you already rely on genuinely cannot be made to work together.

Whichever path you take, budget for what comes after launch. Software without ongoing support is not finished — it is just newer.

---