When I was growing up, finance mostly meant public markets. Trading floors, ringing bells, things like that. But that's not really the case anymore. There has been a huge influx of capital investment into private assets.
Some of this has been because AI seems to be the only growth area in the broader economy. So more people are holding onto land, energy, data centers, GPU clusters.
And of course secondaries. So many secondaries. OpenAI and Anthropic secondaries everywhere.
But a lot of this is a regulation story, and a story about seeking alpha.
High growth companies are finding less and less reason to go public, they would rather just raise a Series F. More control, less paperwork.
And if there are massive, well-funded firms taking over and squeezing the juice out of public markets, well, you're going to start looking elsewhere for your edge.
As usual with all things finance, Matt Levine said it best:
“Private investment firms have become huge [and] the legal distinctions between public and private markets have become less important.”
“If an increasing share of the economy is in private assets, investors can't just index. You can't get ‘the market return’ by buying every public stock if half of the market is in private companies.”
How do you manage private assets? How do you keep track of how many shares you own, or what the strike price is? If you invest in a plot of land next to a hydro plant, where is the info about how much you paid and what your rights are?
It's in PDFs. It's in a Box folder, or in an Outlook email. It's in a Zoom call transcript. It's on a napkin with a hastily scribbled signature from a bar overlooking Columbus Circle.
Welcome to the nightmare world that is managing private asset data.
Amol Kapoor · CEO
Clifford Ressel · CTO
Today we're going to talk about how you can use cloud agents to make it easier to manage, record, and audit a company's investments -- in particular, a company securities master database.
Asset managers need to know what exists in their investment universe. Keeping track of this is a critical back office discipline, bringing together engineering and operations. Put simply, it's the master database of all securities.
For the engineers in the room, the secmaster is like any other master database: It is a source of truth. And often the left side of the join for many business critical analyses.
Say a custodian and a fund administrator report different share counts for the same holding. That conflict gets flagged before it reaches the secmaster. Then you go back to the sources to pinpoint the bug in how each one maps the security. When done correctly, upstream problems are fixed before they contaminate every business critical analysis.
In this way, the secmaster is an organizational primitive. It's a way of separating data producers from consumers, a centralized bottleneck where you can enforce standards, visibility, and quickly enable all data consumers.
Depending on where you invest, you need to take this simple concept and match it up with everyone else around the world, who may be speaking different languages and currencies.
For the most part, publicly traded assets have points of centralization: data vendors use identifiers like Bloomberg FIGIs or LSEG Rics, and numbering agencies provide identifiers like ISIN, CUSIP, and SEDOL.
So your secmaster maps from anyone else's view of an asset into your own, which is basically the only way to understand your positions, like modeling risk or reporting holdings.
Secmasters can contain a lot of information, but mostly they orient around identifiers. Knowing what kind of assets you have is surprisingly tricky. It's a bit like a datetime library: it seems simple, but there are tons of edge cases.
Let's take the simplest example. Your company holds some Google stock. Surely you can just record that stock in your table and you're done, right?
Not so fast. Which Google stock? On which exchange? Does the ticker match the name of the company?
Here's what that looks like in practice. Alphabet is one legal entity, three share classes, and a row for every listing, each with its ISIN, CUSIP, exchange, ticker, and currency.
Say some data comes in with only a subset of those columns. Code can still map it, because the columns it does have are standardized by exchanges and regulators.
But once the code can't generalize over the data with no regular identifiers, we're left with a mountain of manual verification and mapping.
Private assets make this all really hard. When you buy some Google stock, you have a pretty good idea of what you are buying, at what price.
But say you lend money to the company building a power plant near current data center developments. There's no shared identifiers going into the deal. No one is regulating the full structure of information you get, and there's no data vendor with an API that's already thought through the ontology of these entities in particular.
The repayment schedule, the conditions, and the collateral live in a one-off credit agreement and its amendments. It's all non-fungible. The asset is captured entirely in documentation.
It's not like the audit requirements and the cleaning requirements go away. If anything, it's worse now because it's so much less standardized!
Somehow, the data that lives in some PDF somewhere needs to make its way to the secmaster.
This is an extremely high-labor task. Generally, it just takes a lot of people-hours and a lot of domain expertise.
I want to ground this in a specific example. We work closely with a Fortune 200 asset manager here in NYC. They recently started owning a bunch of private assets, and it was causing a lot of problems for their data engineering team.
When any of the assets in the secmaster changed, they had to make sure the change was correct. So they had a system that did a day-over-day change analysis of their table.
If you have a table with 50,000 assets and 200 columns, even infrequent changes are going to happen on some daily cadence.
Every single changed cell was then sent to a team of people to triage. That team would manually go through docs and data sources to determine if the change was good or bad.
Not every row. Not every column. Every cell.
An asset changes price, or changes names, or goes bankrupt, or changes ownership. Every change in the investment universe has on average an hour of work behind it. That's hundreds or thousands of hours a month.
In simplest terms, a cloud agent is a coding agent, like Claude Code or Chat GPT, that lives and runs in a remote environment instead of on your local machine.
Because it lives in the cloud, we can spin it up and have it do work on a schedule, or in response to events -- for example when new data hits the secmaster.
Whenever there is a change in the investment universe for this asset manager, a Nori cloud agent spins up, in this case running a locally deployed open source model under the hood.
The agent has explicit instructions to figure out the source of the change. It also has access to a few useful tools: Box for PDFs, public APIs like Bloomberg, and even a small segment of email.
The agent then assembles an explanation of the change, citations for why it happened, and a recommendation for whether to keep or discard it. Finally, it pings the owner of the cell in Slack for review.
You still need a human to review changes!
But this dramatically cuts down the response time, because most of the previous slowness was people having to manually search through a bunch of documents.
But wait, how does the agent get domain expertise? How does it know what a 'good change' looks like?
The same way a new analyst does: from written instructions about where documents live, which sources to trust, and how to judge a change.
Agents are pretty good at self-modification! Changing how an agent behaves is as simple as editing natural-language English markdown files. So you use 'generic' agents that are skinned with configs like SKILLs or AGENT.md files.
The agentic secmaster is essentially a database with a bunch of cleaner-fish automatons that are dynamically making sure everything is up to date.
They can quickly spot problems and proactively surface them.
This technology is not limited to secmasters! Or even data cleaning in general. It can be useful across the firm.
The incredible potential of AI tools in finance is that they can make a huge range of tasks proactive instead of reactive.
The future of enterprise AI is not "use a robot on your laptop to solve a problem." It's having the robots come to you with tasks, advice, analysis, and recommendations.
To make that future a reality, you need to use flexible infrastructure that can be used for any task.
Your secmaster agent should just be the same cloud agent infrastructure as your audit agent or even your engineering agents.
Each has different instructions, tools, and triggers. That's owned by you. But the orchestration, security, integrations...all of that should just be owned by a vendor.
People want to buy solutions; engineers want to sell building blocks. We have to meet in the middle.
We found the most success working with brilliant folks who were able to make the leap from "cloud agents" to "wait, this can solve a problem I have today."
People want to use AI tools to do 100% of everything. This doesn't work in software, but it really doesn't work in finance.
It's OK to have a human in the loop. Lean into it. There are way more problems you can solve if you're OK with having one human spend five minutes looking at something.
Fred Brooks used "accidental complexity" for the difficulty that comes from how a system was built, as opposed to the problem it solves.
In the back office a lot of the work is like this. Teams record the same data in different ways and vendors use different formats, mostly because that's how things evolved.
Agents are now good at handling this kind of work, which gives people more time for the problems that are actually hard.