Platform Agent library
Marketing and referrals Prospects and proposals Client onboarding Client meetings Client service Billing and fees Portfolio oversight Data and reporting Compliance and risk
Wealth Management / RIA Family Office RIA Aggregators Pension / Endowments Asset Management Fund Administration Private Equity Venture Capital
PitCrew app Claude See all
Governed AI framework The Five Steps book Blog Fastlane Partners Press Testimonials
Trust Pricing About Us
Request a call
Governed AI

Building reliable AI for enterprise

A discipline for AI that is grounded in your data, checked against your rules, and provable when someone asks how it works.

Talk to a PitCrew expert
verified_userSOC 2 Type II cloud_doneAWS Case Study groupsBuilt by operators from LegalZoom, Intuit, Atlassian
Five Steps to Governed AI
The full discipline
Five Steps to Governed AI

The complete methodology in detail. Where ungoverned AI costs money, what each step is worth, and ten operations worked through end to end.

Read online About the book
ON THIS PAGE 01THE PROBLEM 02THE FIVE STEPS 03WHERE IT APPLIES 04THREE ACTIONS 05WHO IT IS FOR 06WHERE TO GO
The problem

Why most AI stalls after the demo.

The model is not the bottleneck. The discipline around it is.

01

It does not know your firm's rules, so it guesses at the edges.

02

Nobody tested it on your real scenarios, so failures surface in production.

03

And when the examiner asks "show me why," there is nothing to show.

When someone asks “show me why”
Why did we recommend Balanced Growth to the Ferris household?
What the AI said“Their portfolio looks too aggressive.”
01Rule it followedNone written down
02Tested onNo real cases
03Checked before it went outNo check
Nothing to show
Three things missing. Each one is why the output cannot be trusted.

None of them are model problems. All three are decisions nobody made before the build started.

The discipline

Five steps to AI your firm can trust.

Build it yourself or have someone build it with you. Skip a step, and the output is not trustworthy.

0102030405 DecideGroundCalibrateProveOperate Agree what correct meansConnect it to real dataRun your real scenariosGate every outputApprove, then log it SKIP: REWORK COSTS MORESKIP: ERRORS REACH CLIENTSSKIP: FIRST FAILURE IS LIVESKIP: CARRIES LIABILITYSKIP: NO RETURN
01
Decide · Agree what correct means. Skip: rework costs more.
02
Ground · Connect it to real data. Skip: errors reach clients.
03
Calibrate · Run your real scenarios. Skip: first failure is live.
04
Prove · Gate every output. Skip: carries liability.
05
Operate · Approve, then log it. Skip: no return.
STEP 01

Decide

Agree what the AI should do before anything is built. In plain language. Signed by whoever owns the process. Skip it and rework costs more than the build.

IN YOUR FIRM
An onboarding falls through because two people thought the other had it.
TRIGGER RULES EXCEPTIONS SIGNED OFF
CRM$4.2M CORE LEDGER$4.2M REPORTING DB$4.4M Core ledger SOURCE OF TRUTH
STEP 02

Ground

Connect the agent to your firm's actual data, documents, and policies, so it references them instead of guessing. Skip it and the agent hallucinates.

IN YOUR FIRM
Billing runs on a stale balance because nobody agreed which system wins.
STEP 03

Calibrate

Run it against your hardest real scenarios and compare to what your team actually did. If it cannot match your team on the hardest five, it is not ready for the other 500.

IN YOUR FIRM
It handles 200 cases. Case #201 breaks because nobody tested that one.
AGENTTEAM #01#02#03#04#05
OUTPUT RULES GATE PASS FAIL
STEP 04

Prove

Check every output against your rules. Pass or fail, with the rule named. A separate system, not the AI grading its own work. Skip it and the investment carries liability, not return.

IN YOUR FIRM
Audit prep eats a full week because no trail shows how each number was reached.
STEP 05

Operate

Your team approves what executes. The record assembles itself as a byproduct. Skip it and there is no return on the time saved.

IN YOUR FIRM
Reconciliation ran, but there is no record of what happened or who approved it.
APPROVED · J. OKAFOR GROUNDED14:01:58 CHECKED14:02:03 VERIFIED · PASS14:02:09 LOGGED · EXPORTABLE14:02:11
verified Output: work your team approves, with a run history an examiner accepts
Talk to a PitCrew expert
Where it applies

The work this discipline is built for.

Any job where the answer has to be right, and you have to be able to show why. Six from the agent library, from the first client meeting to the exam.

The domain changes, the discipline does not. Wealth management, asset management, fund administration, banking or insurance: the same five steps decide whether the output holds up.

Start today

Three actions you can take right now.

They take a morning, cost nothing, and reveal whether your firm is ready to build reliable AI.

ACTION 01
Write down what "correct" looks like

Pick your most painful workflow. With whoever owns it, write the trigger, the rules, the exceptions. Get sign-off. That is your spec.

WORKFLOWTRIGGERRULESEXCEPTIONSSIGN-OFF ONE PAGE
ACTION 02
Find where the data actually lives

List every system holding the data the agent needs. Ask which one wins when they disagree. No answer? That is your grounding problem.

SYSTEMWINS? ?
ACTION 03
Find your five hardest scenarios

Pull five real cases from the past year where the workflow got tricky. Those are your first test cases, and your bar for ready.

FROM THE PAST YEAR 0102030405
Who this is for

Written for firms that have to prove their work.

donut_smallWealth managers and broker-dealers
family_restroomFamily offices
account_treeFund administrators
show_chartAsset managers
business_centerPrivate equity and private credit
account_balanceBanks, credit unions and insurers

This discipline works with any tools. We publish it freely because the industry needs a standard for how reliable AI gets built in environments where the output has to be defensible.

handshakeVendor agnostic lock_openFree and ungated
Where to go from here

PitCrew is where all five steps are built in.

Follow the discipline with any tools, or use PitCrew, where the five steps are built into the platform: spec templates, 40+ integrations, industry test scenarios, output verification and automatic run histories.