What an MVP Actually Costs to Build in South Africa
The four realistic ways to build a first version here, what each costs, and the scoping decisions that make the same brief come back cheaper from everyone you send it to.
Almost every South African founder who wants to build software asks the same question first: what will it cost? The honest answer is that the number depends far less on the technology than on how much you have already decided. A founder who can describe exactly what the first version does gets a quote. A founder who cannot gets an estimate that doubles.
This guide covers what an MVP really is, the four realistic ways to build one here, what each costs, and the mistakes that turn a three-month build into an eighteen-month one.
An MVP is not a small version of everything
It is the smallest thing that lets one type of user complete one valuable job end to end.
The build is not the whole cost
Hosting, support, payments, and the changes you make after launch are ongoing. Budget for the year, not the launch.
Scope drives price, not code
Every 'while we are in there' request is paid for twice - once to build, once to maintain.
You need users before you need features
The cheapest MVP is the one you did not need to build because the manual version already proved nobody wanted it.
What an MVP actually is
Minimum viable product is the most abused phrase in startups. It does not mean a cheap version of your full idea, and it does not mean a prototype that cannot handle real money. It means the smallest thing you can put in front of a real user that lets them complete one valuable job, end to end, so that you learn whether they will come back and pay.
The practical test: if you removed any single feature from your build list and the user could still finish that one job, it was not part of the MVP.
The four ways to build, and what each really costs
These are ranges seen in the South African market, not quotes. Where you land inside a range is set by how clear the scope is, how much design you need, and whether the product handles payments or personal information.
Typical range: R0 to R30,000 to launch, plus monthly platform fees
Good for: Marketplaces, booking, internal tools, directories, simple subscription products - anything where the behaviour is standard and the value is in the audience, not the engineering.
The catch: You are renting the foundations. Platform fees scale with usage, and moving off later is a rebuild. That is usually a good trade for a first version and a bad one for a business at scale.
Typical range: R40,000 to R150,000 for a first version
Good for: Founders with a clear, written scope and the time to manage the work.
The catch: One person is a single point of failure - for delivery, for knowledge, and for your access to your own code. Own the repository and the hosting accounts from day one, in your name, not theirs.
Typical range: R150,000 to R800,000 and up
Good for: Products with real compliance or integration requirements, or where you need design, build and testing as one accountable unit.
The catch: Agencies price uncertainty. A vague brief gets a defensive quote. The same agency will quote materially less against a specification that has already been written down.
Typical range: No cash, meaningful equity
Good for: Products that will need continuous engineering for years rather than a one-off build.
The catch: This is the most expensive option on this page if it goes wrong, and the cheapest if it goes right. Put the vesting and the IP assignment in writing before the first line of code, not after the product works.
What to decide before you ask anyone for a price
The single largest lever on what you pay is not who you hire. It is how much you have decided before you ask. Work through these and the same brief will come back cheaper from everyone you send it to.
Name one user and one job
Not three user types. One. Write the sentence: "A [who] can [do what] so that [why it matters]."
Write the screens
List every screen and what a user can do on it. If you cannot list them, the scope is not finished, and you will pay a developer to finish it for you at their hourly rate.
Decide what happens with money
Does the product take payment? In-app, or on invoice? Payments add integration, reconciliation and dispute handling - it is a real chunk of the build, not a plugin.
Decide what personal information you store
This drives your POPIA obligations and part of your architecture. Decide it now, because retro-fitting it after launch is the expensive way.
Write down what version two is - and cut it
Everything you can name as "later" is a thing that will not creep into the quote as "while we are in there".
Build it, or buy the time back
Protect the two things that are actually yours
Whatever route you take, two things must end up in your company's name and not a contractor's. Founders discover this at the worst possible moment, usually during due diligence or an argument.
The intellectual propertyRequired
A written agreement assigning the IP in the work to your company. Paying an invoice does not automatically transfer it.
The accountsRequired
Code repository, domain, hosting, database and payment gateway registered to your company email, with you as owner. Give the developer access; do not let them hold it.
Between co-founders, a founders or shareholders agreement covering vesting, roles and what happens when someone leavesRequired
Between co-founders, a founders or shareholders agreement covering vesting, roles and what happens when someone leaves.
Paying for it
Most South African software MVPs are funded out of revenue from something else, not from investment. Investment tends to arrive after there is a product with users, which is the opposite order to the one most founders expect. If you are approaching funders, what they read first is the plan and the numbers, not the code.
Funding options for South African startupsTech business ideas you can build hereCommon questions
How long should an MVP take to build?
For a genuinely minimal first version, six to twelve weeks is a realistic target once the scope is written down. Builds that run materially longer than that have usually not been cut down to one user and one job - the time is going into deciding, not building.
Should I sign an NDA before showing my idea?
Usually the idea is not the valuable part - the execution and the customer relationships are. Reputable developers will often sign one, but insisting on it before any conversation tends to cost you good advice. Protect the code and the data through the contract, which is where the value actually sits.
Do I need to register a company before building?
You can start without one, but the IP assignment, the hosting accounts and any co-founder agreement all want a legal entity to attach to. If more than one person is involved, or money is changing hands, register first - it is inexpensive and it prevents an expensive untangling.
What is the most common reason MVPs fail?
Building for a user who was never asked. The second most common is scope: a first version that tries to serve three different customer types at once takes three times as long and satisfies none of them.
Can I build it myself with AI tools?
For a genuine first version, increasingly yes - particularly for standard behaviour like listings, bookings and simple dashboards. The constraint is not writing the code; it is knowing what should happen when something goes wrong, where the data lives, and how payments reconcile. Those are the parts worth getting help with.
Insure your business equipment
Tools, cameras and gear are your livelihood. Naked offers app-based cover for single items, home contents, buildings and vehicles - get a quote in minutes, all from your phone.
Get a quote with NakedOkhantu may earn a referral fee if you sign up via Naked Insurance. This does not affect what you pay.
Free check - about 3 minutes
Is your tech idea ready to build - and do you own what gets built?
For anyone building software: check whether you have evidence a customer wants this, whether the scope is decided enough to get an honest quote, whether the code and accounts are actually yours, and which POPIA obligations apply the moment you store a user's details.
Free, and you see your full result immediately. We ask for your name and an email or phone number so we can send you the scorecard.