A portfolio company should hire a full-time head of RevOps when its fractional hours stop tapering, its forecast stops matching reality, and the next budget cycle lands after the round closes rather than during it. Funding stage sets the window, rep count and data trust set the trigger, and the fundraise calendar sets the timing.
I'll walk through how I size that decision for vc portfolio revops, because the usual answer ("hire at X reps") hides the mechanism.
Why fractional is the right default for vc portfolio revops
Fractional is usually 5, 10 or 15 hours a week. It runs heavier at the start while the system gets built, then tapers to about five and stays there. That shape is the whole point: you pay for a build once, then for maintenance at a fraction of a salary.
At seed and early Series A, that is the right deal. You are going from founder-led sales to two or three AEs, the process changes monthly, and a full-time hire would spend half the week with nothing to own. We cover the engagement model on our fractional RevOps page.
The signal that matters: hours that stop tapering
Rep count is the number everyone quotes, and it is a proxy. The better signal is the shape of the fractional hours. If you started at 15 a week, expected to land at 5, and you are still at 12 or 15 two quarters later, the system is growing faster than the maintenance budget.
As an example, a B2B software company adds a second sales segment. Now there are two lead routing paths, two sets of stage definitions and a new renewal motion. Each one is a design decision, and design decisions need someone in the room on Tuesday afternoon, not on Thursday's call.
I look at three other signals, and I rank them above headcount:
- Forecast variance: the number the CRO gives the board misses by more than the board tolerates, quarter after quarter.
- Data trust: reps keep side spreadsheets because they don't believe the CRM.
- Tool sprawl: a new tool arrives every quarter and nobody owns the integration map.
Buyers we talk to describe the same root cause. Account assignment and other processes live in people's heads, and manual updates by SDRs create errors. That is a system with no full-time owner.
Funding stage sets the window, not the rep count
My rule of thumb: the window opens after the Series A closes and shuts as Series B preparation starts. Before it, fractional covers you. After it, diligence tests your pipeline data, and someone has to be accountable for that data every day.
Rep count matters because each rep multiplies what can drift: territories, quotas, comp plans, handoffs. As a worked example (my own assumption, not a benchmark), with 3 reps one fractional operator can hold the whole system in their head. With 10, that operator is mostly doing triage. I don't have a clean number for the crossover, since it depends on how many motions you run, and I'd be inventing one if I gave it to you.
If a CRM switch is on the table too, read the Salesforce to HubSpot migration case study first. A migration is the one project that almost always justifies a fractional surge before the hire.
Mid-fundraise cost sensitivity and budget cycles
This is the part the standard advice skips. A company in the middle of a raise is cost sensitive, and rightly so. A customer told us exactly that: the year's budget was already allocated, the company was mid-fundraise, and marketing cost was the constraint, so anything new was exploratory at best.
So the timing mechanism for vc portfolio revops is this. Headcount gets approved at the budget cycle. If your cycle falls mid-raise, you won't win a full-time requisition, and you shouldn't spend political capital trying. Keep the fractional engagement lean, document everything, and write the job description while you wait. If the cycle falls after the close, the new money funds the hire.
The reason to plan this out loud with the board is so that later on nobody is surprised. A fundraise is also when bad data gets exposed, and hiring in a panic the month after a diligence finding is how you get the wrong person.
Who owns the vc portfolio revops call
The CEO owns the decision, with the operating partner or lead investor as the sounding board. The investor sets the trigger conditions, such as forecast variance and data trust. The CEO decides when they are met. Any other split means the person paying for the hire isn't the one feeling the pain.
On scope, a head of RevOps owns system design, the forecast process, territory and comp mechanics, tool decisions and the RevOps budget. A RevOps manager or analyst runs admin, reporting and enablement requests inside a design that already exists. My recommendation: if the design is still moving, hire the head first. If it has been stable for two quarters and the work is queue-driven, hire the manager.
If you are inheriting a broken portal, the HubSpot reimplementation post covers how to tell a rebuild from a cleanup before you set the new hire's first-year plan.
How to hand off from fractional to full-time
Keep the fractional lead through the first weeks of the hire. Undocumented logic is the most expensive thing in the company, and the person who built it can explain it in an afternoon.
- Before the search starts, have the fractional lead document every workflow, property, routing rule and report definition. We pride ourselves on documenting projects, as weird as it sounds, because this is where it pays off.
- Interview candidates on a real artifact: give them an anonymised pipeline report and ask what they would fix first.
- Overlap for four to six weeks, then drop the fractional hours to an advisory five.
- Set a 90-day plan: audit in the first 30 days, fix forecast inputs by day 60, and present a scorecard to the board by day 90.
For the scorecard, the 30, 60 and 90 day format in our AI GTM scorecard works for a first-quarter RevOps plan too.
What I'd do in your seat
Check the taper first. If hours are flat or rising, look at forecast variance and data trust. If two of those three are failing, start the search so the offer lands after the close, not during it. If you want a second opinion on vc portfolio revops, our VC portfolio support team runs this assessment, and the system you inherit is documented either way.
A clean setup also ramps a new hire faster. Platforms like HubSpot and Salesforce document their data models well, so the ramp depends on how tidy your own configuration is.
I'm not here to convince you to hire. For better or worse, sometimes five more hours a week of the right fractional operator is the cheapest answer, and good vc portfolio revops planning means knowing which side of that line you are on.