Know what your AI decides, on what data, and who answers for it.
Most organisations find out at the audit. We help you know before the next tool goes live, by building governance into how your data is made and your decisions are taken.
What every AI audit will ask
Where did it come from, and what does it leave out?
Which decisions does AI shape, and who signs them off?
Who is affected, and could they challenge the outcome?
AI governance fails in the gap between the data team and the legal team. That gap is where we work.
Legal writes the obligations. The data team builds. Nothing connects the two until an auditor asks a question nobody can answer. We turn each obligation into a requirement your teams can build and test: what the data must hold, where it is captured, and how it is checked.
Not a technology vendor. Not a law firm. The layer in between.
01 · See
Map how AI is used and who really decides, under the official structure.
02 · Trace
Follow a decision back to the data underneath it, and find where the gap entered.
03 · Specify
Write each obligation as a requirement your teams can build and test.
04 · Hold
Put decision rights and checks in place, and leave a structure that stays standing.
Unseen data does not stay the same size. Every new system inherits the blind spots of the last.

Who you work with
Our founder, Mbali Chaise, has spent her career designing the evidence organisations base their decisions on, across healthcare, defence, banking and higher education. It is why Intrahaero starts with the data.
Read our founder’s story →Six questions. Where do you stand?
Two each on data, decisions and people. Your answers draw your governance as it stands today, and show where it would break under audit.
- 6 questions
- About 90 seconds
- Nothing sent or stored
One method. Start where you are.
For organisations of 50 to 500 people deploying AI in the EU. Most start with the review or a leadership session.
- TYPICALLY 4–6 WEEKS
Governance review
Find out where your AI governance would break, before an auditor or a customer does.
What changes: you know what to fix first, and who owns it.
STEPS 01–02 · SEE, TRACE→ - TYPICALLY 6–10 WEEKS
Requirements design
Turn governance into something your teams can build, not a document they have to interpret.
What changes: legal, data and product work from the same requirements, and build it right the first time.
STEP 03 · SPECIFY→ - ONGOING
Leadership advisory
Keep governance holding as new tools and new rules keep arriving.
What changes: new tools go live sooner, with Mbali on call before decisions are made.
STEP 04 · HOLD→ - HALF A DAY TO TWO DAYS
Workshops and training
Give your teams the confidence to spot problems themselves.
What changes: one shared language across teams, and less dependence on outside help.
SUPPORTS EVERY STEP→