Hetu / Consulting
Forward-deployed decision verification engagements
Hetu Consulting embeds a forward-deployed engineering team — not a sales engineer with a demo script — to encode your constraint framework, seed the causal graph with your domain experts, and ship a working verification layer on one real decision. Then we hand off to the platform once it's proven. Looking for broader AI adoption or modernisation work instead? See Deployment.
How an engagement runs
Not a platform rollout — one real, currently-manual, expensive-to-get-wrong decision your team already makes.
Your domain experts encode the failure patterns they already know. This is configuration, not a model to train.
The verification layer runs alongside the existing process until its confidence labels earn trust against real outcomes.
Once proven on one decision, the same graph and gates extend to the next — on the platform, without us in the room.
Engagement packages
We scope one decision, map its failure patterns with your domain experts, and run the Calibration Benchmark live against your own historical data.
Full build: causal graph, gates, confidence labels, audit log — shadow-run against real outcomes before it ever touches production.
Ongoing FDE staffing to extend the graph to additional decision types across the org as each one proves out.
Any of the above, purchased through AWS, GCP or Azure marketplace and routed through existing cloud spend commitments.
A typical first engagement
Weeks 1 through 10
Week 1: we sit with your credit ops team and write down the six failure patterns they already recognise by feel — the ones nobody had encoded because nobody thought a rule tree needed writing down.
Week 3: those patterns are traversals in the graph, running in shadow against real applications, next to the analyst who already does this by hand.
Week 7: the first live decision — a same-day underwriting exception — clears CONFIRMED, and the risk committee sees a rendered audit trail instead of a Slack thread.
Week 10: we hand off. Your team owns the graph, and the next decision type is a platform license, not a new engagement.
Where the FDEs come from
These engagements are staffed from Academy's Decision Verification track: causal reasoning, audit design, calibration, and a vertical elective. Full syllabus on its own page.
Trains the discipline these engagements run on, then staffs them at a lower blended cost.
Explore
Design partners
We start with a scoping call: what the decision is, who owns it today, and what "wrong" costs. Most engagements are live in weeks. Applying to Academy? Say so in the same email.