Software · 9 min read
Custom Software Development in South Africa: Pricing and Delivery Guide
Quotes for custom software in South Africa can differ by a factor of several for the same idea. This guide explains why, how the main pricing models work, and what your procurement, legal and finance teams will want answered before you sign.
Groow editorial team · Reviewed
Key takeaways
- The type of project and the pricing model shape your budget more than the vendor's day rate.
- Fixed scope suits a well-defined first release; time and materials suits discovery; a dedicated team suits a product you'll keep growing.
- POPIA requires a written contract that makes your developer keep personal information secure, so settle it before the build starts.
- Many buyers ask suppliers for B-BBEE evidence, because spend with empowering suppliers counts on the buyer's own scorecard.
- Plan for power and network interruptions, and decide early where your data will be hosted.
The short answer on custom software development in South Africa
Custom software development in South Africa is priced mainly by team time. Your quote is roughly the people needed, multiplied by how long they work, plus hosting and support. Three choices move that number most: the type of project, the pricing model and how much of the scope is known before work starts.
Nobody publishes a reliable national price list, so we won't invent one. Instead, this guide shows how to get quotes you can compare, how long each kind of project tends to take, and the local questions procurement will raise.
What kind of software project are you buying?
Start by naming the project type. Vendors price a customer portal very differently from a SaaS product, even when both have a login and a dashboard. The table helps you place your idea and spot the South African extras early.
Here is an illustrative example. A property firm wants tenants to log in, see statements and pay rent. That is a client portal. If the firm later wants to sell the same tool to other landlords, it becomes a SaaS product. Now each landlord needs a separate account, a subscription and its own data kept apart. The idea looks the same, but the work is far bigger.
| Project type | Typical scope | What drives the budget | South African extras |
|---|---|---|---|
| Internal tool | Replaces spreadsheets for one team, such as job cards or approvals | Number of roles and reports | POPIA access controls for staff data |
| Customer or client portal | Clients log in to see accounts, documents or bookings | Security, integrations with your core system | Online payments through local gateways |
| Workflow and automation system | Connects several departments and existing tools | Integrations and data migration | Offline tolerance during power or network outages |
| Mobile app | Field staff or customers on Android and iPhone | Offline sync, device testing, app store releases | Data-light design for prepaid mobile users |
| SaaS product | Software you sell to other businesses by subscription | Multi-tenant design, billing, onboarding | Recurring billing in rand, hosting location |
| Legacy replacement | Rebuilds an old system the business depends on | Data migration and running both systems side by side | Records retention under POPIA |
If your idea is mostly about automating repetitive admin, read our guide to software automation in South Africa first. A smaller automation may solve it without a full custom build.
What people search for
Our analysis of Google Ads keyword data shows about 90 searches a month for “custom software development” in South Africa, with medium advertiser competition and top-of-page bids of up to €8.70.
How much does custom software development cost in South Africa?
We don't quote rand ranges here, because we couldn't find public, reliable data to back them. What we can show is how a quote is built, so you can check any number you receive.
Every quote has two parts. The build cost covers discovery, design, development, testing and launch. The running cost covers hosting, monitoring, security updates and small changes, usually billed monthly. Ask for both, because a low build price with an expensive support plan is not a bargain.
A clear quote splits the work into the phases below, with hours or a price for each. If a quote shows one total with no breakdown, ask for one. You can't compare vendors, or cut scope wisely, without it.
These factors push a quote up or down:
- Scope clarity: a written brief with user roles, key workflows and reports cuts the vendor's risk margin.
- Integrations: each link to your accounting, ERP, payment or HR system needs building, testing and error handling.
- Payments: online payment gateways such as PayFast (cards, recurring billing) or Ozow (pay by bank) each have their own integration and notification rules.
- Security and compliance: audit trails, role-based access and POPIA features add work, but retrofitting them later costs more.
- Offline and resilience needs: saving work locally and syncing later is more complex than an always-online app.
- Currency: much cloud hosting and many developer tools bill in US dollars. Ask vendors to split rand and dollar costs so exchange rate swings don't surprise you.
- 1Discovery and scope: workshops, a process map and a feature list with estimates.
- 2Design: wireframes and a clickable prototype your team can test.
- 3Build: development in short cycles, with a demo at the end of each one.
- 4Testing: automated tests, a security check and user testing with your staff.
- 5Launch: data migration, go-live support and training.
- 6Running costs: hosting, monitoring, updates and a monthly pool of hours for changes.
Ask each vendor for a quote as a range, with the assumptions that move it from the low end to the high end. The assumptions tell you more than the totals.
How long each type of project takes
A small internal tool with one team and no integrations can move from brief to launch far faster than a SaaS product or a legacy replacement. Treat any timeline as a range that depends on your decisions as much as on the developer.
Four things stretch South African projects most often. The first is slow feedback from busy managers. The second is data migration, because old records are messier than anyone expects. The third is integration access, such as waiting for a supplier to issue test credentials. The fourth is regulatory steps that start late.
You can shorten most of these yourself. Name one decision-maker who can approve screens quickly. Clean your data before the build, not during it. Request test access to other systems in the first week.
One regulatory step has fixed waiting times. Some processing needs prior authorisation from the Information Regulator under POPIA section 57, for example credit reporting or linking unique identifiers across organisations. The Regulator must say within four weeks whether it will investigate further. A detailed investigation may take up to 13 weeks, and you may not start that processing in the meantime.
Fixed scope, time and materials, or a dedicated team?
The pricing model decides who carries the risk when things change. None is always best. Match the model to how well you understand the work.
| Model | Best for | Who carries the risk | Watch out for |
|---|---|---|---|
| Fixed scope, fixed price | A well-defined first release with a clear brief | Mostly the vendor, which adds a risk margin to the price | Every change becomes a paid change request |
| Time and materials | Discovery, prototypes and projects where needs will shift | Mostly you, since you pay for hours worked | Budget drift without weekly reporting and a cap |
| Dedicated team | A product you'll keep improving for a year or more | Shared; you direct priorities, the vendor supplies people | Paying for idle capacity if your backlog runs dry |
| Hybrid | Paid discovery, then a fixed price for the first release | Balanced | Make sure discovery produces a document you own |
On time and materials, ask for a weekly report of hours used against the plan, and agree a cap that needs your sign-off to exceed. That keeps the flexibility without the surprise bill.
South African requirements to build in from day one
POPIA. When a developer or host processes personal information for you, POPIA calls them an operator. Section 21 requires a written contract that makes the operator keep security measures in place and notify you immediately of a suspected breach. Your organisation must also register its Information Officer with the Information Regulator before that person takes up their duties.
Data location. POPIA section 72 limits sending personal information outside South Africa, unless conditions such as adequate protection or consent are met. Some global cloud providers now run South African regions; AWS, for example, has one in Cape Town. Decide where production data will sit and write it into the contract.
Payments. If customers pay online, choose the gateway early, because it shapes the checkout and the admin screens. Payfast's documentation covers card payments, subscriptions and payment notifications. Ozow's developer hub covers pay-by-bank payments, refunds and payouts. Each needs a merchant account in your company's name.
Power and connectivity. Eskom says it is not load-shedding at the time of writing, but it still publishes schedules by area. Ask how the system behaves when a branch loses power or signal. Good answers include saving drafts on the device, queuing payments safely and clear messages when the user is offline.
Vendor checklist for South African software companies
Use this checklist on every shortlisted vendor. A vendor who struggles to answer three or more items in writing is a risk, however good the demo looks.
Our own approach is set out on the custom software development services page. Our guide to building software walks through the options. Hold us to the same points.
- They ask about your business problem before talking about technology.
- They show similar work and let you speak with a past client directly.
- They explain their pricing model and what happens when scope changes.
- They name who will work on your project, not only the sales lead.
- They demo working software regularly and give you access to the task tracker.
- They describe their POPIA approach, including access control, logging and breach handling.
- They set up code, cloud and domain accounts in your company's name.
- They explain how the system behaves offline or during outages.
- They offer a support plan with response times and a monthly rand price.
- They tell you what to leave out of the first release, not only what to add.
Procurement questions your finance and legal teams will ask
Larger buyers often run software through a formal procurement process. Prepare these answers early, whichever side of the table you're on.
B-BBEE status. Under the ICT Sector Code, a company's spend with empowering suppliers counts towards its own scorecard under preferential procurement. That is why many buyers ask for a supplier's B-BBEE certificate or affidavit. The B-BBEE Commission says an exempted micro-enterprise, with annual revenue of R10 million or less, uses a sworn affidavit or CIPC certificate rather than a verification certificate.
- 1Can the supplier provide current B-BBEE evidence, and is it valid for the full contract period?
- 2Is there a POPIA operator agreement covering security, breach notice, sub-processors and data return at the end?
- 3Where will production data and backups be stored, and does any transfer outside South Africa meet section 72?
- 4Who owns the intellectual property in the code, designs and documents once they are paid for?
- 5Are prices in rand, VAT-inclusive where applicable, and which costs are passed through in dollars?
- 6What service levels apply after launch, and what are the penalties or credits if they're missed?
- 7What is the exit plan: handover, documentation and notice period?
Getting a custom software development estimate you can compare
Send every vendor the same brief: the problem, the users, the key workflows, the systems to connect and the reports you need. Ask for a range, the assumptions behind it, the pricing model and the running costs. Then score the answers against the checklist above.
If your project includes AI features, such as document reading or a support assistant, our guide to AI software development in South Africa covers the extra questions to ask. For more on how we work with local businesses, see our South Africa page.
Custom software development is a long relationship, not a one-off purchase. When your brief is ready, get a software project estimate and compare it on the same terms as the others.
Frequently asked questions
How do we compare two quotes that use different pricing models?
Put both on the same basis: the total for the first release plus a year of running costs. Then list what each one includes and leaves out. The cheaper quote often skips testing, data migration or support, which you will pay for later.
Is it cheaper to hire an offshore team than a South African one?
Hourly rates may be lower offshore, but the total cost depends on more than rates. Time-zone overlap, POPIA contracts for data processed abroad, and how easily you can meet the team all affect delivery. A local or nearby team often reduces rework on unclear requirements.
Should we pay a deposit before work starts?
A deposit is normal, but link the rest of the payments to approved milestones rather than dates. Paid discovery is a good way to start: you get a scope document you own, and you can take it to another vendor if you prefer.
Can we get a fixed price without a detailed specification?
You can, but the vendor will add a larger risk margin to cover the unknowns. A short paid discovery phase usually costs less than that margin. It also makes the fixed price for the build more reliable.
Who owns the software once it's built?
Only you, if the contract says so. Ask for intellectual property to transfer to your company once each phase is paid. Keep the code repository and cloud accounts under your company's name from the start.
What does support usually cover after launch?
Support plans typically cover hosting, monitoring, security updates and bug fixes, with a set number of hours for small changes. New features are normally quoted separately. Check response times for urgent issues and whether weekends are included.
Sources
- Protection of Personal Information Act 4 of 2013 — Department of Justice and Constitutional Development
- POPIA guidance and compliance resources — Information Regulator (South Africa)
- Amended B-BBEE ICT Sector Code (Government Gazette 40407) — Department of Trade, Industry and Competition
- Exempted Micro-Enterprises brochure — B-BBEE Commission
- Payfast developer documentation — Payfast
- Ozow developer hub — Ozow
- Load shedding — Eskom
- AWS Regions — Amazon Web Services