There’s a fair amount of received wisdom about what determines whether an exit hits its target multiple, growth rate at exit, market conditions, quality of the banker running the process. All genuinely matter. 

What predicts outcomes more reliably than any of these, in the deals that go well versus the ones that disappoint at the final number, is something that gets decided far earlier and gets far less attention at the time: whether the metrics the business is being sold on are ones that were built to survive scrutiny, or ones that were built to look good internally and never seriously stress-tested against how a buyer’s diligence team will actually treat them. 

This connects directly to points made elsewhere about NRR that survives diligence versus NRR that merely looks good in a board pack, and about data rooms that reflect genuine operational discipline versus ones assembled hastily for the occasion. 

The businesses that hit or exceed their target multiple are disproportionately the ones where these things were treated as ongoing operational discipline throughout the hold, not as a checklist assembled in the final year before a process starts. The businesses that disappoint at the final number are disproportionately the ones where a metric that looked strong internally turned out to have a gap, discovered by the buyer’s advisors during the process itself, that meaningfully changed how the buyer valued the business, sometimes after an agreed price had already been informally discussed. 

The uncomfortable implication is that exit outcome is substantially determined well before the exit process itself begins, by the quality and honesty of the metrics and documentation maintained throughout the hold, not primarily by the skill of the process run at the end. A brilliant banker running a well-timed process on a business with metrics that don’t survive scrutiny will still produce a disappointing outcome relative to what the headline numbers suggested going in. 

A well-run business with genuinely clean, defensible metrics tends to produce a strong outcome even in a mediocre process, because the underlying evidence does most of the work. 

The practical takeaway, and it’s really the thread running through everything in this collection: the work that determines your exit multiple mostly happens quietly, in ordinary months, long before anyone’s thinking about an exit process at all. 

Nearly every portfolio company conversation right now touches on AI in some form, and there’s a specific pattern worth naming honestly, because it’s shaping a lot of capital allocation decisions in ways that deserve more scrutiny than they’re currently getting. 

The pattern is a gap between AI initiatives that are genuinely producing measurable operational value and AI initiatives that are primarily producing a compelling narrative for the next board meeting or the next fundraise. 

Both categories exist in real numbers right now. The genuinely valuable initiatives tend to be narrow, specific, and boring to describe, a support ticket triage system that’s measurably reduced resolution time, a sales process step that’s genuinely faster with a specific tool. 

The narrative-driven initiatives tend to be broader, more ambitious in description, and considerably harder to point to a specific, measured outcome for, “we’re transforming our customer service function with AI” without a specific before-and-after metric attached. 

The reason this matters beyond intellectual honesty is that capital and management attention are being allocated toward AI initiatives right now partly on the strength of the narrative rather than purely on evidence of return, because the current environment rewards being seen to be doing something with AI, and that reward structure creates a genuine incentive to overstate what a specific initiative is actually delivering. 

The practical discipline worth applying to any AI initiative currently being discussed in a portfolio company: ask for the specific, measured before-and-after metric, not the description of the initiative’s ambition. If a genuinely specific metric exists and has moved, that’s a real result worth continuing to invest in. 

If the answer is a description of scope and potential rather than a measured outcome, that’s worth treating as an early-stage bet, not a proven value driver, regardless of how confidently it’s being presented. 

Funds building out or expanding an operating partner function often hire for a specific profile, deep functional or sector expertise, strong analytical capability, a track record of value creation at previous roles, and then find that a meaningful proportion of these hires don’t work out particularly well in their first year, despite genuinely strong credentials on paper.

The reason usually isn’t a mismatch in capability, it’s a mismatch in a specific skill that credentials don’t reliably signal: the ability to build genuine influence with a management team that has no formal obligation to listen to you. 

An operating partner has, in most structures, no direct line authority over portfolio company management. Whatever influence they have is built through credibility, relationship, and demonstrated usefulness, not through organisational position. 

Candidates coming from backgrounds where they held direct authority, a former operating executive, a former consultant used to being explicitly engaged and paid to be listened to, often underestimate how much of the job is this specific kind of influence-building, because it wasn’t the primary skill their previous roles demanded of them. 

The hires who work out well in year one, regardless of their specific background, tend to be the ones who invest heavily and early in exactly this skill, building genuine relationships and demonstrating value on small, concrete things before attempting anything more ambitious, as covered in more depth elsewhere. 

The hires who struggle tend to arrive assuming their credentials alone will earn the trust and access the role requires, and find, often around month three or four, that credentials open the door but don’t keep it open. 

For funds building this function, the practical implication is that hiring criteria weighted heavily toward credentials and analytical pedigree may be systematically underweighting the specific relationship-building skill that actually predicts year-one success. Worth testing for directly in the hiring process, rather than assuming it correlates reliably with the more visible signals on a CV.

When a portfolio company genuinely goes into distress, there’s a natural instinct on the board and deal team side to want a clear, fast turnaround timeline, both because that’s genuinely what everyone wants and because it’s what tends to get promised in the early stages, before the full shape of the situation is properly understood. 

