the technical partner south african operators bring in when the data has to hold up under audit, the ai has to actually shift how the team works, and the build has to survive being handed over.
a three-month build. a three-week hand-over. then we leave. the work keeps running because the team owns it.
working papers, ledgers, audit trails — designed to survive the audit.
not a demo. a tool the team uses on a tuesday, then forgets we built it.
three weeks of pairing. documented. then we leave. it keeps running.
one method, seven shapes. pick the one that matches the corner you are trying to complete.
we sit inside your team as cto / head of data, two or three days a week, for a fixed term.
eight-week programmes. the tool ships on day forty. the team owns it on day fifty-six.
a fixed-scope build of the data layer, the warehouse, the api, the audit trail.
popia, audit, sovereign hosting, halal-compatible commercial structures. the trust surface.
six packages with priced sows. the audit-ready ledger. the popia kit. the working-paper template.
an investor needs a second opinion. a board wants the architecture read. we write it up.
a working paper on your sector, your data, your question. published or held — your call.
we sit inside the team for three months. then we hand it over and they run it without us.
five marks · one parent. each product carries the parent corner at twelve percent — visible attribution.
a thirty-minute call. no slide deck. you describe the square; we sketch the corner.