Introducing Scout Operations
Scout Operations is being built to investigate reconciliation breaks and coordinate fund workflows. Deployment scope, automation and human review are agreed with each team.
By Nisarg
The hardest part of running a fund isn't always research. It's the back office: messy data, reconciliation breaks, manual follow-ups, and teams burning hours figuring out what changed and who needs to act. Scout Operations is the product we are building for that work: software to investigate discrepancies, gather supporting evidence, and coordinate the next action. Capabilities and staged delivery are agreed for each deployment; your team approves changes to official books and the release of investor reports.
The first wedge: reconciliation
Every fund runs this workflow. Data arrives from prime brokers, internal books, OMS/PMS, spreadsheets, research platforms. Someone normalizes it, compares it, explains the breaks, and chases the right person down. That is the first workflow we are designing Scout Operations around: compare agreed records, flag breaks, investigate likely causes, and keep supporting evidence with the follow-up. Supported sources, checks and notification permissions are confirmed during scoping.
But reconciliation is the entry point, not the ceiling. Once an agent understands your data, your recurring exceptions, and your escalation paths, the real question is what else it should be doing.
Where the agent sits
More than a report
A report that lands in an inbox and waits isn't the goal. The intended workflow connects checks, investigations, explanations, and follow-ups. An explanation or proposed fix still needs review; it is not proof that an official record has changed. Questions the workflow is designed to help teams investigate include:
That's the line between a dashboard and a teammate: one shows you data, the other does something with it.
Knowing who needs to act next
Finding the issue is rarely the hard part. Knowing who acts next is. Accounting reviews a fee or NAV item. Legal reviews a restriction. A trader chases a failed trade or counterparty mismatch. A PM checks exposure before the morning meeting. Engineering investigates a broken feed. The Ops Agent cuts out the coordination tax that shows up after an issue is already found.
Built to run where your data lives
For funds, data privacy is not a feature. It is a requirement. Private deployments are scoped for your cloud or VPC, with agreed sources, permissions and model connections. Data flows depend on the deployment and providers you choose; confirm those boundaries before connecting confidential records.
We're looking for Design partners
This is an early product direction, and we want funds to help shape it. We're starting with reconciliation because it's clear, painful, and high-value, but the best automations are usually hiding inside the daily work nobody talks about. Tell us where your team loses the most time, which checks are still too manual, and what you'd actually trust an AI ops employee to own.
If that's you, reach out or book a call.