The actual timeline for a genuine turnaround is, almost without exception, longer than the timeline that gets initially communicated, and understanding why matters for managing the process well rather than repeatedly resetting expectations downward. 

The specific reason distress takes longer to resolve than initially expected is that most genuine distress situations have multiple compounding causes rather than a single fixable problem, and each cause typically takes time to diagnose properly before it can be addressed, let alone resolved. 

A cash flow problem is often, underneath, a combination of a specific customer concentration issue, a cost structure that’s grown faster than the business justifies, and a management team that’s been managing symptoms rather than causes for long enough that the underlying issues have compounded. 

Fixing the visible symptom, the immediate cash position, buys time but doesn’t resolve the underlying causes, which take considerably longer to properly address, and boards that treat the symptom fix as evidence the situation is resolved tend to be surprised when the same pressure resurfaces months later. 

The practical implication for anyone managing a genuinely distressed situation: resist the pressure, from the board or from yourself, to commit to an optimistic timeline before the underlying causes are properly understood, and communicate explicitly that the initial stabilisation phase is different from full resolution, with a longer and less certain timeline attached to the latter. 

Boards that understand this distinction upfront tend to stay more patient and more supportive through a genuinely difficult period than boards that were given an optimistic timeline early and watched it repeatedly slip.

Fund administrators are, understandably, focused on getting their specific deliverables right, NAV calculations, capital call notices, LP reporting on schedule, and less inclined to flag broader inefficiencies in how a fund’s reporting cycle is structured, because that’s genuinely outside their remit rather than something they’re being negligent about.

The specific gap this creates is around timing dependencies that nobody’s actively optimising because no single party owns the full picture. A fund’s quarterly reporting cycle often has a chain of dependencies, portfolio company data needs to arrive by a certain date for the fund administrator to process it, the fund administrator’s output needs to be ready by a certain date for LP reporting, and each individual link in that chain gets managed reasonably well in isolation, while the overall cycle time, from portfolio company data close to final LP report, is longer than it needs to be, because nobody’s specifically responsible for compressing the whole chain rather than just their own piece of it. 

The practical exercise worth doing periodically, and it’s rarely done because it falls between roles, is mapping the entire reporting cycle end to end, every handoff and every dependency, and asking specifically where the chain could be compressed without compromising quality anywhere in it. 

Often the answer isn’t that any single party is slow, it’s that the handoffs between parties carry more buffer time than genuinely necessary, buffer that accumulated for good historical reasons but that nobody’s revisited since. 

A reporting cycle that’s a week or two shorter end to end doesn’t sound dramatic, but it compounds meaningfully across every quarter of a fund’s life, and it’s the kind of improvement that’s available to almost any fund willing to actually map the full chain rather than optimise each piece separately.

There’s a consolidation wave building quietly in vertical practice-management software, the niche systems that dental practices, veterinary clinics, and optometry groups run their day-to-day operations on, and it’s worth paying attention to now, before it becomes an obvious, crowded thesis that every fund is chasing at the same time. 

These businesses share a specific set of characteristics that make them attractive roll-up candidates: high switching costs once a practice is embedded in a system, genuinely fragmented ownership with a long tail of small, founder-owned vendors serving specific niches, and typically underinvested product development because most of these vendors have historically been too small to fund meaningful engineering investment. 

What’s changed recently is that a handful of larger platforms have started acquiring these smaller vendors specifically for their customer bases rather than their technology, with a plan to migrate customers onto a shared, better-funded platform over time. 

The part that isn’t being discussed enough is what this consolidation does to the economics of the smaller, independent vendors still operating in the space. As larger platforms acquire customer bases and improve the product experience across a wider footprint, independent vendors who haven’t been acquired face a widening product gap they increasingly can’t close on their own, which either makes them cheaper, more attractive acquisition targets over the next 18 to 24 months, or pushes them toward a slow, terminal decline as customers migrate toward better-resourced alternatives. 

For anyone looking at this space, the practical implication is that the window for acquiring these smaller vendors at a reasonable multiple, before consolidation dynamics either raise prices as competition for targets increases or erode the value of the remaining independents, is narrower than the current lack of attention to the space would suggest. 

This is exactly the kind of consolidation pattern worth tracking with current data rather than a stale sector thesis, because by the time it’s an obvious story, the attractive entry points will likely already be gone.

Multiples compression gets discussed almost entirely as a pricing phenomenon, what a business is worth on entry and exit, and that’s obviously the headline effect. What gets discussed far less is how compression changes behaviour inside portfolio companies during the hold itself, often in ways that quietly undermine the value creation plan. 

The most consistent effect is a shift in what “good performance” looks like from the management team’s perspective. In a rising-multiple environment, growth at almost any cost tends to get rewarded, because the market will pay for growth even if margins are thin. In a compressed-multiple environment, the same growth-at-any-cost approach gets punished at exit, because buyers are far more focused on efficiency and durability of margin. 

