The field is busy and moving fast, generative-AI use reached 23.1% of working-age adults in early 2026, the highest in Africa (Microsoft AI Diffusion Report, 2026), and the tooling has reset what a small team can ship: AI now resolves over 70% of verified real-world software bugs (SWE-bench Verified). That is good for you as a buyer, but it means a lot of look-alike pitches, from large firms to body-shops renting out hours. The matrix below leads on the pricing model, because that is where the same build becomes a known cost or an open meter.
Buyer's guide
The best software development company in South Africa: how to choose one
The field runs deep, from large firms to body-shops, and most of it sells hours or a deck, not a working system. Here are the criteria that separate a real builder from a reseller, custom versus off-the-shelf, the questions to ask, and why engineer-led and AI-accelerated wins.
Bottom line
For a software build the test that protects your money is the pricing model: a fixed price in rand for a clearly defined outcome, agreed before anyone writes a line. That one demand strips out most of the risk. The two ways to overpay are both about open-ended billing, the agency retainer that drifts into six figures with nothing shipped, and the body-shop that rents you hours and owns none of the result. A firm willing to name the number and the scope up front is telling you it understands the work.
The rest follows. The people who scope it should be the people who write it, you should own the code with no lock-in, and in 2026 the build should run AI-accelerated, so it ships in weeks rather than quarters. The field is deep, from large firms to body-shops, but a fixed price in rand for a defined outcome is the line that separates a partner from a meter that keeps running.
What separates a real software development company from the rest
Pricing model
What good looks like
A fixed price in rand for a defined outcome, agreed before any code is written.
Red flag
An open retainer, or time-and-materials with no cap.
Scope discipline
What good looks like
A written scope that says what ships and what does not, so the number holds.
Red flag
A vague brief that turns every change into a new invoice.
Who builds it
What good looks like
The people who scope it are the people who write the code.
Red flag
Account managers and offshore handovers sit between you and the work.
Proof and ownership
What good looks like
Live software they built that you can open and use, and you keep the code.
Red flag
A portfolio of logos and screenshots, and they hold the keys.
Speed
What good looks like
AI-accelerated, so a first useful build ships in weeks, not quarters.
Red flag
Every project is a multi-quarter commitment.
We quote one fixed price in rand for a defined outcome, after a short brief, so you know the number before we start and it does not move unless the scope does. A retainer with no cap and a body-shop billing by the hour are both selling you uncertainty. Naming the price up front is how a studio puts its own skin in the estimate instead of yours.
Adam Sacharowitz, Co-founder and AI engineer
Custom versus off-the-shelf
Before you hire anyone, decide whether you actually need custom software. If a packaged product covers your need, buy it, and a good company will tell you so even when the cheaper answer is the one that costs it the build. Build custom when the value is in the fit: when you are paying for features you do not use, hand-stitching tools together every week, or your process is the thing that makes you money and no product matches it. A custom build that mirrors how you actually work pays for itself in saved time, where a forced-fit product quietly taxes you forever. The company that talks you out of a build you do not need is the one to trust with the one you do.
The questions to ask before you hire
Raise these five on the first call. The answers tell you whether you are buying a known cost or signing up to an open meter.
- Is this one fixed price in rand for a defined outcome, or billed by the hour with no cap?
- What exactly is in scope, and what would count as a change to it?
- Will the engineers who scope it be the ones who write the code?
- Do I own the code and the accounts the day it is done?
- How are you using AI to ship this faster and for less?
Proof, not persuasion
One build on our Work page shows how we scope. We built a local-first sales-intelligence app over a licensed database, where the data is sensitive enough that it never leaves the building, so the AI runs the queries locally on the client's own machines. We quoted a fixed price in rand for a defined outcome before writing a line, and shipped it at that number. The licensing and the local-only constraint are exactly the kind of detail a written scope has to pin down, which is why naming the price forces the hard questions early.
The founders do the engineering, the work is public, and the client owns the result. Open the work before taking our word for it, and when buying off-the-shelf is the right call, we say so rather than billing you for a build you do not need.
Why a fixed price in rand wins
A fixed price for a defined outcome changes the incentives. The studio carries the risk of its own estimate, so it has to understand the work before it commits, which means the hard questions get asked at the start instead of surfacing as change orders later. You get a number you can budget against and a scope you can hold them to. An open retainer or uncapped time-and-materials does the reverse: every unknown becomes your cost, and the project that should have shipped in weeks drifts into quarters.
It works because the same AI tooling that collapsed build times also makes a fixed quote safer to give, so a focused team can name a price a large firm would hedge. The South African field is genuinely deep and some of the other companies are good, so ask for the fixed number and the written scope, and judge the answer yourself. See how we build in custom software development and the discipline behind it in AI engineering.
What to ask a dev shop
What actually makes one dev shop better than another?
Whether it will name a fixed price in rand for a defined outcome before any code is written. That one demand strips out most of the risk and tells you the shop understands the work. Then the people who scope it should be the people who write it, you should own the code, and in 2026 the build should run AI-accelerated so it ships in weeks, not quarters.
Fixed price, retainer, or time-and-materials?
For a defined build, a fixed price in rand is the model that protects you, because the studio carries the risk of its own estimate and has to understand the work before it commits. An open retainer drifts into six figures with nothing shipped, and uncapped time-and-materials turns every unknown into your cost. Time-and-materials only makes sense for genuinely open-ended work, and even then it should have a cap and a written scope.
Should I get custom software or buy off-the-shelf?
Buy off-the-shelf when a product fits your process closely. Build custom when the value is in the fit: when you pay for ten features to use two, or stitch tools together by hand every week. A custom build that matches how you work usually pays for itself in saved time.
What should software development cost?
Scope sets the number, so be wary of a flat figure quoted sight unseen. A focused tool is far cheaper than a full platform. The model matters more than the price: insist on a fixed price in rand for a defined outcome, not an open retainer or time-and-materials with no cap.
Do I keep the code and the accounts?
You should. With a good studio the code and the accounts it runs on are yours, with no lock-in, so you can run it, hand it to your team, or move it whenever you like. If a company holds the keys so you cannot leave, treat it as a red flag.
Big firm or a focused studio?
For most defined builds a focused studio is the safer buy, because it can commit to one fixed price in rand without the account-management overhead a large firm prices in. The number is cleaner and the scope is easier to hold because the same people scope and build it. A large firm earns its place on genuinely large, multi-team programmes, not on a contained build a small team can quote and ship.
Want the number before the build?
Send ZAIQ a short brief. We will come back with what we would build, what is in scope, and one fixed price in rand.
Start the build→