The first time you review a board deck with a management team before it goes to the wider board, there’s information available that has nothing to do with the slides themselves, and most of it shows up in how specific questions get answered rather than in what the deck actually says. 

Watch what happens when you ask about a number that’s slightly off-trend, not dramatically wrong, just a bit softer or a bit stronger than the surrounding pattern would predict. 

A management team that’s genuinely on top of the business will usually have an immediate, specific explanation, even if the explanation is “we’re not entirely sure yet, we’re looking into it.” 

A management team that’s less in control of the underlying detail will often reach for a broader, vaguer explanation that technically covers the anomaly without actually addressing it, something like attributing it to “seasonality” or “timing” without being able to say specifically what timing or what seasonal factor. 

Watch also for who in the room actually owns the answer. 

In a healthy management team, different people confidently own different parts of the deck, and questions get routed naturally to whoever actually knows the detail. In a less healthy one, everything routes back through the CEO or CFO regardless of the topic, which often means either the rest of the team isn’t genuinely empowered with the detail, or there’s a broader information bottleneck that hasn’t been visible from outside yet. 

None of this replaces the actual analytical review of the numbers. But it’s a genuinely useful second layer, and it’s available in every single deck review if you’re watching for it rather than just listening for the content of the answers. 

A new CEO in the first 30 days of a hold is dealing with more uncertainty than at almost any other point in the relationship, and what they need from an operating partner in that window is quite different from what they’ll need six months in, even though it’s tempting to treat the relationship the same way from day one. 

What they don’t need, in the first 30 days, is a comprehensive strategic review or a long list of areas for improvement. They’re still learning the building. A detailed critique delivered before they’ve had time to form their own view of the business reads as a vote of no confidence, whether or not that’s the intent, and it tends to put the relationship on a defensive footing that’s hard to walk back later. 

What they do need is genuine availability without an agenda attached. A CEO in the first month is going to hit small, specific problems, a stuck vendor negotiation, an unclear reporting line, a board question they’re not sure how to frame, and what they need most is someone they can raise those with quickly, without it turning into a bigger conversation about performance. 

Being useful on the small, unglamorous things in month one is what earns the credibility to be useful on the bigger things in month six. 

The other thing worth doing early, and it’s easy to skip because it feels less urgent than everything else: ask the new CEO directly what kind of support would actually be useful to them, rather than assuming based on what’s worked with previous portfolio companies. 

CEOs vary enormously in how much operational detail they want an operating partner involved in, and guessing wrong in either direction, too hands-off or too hands-on, costs you trust that’s expensive to rebuild later.

There’s a particular kind of dread that sets in around month five or six of a hold, when it becomes clear the CFO isn’t going to be the right person to take the business through the next phase. 

Everyone on the board has half-noticed it for weeks. Nobody’s said it out loud, because saying it out loud means dealing with it, and dealing with it feels like it’ll cost more time than it’s worth mid-plan. 

Here’s what actually costs time: waiting. The longer a CFO who isn’t going to work out stays in the seat, the more decisions get made on incomplete or slightly wrong numbers, and the more those decisions compound. 

I’ve seen boards delay a CFO change for two quarters to “avoid disruption” and end up with a much bigger disruption anyway, just delayed and disguised as a series of smaller reporting problems that all trace back to the same root cause.

The part that actually determines whether this goes smoothly isn’t the firing itself, it’s the sequencing before it. Have the interim plan sorted before the conversation happens, not after. 

Know who’s covering the immediate reporting cycle, know what the board needs to hear in the next update regardless of who’s in the CFO seat, and know roughly what the search timeline looks like. 

A CFO exit handled with a plan already in motion reads to the rest of the organisation as decisive. The same exit handled reactively reads as chaos, even if the underlying decision was exactly right. 

The other thing worth doing, and it’s the bit people skip because it’s uncomfortable, is being honest with the CEO about why this is happening before it happens, not after. 