Management teams that were hired and incentivised during a different multiple environment don’t automatically recalibrate their instincts just because the market has shifted, and a genuine gap can open up between what the management team is optimising for day to day and what will actually be rewarded at exit. 

The second effect, less obvious but just as real, is on risk appetite around add-on acquisitions and expansion bets. In a compressed environment, the same bolt-on strategy that made sense when multiples were rising and integration risk was more easily absorbed by a rising market can look considerably riskier, because there’s less multiple expansion available to paper over integration missteps. 

The practical implication for anyone operating in the current environment: revisit the management team’s incentive structure and explicitly check whether it’s still pointing at growth-at-any-cost or has been recalibrated toward efficient, durable growth that will actually be rewarded by buyers in this specific market. An incentive structure built for a different multiple environment quietly working against the current plan is a more common problem than most boards realise.

There’s a specific pattern that plays out every few years in private equity, and it’s worth naming because it’s happening again right now in a handful of sectors that are currently attracting a disproportionate share of capital relative to the number of genuinely good assets available. 

The pattern goes like this. A sector demonstrates real growth and real resilience, word spreads, and capital follows. That’s healthy, initially. The problem starts when the volume of capital chasing the sector outpaces the number of genuinely strong businesses in it, because at that point the deals that get done aren’t necessarily the best businesses, they’re whatever’s available at the point the capital needs deploying. 

Multiples get bid up on assets that wouldn’t have cleared the same bar a few years earlier, and underwriting assumptions quietly loosen to make the numbers work, because everyone involved wants the deal to happen. 

This isn’t a call to avoid hot sectors entirely, because sometimes the enthusiasm is entirely justified by the underlying fundamentals. 

It’s a call to be more sceptical, not less, when a sector is genuinely crowded, because crowding changes the population of deals available in ways that are easy to miss if you’re focused purely on the sector thesis rather than on the specific asset in front of you. 

The practical discipline worth applying: when a sector is visibly hot, hold the underwriting bar steady rather than letting it drift with the market, and be honest about whether a specific deal would still clear that bar if the sector weren’t fashionable right now. 

If the answer is that the deal only makes sense because everyone else believes the sector story too, that’s worth sitting with before signing, not after.

LPs have gotten considerably more specific about operational value creation in the last few fund cycles, and it’s worth knowing exactly what’s being asked so you’re not caught explaining your process for the first time in an LPAC meeting. 

The questions have shifted away from “describe your operating model” in the abstract and toward specific evidence. How many portfolio companies has the operating team actually touched in a hands-on capacity in the last two years, not how many they were nominally responsible for. 

What’s the actual before-and-after on a specific metric for a specific company, not an aggregate claim about value creation across the portfolio. Whether the operating function is a genuine value driver or a marketing line item that gets invoked in fundraising decks and rarely shows up in an actual board pack. 

This shift matters because it changes what evidence is worth building now, before the next fundraise starts. If your operating team’s work isn’t documented in a way that produces a clean before-and-after story for at least a handful of portfolio companies, that’s a gap worth closing well before an LP due diligence process starts asking for it, because building that evidence retroactively from memory and old board decks is a miserable exercise under time pressure. 

The practical move: for every meaningful piece of operating partner work, capture a simple before-and-after snapshot at the time it happens, not months later when someone asks for a case study. What the metric was, what changed, roughly when. It doesn’t need to be a polished case study yet. 

It needs to exist in a form that can become one quickly when an LP due diligence process asks for exactly this kind of evidence, which increasingly, it will.

The line between an effective operating partner and what’s sometimes, unfairly or not, described as a glorified consultant isn’t really about seniority, sector expertise, or even quality of analysis. It’s about a specific difference in how accountability is held for the outcome, and management teams tend to sense this distinction fairly quickly, whether or not anyone names it directly. 

A consultant, in the traditional sense, is typically engaged to produce an analysis or a recommendation, and their engagement is often substantially complete once that recommendation is delivered, regardless of whether it’s actually implemented successfully. 

An operating partner who behaves the same way, delivering a sharp piece of analysis and a clear recommendation, and then moving on to the next thing without staying accountable for whether it actually gets implemented and actually works, tends to accumulate exactly the reputation the “glorified consultant” label implies, however good the underlying analysis was. 

The operating partners who avoid that label consistently share a specific habit: they treat the recommendation as the easy part and stay genuinely engaged through implementation, including when implementation reveals that the original recommendation needs adjusting. 

This is harder and less glamorous than producing the initial analysis, and it’s exactly the part that a purely analytical engagement model tends to skip. 

The practical distinction worth holding onto for anyone in this role: ask, honestly, whether your involvement with a specific initiative ends at the recommendation or continues through to the outcome. 

If it consistently ends at the recommendation, the label, fair or not, tends to follow, regardless of how sharp the recommendations themselves were.