Bank Controlled Operating Systems for Private Markets
Managing Director at iCapital on wirehouse distribution challenges and tech evolution
The winning architecture is shifting from outsourced workflow execution to bank controlled operating software. In practice, that means the platform owns the rules engine, data model, permissions, and integrations, while the bank home office uses those modules to open funds, set review steps, manage documents, and resolve exceptions inside its own process. That lowers repeat data requests, cuts operational errors, and turns a low margin service layer into a higher margin software and integration business.
-
The core product pieces are already visible. Banks need configurable modules for fund setup, subscription intake, KYC and AML checks, document routing, fee logic, post trade reporting, and exception queues. iCapital already built much of this for itself, but the bottleneck is that staff on the provider side still run too much of the workflow instead of bank personnel running it directly.
-
The hard part is shared data, not screens. Different fund admins, tax providers, and banks each keep separate records, so investors get asked for the same information again and again. The strategic unlock is a common system of record, or at least a standard data layer with permissions, so the bank owns its investor data once and pushes it downstream without rekeying.
-
Comparable private markets infrastructure is converging on the same model. Juniper Square gives GPs one database and lets software and service teams work in the same system. Monark plugs private assets into existing brokerage infrastructure through APIs instead of creating a separate destination. The common lesson is that embedded workflows beat parallel workflows.
Over the next few years, private markets platforms will look less like marketplaces and more like configurable operating systems inside banks, brokerages, and large RIAs. The companies that win will be the ones that can package complex admin work into permissioned modules, connect them to custodians, admins, and tax providers, and charge for the transaction flow and software layer rather than for manual rescue work.