Cost & scope · 7 min read
How much does custom software cost in South Africa?
Published 5 May 2026 · Updated 15 September 2026 · By Sam Fourie, Niddo
In South Africa in 2026, a focused MVP built by a product studio typically costs R250,000 to R600,000 (about $14,000 to $33,000). A full SaaS platform with billing, roles, integrations and security work runs from around R600,000 to R1.5 million, and regulated builds go beyond that. Scope, the number of user types and integrations, and the level of security and compliance drive the price far more than hourly rates do.
The short answer, in ranges
| What you are building | Typical scope | Range (ZAR) | Approx. USD | Timeline |
|---|---|---|---|---|
| Marketing site or product website | Design system, 5 to 12 pages, CMS, forms, analytics | R60,000 to R200,000 | $3,500 to $11,000 | 1 to 3 weeks |
| MVP or v1 of a product | One core workflow, one user type, auth, a simple admin, deployment | R250,000 to R600,000 | $14,000 to $33,000 | 4 to 8 weeks |
| Full SaaS or operations platform | Multiple roles, billing, integrations, reporting, notifications, testing | R600,000 to R1.5 million | $33,000 to $85,000 | 3 to 5 months |
| Regulated or security-critical build | All of the above plus encryption, audit trails, compliance tooling and an external penetration test | R1.5 million and up | $85,000 and up | 4 to 6 months |
These are the ranges we see for work done by a South African product studio that designs and engineers the product itself, at roughly R18 to the dollar. Offshore body shops quote lower; local enterprise consultancies quote far higher. Freelancers can land under the bottom of each range for well-specified work, with the trade-offs covered further down.
What actually drives the price
Two products with the same one-line description can differ by a factor of five. The variables that move the number are predictable, so it is worth knowing them before you ask for a quote.
- Scope, measured in workflows rather than screens. A booking flow with confirmation emails is one workflow. A booking flow with refunds, rescheduling, waitlists and partner payouts is five.
- User types. Every role (customer, staff, admin, partner) needs its own permissions, screens and edge cases, and roughly its own slice of testing.
- Integrations. Each third-party system you connect to (payments, accounting, calendars, booking channels, identity checks) adds discovery, error handling and monitoring. Slow or thinly documented partners cost the most.
- Data and compliance. Personal information under POPIA, financial records, health data or anything that must survive an audit needs encryption, access controls, retention rules and an audit trail, and those are built in, not bolted on.
- Design depth. A product your customers pay for needs a real interface, designed before it is coded. An internal tool can be simpler, but it still has to be fast for the people who use it all day.
- Certainty. A fixed price includes the risk of being wrong about scope. Time-and-materials moves that risk to you and usually costs more in the end, because nobody is paid to say no.
The costs that are not the build
A quote for the software is not the whole bill. Budget separately for the services the product runs on. Most are small at first and scale with usage, and they sit in your accounts, not the studio's:
- Hosting and infrastructure: typically R500 to R5,000 a month for a product on Vercel or AWS with a managed database, more with heavy data or traffic.
- Per-use services: payment processing fees, identity checks, SMS and email delivery, file storage. Each costs cents to rands per use and adds up with users.
- Third-party subscriptions the product depends on, from calendar APIs to accounting connectors.
- An external penetration test if you handle sensitive data, usually R50,000 to R90,000 from a South African specialist.
- Legal and compliance work: privacy policy, terms, POPIA registration and, for some products, agreements with your processors.
- Running it afterwards: monitoring, updates, support and small improvements, either as a retainer with the studio or as your own team's time.
How to spend less without getting a worse product
- Scope an MVP first. One workflow, one user type, one metric. Most products pitched to us as a full platform can prove themselves for a third of the price and then earn the rest.
- Buy the commodity layer. Authentication, payments, email and hosting are solved problems. Pay a vendor a few dollars a month rather than a studio to reinvent them.
- Decide before the build. Every open question that waits for a decision during development costs a day of context switching. A short, honest scoping phase is the cheapest week of the project.
- Design before code. Screens are cheap to change and production code is not. Reacting to real flows before engineering starts removes most of the rework.
- Insist on ownership and documentation. A product you cannot take to another team is a product with a hidden price attached.
What you should get for the money
At the ranges above, expect a written scope that says what is in and what is out; a fixed price tied to milestones you accept on a staging environment; design before engineering; a modern, maintained stack; automated tests on the paths that matter; documentation; monitoring in production; and the code, repositories and accounts in your name.
How Niddo prices
We scope every build with you first, then quote one fixed figure with a milestone plan, and we do not bill hourly. Most first releases ship in one to six weeks. Changes to scope are quoted before they are built, never slipped into an invoice. If you want a number for your idea, tell us what you are building and we will come back with a plan, a timeline and a price.
Questions
People also ask.
Is it cheaper to hire a freelancer?
For a small, well-specified piece of work, often yes. For a product, the gap closes once you add the design, project management and testing a freelancer usually leaves to you, and it reverses if the build has to be redone. See who should build your software.
Do you charge for scoping?
A scoping conversation is free. A deeper discovery phase for a large build is quoted separately, and its output, a written specification, is yours to take anywhere.
Can I pay in stages?
Yes. The fixed price is split into milestones: a deposit on signature, then payments as each milestone is accepted on staging.
What does it cost to keep the software running?
Infrastructure is usually $30 to $300 a month (roughly R500 to R5,000). Maintenance and small improvements are either a monthly retainer or your own team's time, since you own the code. See what happens after launch.