01

embedded fractional technical leadership.

we sit inside the team as cto / head of data, two or three days a week, for a fixed term. the team owns the title; we hold the technical posture.

cadence 2–3 days/wk
term 6–12 months
size series a — pre-ipo
→ read brief
02

ai enablement programmes.

eight-week programmes. the tool ships on day forty. the team owns it on day fifty-six. not a demo. the audit-team using it on a tuesday.

cadence full-time, joint
term 8 weeks
deliverable shipped tool + runbook
→ read brief
03

project-based platform & data engineering.

a fixed-scope build of the data layer, the warehouse, the api, the audit trail. priced sow, paired hand-over, sovereign hosting where it matters.

cadence dedicated build team
term 8–16 weeks
deliverable platform + runbook
→ read brief
04

compliance & data-trust engineering.

popia, audit, sovereign hosting, halal-compatible commercial structures. the trust surface — what the regulator, the auditor and the board can each verify, without us in the room.

cadence embedded + advisory
term 4–12 weeks
deliverable audit-ready working papers
→ read brief
05

fixed-scope productised offers.

six packages with priced sows. the audit-ready ledger. the popia kit. the working-paper template. the data-room rebuild. shipped in weeks, not quarters.

cadence fixed scope
term 2–6 weeks
price r 80k — r 480k
→ read brief
06

technical advisory & due diligence.

an investor needs a second opinion. a board wants the architecture read. an acquirer wants the data room. we write the working paper, hand it over, leave.

cadence intensive read-out
term 2–4 weeks
deliverable working paper · brief
→ read brief
07

commissioned research & working papers.

a working paper on your sector, your data, your question. published under the khwarizmi imprint, or held internal — your call. footnoted, repeatable, signed.

cadence research-lead pair
term 6–10 weeks
deliverable working paper · data
→ read brief
~ one method · seven shapes · always the same hand-over ~
how every engagement runs

three months · three weeks · then we leave.

the surface differs. the method does not. complete the corner, pair the hand-over, hand it back.

  1. M.01

    two weeks · diagnose the square.

    we sit in. we read the data. we name what is missing and what is fine. you get a working paper on day fourteen.

  2. M.02

    twelve weeks · complete the corner.

    we build, in pairs with your team. every primitive is a working paper. nothing ships without a runbook.

  3. M.03

    three weeks · hand over the work.

    we pair. we documented as we built; now we walk the team through it. on the last friday we close the laptop.

  4. M.04

    then we leave. you run it.

    this is the bit nobody documents — but it is where the engagement actually lands. we are an email away. that is all we should be.