Revenue operations for Series A companies: the 90-day install for PE-backed portfolio companies
The exact 90-day plan for standing up revenue operations at Series A — the point where the founder can no longer be every function. Written for operating partners and portfolio CEOs inside private equity.
This edition is written for operating partners and portfolio CEOs inside private equity. In PE-backed portfolio companies, PE-backed operators run on 90-day cycles and reward operating rigor over storytelling, so the way you install revenue operations has to reflect that reality from day one.
Series A is the moment revenue operations stops being optional. The founder has to step out of some of the work, the plan requires a defensible growth number, and every quarter compounds toward the next raise.
Day 1 to 30: diagnosis and instrumentation. Name the constraint, write the ICP, wire days-to-close and forecast accuracy into the board pack.
Day 31 to 60: first live cycle at 20% of planned volume. Founder still in every review. Kill criteria written and enforced.
The binding constraint we see in PE-backed portfolio companies is almost always predictable execution against a hold-period thesis. Revenue operations is only useful in this vertical when it is pointed at that constraint — not at a generic growth number borrowed from another category.
Day 61 to 90: ramp to full volume, hire the first dedicated operator, and hand off ops. Founder retains strategy and the weekly review.
By day 90 the metric is legible and the trajectory is defensible. This is what turns a Series A story into a Series B round.
Trap most Series A companies fall into: hiring RevOps to fix CRM instead of to own revenue. It usually shows up around day 45 when the founder tries to hire ahead of the model.
The Series A version of revenue operations looks small compared to what you will build at Series B. That is the point — it is a foundation, not a monument.
Concretely for PE-backed portfolio companies: the portfolio companies that install this hit the next value-creation milestone on schedule. That is the reason it is worth installing revenue operations properly rather than half-heartedly across three vendors.
Frequently asked questions
RevOps · PE-backed — answered
- Does revenue operations work for PE-backed portfolio companies?
- Yes — provided it is aimed at predictable execution against a hold-period thesis rather than a generic growth number. The portfolio companies that install this hit the next value-creation milestone on schedule.
- Should we start revenue operations before Series A?
- Yes if the founder has time; the Series A version is the same model at higher spend.
- How much of the round should fund revenue operations?
- Meaningful — often 20–30% of the growth line — but only after diagnosis.
- When do we hire the first revenue operations operator?
- Around day 60, once the model has run one full cycle with the founder.
- What Series A trap should we avoid?
- Hiring RevOps to fix CRM instead of to own revenue — usually a premature senior hire.
- What is the PE-backed specific pitfall with revenue operations?
- Running the generic playbook without adapting to PE-backed operators run on 90-day cycles and reward operating rigor over storytelling. The install has to be vertical-first.
Growth Broker editorial
Filed under revops · pe-backed