iCapital feeding private holdings into Addepar

This reveals that iCapital was becoming infrastructure, not just a marketplace. In practice, an adviser could use iCapital to subscribe a client into a private fund, then have iCapital send position and activity data into Addepar so that the same holding appeared inside the adviser’s main portfolio reporting system alongside stocks, bonds, and other alternatives. That let advisers keep one client dashboard even when the subscription workflow happened somewhere else.

• iCapital’s core job was moving messy private fund paperwork into a structured workflow. An adviser entered the client, investment amount, and fund choice, iCapital generated the subscription package, routed signatures, and passed a metadata file to the fund administrator. Reporting data could then be forwarded onward to systems like Addepar.
  1 sacra 3 sacra
• Addepar sat on a different layer of the stack. It was built to aggregate holdings across many custodians and asset types, turn PDFs and fund reports into a unified portfolio view, and sell that reporting system to RIAs and family offices. That is why some firms wanted alt positions sourced through iCapital to flow into Addepar.
  2 sacra 4 sacra
• The overlap matters because it shows where competition actually sat. iCapital owned fund access, subscriptions, feeder structures, and document collection. Addepar owned the master portfolio dashboard for many advisory firms. They could compete on reporting, but they also fit together because advisers wanted one place to see the whole household balance sheet.
  1 sacra 2 sacra 3 sacra 4 sacra

Going forward, the boundary between private market access tools and wealth reporting systems will keep blurring. As evergreen funds spread through RIAs, the winning platforms will be the ones that make private assets look operationally similar to public assets, easy to buy, easy to reconcile, and visible in the same dashboard the adviser already uses every day.