entity
khwarizmi (pty) ltd
2025 / 064405 / 07 · companies act 71 / 2008
§ the firm behind the figure
a name on
every number.
every working paper that leaves khwarizmi carries the founder's signature. delivery runs on playbooks and qa gates, so the quality doesn't depend on who is in the room. the accountability is personal; the system is not.
~ drift is the only failure mode ~
founder · technical principal
the operator.
twelve years in technical leadership across south african healthcare, halal-food supply, and financial-services data. before founding khwarizmi: head of data at a series-c logistics platform; principal engineer on a regulated fintech build; technical lead on two halal-certification working papers commissioned by foundation work in gauteng.
the firm is built around one engine: reconciling data from systems that don't agree into a single figure that survives challenge. two offers carry a published, fixed price; everything else is scoped from the assessment and quoted against the stake. every engagement is read by one person at the desk. governance §13: the founder approves every working paper that leaves the firm.
khwarizmi grows by handing over, not by holding on. playbooks, qa gates and runbooks mean your team runs the system after we step out — and the signature on every paper stays personal. a chair always has a successor. that is the test.
~ that is the operator. here is how the work runs. ~
§ how the work runs · v0.2 · 2026
one method.
one engine.
every engagement follows the same shape — diagnose, complete, hand-over — and closes with a working paper your team can run without us in the room. the managed layer, where you choose it, runs under a published scope.
the engagement, in shape.
every engagement is a square missing a corner. we name the missing corner in the diagnose phase, complete it through the build, pair with your team through the hand-over, and step out on the last friday. quarterly office hours for twelve months. the assessment names the corner; the roadmap prices it.
the four phases
- diagnosew. 01–02
- completew. 03–12
- hand-overw. 13–15
- office hoursq. 01–04
illustrative. durations are fixed per engagement in the roadmap.
- M.01 · diagnose
read · name · sign before scope locks.
we read your systems, your data, your past two board packs. we write a working paper naming what is missing and what is already fine. You read it before scope locks.
- M.02 · complete
build against the playbook · founder reads every commit.
we build against the offer’s playbook. one of our team delivers; the founder reads every commit and signs the closing paper. You see the work in flight, not at the end.
- M.03 · hand-over
shadow · lead · close the laptop.
your team shadows our work for one week. they lead for the next. on the last friday we close the laptop, sign the closing paper, and step out. You keep the working papers, the runbooks, and the canonical copy.
- M.04 · office hours
half a day per quarter · twelve months · free.
you call us; we don’t call you. then the engagement is truly closed. (the managed layer — reporting runs, monitoring, support under a published scope — is a separate, optional order.)
working papers, not slide decks.
a working paper is signed, footnoted, dated, and held in canonical form. it is the audit trail of the build — it documents the system we shipped; it does not replace it. one survives the audit; a slide deck does not. we ship the system and the paper that defends it.
every paper carries.
- a question, named on page one.
- a method, written before the analysis.
- data, sourced and versioned. anyone can re-run it.
- findings, with confidence where they matter.
- limits — where the data is thin, where the method bends.
- a signature from the founder. canonical copy held in your data room.
what we will not write.
- a marketing white paper with our logo.
- a vendor-funded report dressed as objective.
- findings you wrote that we put our name on.
- a deck with no underlying paper.
the qa discipline.
four moments per engagement, every engagement. version-controlled playbooks. the discipline that makes productised delivery defensible at scale — and the structural reason a founder can sign every paper that leaves the firm.
- m.01 · before we start
the engagement is qualified against the offer template — scope fit, price fit, reference rights, halal-compatibility, popia posture, add-on clarity. if it doesn’t pass, we say so and decline cleanly. no fishing.
- m.02 · in flight
two checkpoints. end of week 1 confirms the template path. midpoint catches scope drift before it compounds. each checkpoint produces a one-page working paper.
- m.03 · before the signature
every closing paper is read against an offer-specific checklist — printed or read aloud, never skim. three questions answered out loud about engagement specifics before the founder signs.
- m.04 · after hand-over
what this engagement taught about the template is logged; the playbook is version-controlled in a git repository the firm owns. quarterly review converts patterns into template version bumps. every delivery improves the next.
six principles we do not bend.
these are not preferences. they are the structural reasons the work holds up after we leave.
i.
survives hand-over.
if your next hire cannot ship a feature on their first friday without us in the room, we have not finished. the test is real.
ii.
holds under audit.
every primitive is a working paper. every working paper is footnoted to source. the auditor reads the trail without us in the room.
iii.
sovereign by default.
data stays in the jurisdiction unless there is a written reason otherwise. afrihost / hetzner / your tenancy. not a us-east region.
iv.
halal-compatible where it matters.
commercial structuring avoids riba where the client requires. paired with islamic-finance counsel. it is structural, not branding.
v.
builds end. the layer is a choice.
every build has a last friday, booked on day one. if the figure must stay defensible after it, the managed layer is a separate order with a published scope — never an open-ended retainer.
vi.
one founder reads every paper.
governance §13. the founder signs every working paper that leaves the firm. drift is the only failure mode.
§ entity & posture · for your procurement file
the firm, on paper.
khwarizmi (pty) ltd is incorporated in south africa, johannesburg-resident, vat-registered, and operating under sa companies act 71 of 2008. structurally simple by design — one principal, one signature.
tax
vat-registered · za
invoicing in zar or usd · b-bbee level 4
domicile
johannesburg, sa
services delivered digitally · meetings on request
governance
one founder · one signature
every paper signed; canonical copy held by client
commercial posture
halal-compatible structuring available
paired with islamic-finance counsel on enquiry
data posture
sovereign by default
popia-compliant · data resident in za unless otherwise written