CEOs who get blindsided by a CFO departure they should have seen coming lose confidence in the board’s judgement generally, not just on this one decision. CEOs who were part of the conversation early tend to come out of it more aligned with the operating partner, not less. 

Ask most operating partners why a management team is being difficult and you’ll get some version of “they don’t like being told what to do” or “founder ego.” Sometimes true. Usually not the actual reason, and treating it as the reason tends to make things worse rather than better. 

The more common reason, in my experience, is much less flattering to the operating partner and much more fixable. Management teams resist because the last operating partner who showed up didn’t actually help. 

They arrived with a framework, ran a workshop, produced a deck full of recommendations that sounded right in the room, and then left the actual implementation to a team that was already stretched thin running the business. 

Six months later the deck’s in a drawer and the management team has quietly recalibrated their expectations of what “operating partner support” means. By the time you show up, you’re not the first one through the door. You’re the third or fourth, and the previous ones set the bar low. 

This is worth checking directly rather than assuming either explanation. In your first few conversations with the management team, ask what support from the fund has actually looked like before you arrived. 

Not what the fund’s marketing deck says operating partner support looks like. What it actually was. You’ll usually get a fairly candid answer, because most management teams are relieved someone finally asked instead of assuming. 

If the answer confirms the pattern, the fix isn’t a better framework or a sharper pitch about your own credentials. It’s picking one specific, visible thing you can actually deliver in the first six weeks, doing it properly, and letting that do the work of rebuilding trust that a good first impression won’t do on its own. 

Management teams that have been burned by operating partners before don’t need to hear that you’re different. They need to see one piece of evidence before they’ll believe it, and it’s usually a smaller, more concrete piece of evidence than you’d expect. 

Fix one broken reporting process. Get one stuck hire unstuck. Resolve one vendor negotiation that’s been dragging for months. The size of the win matters less than whether it actually lands. 

There’s a meaningful difference in how top-quartile portfolio companies actually use the data they have, compared to how most portfolio companies use data, and it’s less about the sophistication of the tooling and more about a specific habit around how decisions actually get made in the room. 

Most portfolio companies produce data the same way, a monthly or quarterly reporting pack, reviewed in a meeting, generally confirming or mildly adjusting a view that was already roughly formed before the data arrived. 

The data functions primarily as validation of an existing narrative rather than as an input that can genuinely change the narrative. This isn’t unique to weaker performers, it’s just the default mode most organisations fall into, because forming a view and then seeking confirmation is cognitively easier than genuinely updating a view based on new information. 

The habit that distinguishes top-quartile companies is a specific discipline around actively looking for data that contradicts the current view, rather than data that confirms it, and building this into the reporting rhythm explicitly rather than leaving it to individual initiative. 

Practically, this often looks like a standing agenda item in management or board meetings specifically dedicated to “what in this data surprised us or contradicts what we expected,” rather than simply walking through the metrics in the order they appear on the dashboard. 

This small structural change shifts the function of data from confirming decisions already made to genuinely informing decisions that haven’t been made yet. 

The other consistent habit is speed between a data signal appearing and a decision being made in response to it. 

Top-quartile companies tend to have shorter gaps between “we noticed this in the data” and “we changed something because of it,” not because their data is faster to produce, but because the organisational habit of actually acting on data, rather than discussing it and moving on, is stronger. 

Building that specific habit, actively looking for disconfirming signals and acting quickly once found, matters more than any dashboard upgrade in getting a portfolio company closer to how top-quartile companies actually operate. 

Walking into a first board meeting on a new portfolio company, it’s tempting to ask for everything, the full metrics suite, every dashboard the business has. In practice, three specific numbers, asked for directly and pursued until you get a genuinely clear answer, tell you more than a full dashboard dump usually does, because a full dashboard dump invites a passive scan rather than the kind of direct scrutiny that actually surfaces something useful. 

