White-Label Infrastructure for Wirehouses
VP of Product at iCapital on streamlining alternative investment administration
This reveals that winning the biggest wirehouses was less about selling a portal and more about becoming invisible infrastructure inside the bank's own client experience. The largest firms wanted control over every client touchpoint, from login screens to outbound emails, so iCapital had to separate its workflow engine from its surface layer and support bank specific branding, document templates, delivery rules, and hosted implementations. That made large accounts sticky, but it also made the product heavier to build and operate.
-
Wirehouses were the core economic prize. One product leader estimated that more than 80 to 85% of iCapital's business came from wirehouses, and another executive described four major wirehouses as the dominant distributors in private wealth alts. That explains why custom bank workflows got so much product attention.
-
The customization went far beyond swapping logos. Firms could set headers, footers, email templates, placeholders, aggregation logic, send timing, and whether investors received one combined email or real time messages. In practice, that means the same underlying NAV, tax, and reporting engine had to produce many bank specific client experiences.
-
A useful comparison is Juniper Square, which gives GPs white label LP portals and embedded admin on a shared system of record. iCapital faced a harder version of the problem because its most important customers were giant distributors with their own home office processes, internal systems, and brand control standards, not just fund managers serving LPs directly.
The direction of travel is toward more modular, bank embedded software. As feeder funds give way to registered products and transaction based enterprise contracts, the winning platform will be the one that lets banks self service more of the workflow while still keeping iCapital's data, compliance, and post trade machinery underneath the hood.