The isolation is the product
Aduro Advisors is a Denver-based fund administrator serving venture capital and private equity firms. Each client firm operates in its own Salesforce organization, with its own accounting systems and banking relationships — capital calls, transactions, and GP/LP data, kept deliberately apart. That separation is part of what Aduro sells: a firm's data sits on its own, apart from every other firm's.
It also meant Aduro's own team couldn't see across it. The company's operating data lived in roughly 680 separate places. Every question that spanned firms had nowhere to be asked; answering one meant assembling it organization by organization, and every new client added another system to the count.
The isolation Aduro sells to its clients is the same isolation that blinded Aduro — and it couldn't be fixed by loosening the boundary, because the boundary is the product.
The layer above
Nteli didn't build the application or the org structure — that was in place and working. What was missing was the ability to see across it. All 680 orgs now feed Salesforce Data Cloud, where the program can be examined whole: a single mastered dataset reconciling equivalent entities across independently managed sources, extended beyond CRM with Xero financials and Crunchbase enrichment. The agreed measure of success was one analytics report drawing all three together — and that's what runs.
The architecture was proven on a pilot of ten organizations, then rolled out across the full estate. Scaling from ten to several hundred surfaced the real constraints — performance, memory, concurrency — and addressing them is what shaped the final design. Deletes, reconciliation, and full resynchronization were part of that design from the start, so the consolidated view doesn't drift from the systems it draws on.
Onboarding as a routine, not a project
The second system moves bank data. Transactions flow from Kyriba into Xero as a direct bank feed, replacing statements that used to be uploaded by hand, one organization at a time, across an estate too large for that work to ever be finished.
The volume was never the hard part — the turnover was. Firms join, accounts close, organizations leave. In the manual world, every one of those events was somebody's project. Nteli built connecting and disconnecting as routine operations — including the messy version, where an organization disconnects on its own side without telling anyone. Those get recognized and cleaned up rather than left as a broken connection nobody notices until the numbers look wrong.
The integration doesn't get harder to run as it gets bigger. Adding the next hundred organizations costs roughly what adding the last one did.