The first is cohort-level retention, not blended NRR. As covered elsewhere, blended averages hide deterioration that cohort data reveals, and asking for this specifically, in the first meeting, signals immediately that you’re going to look past the headline numbers, which tends to raise the quality of everything else you’re shown afterward. 

The second is the split between new logo and expansion revenue over the last several quarters, and how that split has trended. This tells you, faster than almost anything else, whether growth is becoming more or less dependent on constant new customer acquisition, which is itself a proxy for how sustainable the current growth rate actually is. 

The third is a specific, named answer to who owns each major initiative currently in flight, not which team or function, which specific person. As covered in the piece on value creation plans dying quietly, initiatives without a genuinely named, accountable owner tend to lose momentum invisibly, and asking this question directly in the first meeting establishes early that vague ownership won’t be accepted as an answer going forward. 

None of these three requires exotic data infrastructure. All three require asking specifically, rather than accepting whatever’s already in the standard board pack, and asking for them clearly in the first meeting sets an expectation for the rigour of every meeting that follows. 

I want to talk about a specific way benchmarking quietly misleads people, because it’s one of those things that looks completely reasonable in the boardroom and falls apart the moment you actually dig into where the comparison data came from. 

Here’s the pattern. Someone pulls a benchmark deck. Your NRR is at 105%, median for your sector is 112%, so the obvious conclusion is you’re underperforming and need a retention initiative. Sounds sensible. Gets nodded through. Retention project gets greenlit. Six months and a fair amount of budget later, NRR hasn’t moved much, and nobody’s quite sure why. 

The problem usually isn’t the retention work. It’s the benchmark itself. 

Median figures in most benchmarking datasets are built from whoever happened to submit data, or whoever the data provider could scrape pricing pages and public filings from. That’s a very different population from “companies structurally similar to yours.” 

A company with a genuinely different customer concentration, contract length, or price point can post a very different NRR number for reasons that have nothing to do with how well they retain customers and everything to do with how their book is built. Comparing yourself to that median isn’t benchmarking. It’s noise dressed up as insight. 

The tell is usually in the confidence of the number rather than the number itself. If someone hands you a single median figure with no distribution, no segment breakdown, and no visibility into company size or contract structure behind it, that number is decoration, not evidence. 

Good benchmarking data comes with a shape, not a point. You want to know what the spread looks like for companies genuinely similar to yours on size, motion, and contract structure, not the entire category lumped together. 

There’s a second version of this trap that’s even more common and slightly more dangerous, because it survives scrutiny better. It’s when the benchmark is genuinely well-constructed, genuinely apples to apples, and the target you’re being measured against is still wrong for you. 

Median is a description of the middle of a distribution. It is not automatically the right ambition for your specific business. A company two years post-carve-out with a legacy pricing structure has no business chasing the same NRR target as a company three years into a land-and-expand motion with modern packaging. Both might be “at benchmark” for their sector and be in completely different positions of health. 

What I’d actually do with a benchmark number before it drives a board decision: ask who’s in the comparison set, ask what the distribution looks like rather than just the median, and ask whether the target implied by that median makes sense given your specific contract structure, pricing model, and customer concentration. 

If the answer to any of those is “we’re not sure,” treat the benchmark as a conversation starter, not a target. 

This is exactly the kind of thing worth stress-testing properly rather than eyeballing off a slide, which is a big part of why we built the benchmarking work the way we did inside this community. 

A number without its context isn’t a benchmark. It’s just a number that sounds like one. 

CAC payback gets treated as a single, self-contained metric, a clean readout of sales and marketing efficiency, and boards spend a lot of energy trying to improve it by attacking the acquisition cost side directly, tightening ad spend, improving conversion, optimising the funnel. Often the actual lever that matters most isn’t on the CAC side of the ratio at all. 

CAC payback is a function of two things: acquisition cost and the revenue rate that pays it back, and in most businesses, contract structure has a bigger effect on payback than acquisition efficiency does. 

