Riaan Kleynhans · Operating architect
The architect of the promise
I close the gap between what was sold and what gets delivered — in enterprise AI and creative operations. Not tools: a code-enforced operating model your teams can run, price and audit.
For CMOs, CFOs, CISOs and heads of transformation who need predictable unit economics, zero-data-retention security and delivery discipline — not another AI narrative.
Why promises break
The gap forms in six disconnects
In this order, every time. Each link is closed by a named interface with a named owner — never by goodwill at the end.
- 01Executive ambition
Closed by New business → Solution design
- 02Vendor narrative
Closed by New business → Solution design
- 03Unvalidated use case
Closed by Solution design → Commercial finance
- 04Unpriced gap
Closed by Solution design → Commercial finance
- 05Unprepared organisation
Closed by Commercial finance → Implementation
- 06Disappointment, rework, trust loss
Closed by Implementation → Client operations
What I do
Four interfaces, one reality
Operations, architecture, commercial finance and implementation describe the same solution before anything is promised. Each interface is held by one role with a checklist, not a title.
Ambition into a charter, an evidenced diagnosis and the gaps with their causal chain.
Solution Design Architect
Gaps into a prioritised portfolio with benchmark investment and a value ledger.
Commercial Presales Lead
The design into real controls, owners and a governed pilot.
Implementation Director
Proven value, then handover to independent operation.
Advertising Operations Consultant
How I work
Eight stages, each with a question that must be answered before the next
From alignment to evidence-based scale. Validate is a gate, not a meeting: four signatures, each blocked by any open condition.
- 1Align
What must be true for this client to say yes, and who must be comfortable before it can proceed?
- 2Diagnose
Where is the operating system consuming time, money, capacity, or trust?
- 3Model
What would the client actually operate after implementation?
- 4Validate
Can the teams responsible for delivery confirm that this design, timeline, cost, and control model are realistic?
- 5Govern
Who is authorized to decide, what evidence must they see, and what happens when the system is wrong?
- 6Mobilize
What must be ready before the first live transaction or asset enters the new model?
- 7Prove
Did the new operating model produce better approved outcomes than the old one?
- 8Scale
Can the model expand across brands, markets, languages, and channels without losing accountability or local relevance?
The proof
An honest engine, not a slide
Every number here is read from the code and the last verification run. Inside the engine the same page reads your ledgers. Unknown stays unknown — it prints [ TO BE COMPLETED ], never an estimate.
- Tests
- 223/223
- verified 2026-09-19
- Room rules
- 23
- conditions for approval, by seat
- Handoff approvals
- 4
- incomplete → release refused (409)
- Chained ledgers
- 5
- append-only, sha256-linked
- Capabilities
- 18
- agentic · deterministic · human
- TOM lines held
- 18/23
- 5 marked open, not hidden
Start here
Baseline your own operating model
10 dimensions, a few minutes, no sign-up. The result is labelled unverified until a Diagnostic — and you can carry the answers straight into the engine.