Blog
5 min read

Introducing the Finny Ops Agent

A virtual back-office employee for modern funds. It starts with reconciliation, and it does not stop at a report.

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. So we built something for it. Not a chatbot, not a dashboard, not another ETL pipeline. An agent that sits inside your environment, understands your workflows, and gets the right context to the right person at the right time.

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. The Ops Agent does that first: it brings the data together, matches positions, trades, cash, and fees, flags breaks, explains likely causes, and keeps an audit trail as it notifies whoever owns the fix.

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

Diagram showing the Finny Ops Agent positioned between fund data sources (prime brokers, OMS/PMS, internal books) and the teams that act on exceptions
The Ops Agent sits between your data sources and the people who need to act on what it finds.

More than a report

The Ops Agent catching a break, explaining the cause, and routing it in minutes, not a morning.

A report that lands in an inbox and waits isn't the goal. The agent does the work around the information: it monitors a workflow, investigates an issue, explains what happened, and routes the follow-up. Ask it things like:

Why is our book different from Goldman today?Which breaks are still unresolved?Does accounting need to review anything?Anything the PM should see before the morning meeting?Draft a note explaining this mismatch.Is this related to yesterday's rebalance?

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.

Diagram showing a reconciliation break flowing from detection through explanation to routing and follow-up with the correct team
From break to follow-up: detect, explain, and route without a human doing the triage.

Built to run where your data lives

For funds, data privacy is not a feature. It is a requirement. The Ops Agent runs inside your own cloud or VPC, connects only to systems you approve, and follows your permission model end to end.

No fund data leaves your cloud. No call-home. No training on your strategies.

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.