A shift from monthly to annual billing, a change in average contract value, or a shift in the mix of deal sizes being closed can move payback period substantially without acquisition cost changing at all. 

When payback deteriorates, the instinctive response is almost always to scrutinise the sales and marketing spend, and that’s often the wrong place to look first. 

The more useful diagnostic question, before touching acquisition spend at all, is whether the deteriorating payback period is actually a CAC problem or a contract-mix problem. 

If average contract value has been quietly drifting down, or billing terms have shifted toward more monthly and less annual, that’s a pricing and packaging conversation, not a sales efficiency conversation, and treating it as the latter means optimising the wrong side of the equation while the actual driver keeps moving in the wrong direction. 

The practical habit worth building: whenever CAC payback moves meaningfully in either direction, check contract mix and average deal size before concluding anything about acquisition efficiency. 

More often than the standard board narrative suggests, the payback story is really a packaging and pricing story wearing a sales efficiency costume.

Most portfolio companies only build a genuinely clean, well-organised data room when a sale process is imminent, which means the work happens under significant time pressure, often revealing gaps that would have been far easier to fix eighteen months earlier when there was no deadline attached. 

The specific problem with building a data room reactively is that a lot of what a good data room needs isn’t a document that already exists somewhere and just needs collecting, it’s a clean version of an analysis that’s currently scattered across several spreadsheets, several people’s heads, and several slightly inconsistent versions of the same metric that were each built for a different specific purpose at a different point in time. 

Reconciling those inconsistencies under deal-process time pressure is a genuinely miserable exercise, and it often produces answers that look hastily assembled to a buyer’s diligence team, which itself becomes a negotiating point even when the underlying business is healthy. 

The alternative, and it’s a fairly modest ongoing investment relative to the pain it avoids, is maintaining a lightweight internal version of a data room throughout the hold, not built for a specific buyer but built as good practice regardless of whether a sale is on the horizon. 

Clean cohort-level retention data, a consistent methodology for calculating core metrics that doesn’t change every time someone new builds the analysis, and organised documentation of customer contracts and key vendor relationships.

None of this is difficult. It’s mostly discipline applied early and maintained consistently, rather than assembled in a panic once an exit process actually starts.

The businesses that go through a sale process calmly are almost never the ones that started preparing when the process began. They’re the ones where the preparation was actually just good ongoing housekeeping, and the sale process mostly involved packaging something that already existed rather than constructing it from scratch under a deadline. 

An NRR number that looks strong in a board pack and an NRR number that survives a buyer’s diligence team pulling it apart are not always the same number, and the gap between them tends to surface at exactly the wrong moment, which is during a sale process rather than well before one.

The most common gap comes from how discounting and concessions get treated. A renewal at the same price with a meaningful new discount baked in often still gets counted as “retained” revenue in an internal NRR calculation, because the logo stayed and the top-line number didn’t visibly shrink. 

A buyer’s diligence team will strip that out fast, because they’re looking at net effective pricing, not gross retained logos, and a business with real price erosion hiding inside a headline NRR number gets a materially different valuation once that’s surfaced. 

The second common gap is how expansion revenue from one-off, non-repeatable events gets treated. A large one-time upsell tied to a specific project or a specific customer circumstance can meaningfully flatter a single quarter’s NRR without representing a repeatable pattern.

Internal reporting often doesn’t distinguish structural expansion from one-off expansion, because both count the same way in the topline metric, but a buyer’s diligence team will absolutely separate the two, and a business whose NRR was quietly propped up by non-repeatable events looks considerably weaker once that separation happens. 

The practical fix, well before any sale process starts, is to build and maintain an internal NRR calculation that already strips out discounting effects and separates structural from one-off expansion, rather than only discovering the gap when a buyer’s advisors do it for you under time pressure. 

A number that’s already been stress-tested this way internally is a number you can defend with confidence in a process. A number that hasn’t is a number that gets renegotiated against you in the room.