Part 1 of 4 — Building portfolio services that actually work

The best venture capital firms figured this out a long time ago: writing the check is the easy part.

When Andreessen Horowitz launched in 2009, it did something that made traditional VCs uncomfortable. It built an entire operating platform alongside the fund: dedicated teams for talent recruitment, marketing support, business development introductions, technical guidance. It looked less like an investment firm and more like a full-service advisory firm that happened to deploy capital. Portfolio companies didn't just get money. They got infrastructure.

A decade later, Y Combinator's alumni network is one of the most valuable assets in Silicon Valley. Not because of the three-month program, but because of what persists after it. Thousands of founders share a common credential, refer each other business, make introductions, hire from each other's alumni pools. The network compounds in ways the original check never could.

Funders in the social sector have noticed. Foundations, accelerators, and impact funds are increasingly trying to build their own versions of portfolio support. The question is which parts of the VC model are worth borrowing, and which parts will lead you astray.

What transfers

The platform model. a16z proved that a portfolio's value isn't just the capital; it's the operating infrastructure around it. For social sector funders this translates directly. The networks you've built with corporate partners, technical advisors, and peer funders shouldn't activate only at the moment of the grant or cohort. They should stay accessible to portfolio organizations in year two and year three, not just during the application window. The lesson isn't to become a VC. It's to stop treating your network as a program feature and start treating it as an ongoing asset.

Dasra, a philanthropic accelerator working with Indian nonprofits, operates on the same logic. It provides financial management support, board development, and funder introductions as infrastructure around the grant, not just at the grant moment. Organizations in its portfolio gain access to peer networks and advisors that remain available long after any individual engagement ends.

The named relationship. Echoing Green, one of the oldest fellowship programs in social entrepreneurship, does something deceptively simple: every fellow gets a dedicated portfolio manager. Not a shared inbox. Not office hours twice a month. A person whose job is to know their organization, understand their current blockers, and route them to the right resource before they have to ask. At scale this requires a tiered model, since not every organization needs the same intensity of relationship at every moment. But the principle holds. Founders should know exactly who to call.

Ashoka operates the same way at a much larger scale, particularly across India and Africa. Ashoka fellows have lifelong access to a peer network and a dedicated regional staff lead. The relationship doesn't end when the fellowship period does. In contexts where founders often lack a peer cohort working on similar problems, that continuity is the infrastructure.

The convening as infrastructure. The Skoll World Forum is the most important annual gathering in social entrepreneurship, not because Skoll requires attendance, but because enough good people show up that missing it has a real cost. That's network effects applied to community. It didn't happen by accident; Skoll invested in making the convening valuable enough to be self-sustaining. For funders building portfolio communities, the question isn't whether to host a gathering. It's what it would take for your gathering to become the one people plan their year around.

Where it breaks down

Many well-intentioned funders borrow the VC vocabulary without accounting for the structural differences underneath it.

Equity creates accountability that grants don't. When a VC firm backs a company, it holds a stake. That stake creates a natural activation mechanism: the portfolio company has financial incentive to stay engaged, report honestly, and ask for help before things go wrong. In a grant relationship, that mechanism doesn't exist. Portfolio support in the social sector has to be built on relationship and community rather than financial stakes. That's not a weakness; it's a different design problem. But funders who import VC-style dashboards and quarterly reporting cadences without accounting for this often find portfolio organizations going through the motions rather than actually using the system.

Growth at all costs is the wrong goal. The VC model is optimized for outlier returns. It expects most investments to fail and a few to return the whole fund. That logic doesn't translate to mission-driven organizations. A tech nonprofit that serves 50,000 people well and sustains itself for twenty years is a real success, even if it never scales to millions. Portfolio support that pushes every organization toward hypergrowth misallocates resources and can push founders toward decisions that compromise the mission. The right goal is appropriate scale, and support infrastructure should be designed around that.

Sector specificity is a feature, not a constraint. A generalist VC portfolio spans fintech, biotech, consumer apps, enterprise SaaS. That diversity is intentional; it hedges risk and surfaces unexpected connections. In the social sector, portfolio diversity often works against community cohesion instead. Founders building AI tools for judicial access have little to learn from founders building climate tracking platforms, even in the same cohort. The most valuable portfolio communities form around shared identity and shared challenge, not shared funder. Funders with the discipline to stay focused on a specific intersection (tech and nonprofit, or AI and education) build stronger communities as a result.

The insight VC can't give you

There's one thing the best social sector portfolio programs have figured out that has no real VC equivalent: the proximate founder community.

When the people building solutions have lived experience of the problems they're solving, something shifts in how a portfolio community functions. The knowledge that matters most isn't in the advisor's rolodex or the funder's theory of change. It's in the room, in the founders themselves. A peer conversation between a founder who navigated a state procurement process last year and a founder about to attempt the same thing is worth more than any expert panel.

Village Capital has operationalized this deliberately. Working with entrepreneurs in emerging markets across East Africa and South Asia, their cohort model uses peer review rather than external expert judgment: founders in the portfolio evaluate each other's investment-readiness. The funder's role becomes facilitation, not arbitration. The knowledge inside the portfolio flows to the people who need it, rather than being routed through a central authority.

This means the most important design decision for social sector portfolio support isn't which advisors to recruit or which curriculum to build. It's how to make the knowledge inside the portfolio flow to the people who need it, when they need it. The funder's job isn't to be the expert. It's to build a community that doesn't need to depend on the funder to function.

That's a different job than portfolio management in venture capital, and it needs a different skill set.

Three questions for funders building portfolio services

1. What activates support in your current model: relationship or obligation? If portfolio organizations engage mainly because reporting requires it, your support infrastructure is working against you. The goal is to make engagement useful enough that founders reach out before they have to.

2. Where does your network stop flowing? Most funders activate corporate, advisor, and funder relationships during the grant or cohort period. Map what's available to a portfolio organization two years after funding ends. If the answer is "not much," that's the gap worth closing first.

3. What does your portfolio already know that you haven't systematized? The founders you fund have navigated procurement processes, funding cliffs, board development, and product scaling decisions. That knowledge exists in your portfolio right now. A peer learning structure that makes it flow is often more valuable than any expert advisor you could bring in.

The VC model is a useful starting point. It proves that the infrastructure around capital matters as much as the capital itself. But the most effective social sector portfolio programs aren't VC programs with a mission overlay. They're built from the ground up for mission-driven founders, nonprofit business models, and communities held together by shared purpose rather than shared financial stakes.

That distinction is worth getting right.