Home/Insights/Technology Consulting
Technology Consulting5 min readOctober 15, 2026By Loyiso Ngcala

Build, buy or configure? How to choose business software

A team comparing business software options on a laptop

When a process starts to strain, most businesses jump straight to a product search or a quote for custom software. Both can be the right answer. But there is a third option that is often cheaper than either, and the choice between the three deserves an hour of structured thinking before any money is committed.

This article sets out the three options, when each one fits, and a simple test for comparing their real cost.

Option 1: Buy an off-the-shelf product

Off-the-shelf software, usually sold as a monthly subscription, is the fastest route when your process is close to how most businesses work. Accounting, payroll, email, basic CRM and help-desk tools are mature categories with good products.

Buying fits best when:

  • Your process is standard and you are willing to adapt to the product's way of working.
  • You need something running within weeks rather than months.
  • The vendor's roadmap covers what you will need over the next few years.

Watch for the costs that do not show on the pricing page: per-user fees that grow with headcount, add-on modules that turn out to be essential, pricing in US dollars that moves with the exchange rate, and the effort of getting data out if you ever leave.

Option 2: Configure what you already have

Many businesses already pay for tools that could solve the problem with some configuration: Microsoft 365 or Google Workspace, an existing CRM or ERP, or a low-code platform. Shared lists, approval flows, forms and simple dashboards can often be built on top of these without a new licence.

Configuring fits best when:

  • The process is relatively simple, with a few steps and a handful of roles.
  • Your team already uses the platform every day.
  • Someone will own and maintain the configuration after it is built.

The risk is building something that only one person understands. Configuration still needs documentation, permissions and a named owner, or it becomes the next spreadsheet nobody dares to touch.

Option 3: Build custom software

Custom development makes sense when the way you work is part of what makes the business competitive, or when no product fits without heavy workarounds. It is also worth considering when you would otherwise license and connect several separate products to cover one process.

Building fits best when:

  • Your process, approvals or reporting lines are specific to your organisation.
  • You need several functions to share one set of records.
  • Licence costs are rising faster than the value you get from them.
  • You want to own the system and its data outright.

The trade-off is a larger upfront investment and the need for ongoing support. Custom software should be delivered in phases, so the first module is in use and proving its value before the rest is built.

A simple test: compare three-year cost, not the first invoice

Comparing a monthly subscription with a once-off development quote is misleading unless both are stretched over the same period. A three-year view is a practical starting point.

As an illustration only: a product costing R400 per user per month for 25 users comes to R10,000 a month, or R360,000 over three years, before add-ons, price increases or exchange-rate changes. A custom system has a build cost plus a monthly support amount. Neither option is automatically cheaper; the point is to compare them on the same basis.

For each option, add up:

  • Licences or build cost over three years.
  • Setup, configuration, data migration and training.
  • Support, maintenance and hosting.
  • The cost of the workarounds that remain, measured in staff hours.

Five questions to ask before deciding

  1. Which specific problem are we solving, and how will we know it is solved?
  2. How different is our process from the way a standard product expects us to work?
  3. What do we already own that could do part of the job?
  4. What will this cost over three years, including the workarounds?
  5. Who will own the system, the data and its upkeep once it is live?

Mixed answers are normal

The best outcome is often a combination: buy the standard parts such as accounting and payroll, configure the simple workflows on the platform you already use, and build only the part that is genuinely specific to your business, connected to the rest. That keeps custom development focused where it creates the most value.

Key takeaways

  • There are three options, not two: buy, configure or build.
  • Compare options over three years, including hidden and workaround costs.
  • Build only what is specific to your business, and deliver it in phases.
  • Every system needs a named owner, whichever option you choose.
The right answer is the one that solves the problem at the lowest total cost, not the one with the smallest first invoice.

If you want an independent view before committing budget, our technology consulting service compares build, buy and configure options for your process and gives you a costed recommendation. Where custom software is the right answer, we build it as business systems delivered in phases.

Put it into practice

Talk through your next software decision.

Keep reading

Related insights

Why South African Businesses Should Stop Running Critical Processes on Spreadsheets
Business Systems9 min read

Why South African Businesses Should Stop Running Critical Processes on Spreadsheets

Read article
Building software that scales with the business, not against it
Software Development5 min read

Building software that scales with the business, not against it

Read article
POPIA and your business systems: a checklist before you build or buy
Data Protection5 min read

POPIA and your business systems: a checklist before you build or buy

Read article