Loading…
Working With Us
How an engagement actually runs.
A documented delivery lifecycle, clear terms, and a continuity guarantee. No mystery, no lock-in, you always know where the work stands and what you'll own at the end.
.jpg&w=3840&q=75)
The delivery lifecycle
Discovery to handover
Seven stages, governed and documented. We even diagram our own process, the same discipline the systems get.
Deposit-first (stage 2) gates the build; handover (stage 6) transfers full ownership to you.
01
Discovery
You tell us the problem, through a project brief or a discovery call. We research your domain before we meet, so we arrive already understanding it. Precision, not a sales pitch.
02
Deposit & scope
A deposit confirms the work, with a fixed scope and milestones written down. Deposit-first is non-negotiable. It protects the seriousness of the engagement on both sides.
03
Architecture
Before a line of feature code: the database schema, the row-level-security model and the integration design are decided and documented as architecture decision records.
04
Build sprints
We build in visible increments, committed constantly, type-checked, mobile-first, with progress you can follow rather than wait for in silence.
05
QA & security
Before handover: a row-level-security audit, signed-webhook verification, and a fixed smoke-test checklist run against the live deployment.
06
Handover
You receive the code, the schema, the runbooks and the data, plus a plain-language handover so your own team can operate the system.
07
Support
A response window, agreed in your contract, for the agreed support period, backed by the runbooks, so most issues are already documented.
.jpg&w=3840&q=75)
The terms
What you sign up to
Deposit-first, always
Every client engagement starts with a deposit against a written scope. It keeps both sides committed and the milestones honest, there is no "we'll sort the money out later."
You own everything
On handover, the code, the database schema, the runbooks and the data are yours. No proprietary lock-in, no platform you can't leave, no hostage data. You can hire anyone to continue.
Documented by default
Architecture decision records, runbooks and a handover checklist ship with the build, not as an afterthought, but as the way the work is done.
See a real runbookSecurity & compliance built in
Row-level security, signed webhooks and an append-only audit are the defaults; the company operates under POPIA (Reg 2026-005658) with SA data residency and signed digital agreements.
See the controls.jpg&w=3840&q=75)
The honest question
“What happens if you're not available?”
This is the honest question about working with a focused studio, and the answer is built into how we work. Because every system ships with documentation, runbooks and a clean handover, and because you own the code and the data, the system does not depend on any one person staying reachable. You, or anyone you hire, can keep it running. Documentation-first isn't a nicety here; it's the continuity guarantee.
.jpg&w=3840&q=75)