A value creation plan names three or four commercial priorities. The operating review is where those priorities either move or become a slide. Most portfolio companies confuse the two.
The design work is already on the site: operating partner revenue work that holds is motions, owners, and the few objects a board is allowed to ask for. This piece is the next layer. How the monthly room actually runs once those objects exist.
Jennifer Mellet sits in that room as an independent director, operating partner, and growth advisor. The failure she sees is not missing dashboards. It is a packet that changes every cycle, a blended growth line nobody can unpick, and no written consequence between meetings.
The review has one job
Are we on the plan we underwrote? If not, why? What changes before the next meeting?
Status is not the job. Status is the first ten minutes. The rest of the hour is variance, owners, and the decision the packet was built to force.
That matters more in 2026 than it did when multiple expansion did more of the work. Oliver Wyman’s August look at private equity value creation found revenue growth accounted for 71% of value created, up from 43% in 2019, while multiple expansion fell from 47% to 17% in 2023 and 2024. Trajectories get set in the first twelve to eighteen months. Exits inside four years created value at a much faster annualized rate than holds past eight. The operating review is how you find out, monthly, whether the two or three commercial levers you actually funded are moving.
If the packet cannot answer those three questions in an hour, you do not have a review. You have a narrative contest.
Three altitudes, not one dashboard
The same number should not serve the board, the operating partner, and the management team. Flatten it and the board debugs conversion rates while the CEO defends a slide.
The board sees five to seven outcome metrics that test the thesis: revenue versus the underwritten plan, EBITDA, net revenue retention, pipeline that uses one written definition of an opportunity, and one or two thesis-specific objects. The board should not be in the funnel.
The operating partner sits one layer down: the revenue bridge, stage velocity, concentration, margin by segment, and whether last month’s actions closed. This is the altitude that asks the question before the quarterly.
Management owns the full operational set. Funnel by channel, rep productivity, cohorts, support load. Those numbers feed the layers above. They do not belong in the board pack unless something is broken and the board is being asked to change a rule.
Write the altitudes down. When a director asks about email open rates, the packet failed upstream.
Actuals versus the plan you funded
Every review starts with actuals versus the plan that was underwritten at close, or the annual plan the board approved. Not last year. Not the “revised forecast” that quietly lowered the bar in week six.
If the plan was wrong, say so and reforecast with board approval. Do not let a softer comparison replace the original without naming it. Drift hides in the substitute baseline.
That is the same break as why GTM attribution breaks before anyone picks a model: two teams, two truths, a request for a prettier chart. Freeze the definition. Then argue about the gap.
A revenue bridge, not a blended growth line
A single revenue number cannot diagnose. Split opening booked revenue, new logo, expansion, contraction, churn, and close. Transactional books use bookings or recognized revenue the same way: separate what grew from what eroded.
A company can hit the top line while existing customers leave. The blend looks like momentum. The hold period later prices the leak. The bridge is how the operating partner sees that in month four instead of at the banker meeting.
Put a simplified bridge in the board pack. Keep the definition fight out of the quarterly. Finance and sales have to agree on the objects before the meeting, not during it.
Pipeline health beyond coverage
A 3x coverage ratio is not a health metric. Aged deals, one-account concentration, and early-stage inventory with no recent activity all still count as coverage on a lazy slide.
The review should show coverage by segment, stage mix, age in stage, velocity, and concentration. Flag deals that have sat through more than one full cycle. Flag any segment that dropped below the coverage rule you wrote at close. Show creation trend, because a quiet top of funnel this quarter is a miss two quarters out.
If forty percent of “healthy pipeline” is one deal, the coverage number is fiction. Write that in the packet. Do not wait for the board to find it.
Retention the blend cannot hide
Net revenue retention is a board metric. The operating review needs the split underneath it: logo retention, gross revenue retention, and net. Each answers a different question. Customers leaving. Remaining customers spending less. Expansion covering the leak.
Cohorts make the investigation possible. If last year’s book holds and this year’s does not, the problem is not “retention.” It is fit, onboarding, or a motion that closed worse accounts to make a new-logo slide. Segment the same way. A healthy enterprise book sitting on a deteriorating SMB book is two theses, not one NRR.
Vx Group’s August value creation note put relationship ownership next to cost work for the same reason. A plan that hits margin while the ten accounts that fund the thesis quietly change champions is not value creation. Put named relationship owners in the packet when concentration is real. Do not treat a twenty-year account like a subscription that renews itself.
Do not copy anyone else’s retention figure into your board deck as a target. Use the company’s own cohorts. Jennifer’s operating history is proof she has sat in those chairs. It is not a template for your hold period.
The action log is the review
Every operating review should leave a short log: action, owner, due date, status. Discrete work that can finish in two to four weeks. Not a program plan. Not a parking lot.
Open the next meeting on that log. What was due. What closed. What slipped. If the same item returns three times, it is not an action. It is an owner or a rule that still is not written.
This is cadence with consequences, the same standard as the commercial design post. A missed coverage number produces a territory or capacity decision. A forecast miss two months running produces a definition or process change. The log is how those decisions survive the meeting.
Put the rhythm on the calendar at close
In August 2026, Vx Group’s value creation plan guidance put the review dates on the calendar when the plan is written, not when someone remembers to ask. Three or four named priorities. One owner each. Milestones at 30, 90, 180, and 360 days. Monthly with the operating partner. Quarterly with the board.
That is the right shape. The 30-day check is a named owner and a written plan per priority. The 90-day check is a concrete deliverable. The 180-day check is an early result tied to the thesis. The 360-day check is the number the deal actually depends on, or an honest account of why it did not land.
A plan that only appears in the quarterly will be performed for the quarterly. A plan that is discussed every week and never changes an owner is extra staff. The useful operating partner can change the design, then leave the monthly running without them in every chair.
What diligence should already have given you
The first operating review is only as good as the baseline you inherited. Robust Branding’s August note on RevOps diligence in private equity is the right test: build the revenue number from systems of record, not the seller’s summary deck. Split new logo, expansion, and renewal. Rank the gap between actual and plan as supported, partly supported, or unsupported. Sort fixes into what can move in a quarter and what is multi-quarter structure.
If diligence never produced that baseline, the first hundred days are not a growth sprint. They are a rebuild of the objects the review will use. Do not fund a 30 percent net-new case in the monthly until someone can reproduce the starting number from exports that also reconcile to finance.
Quick wins in that window are definition, pipeline hygiene, and a weekly view that matches the board objects. Structural work is the stack, the demand engine, or a motion that was never repeatable. Mixing those in one “transformation” slide is how the first year disappears.
When the packet is lying
Commercial design without an operator on the plumbing becomes another PDF. Routing, lifecycle stages, campaign names, and the living view of the work have to match the map. That is Jason Mellet’s seat.
If the monthly still starts by reconciling three files, you do not have an operating review. You have copy-sync. Replace the file ritual with a living GTM operations system that the meeting can decide against. Keep the rules in a RevOps playbook the team can actually run.
Pair the seats when the board can describe the motion and the CRM still cannot. Strategy and systems are one company. They are two people because the work is different.
What to freeze this quarter
Keep the board pack short enough to read in half an hour. Executive summary with the three things the room must know. Actuals versus plan. The revenue bridge. Pipeline health, not only coverage. Retention that splits logo, gross, and net. One or two thesis KPIs. Integration status if you are in one. The decisions you need.
Keep funnel debugging, deal-by-deal theater, and channel trivia in the operating room. If directors keep asking for more pages, the summary layer is unclear. More pages will not fix that.
All Great Things does not sell a diagnostic and then a menu of sprints. Seats and retainers. Stay in the work until the packet is boring and the next action is named.
What belongs in a portfolio company operating review?
Actuals versus the underwritten plan, a revenue bridge, pipeline health beyond coverage, retention split into logo, gross, and net, and an action log with owners and dates. Status without those objects is a story.
How is the board pack different from the monthly operating review?
The board pack is five to seven outcome metrics and the decisions required. The monthly is the operating partner and management working the layer underneath. Do not send the funnel to the quarterly and call it transparency.
When should the operating partner pair with an embedded RevOps seat?
When the packet is designed and the systems still disagree, or when the systems are clean and the packet still changes every meeting. That is how Jennifer and Jason work together. It is not a product bundle. It is two seats on one problem.
If you want board-level commercial cadence, start with Jennifer. If the engine underneath that cadence has to run every week, start with Jason. If you need both, say so.
