This is the last post in the series. We want to use it to make a direct ask of the industry — peers, partners, clients, the firms we work with and the firms we don’t.
Across nine posts we’ve walked through one argument: the wealth-tech category has been competing at the rendering layer for fifteen years, and the durable opportunity is at the structured data layer underneath. Family offices are spending $200K–$500K a year keeping that layer alive by hand. AI changes the math, but only in combination with domain experts. The data layer makes possible everything that comes next — render-anywhere reporting, intergenerational transfer that doesn’t transfer as chaos, the financial operating system of the next decade.
Now the ask.
What we’re asking the industry to commit to
Four things. None easy. All worth it.
If you are buying software, ask yourself if you want to be the service — because software isn’t SaaS anymore, it’s just software. You at minimum need SaS (Services as Software). But likely something a little more advanced than that, which is what we are suggesting. We have an internal name for it. We’ll leave that for our guys for now.
(1) The hard work is the moat. Do the hard work.
For too long, the wealth-tech category has chased the renderings — the dashboards, the client portals, the slick PDFs — because they demo well and they sell well. The structured database underneath has been left to humans because it’s expensive, weird, and unsexy.
The hard work — structuring K-1s, mapping trust ownership, reconciling capital balances, ingesting mortgages and intercompany loans, handling carry and waterfalls and side pockets — is exactly the work that produces durable infrastructure. Bain’s analysis of where private markets are going, McKinsey’s projections on advisor capacity, Deloitte’s view of family-office growth — all of them point at the same place: the volume of complex, structured wealth data is going up faster than the labor supply to handle it. The firms that build real infrastructure here will own the next thirty years. The firms that keep selling charts will be priced like the BI vendors of 2015.
Do the hard work. The hard work is the moat.
(2) The client owns their data.
This is not a marketing line. This is an architectural commitment.
If you are a wealth-tech vendor, ask yourself: when a client leaves us, what do they take with them? If the answer is “a PDF” or “a CSV export,” you don’t believe the client owns their data. If the answer is “a structured, portable, machine-readable representation that any other system can read on day one,” then you do.
If you are a family office or RIA, ask your vendors the same question. Put it in the contract. Make portability a procurement criterion, not an afterthought.
The CFPB’s open-banking push, the maturity of MCP, the AI agentic-tooling wave — all three forces are pushing the industry toward client data ownership whether the industry wants to go or not. Get there voluntarily and you get to design the standards. Get dragged there and you get to comply with someone else’s.
Stop selling data. It’s the strongest currency out there — let’s stop treating it like a commodity, even if it is anonymized. Ask your vendor, if you are buying: do you sell my data, even anonymized? Here, we say we don’t really know if anything is perfectly anonymized — so let’s just not sell it.
(3) Render anywhere.
Once the client owns the data, the dashboard has to win on its own merits. That’s good for the dashboard businesses that are actually good, and bad for the ones that have been coasting on lock-in.
A render-anywhere world means the family-office principal can use whichever portal she prefers. Her CPA can pull from a live feed instead of asking for a year-end package. Her estate attorney can see the current ownership graph instead of asking what changed since 2019. Her kids can interact with their share through whatever interface feels natural to them — which, for most of them, will increasingly be a conversational AI rather than a chart.
McKinsey’s 2035 wealth-management projections suggest the rendering layer is where AI competition will be fiercest. Building for that future is building for clients, not against them.
(4) Truth in finance — the database wins when there’s a discrepancy.
Today, when a number doesn’t tie — when the dashboard says one thing and the CPA’s books say another and the GP statement says a third — the resolution is usually political. Whose phone call wins. Which system gets manually overridden. Which version makes it to the principal first.
That is not how a serious financial infrastructure works. In a serious system, every number has a provenance, every reconciliation has an audit trail, and when there’s a discrepancy, the structured database — the source of truth that everything else renders from — wins, and the renderings update.
Trust in financial data has to be earned the same way trust in code is earned: by being checkable, versionable, and auditable. The vendors that build for that earn the kind of trust that compounds. The ones that don’t get eroded a quarter at a time, every time a number doesn’t tie.
Store the documents in line — by which we mean in the database, with their details directly alongside the records, so we can render those too.
What we’re committing to ourselves
Architectural commitments are explicit and non-negotiable:
The client owns their data, in structured form, on day one. Anything we build is renderable anywhere — through our interface, through our partners’ interfaces, through AI agents that our clients permission. The database is the source of truth, and our team — domain experts paired with AI — is what keeps it honest. Where humans are doing work AI should do, we automate. Where AI is doing work humans should do, we don’t.
White Glove × AI is the new model. It’s powerful, and we are harnessing it.
The closing ask
To family-office principals, RIA founders, and the firms we work with — push your vendors. Ask the portability question. Ask the audit-trail question. Ask the render-anywhere question. The answers will tell you who’s building for 2035 and who’s hoping nobody asks until 2030.
To the next generation, the heirs, the operators who will run all of this in twenty years — the infrastructure we build now is what you’ll inherit. We are trying to build something you can actually use, in interfaces you actually like, with data you actually own.
Where we’re going is a structured, portable, render-anywhere financial life. The data layer is the asset. The renderings are the experience. The combination of domain experts and AI is the engine. The client owns the result.
Thank you for reading the series. We’ll keep doing the durable thing.
Real Work. Hard Work. Real Moat.