How we work
Working software, early, in front of you.
Three principles, and they are not decoration. They decide what we say yes to, how we bill, and what happens when a project turns out to be harder than anyone thought.
We learn the business before we write code
The first weeks are spent understanding how work actually flows, where it jams, and what the people doing it have quietly built workarounds for. Software that ignores this gets installed and abandoned. We would rather find out early that the problem is a process, not a platform — even when that means a smaller invoice.
We ship in small, honest steps
You see working software early and often. Every increment is something you can open and react to, which means the cost of us misunderstanding you is one iteration, not one project. When something is behind or harder than estimated, you hear it from us in that week's update, not at the deadline.
We build it to last
Clean, tested, documented work, in a repository you own, on infrastructure you control. The measure we hold ourselves to: could a competent engineer who has never met us pick this up and be productive in a week? If not, it is not finished.
The commercial side, plainly
| Question | Answer |
|---|---|
| How we bill | Monthly retainer against an agreed scope for ongoing work; fixed price for discrete, well-bounded pieces. We tell you which one fits before you commit. |
| Currency | Rand for South African clients, pounds for UK and international clients. |
| Who owns the code | You do. IP transfers to the client and the code lives in a repository you control. |
| Where the infrastructure lives | In your cloud accounts, under your billing, with our access granted rather than owned. |
| Notice | Retainers run month to month after any agreed initial term. If it stops working, you should be able to leave. |
| Handover | Code, documentation and infrastructure, plus our time to hand it over properly. |
What we will tell you before you sign
- If the thing you are asking for should be bought rather than built.
- If your real problem is a process or a person, and software will only make it faster.
- If the timeline you have in mind is not achievable with the budget you have in mind.
- If we are not the right studio for it — including who might be.
None of that is generosity. Projects that start on a polite fiction are the ones that end badly for both sides, and we would rather keep the relationship than win the contract.
Next step
Tell us what is not working.
One email, a short conversation, and an honest answer about whether we are the right people for it. No pitch deck.