How do non-investment staff build influence at a VC firm?

Influence comes from credibility: sound judgment, clear communication and results the partners can see. Start by getting explicit goals from the GP so everyone agrees what success looks like. Then bring data and a recommendation rather than a problem, and choose your battles. A visible record of being right and easy to work with counts for more than a title.

This one's personal for me. I was a startup chief of staff, which is a job with a lot of responsibility and no formal authority. So I learned most of what follows the hard way.

If you work on the platform, talent, community or ops side of a fund, you don't get a vote on deals. That's fine. But almost everything you want to do still runs through the partners: the budget for the founder summit, a second hire, a new tool, whether anyone reads the portfolio survey results. Influence is how your work gets done without a vote.

I talk to platform leads about this constantly. The ones with real pull rarely got it from a title change. They got it by making the partners' lives easier in ways the partners actually noticed.

Get explicit goals from the GP first

I hear this on almost every call: nobody ever gave them KPIs. The role is "evolving," which sounds flexible right up until review season. Without agreed goals, you can't prove impact and you can't make a case for a promotion. Each partner grades your work against a different bar that nobody wrote down.

So ask for the goals directly. Book 30 minutes with the managing partner and walk out with two or three goals, each with a number and a date. Something like:

• 25 customer intros a quarter that turn into a first meeting
• Six portfolio hires closed with talent team help this year
• Every founder request answered within five business days

Then ask the question most people skip: "If I hit these, what does the next role look like?"

Goals help you pick projects, too. When a partner suggests a new program, ask which goal it serves. If the answer is none, you have a polite way to say not now.

Map what each partner cares about this quarter

Partners aren't one audience. One is mid-fundraise. Another has a board company that's missing plan. A third wants to win a competitive Series A next week. Your program matters to each of them only as far as it touches those things. A partner map takes 30 minutes. Refresh it every quarter.

Once you see the table, your pitch changes. You stop saying "community events are important." You start saying "this dinner puts three of the founders Partner C is chasing in a room with our best portfolio CEOs."

Bring a recommendation, not a problem

The fastest way to lose standing is to walk into the Monday partner meeting with an open-ended problem. Partners already carry too many open loops. Each one you add costs you a little.

So I use a short decision memo. Mine has four parts:

1. Situation. Two sentences on what's happening.
2. Options. Two or three, with the cost and trade-off of each.
3. Recommendation. The one you'd pick, and why.
4. Ask. The exact decision you need, and by when.

Here's what that looks like as a Slack message:

Founder dinner budget for Q4. We have room for two dinners at the current budget. Option 1: two dinners in SF, as last year. Option 2: one in SF and one in New York, where 9 of our 30 companies now have teams, for about 15% more. I recommend option 2. Can I get a yes or no by Friday so I can book venues?

A partner can answer that in 30 seconds. "We should talk about events strategy" turns into a meeting nobody wants.

Bring the data, too. If you claim New York matters, show the count of portfolio teams there. Numbers from your own records beat opinions, even good ones.

Choose your battles with a simple rubric

You'll disagree with partners, and sometimes you'll be right. You still can't fight every time. Before you push, score the issue from 1 to 3 on three questions:

• Impact. How much does this affect founders, LPs or fund outcomes?
• Reversibility. If the partners get it wrong, how hard is it to undo?
• Your edge. Do you know something they don't, such as founder feedback or your own data?

A total of 7 to 9 is worth a real argument, in writing, with data. A 4 to 6 gets one clear comment. Below 4, let it go and save the credit. Honestly, most of the arguments I see platform people lose scored a 4 and got fought like a 9.

Keep a value-add log, and show it

Credibility builds from a record of things you said you'd do and then did. But the partners have to actually see the record.

I call this a value-add log: a running count of the work. Intros made, hires closed, founder asks answered. Partners care about it more than you'd expect, because they use it. It's the proof they reach for in LP diligence, in a pro-rata fight and when they're up against a bigger brand for a deal.

A monthly note to the partnership is enough. Five or six bullets:

• Intros made this month, and how many led to a meeting
• Hires closed with talent team help
• Founder requests still open, with an owner on each
• One thing that worked and one that didn't
• What you need from the partners

Say your team made 40 customer intros last quarter and six turned into pilots. The partners will remember the six pilots long after they forget the event you ran. So track outcomes, not activity, and report them even when they're small.

Don't rebuild the log from memory at month end. Most intros happen in email, so count them from your sent folder or your CRM's email sync. People who log by hand forget (everyone does), and gaps undersell the team.

The best line in the note often isn't yours. Two sentences from a founder about an intro that worked carry more weight than any count you report. When a founder thanks you, ask if you can share it with the partners.

For more on which outcomes are worth tracking, see how portfolio support wins deals and the value-add gap.

Build relationships across the whole partnership

Most platform people have one sponsor partner. That's useful. It's also a risk. If all your influence runs through one person, it disappears when they're traveling, distracted or gone.

Set up a light cadence with every partner: a monthly 20-minute one-on-one in a large firm, a quarterly coffee in a small one. Ask what's on their mind, not what you can do for them. And don't skip the CFO, the EAs and the senior associates. They often decide what makes the partner meeting agenda.

Keep confidences, no exceptions. And give credit away. When a portfolio win came partly from a partner's intro, say so in the monthly note.

How does a VC chief of staff gain partner trust?

A chief of staff gains partner trust by being reliable on small things first: closing loops fast, keeping confidences and anticipating what a partner needs before they ask. Once partners see you protect their time and their reputation, they start handing you decisions instead of tasks.

Day to day, it looks like this:

• Close every loop within one business day, even if the answer is "I'm on it, back to you Thursday."
• Prepare before the partner asks. If a partner has a board meeting on Wednesday, the board pack, the last three founder updates and the open asks are in their inbox on Monday.
• Own the operating rhythm. The partner meeting agenda, the action list and the follow-ups are yours. When nothing falls through the cracks, partners notice.

Trust usually moves in a set order: logistics → information → judgment. Don't try to skip a step.

Do platform teams get a seat at the table?

Some do, and they earn it rather than receive it. Platform teams get a seat at the table when they bring information partners can't get elsewhere, such as portfolio health, founder sentiment or hiring data, in a format that fits the partner meeting. A short, useful standing update is usually what earns the invitation.

A good way in is a standing ten-minute slot in the weekly partner meeting. Use it for a portfolio pulse: which companies need help this week, which founder requests are stuck, and one thing partners should know before their next board meeting. And stay inside the ten minutes. Running over is the fastest way to lose the slot.

The best material is the signal partners miss. A founder ask buried on page 12 of a quarterly update. A company that posted three sales roles in a month. A hiring problem that's come up in three updates in a row. I see this all the time: founder asks die in email, and the partner who could help never sees them. When you route those asks, you bring something nobody else at the table has.

It also helps to agree on who owns what. A simple RACI chart for portfolio support clears up a lot of friction:

Once the partners sign off on a chart like this, you stop asking permission task by task. That's what a seat at the table looks like day to day. For where the team goes next, see growing a VC platform team.