Running the investment arm of a family on AI rails

The mandate

The investment arm of a family. A concentrated portfolio spanning public equities and private positions, run to a real objective with real money, not a model in a spreadsheet. Two jobs sat inside one mandate: produce results, and build the operating system that produces them reliably, so the returns come from a process and not from luck or a single good year.

The problem

Decisions drift. They get made in conversations, half-remembered later, and quietly contradicted. The book is also noisy: too much to monitor, too many holdings and moving parts for any one person to track by attention alone, so things get missed. A concentrated book makes both worse, because concentration means the mistakes are larger when they land.

What I built and ran

The book is ahead of the S&P 500 over five years. The private positions are above the family's own target range. That result came from a concentrated, conviction-weighted book, and from the operating layer underneath it. I built an AI operations layer that runs the day-to-day discipline of the portfolio, so my judgment goes on decisions instead of data-gathering and monitoring.

How it works, the operating layer

Each part does a job a human does badly under load.

Research runs through AI pipelines that pull, reconcile, and re-derive the numbers behind every position, with a standing rule that any load-bearing figure gets recomputed from raw source rather than trusted from a summary. The pipeline catches the classic aggregator trap, a cumulative return quietly presented as an annualized one, before it reaches a decision.

Monitoring runs continuously against a defined scoreboard. The portfolio is measured against its benchmarks on a live basis, and the system is built to fail loud: if a data slot is empty, it refuses to produce a number at all. A flag stays a flag until it is resolved, not until it is forgotten.

The records enforce decision hygiene. Every material decision is written down with its reasoning at the moment it is made, so the book carries its own audit trail. What got decided and why is always recoverable, across years and across advisors.

Execution is gated. Nothing trades automatically. The AI does the reading, the scoring, and the monitoring; a human makes and authorizes every actual move, and that boundary is asserted in the system itself, in code. The infrastructure is there to make the human decision better informed, never to leave it unattended.

The outcome

The portfolio produces a result ahead of its public benchmark, and it produces it from a system that a second person could pick up and run, because the reasoning, the measurements, and the guardrails all live in the records rather than in one person's head.

What transfers

Research recomputes load-bearing figures from raw source, monitoring refuses to invent a number from an empty slot, every material decision is written down when it is made, and nothing trades until a human authorises it. The operating layer is the transferable part: research pipelines that check their own arithmetic, monitoring that fails loud, decision records that survive the people who made them, and execution that stays under human control by design.

One of a set of engagement and systems case studies. If a problem like this is on your desk, start with a conversation.