Working parents in venture make it work with systems, not willpower. They choose trips by expected outcome, batch travel, protect a few fixed family blocks and push admin off their evenings. They make their impact visible so career growth doesn't depend on being in every room. Firms help with written goals and clear norms.
I'm not going to pretend I'm an expert on parenting. But this topic comes up on my calls with platform people more than you'd guess, usually near the end, once the official agenda is done. Someone mentions the third dinner this month, or a conference that lands on a school holiday, and the conversation turns honest fast.
What I've noticed is that the platform people who make it work don't describe grit. They describe systems: how they pick trips, how they run events, how they keep admin out of their evenings, and how they make sure their work gets seen. So that's what this post is about. Take what's useful and skip the rest, because every family's setup is different.
Why platform roles are hard on parents
Platform work has a particular shape. A lot of it happens after hours: founder dinners, portfolio events, LP gatherings and conferences in other cities. Much of it is reactive, since a founder in trouble doesn't wait for office hours. And many platform roles have no defined scope, so the job keeps expanding to fill whatever time exists.
Then there's visibility. A partner sees the person who was at the dinner. They don't see the intro that person drafted at 6am, or the event playbook that let someone else run the dinner. If your career growth depends on being in the room, every missed evening feels like a cost.
None of that changes overnight. But each piece has a fix.
Choose trips by expected outcome
In-person time still matters in venture. Meetings in the same room build trust faster, and a lot of deals and partnerships still start that way. So the goal isn't to stop traveling. It's to make each trip earn its place.
Before booking, run three questions:
- What's the outcome? Name the meetings, intros or decisions the trip should produce. "Good to be there" isn't an outcome.
- Does it have to be me? Could a partner, a colleague or a local co-host cover it?
- Can it stack? Can one trip cover a conference, two portfolio visits and an LP coffee?
Here's how a quarter might sort out (illustrative):
| Trip | Expected outcome | Someone else? | Decision |
|---|---|---|---|
| Industry conference | 12 booked buyer meetings for 4 companies | No, I own the buyers | Go, two nights |
| Portfolio offsite | Facilitate one session | Partner already going | Join by video |
| Community meetup, other city | General networking | Local co-host | Skip |
| Founder dinner series | 3 matched intros per dinner | Rotate hosts | Host one of three |
Platform people tell me the biggest change is planning travel a full quarter ahead. Once trips are on the family calendar early, the household can plan around them instead of scrambling.
Design your events around your life
Not every event has to be a dinner. Breakfasts and lunches often work just as well for small, matched groups, and they finish before pickup. Co-hosting with a portfolio company, another fund or a vendor partner splits the hosting load. And a written playbook means you don't have to personally run every event. I covered this in designing VC events as a repeatable system.
A simple rule some teams use: each person hosts a set number of evening events per quarter, and the rest rotate. That makes evening duty a shared job instead of a default that falls on whoever said yes first.
Keep admin out of your evenings
Here's a pattern I hear a lot. The day is full of founder calls and meetings, so the admin (notes, CRM updates, follow-up emails, chasing data) gets pushed to 9pm, after the kids are asleep. It's the quiet tax on every parent in the job.
Most of that admin shouldn't need a person at all. Meeting notes can land in the CRM automatically. Data requests and follow-ups can run on their own. Intros can be drafted for you and sent with one click. A three-minute voice memo on the drive home can replace a written recap. Every hour you take back from admin is an hour you can spend with your family or with founders. The post on extending platform capacity without new headcount covers who else can take work off your plate.
Make your impact visible
If growth depends on presence, parents lose. If it depends on outcomes, the playing field gets a lot more even. So make the outcomes easy to see.
Keep a running record of your work and what came of it: intros made and what they turned into, hires closed, events and the deals or pilots that followed. Share a short summary with your partner every month. For example:
July: 14 customer intros (5 became meetings, 1 pilot so far), closed the VP Engineering search for one company, ran two founder breakfasts. Next month: the fintech buyer series and the Q3 metrics round.
That message takes five minutes and does more for your career than another evening at an event. It also sets you up to ask for explicit goals and a promotion path, which what platform teams should measure can help you frame.
Set your boundaries in writing
Unspoken boundaries get crossed by accident. Written ones mostly get respected. A short note to your team works well:
A heads-up on how I work: I'm offline most weekdays from 5:30 to 8. If something is urgent for a founder, text me and I'll pick it up. Otherwise I'll reply that evening or first thing the next morning.
Pair it with a backup. Name who covers a founder emergency if you can't, and make sure they have the context. Which brings up the firm's side of this.
How can VC platform teams make travel-heavy roles work for parents?
Plan travel a quarter ahead, choose each trip by its expected outcome, and batch meetings so one trip does the work of three. Share event duty across the team, use co-hosts for some events, and agree with your manager on a set number of overnight trips per quarter.
A trip budget measured in nights, not dollars, helps a lot. Agree on a number with your manager, then spend it on the trips with the clearest outcomes. When a new trip comes up mid-quarter, the question becomes "which trip does this replace?" That's a much easier conversation than an open-ended yes or no.
Also prepare the people who'll cover for you. A trip is easier on everyone when the platform work doesn't stall while you're away.
What can firms do to keep working parents on the platform team?
Judge people on outcomes, not hours or visibility. Give platform roles written goals and a promotion path, publish travel and after-hours norms, share event duty across the team, and keep context in shared systems so nobody is a single point of failure when a kid gets sick.
That last point matters more than it sounds. When founder context lives in one person's inbox and WhatsApp, that person can never really be offline. When it lives in a shared system, a colleague can pick up a founder request on a sick day without a handoff call. That's good for parents, and it's good for the firm, because the firm keeps its knowledge when anyone is out.
Platform people tell me the firms that keep parents aren't always the ones with the most generous policies. They're the ones where partners judge the work, not the calendar.