Private equity · Portfolio RevOps
Built, staffed, and measured at the fund level — not left to twelve portcos to reinvent one at a time.
Finance got standardized a decade ago. Revenue never did.
01 · The premise
A CRM line item. Something the CRO complains about at the second board meeting.
That framing is why GTM is the least professionalized function in the average portfolio. Finance got standardized a decade ago — one chart of accounts, one close calendar, one reporting pack, one FP&A standard enforced from the fund. Revenue never got the same treatment. Twelve portcos run twelve different definitions of “qualified pipeline,” and nobody can roll them up.
The consequence is not cosmetic. It shows up in three places that matter.
You diligence financial quality of earnings rigorously and revenue system quality barely at all. GTM risk enters the model as an assumption, not a finding.
Every portco rebuilds the same infrastructure from zero. No pattern library, no comparables, no leverage. Twelve companies paying twelve times for the same fix.
Messy ARR, unreconcilable cohorts, and attribution nobody trusts get discovered in the data room. That is the most expensive possible place to find them.
RevOps at the fund level is the correction: revenue treated as an engineered system, standardized where standardization compounds, and left alone where it doesn’t.
02 · Structure
The most common structural mistake is collapsing these. They are different jobs with different owners.
The fund layer defines what gets measured and how good looks. The portco layer owns hitting it. When the fund layer starts owning portco outcomes directly, it loses its leverage and becomes an unfunded consulting arm. When it owns nothing, it becomes a slide deck.
03 · Mandate
If it owns more than these, it’s over-scoped. Fewer, and it’s decorative.
A minimum viable data model every portco conforms to — regardless of what CRM they run. Not a forced migration to one platform. A conformance layer: agreed objects, agreed stage definitions, agreed calculation logic, agreed reporting cadence. Standardize the semantics, allow variance in the tooling unless there’s a real consolidation case.
One diagnostic instrument, run identically across every portco, producing scores that are actually comparable. This is what turns “who’s shouting loudest” into “where does capital and attention go.” Rerun it on a fixed cadence — semiannual is usually right — so you get trend, not snapshot.
Every fix that works at one portco gets documented with the run count and the outcome, then deployed at the next. This is the compounding asset and the reason a fund-level function beats twelve independent efforts. A play without a run count and a result is a theory, not a play.
Pre-LOI and pre-IC: a revenue-system read alongside the QoE. What’s the actual pipeline quality, is the reported conversion data defensible, how much of the growth is system-driven versus a few heroic reps, and what does it cost to fix. This is where fund-level RevOps pays for itself most directly and most invisibly.
Starting 18–24 months out, not 6 weeks out. Clean ARR schedules, reconciled cohort data, defensible funnel metrics, documented systems, and a narrative the buyer’s diligence team can verify rather than dispute.
Each portco reaching the same definitions on its own: 6 months of a $180K RevOps hire ($90K of loaded time) plus $60K of contractor build.
Running portco campaigns, administering portco CRMs day-to-day, or hiring portco reps.
The moment it does, it stops scaling.
04 · Org design
Pick based on portfolio size, check size, and how operationally involved the firm actually is — not on aspiration.
One senior operator at the fund. Sets the standard, runs the scorecard, advises portco leadership, brings in execution partners for the build. Works for portfolios under ~10 companies or firms with a light-touch model.
Breaks when portcos nod at the advice and nothing gets built. Advisory with no execution arm is the single most common failure mode in this function.
Small fund-level team with real hands. Owns the standard and does the first build at each portco, then hands off to the in-company team. Higher fixed cost, dramatically better landing rate.
Breaks when the team gets absorbed into whichever portco is loudest and stops serving the portfolio.
Internal operator owns the standard, the relationship, and the roadmap. Execution capacity is bought — scalable up at post-close and down mid-hold, no permanent headcount, no single-point-of-failure operator risk. Most common shape at mid-market firms in practice, and usually the best cost-to-outcome ratio.
Breaks when the internal owner is too junior to hold the standard against a portco CRO who pushes back.
Each portco has its own RevOps leader; the fund provides the standard, the benchmark, and a community of practice. Right for large portfolios of scaled companies.
Breaks when there’s no enforcement mechanism and the standard quietly decays into twelve dialects.
05 · The standard
This is the deliverable that makes the function real. Everything else is commentary.
Comp is the only mechanism that changes rep behavior at scale, it’s usually designed once and left to rot, and it’s almost always misaligned with the current thesis — plans that pay for logo count during a year the thesis is net revenue retention, or that pay full rate on a segment with negative contribution margin. A portfolio RevOps function that can model and redesign comp against the investment thesis is worth more than one that can only build dashboards.
06 · Working thresholds
Directional operating ranges for B2B SaaS portcos, not academic benchmarks. The value is in the shape of the scale.
If the two numbers don’t match, you’ve found the work.
If nobody knows, that answer is the finding. Best-in-class is under 5 minutes; most portcos measure theirs in hours.
07 · Sequencing
The first 90 days post-close matter more than the next 900.
Alongside the QoE. Is the growth system-driven or hero-driven? Are the conversion metrics defensible? What’s the cost and timeline to bring the revenue system to standard? This becomes a line in the value creation plan instead of a surprise in month four.
Not transform. Definitions locked, reporting pack live, forecast process installed, the two or three worst leaks fixed, comp plan reviewed against the thesis. Target: by day 100 the board sees numbers everyone agrees on. That single outcome buys credibility for everything after it.
Systems rebuilt where the diagnostic scored worst. Plays from the library deployed in priority order. Demand engine built on top of infrastructure that can actually capture, route, and attribute. This is where the multiple actually gets made.
Reconciled cohorts, clean ARR schedules, documented systems, defensible funnel data. Everything a buyer’s team will interrogate, prepared before they ask. Diligence-readiness built in advance is cheap; built under deal pressure it is expensive and it leaks into price.
A portco that leaves the stabilization window with contested numbers spends the entire hold period arguing about the number instead of moving it.
08 · The hire
The profile is unusual, which is why the role is so often miscast — either a CRM administrator with no strategic seat, or a strategist who has never built anything.
They can architect the CRM, write the logic, build the model. Not “manage a vendor who does.” Credibility with a portco CRO is earned by demonstrating the fix, and the gap between recommending and building is where most portfolio ops initiatives die.
They sit with a CEO on strategy in the morning and debug an integration in the afternoon, and they’re respected in both rooms. The role has no direct authority over portco teams. Influence is the entire delivery mechanism.
Comfortable in the data at a level most GTM leaders are not: cohort analysis, attribution modeling, unit economics by segment, quota and capacity modeling. Not “data-informed.” Can build the model themselves.
In 2026 this is a competence question, not a differentiator. The operator who has automated their own analysis, research, and reporting workflows produces multiples of the output of one who hasn’t. Curiosity is table stakes; a working practice is the bar.
Territory design, quota setting, capacity models, headcount plans, role definitions. Structural work, not process documentation.
Can model, redesign, and defend a sales compensation plan against the investment thesis. Rare, and disproportionately valuable.
Presents to boards and holds a position under pressure from a CRO who doesn’t want to be measured. This is where the seniority requirement is real. A junior operator can build the standard but cannot enforce it.
The part firms underweight. The best candidates don’t want to wait for someone else’s exit to build something. They want ownership, compounding leverage, and visible impact. The firms that lose them offer a reporting job with a five-year vest and no upside.
Base plus an annual bonus tied to portfolio-wide maturity movement and exit outcomes, plus carry or co-invest participation. A portfolio ops role with no equity participation attracts people optimizing for stability, which is the opposite of the disposition the job requires. Benchmark against your operating partner comp band, not a VP RevOps market rate — the market rate will undershoot the profile you need.
09 · Failure modes
Five of them are structural.
The most common by far. Excellent recommendations, nothing built. Portcos agree in the meeting and revert the following week.
No mechanism, no consequence, no reporting requirement. The standard becomes optional, and optional means twelve dialects within a year.
The function generates work for portcos and returns nothing to them. Portcos comply grudgingly, then stop.
Forcing every portco onto one platform on a fund-level timeline. Sometimes correct, usually a distraction that burns the relationship. Standardize definitions first.
The role is 60% influence. An operator without executive presence gets rolled by the first portco CRO who resists measurement.
Diligence readiness begun six weeks before the data room is a discount, not a project.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
