What changes when a VC platform function grows from one person to a team?

When a platform function grows past one person, the leader moves from doing the work to managing people, priorities and budget. Roles specialize across talent, community, marketing and data. Context has to move out of one person's head into a shared system, and the team needs clear owners and goals agreed with the GP.

This comes up on a lot of my calls, usually framed as a hiring problem. I don't think it is. The solo platform lead does everything. They run the newsletter, book the dinners, chase the metrics, answer the founder who needs a lawyer by Friday, and still sit in the Monday partner meeting. It works because all the context lives in one head.

Adding a second or third person breaks that. Context now has to move between people. Partners don't know who to ask. Founders get two emails about the same event. And the thing that made the first person great, knowing everything, turns into the bottleneck.

Move the context out of your head first

The solo lead's real asset is context: which founder is struggling to hire, which partner promised which intro, what the last board deck said. A new hire can't use any of it while it lives in your head, your inbox and your WhatsApp.

So before the second person starts, get that context into one shared place. Don't plan on logging every call by hand. People who log and forward things manually stop within a month (and I don't blame them). The context should flow in from where the work already happens: email, meeting notes, decks, the portfolio Slack. People add judgment on top, not data entry.

Honestly, the blocker here is behavioral, not technical. A shared context layer only works if everyone puts what they know into it, partners included. I see the same pattern at many firms: one person builds a clever personal AI setup, it never reaches the rest of the team, and it dies when that person leaves. Build a shared brain for the firm, not a private one.

Your job changes before your team does

The hardest shift is personal. As a solo lead, your output is your work. As a team lead, your output is your team's work.

A rough before and after:

The common trap is to hire someone and keep doing all your old work, plus managing them. I get why: it's the part you're good at. But decide in advance what you'll hand off completely. If you're still writing the newsletter six months after you hired someone to own it, you haven't let go.

Specialize the roles

Two generalists sharing everything means duplicated work and gaps, so split by function as soon as you have two.

The common specialties:

• Talent: executive search support, recruiting help, compensation data, the portfolio jobs board. See what portfolio companies need from VC talent teams.
• Community and events: dinners, roundtables, the portfolio Slack, peer groups. See how VC firms design events with lasting impact.
• Marketing and content: the firm's newsletter, website, social, partner content.
• Portfolio data and ops: metric collection, LP reporting inputs, the CRM, internal tooling.
• Go-to-market: buyer networks, customer intros, corporate partnerships.

Your first hire should cover the area that's most valuable to partners and weakest in your own skills. If you came from events and partners keep asking for talent help, hire talent.

Good data can cover a gap for a while. If you have a clear view of every open role in the portfolio and every candidate the firm has met, a team with no talent person can still answer most talent requests. Hire for the areas where judgment and relationships matter, not where the work is mostly lookup.

Write down who owns what

Once there are two people, ambiguity costs time. A RACI chart is the simplest fix I know. For each recurring piece of work, name who is Responsible (does it), Accountable (signs off), Consulted and Informed.

An example for a three-person team:

Each row has exactly one A. Share the chart with partners so they know who to ask, and revisit it when someone joins or leaves.

Build internal workflows

The solo lead's system is often a notebook and a good memory. A team needs a few shared habits:

1. One intake channel. All founder and partner requests go to one place, such as a shared inbox or a Slack channel. No more requests in DMs to whoever partners happen to remember.
2. A shared tracker. Every open request, intro and program lives in one board: request → owner → due date. Notion, Airtable or Linear all work.
3. A weekly 30-minute team meeting. Review open requests, upcoming programs and any founder who needs attention.
4. Context captured where the work happens. Emails, meeting notes and decks land in the company record without anyone logging them. People add a line only for judgment: what they promised, what worries them.
5. A monthly partner update. One page: what the team did, what's next, what you need.

These feel like overhead at first (they are, a little). They save time within a month, once nobody has to ask "did anyone reply to that founder?"

Pick shared tools and one source of truth

Each new person brings their own tools. Agree early on where the important things live: the founder and company record, the intro log, the event list and the portfolio data.

Buy the plumbing and build on top. I don't meet a lot of people who are happy about having built everything in-house a few months later, when they're maintaining it. The maintenance never goes away, and the tool goes stale. Whatever you pick, make sure you own the data and can move it.

Portfolio data is the one that hurts most when it's split. If the community lead has metrics in one spreadsheet and the head of platform has another for LP reporting, the numbers will drift. Cura fixes that. It sends metric requests from your own inbox, pre-fills what it has, and asks founders only to confirm or fill gaps. Every number links back to its source, and portfolio news and signal land in one feed the whole team reads from.

Agree on success metrics with partners

A team costs more than a person, so partners will ask what it delivers. Agree on the metrics up front, before the budget conversation.

This one baffles me, and I hear it on call after call: platform people who've never been given goals. "The role is evolving with me" is a common answer. That hurts the team's budget and your own promotion track. Ask the GP directly: what would this team have to deliver for you to call it a great year, and what would get each of us promoted?

Sample definitions:

• Value-add log: customer, investor and talent intros made this year, counted from the record, not from memory. This is the number that helps in LP diligence and in pro-rata fights.
• Intro conversion: share of founder-requested intros that lead to a meeting within 30 days.
• Hiring support: number of executive and senior hires where the talent lead sourced or closed the candidate.
• Data coverage: share of portfolio companies with current numbers by the reporting deadline.
• Response time: median time from a founder request to a first useful reply.

Pick three to five, set a baseline in the first quarter, and report them in the same format every time. For more on proving value, see how AI is changing the role of a VC platform team.

When should a VC firm hire a second platform person?

Hire when the first person spends most of their week on reactive requests and has dropped a program partners care about, or when one area such as talent or events needs depth they can't provide. Before hiring, check whether better data and automation would free up that time instead.

Some signals it's time:

• The platform lead has stopped proactive work, such as programs or founder check-ins, for a full quarter.
• Founder requests regularly wait more than a few days for a reply.
• The fund has raised a larger vehicle and the portfolio will grow by a third or more.
• Partners keep asking for a capability the current lead doesn't have.

If you see the first two signals but not the last two, try fixing the workload first. Better data, automated collection and a clear intake process can free up real time. I wrote about where that line falls in how to scale a VC platform without losing the human touch.

How should a platform team be structured?

Small teams usually organize by function, such as talent, community and events, marketing, and portfolio data. Larger teams sometimes add portfolio coverage, where each person is the main contact for a set of companies. Whatever the structure, every recurring task needs one named owner.

The two models compared:

Many teams end up with a hybrid: functional specialists, plus a named platform contact for each company who routes requests to the right specialist. Whatever you choose, write it down and tell founders who their contact is.