The cost of custom software in South Africa is mostly the time of the people who design, build, test and run it. Seven things decide how much of that time a system needs:
- how much of the business it runs
- what it has to connect to
- whether it replaces a live system
- how many people, sites and roles use it
- how settled the process is
- how sensitive the data is
- who builds it, and how they're paid
A custom AI adds more on top, chiefly the state of your data and a usage bill that arrives every month. Knowing what moves the price lets you see what's driving a proposal, and whether anything is missing from it.
Why can't anyone give you a price on the first call?
Every software estimate is effort multiplied by a rate, so it's only as good as the understanding behind it. On a first call, neither side knows how many exceptions your process carries, which systems hold the data, or what state that data is in. A quantity surveyor won't price a building without drawings, and a software supplier can't give a real estimate before someone has studied how your operation runs.
A 2012 study by McKinsey and the University of Oxford, covering more than 5,400 IT projects in general, shows what a weak estimate costs. The large projects in it ran 45% over budget on average and delivered 56% less value than predicted.
For a buyer, the cheapest time to find the real scope is before anyone signs. That's why CBOS holds a consultancy session before it writes a proposal.
What decides how much custom software costs in South Africa?
Each of the seven factors adds work in its own way. Knowing which ones apply to your company tells you more than any average figure would. Few projects score high on all seven, and a good proposal shows you which ones are driving yours.
How much of the business it runs
One process for one team is a smaller job than a system that runs everything from order to invoice. Every process you add brings its own screens and rules, and the rules carry most of the work. An approval limit that differs for franchise customers, or a rate only one client gets, has to be written into the software so nobody has to remember it.
What it has to connect to
A new system earns its keep by sharing data with the systems around it. For example, a company running Sage, an ERP and Microsoft 365 needs each connection built and tested on its own. One accounting system can mean several connections: the Sage integrations CBOS has built include point-of-sale, sales invoices and inventory. An older application without a modern interface (an API) usually costs more to connect than a current product.
Whether it replaces a live system
Replacing a live system means understanding the old one first, moving its data across and keeping the business trading during the switch. Moving the data is a cost of its own, set by how clean the old data is, how different its format is and how much downtime the business can accept.
When CBOS rebuilt Gallo Images' platform, the work began with an analysis of the old architecture and its legacy source code. Operations also had to keep running through the move from the previous provider. That groundwork is paid for before a single new screen exists. It's why a replacement usually costs more than a new build of the same size.
How many people, sites and roles use it
Every branch, region and role adds permissions to manage, such as who sees which records and who approves what. Supa Quick's Franchise Management System, which CBOS built and still supports, connects more than 200 fitment centres, head office and fleet partners on one platform.
That system gives head office central oversight while each centre keeps room to work locally. Getting that balance right is design work, and it grows with the number of sites.
How settled the process is
A process agreed before the build starts gets built once, whereas one still being decided gets parts built twice. Someone on your side pays for both versions. Naming one person with the authority to decide costs little and prevents a lot of that waste.
CBOS builds in short cycles and you review working software as it grows, so a wrong turn shows up while it's cheap to change.
How sensitive the data is
A system that holds personal information has to protect it. Section 19 of the Protection of Personal Information Act (POPIA) requires "appropriate, reasonable technical and organisational measures" to secure it. In the build, that means access control, backups, logging and security testing. Financial or medical records need more of each than a scheduling tool does.
Where the data is kept matters as well. Section 72 limits sending personal information to a third party abroad. That makes the hosting, and any outside service the system calls, part of the design. CBOS builds systems whose data stays in South Africa when the work needs it.
Who builds it and how they're paid
Team cost depends on seniority, location and mix, and the hourly rate is only half the sum. A cheaper team that needs twice the hours costs more in the end, and misreading the process costs more again when the work is redone.
Ask who will do the work, how senior they are, and whether the people who scope the project are the ones who build it. At CBOS one team does the work, from understanding the process to looking after the system once it's live.
What decides the cost of a custom AI?
A custom AI is software too, so the seven factors above still apply, including the integration work for an AI that looks up orders or drafts invoices. Four more factors decide what it costs.
The state of your data
An AI can only answer from data it can reach and read. If your records sit in spreadsheets, scanned PDFs and three systems that disagree, the first phase is getting that data captured, cleaned and connected. On 26 February 2025, Gartner predicted that through 2026, organisations will abandon 60% of AI projects that aren't supported by AI-ready data.
I&J's project wasn't an AI build, but it shows what getting data ready looks like. Before CBOS built its system, the logs from I&J's ten deep-sea trawlers were hand-written and sent ashore irregularly. The system now captures data from onboard machines and from crew and vessel apps, and sends it over a satellite link to one shore platform. Data has to be captured in one place like that before an AI can work with it.
Which model it uses and how much it's used
The model behind an AI is billed by use. A model provider charges per token (roughly a piece of a word) for what goes in and what comes out. The bill therefore grows with every user and every question. Those prices are usually set in US dollars, which means your rand bill also moves with the exchange rate.
This usage bill is a running cost that never appears in the build price. Caching the instructions the AI receives over and over brings it down, and so does batching jobs that aren't urgent. Ask whether a proposal's design uses both.
Guardrails and permissions
An AI that's billed by use needs limits on how much it can be asked. The OWASP Top 10 for large language model applications lists runaway usage as a risk in its own right. It even covers attackers driving up a pay-per-use bill on purpose, and its defences are rate limits, quotas, timeouts and monitoring.
Permissions matter as much, because an assistant that answers from every document can tell a junior clerk what's in the payroll file. CBOS builds private AI with permissions set per user, data stored and processed in South Africa, and no outside AI model training on it. Each guardrail is designed and tested like any other part of the system, so each is part of the cost.
Testing and watching it after launch
An AI's answers have to be checked against a set of known questions before launch. They have to be checked again after every change to the model, the instructions or the data. Someone also has to watch what it's asked and what it costs each month, for as long as it's in use.
What does custom software cost after it goes live?
The build is the price everyone compares, but a system keeps costing money after it goes live. These are the running costs to ask about:
- Hosting and monitoring, billed monthly, with a bill that grows with your users and your data.
- Support for the day a user is locked out or a sync fails at month-end.
- Maintenance: fixing faults, adapting to changes around the system (a new Sage version, a supplier's new interface), improvements users ask for, and preventive work such as security updates.
- Change after go-live, which CBOS treats as its own stage so the platform doesn't become the next legacy system.
- AI usage, billed every month, if the system includes an AI.
- Your own people's time for testing, checking data and training staff.
Maintenance is usually budgeted as a yearly amount set against the build, and the proposal should state it. The adapting and preventive kinds tend to be underfunded, because nothing looks broken until a connected system changes.
The lowest build price can still give you the most expensive system to own over five years, so ask for every running cost next to it. If a proposal can't show these, the price on it is still a guess, however precise it looks.
Is it cheaper to build software or pay for a subscription?
Neither is cheaper in every case, so compare the same functionality over the same period. A subscription looks smaller than a build in year one because it spreads its cost. Seat-based fees then grow with every user you add, and customisation is often charged on top. The hours your staff spend working around what a product can't do appear on no invoice at all.
| Subscription (SaaS) | Custom build | |
|---|---|---|
| What you pay for | A licence, usually per user per month | The build, then hosting, support and change |
| Who owns it | The vendor | You own the code and data, if the contract says so |
| What grows the cost | More users, add-ons and customisation | More processes, connections and changes |
| Usual accounting treatment | An operating expense | Can be capitalised once it meets IAS 38 |
For most companies the answer is a mix. Products for solved problems such as accounting, payroll and email are worth buying. The custom work belongs in the processes that set your company apart, and in the connections between the products you buy.
A billing project CBOS is working on follows this pattern. CBOS designed and is building a rating and billing engine in Odoo for a usage-based business, while the accounting system still issues the final invoices. The business runs on Odoo, a bought ERP, and CBOS is building only the billing logic it needs inside it. The build vs buy article on this blog sets out when each choice makes sense.
Fixed price or time and materials: which suits your project?
The way a project is paid for decides who carries the risk of a wrong estimate. The three common models compare like this:
| Fixed price | Time and materials | Phased | |
|---|---|---|---|
| How it's billed | One agreed figure for an agreed scope | The hours used, at agreed rates | A fixed first phase, then later phases estimated and confirmed |
| Who carries the estimate risk | The supplier, who prices that risk in | You | The supplier for the first phase, then shared |
| When the scope changes | A change request with its own cost | The work goes into the backlog and the hours | The change goes into a later phase |
| Suits | A scope that can be written down completely | Work that will change as people see it | A process that's partly understood |
A fixed price gives you one number to take to the board. You pay for that certainty through the supplier's risk margin and every change request after signing. Time and materials follows the work as it unfolds. It needs a monthly budget, a ranked list of what to build next and regular spend reports on your side.
Phased pricing suits a process that used to live in spreadsheets and email, because the process becomes clearer once people see the software. Whichever model you choose, the proposal should name it and say what happens when the scope changes.
How do you estimate the cost and keep the first phase small?
An estimate is only as good as the scope behind it, so write the scope down before you ask anyone for a price. It should cover:
- the processes the system must run, and the exceptions in each
- the users, roles and sites, and what each may see
- every system it must connect to
- the data that has to move from the old system
- the personal information it will hold, and where that may be kept
Give every supplier the same list, so that their estimates answer the same question. Expect a range until someone has done discovery on your operation.
The cheapest way to buy custom software is to build less of it at the start. Find the manual process that costs you the most each month and build that first. It might be the report someone builds by hand every Monday, or the order typed into three systems. A first phase priced on its own can be used and judged before the next one is approved.
Small doesn't always mean light, though. A first version still carries the full cost of whatever it touches, such as payments, personal information or a difficult integration. CBOS modernises older systems in phases too, rebuilding piece by piece around the running system so that operations carry on.
Is custom software OpEx or CapEx?
Custom software can be either, depending on the phase of the work. Under IFRS, the standard IAS 38 treats software as an intangible asset and splits a project into research and development. Research, which covers planning, scoping and comparing options, is always an operating expense. Development can be capitalised once the company can show six things the standard lists, and it's then amortised over its useful life.
Subscriptions follow a different rule. A 2021 IFRS Interpretations Committee decision found that configuring a SaaS product usually doesn't create an asset, so those costs are expensed. That's the general accounting position only. Tax is a separate question, so confirm both with your auditor and your tax adviser.
How does CBOS scope a project?
Every CBOS project starts with a discovery call. A consultancy session follows, which works through your operations to find where new systems are needed and where they aren't. Sometimes the answer is a good product with one or two gaps that an integration or a small add-on can close, and CBOS will say so. The written proposal comes after it, built on what it found.
The build then runs through six stages, set out on the page about how CBOS runs a bespoke build, from the first conversation to long after go-live.
If you'd like to know which of these factors drive the cost for your own operation, a discovery call is where that starts.
Frequently asked questions
How much does it cost to build an app in South Africa?
It depends more on what the app connects to and who uses it than on its screens. An app that stands alone is a different job from one that reads and writes to your ERP, Sage and customer records. Building for the web, one phone platform or both also multiplies the testing work, so ask for the app priced as a first phase with each connection listed.
How much does it cost to build a custom AI?
Four things set it on top of the usual build factors: the state of your data, which model it uses and how heavily, the guardrails and permissions it needs, and testing and monitoring after launch. The build is a one-off cost, while model usage is a monthly bill, usually priced in US dollars, that grows as more people use the AI.
Is there an AI cost estimator?
Online cost calculators exist, and they give a rough sense of scale from a feature list. They can't see the state of your data, your integrations or how many people will use the system each day. Those are what move an AI bill most, so a scoped first phase is what gives you a real figure.
Does POPIA affect the cost of custom software?
It does if the system holds personal information. Section 19 means its security has to be designed in and paid for, and section 72 limits sending that information abroad, which shapes where the system is hosted. This isn't legal advice, so check your obligations with a POPIA specialist.