Evergreen Funds Pressure Feeder Platforms

Diving deeper into

Managing Director at iCapital on how evergreen funds are eating private market share

Interview
they quickly realized that there was very little that either one of those entities would want to pay anything for that service
Analyzed 4 sources

The key lesson was that matching institutions to private equity funds is not a software market, it is a relationship market where neither side sees enough extra value to add a new paid middleman. Big LPs already have manager networks and internal teams, and big GPs already raise from those LPs directly, so the real monetizable pain sat in private wealth, where smaller checks created paperwork, minimum size, and reporting problems that someone would pay to remove.

  • iCapital found willingness to pay in feeder funds and admin, not simple introductions. Wealth advisors needed someone to pool many $25,000 to $100,000 client tickets into a single vehicle that could meet a manager's $5 million to $10 million minimum, while handling KYC, subscriptions, capital calls, distributions, and tax documents.
  • That is why the company evolved into a dual model. It became both a distribution platform and the GP or administrator sitting in the middle of the transaction flow. For the fund manager, it looked like one institutional investor. For the advisor, it became one login and one operating system across many funds.
  • The same logic explains why direct registered evergreen funds now pressure iCapital's highest margin business. When products like BREIT or BCRED let wealth clients invest directly, the introduction layer still matters, but the richer economics from custom feeder structures and admin work shrink, pushing the market toward lower margin software and enterprise service fees.

Going forward, value will keep shifting away from access alone and toward infrastructure that makes private markets feel operationally similar to mutual funds for advisors and brokerages. The winners will be the platforms that own onboarding, data flow, reporting, and enterprise integrations, because that is the part of the workflow customers repeatedly pay for at scale.