The model The engine Examples Working together Book a scoping call
Factory — example builds
[ Example build — Kestrel Asset Management ]

Kestrel runs a good investment process on spreadsheets. They kept their order management system and their fund administrator — the official NAV never moved — and we built the working layer around them. Live in five months.

$3.2B · 14 peopleequity mandates and a private credit fund
Kept the OMS and the administratorthe official NAV is still the official NAV
Prototype in 2 weekslive in month five

Kestrel Asset Management is an example, not a client. The firm and the numbers are made up. The shape of the problem, the parts of the engine, and the way a build runs are real.

[ № 01 — The situation ]

A good process, documented badly

Nothing here was broken enough to fix on its own. Together they cost the firm a person and a half.

Mandates

Model weights in one shared spreadsheet

A single file, opened by four people, with the version in the filename. Nobody could say when a weight last changed, who changed it, or what the book looked like on a date in the past.

Research

Research nobody could find again

Notes in documents and email threads. When a position moved, the reasoning behind it took an hour to dig up — if anyone had written it down at all.

Reporting

Eight days for a quarterly letter

Two people, a copy and paste from last quarter, and a manual check of every number against the administrator’s file. The commentary was the easy part.

“Our investment process is good. The paperwork around it is held together with spreadsheets.”

Chief investment officer, first scoping session
[ № 02 — The constraint ]

What they would not replace

For an asset manager the book of record is not negotiable, and it should not be. We build around it.

Stays exactly where it is

The order system and the administrator stay

Trades go through the order management system. The fund administrator strikes the official NAV, and that number is the number. We read both, we reconcile to both every morning, and we never pretend to be either. The book of record does not have to move for the work around it to get better.

[ № 03 — The scoping sprint ]

What we learned first

Two sessions and one real mandate taken apart, at our cost.

01

Drift was checked monthly because it was checked by hand

Three of their last four client complaints came from a position that had drifted between checks. The check itself was sound. Its frequency was set by how long it took a person to do.

02

The exceptions that mattered were not the big ones

Most breaches were small and stale — a cash weight left over after a redemption, sitting there for weeks. Nobody was watching for age, only for size.

03

The letter was slow because the data arrived late

Numbers were only trusted once the administrator closed the period, so everything else queued behind that. Live positions, reconciled daily, take the queue away.

04

Research and holdings had never been linked

The note that explained a position and the position itself lived in different systems, so nothing could ever prompt anybody at the moment it mattered.

[ № 04 — The build ]

The mandate cockpit

Every account against its model, checked every morning. Anything outside tolerance lands in one queue with the reason attached, and the research note sits with the position that caused it. Client and consultant letters generate from live holdings, so the commentary is written once and the numbers come from the book.

Kestrel · Mandate cockpit Yours
Exceptions this morning · 5 open
Cash 6.2% vs 3.0%12 days
Balanced Growth · 14 accounts
TD 5.8% vs 5.0% maxSingle name
Canadian Equity · 3 accounts
Duration 6.1 vs 5.5Open
Core Bond · 8 accounts
Unsettled redemptionWatch
Income · 1 account
Cash 0.4% vs 1.0% minCleared 08:15
Global Equity · 2 accounts
Mandate · Balanced Growth
Equitytarget 60.0%61.4%
Fixed incometarget 35.0%32.4%
Cashtarget 3.0%6.2%
Alternativestarget 2.0%0.0%
Why · research on the position

“Trimming the banks into strength, holding the cash until the December meeting.” — R. Vasquez, 12 Aug

Attached to 3 positions Cited in the Q3 letter
Q3 reporting
Client letterfrom live holdingsDraft ready
Consultant pack14 mandatesReconciled to the administrator

Illustrative screen. Positions reconcile to the order system and the administrator every morning before the queue is built.

[ № 05 — The parts ]

What it was assembled from

The investment plumbing already existed. Kestrel paid for their rules and their reporting.

In the engine

Portfolios and mandates

Positions and performance, mandates and model templates, and assigning them across the book.

In the engine

Client and household records

The client, the entity and the mandate they hold, in one record instead of three lists.

In the engine

Documents and reporting

Letters, packs and exports generated from live data, in their brand.

In the engine

Permissions and audit history

Who changed a model weight, and when. This is what the spreadsheet could never give them.

In the engine

The AI layer

Drafting commentary from the quarter’s real moves, for a human to edit.

In the engine

Client portal

Where consultants and clients see their own mandate.

Built for them

The reconciliation feed

A daily read of the order system and the administrator, matched, with breaks shown.

Built for them

Exception rules and tolerances

Their rules, including how long a breach is allowed to sit before it is escalated.

Built for them

The consultant reporting pack

The format their institutional clients ask for, produced from live holdings.

Six of the nine pieces already existed. Three were built for Kestrel.

[ № 06 — The line ]

How it actually ran

A short build, because most of what an asset manager needs is the part that already exists.

01

A free scoping sprint

Two sessions with the CIO, a portfolio manager and the operations lead. We took one real mandate apart, weight by weight.

2 weeks · Free
02

A prototype on one mandate

Their largest mandate, real positions, real drift, on screen. It found two live breaches on the first day.

Week 2
03

Monthly releases

Mandates and drift. Then the exception queue and research notes. Then reporting. Then the consultant view.

Months 1–4
04

Live

Everything runs from the cockpit. The spreadsheet still exists as a backup, and nobody opens it.

Month 5
[ № 07 — The result ]

What changed

The investment process did not change. The evidence and the speed around it did.

BeforeAfter
Drift checked monthly, by hand
Checked every morning, automatically, with age tracked
Research in documents and email
Attached to the position it explains
Quarterly letter: eight days, two people
Half a day, one reviewer
Model weights in a file with a version in its name
One record, with who changed it and when
“Why do we hold this?” — an hour of digging
On the position, with the date and the author

Illustrative figures for an example build.

[ № 08 — Optionality ]

Where it goes next

The cockpit was the first thing. What comes after it is entirely their call.

Up next

The next two releases

Already agreed and dated.

  • The private credit fund on the same engine — subscriptions, capital calls and investor reporting
  • A consultant portal with their own view of each mandate
  • Pre-trade checks against the model before an order leaves the desk
The longer game

Take on more of the stack

Only if and when it is worth it.

  • Hold positions and a shadow NAV themselves
  • The administrator becomes the check, not the only source of truth
  • Add new mandate types and new fund structures without adding people
  • Every step is a decision they make with a year of parallel data behind it
Or pause

Or stop, and keep the cockpit

A finished thing is allowed to be finished.

  • The cockpit is in production and does not need us
  • Stop the build team, keep the engine licence
  • Feeds, tax rules and models stay current underneath
  • Come back when the next fund launches

You choose the direction each month. Nothing about this build makes the next decision for you.

[ More — Other example builds ]

Same engine, different firm

[ Get started ]

Your firm is not Kestrel Asset Management

Tell us how yours runs and what you wish it did instead. Half an hour on a call. We'll tell you what's already built, what we'd have to make, roughly what it costs, and whether it's worth doing at all. Scoping after that is free.

or email us directly at factory@superadvisor.ai
Factory by Super Advisor — the wealth software factory