The studio
A South African software studio
We turn real problems into working outcomes — for businesses with a process that’s costing them, and for founders with an idea worth building. The proof is on the record: 14 projects, 8 of them live and open right now, before you speak to anyone here.
How we work
We survey it before we build it
Most software goes wrong before anyone writes code — in the gap between what was asked for and what was understood. So the scope is agreed first, in writing, by both sides. It is the least glamorous part of the process and the only one that reliably decides whether the rest works.
01
Conversation
Week 1–2 · no charge
We work out what you are actually trying to achieve — which is often not the thing first described. Nothing is billed and nothing is committed.
02
The survey
Week 2
The scope gets agreed in writing: what's in, what's out, and where the edges are. You leave with a written proposal that is yours to take away, whether or not you proceed.
03
Build
Weeks 3–12
Working software at every milestone — real deployments you can open, not mockups. Each stage is agreed before it begins, so you decide how much to take on at a time.
04
Hand over
From week 13
Your domain, your hosting, your database, your code. Whether we stay involved afterwards is your call and not a default.
How the studio is set up
Small team, large output
One process, every time
Every project is scoped, built, tested and handed over the same way. You get something predictable rather than a bespoke guess arranged around whoever happens to be free.
People decide, AI does the volume
AI handles the sheer quantity of development work. A person decides what gets built, when something is actually finished, and what gets rejected. That is why weeks is a real number and not an optimistic one.
The record is public
Every project is on a page with its real stage and progress, and where there is something to open, a link that opens it. Work that is early is labelled early. Work that is paused says so.
No account managers
There is no bench to keep busy and no billable-hours incentive to make work last longer than it should. The overhead you are not paying for is the reason the timeline is short.
What we will not do
The commitments, stated plainly
- We do not name a client without their written permission. By default the work is described and the client is not — including when naming them would help us.
- We do not publish a price before we understand the work. A number without a boundary is a guess, and a guess is what gets renegotiated later.
- We do not put a number on this site that we cannot trace to a record or a URL that resolves. Where a figure is partial or a link would not survive being clicked, we say so or we withhold it.
Ready when you are