How much does custom software cost in South Africa? A small, focused tool costs the least. A bigger system with client logins, integrations and a mobile app costs more, and a sensible developer will split it into phases so you pay for one working piece at a time. Where your project lands depends on four things: how many kinds of people use it, how many other systems it talks to, how many business rules it has to follow, and how much of it has to work on a phone.
This guide explains what pushes the price up or down, what a fair quote should include, and the running costs people forget. It’s written for owners and managers who run their business on spreadsheets, email and too many apps, and who want a straight answer before they speak to a developer.
Why there is no single price for custom software
Custom software is priced like building work, not like a subscription. You’re paying for skilled people’s time to understand a problem, design a fix, build it, test it and put it live. A two-screen tool for your office and a portal that hundreds of clients log into are both called custom software. They’re as different as a garden shed and a double-storey house.
So be careful when someone quotes before asking questions. Either they’re guessing, or they’ve padded the number to cover what they don’t know. Both cost you money, one now and one later.
What drives the cost of custom software
Every quote is a sum of hours. These are the things that add hours.
How many kinds of users there are
Staff, managers, clients and suppliers each need their own screens and their own permissions. One type of user is simple. Four types, each allowed to see and change different things, is where the hours climb.
Integrations with other systems
Connecting to Sage, Xero, a payment gateway, a booking engine or your CRM takes time. Every outside system has its own rules, limits and quirks. Some have clear, well documented connections. Others barely do. A good developer checks each one before quoting, not halfway through the build.
Business rules and exceptions
Rules are the “if this, then that” parts of your business. A discount for repeat clients. Manager approval above a certain amount. Different pricing for trade and retail. Each rule is small on its own. Twenty of them, each with its own exceptions, is a real chunk of the build.
The data you already have
Moving years of records out of spreadsheets or an old system is the most underestimated job in most projects. Data has to be cleaned, matched and checked before it goes in. Messy data in a new system is still messy data.
Phones and field staff
If people need the system on their phones, you can build a web app that works well on a small screen, or a proper app that installs from the app stores. An app that shares logins and data with the web app adds work. It’s still far cheaper than building and maintaining two separate systems.
Security and POPIA
If the software stores personal information about clients or staff, it needs access controls, activity logs and backups from day one. This isn’t an optional extra. The Protection of Personal Information Act requires reasonable technical and organisational measures to protect that information, so the work belongs in the quote, not in a later surprise.
How much does custom software cost in South Africa by project size?
Rand figures without a scope are guesses, so here’s how projects group instead. Use it to work out which bucket you’re in before you ask for a quote.
A small internal tool
A quote calculator. A job card system for one team. A dashboard that pulls numbers from two spreadsheets so the owner stops asking for them on Friday afternoons. One type of user, a handful of rules, maybe one integration. This is the lowest cost band, and a first version can be live within weeks.
A business system with logins
A CRM built around how you actually sell. A booking system. A client portal where customers log in to see their documents, quotes and invoices. Several user types, a few integrations and a real data migration. These cost more, and they usually go live in phases.
A platform
Several systems talking to each other, a mobile app, client and supplier access, reporting and AI steps. Nobody should give you one fixed number for all of that upfront. Scope it in phases, price each phase, and go live with the first useful part while the rest is still being built.
Here’s an example of how phasing works. Say a plumbing firm in Somerset West runs bookings on WhatsApp and a shared spreadsheet. Phase one could be a booking screen for the office, a job list for plumbers on their phones and a daily summary for the owner. Phase two pushes finished jobs to Xero as invoices. Phase three adds a client login to see job history. Each phase has its own price and its own go-live date, and the owner can pause after any phase if the next one doesn’t make sense yet.
Fixed price or hourly billing?
Hourly billing puts the risk on you. Every unclear requirement turns into more hours, and you only find out at month end. A fixed price puts the risk on the developer, which is exactly why a fixed price only works after a proper discovery. Nobody can fix a price on something they don’t understand yet.
Our process at Clonelabs is discovery first, then a written scope and a fixed price. If something new comes up during the build, it’s quoted separately and you approve it before anyone works on it. No surprise invoices.
One more thing to check when comparing quotes. If the developer is VAT registered, VAT at the standard rate is added on top, so make sure you’re comparing inclusive with inclusive.
Costs people forget to budget for
The build is only part of the bill. Plan for these as well.
- Hosting and the domain, paid monthly or yearly.
- Maintenance and support, which covers updates, backups, uptime monitoring, security and fixes.
- Outside service fees for things like SMS, email sending, card payments and AI usage.
- Changes after launch. Once your team uses the system every day, they’ll ask for things nobody thought of in the planning meeting.
- Your own people’s time to answer questions, test screens and sign off each phase.
What a fair software quote should include
A one-line quote that says “CRM system” and a number is a warning sign. A fair quote spells out:
- The screens, user types and integrations that are in scope.
- What is not in scope, written down just as clearly.
- The price per phase and when each payment is due.
- How long until the first version goes live.
- Who owns the code and the data, and on what licence terms.
- What support costs after launch and what it covers.
- How change requests are priced and approved.
Ownership trips up more businesses than price does. At Clonelabs, ownership and licensing are set out in writing in every quote, so you know where you stand before you pay a cent.
How to keep the cost down without cutting corners
- Start with the one process that hurts most, not the whole business.
- Use ready-made software where it fits. Our guide to custom software vs off the shelf helps you split the two.
- Write a clear brief before you ask for quotes. Here’s how to write a software brief that gets an accurate number.
- Clean up your spreadsheets before migration starts.
- Give the project one decision maker. Committees add weeks.
- Go live small, learn from real use, then grow.
Questions people ask
How long does custom software take to build?
Most first versions go live in 4 to 10 weeks once the scope is agreed. Larger platforms go live in phases, with the most useful part first.
Is custom software worth it for a small business?
It’s worth it when a process costs you time or money every week and no ready-made product fits. If an existing tool already does nearly everything you need, use that tool instead.
Who owns custom software once it’s paid for?
Whoever the contract says. That’s why ownership and licensing must be in writing before you sign. Ask the question early and get the answer in the quote.
Can I get a price without a meeting?
A clear brief can get you a rough idea for a small tool. A fixed price needs a short discovery so both sides agree exactly what’s being built. More answers are on our FAQ page.
How do I compare two software quotes fairly?
Line them up on scope, exclusions, ownership, support and VAT. A cheaper quote that leaves out integrations or support often costs more by the end of the first year.
Got a process that eats your week? Tell us about it on our contact page or at [email protected], and we’ll reply within one working day with a clear next step.