You are holding a portfolio company that looked clean in diligence, has a credible management team, and still feels harder to move than the investment memo suggested. Revenue is lumpy. The tech roadmap keeps slipping. Sales blames product. Product blames legacy systems. Finance has the numbers, but not always the operating explanation behind them. That is usually when a sponsor or operating partner starts searching for a value creation diagnostic private equity playbook.
In my experience, the phrase sounds more clinical than the actual work. A good diagnostic is not a 90-page audit deck designed to prove that something happened. It is a fast, structured way to answer three questions: where is enterprise value currently leaking, which levers are worth pulling first, and who is accountable for the next decisions?
I normally sit alongside sponsors, operating partners and mid-market CEOs as a fractional operating partner or technology advisor. I am not trying to sell a bench of consultants. The value of this work is judgement: knowing which symptoms matter, which are noise, and which require a deeper diligence sprint before the board commits capital or management attention.
What buyers actually mean when they search this term
When a PE buyer searches for a value creation diagnostic, they are usually not asking for one single service. They may be trying to solve one of several situations:
- Post-close reality check: the deal has closed, the 100-day plan is still high level, and the sponsor wants an independent read on the business before priorities harden.
- Portfolio company audit: the asset has been held for a while and the sponsor wants to understand why growth, margin, delivery or product velocity has stalled.
- Board second opinion: management has a plan, but the board wants a practical challenge before approving budget, hiring, platform investment, or M&A integration.
- Exit preparation: the company is 12-24 months from exit and the sponsor wants to remove avoidable diligence objections before the next buyer asks the obvious questions.
- Underperformance triage: the company has missed plan, churn is rising, delivery cost is drifting, or sales productivity is unclear, and the sponsor needs to separate root cause from commentary.
The common thread is uncertainty. The sponsor does not yet need a full transformation office. They need a clear operating diagnosis: what is broken, what is merely immature, what is already improving, and where intervention will create the most value.
What a useful diagnostic should cover
A diagnostic should be broad enough to connect the dots, but not so broad that it becomes a generic business review. For a mid-market portfolio company, I normally want to examine five areas.
1. Commercial engine
This is the quality of growth. I would look at pipeline hygiene, lead sources, conversion, sales cycle length, pricing discipline, expansion motion, churn signals, and whether the company has a repeatable route to market. The diagnostic question is not simply, “Can sales grow?” It is, “Can this company grow predictably without heroics?”
2. Product and service economics
Many companies have revenue that looks fine until you inspect the delivery model. Custom work hides in product businesses. Support load hides inside customer success. Professional services margin subsidises weak product adoption. A diagnostic needs to identify whether growth improves the model or adds operational drag.
3. Technology and systems
For software, tech-enabled services, ecommerce, media, marketplaces and data-heavy businesses, technology is rarely just an IT line item. It affects scalability, reporting, customer experience, security, integration capacity and exit readiness. The practical question is whether the current architecture, roadmap and team can support the investment thesis.
4. Operating cadence
Some portfolio companies do not have a strategy problem. They have a cadence problem. Weekly meetings do not connect to KPIs. KPIs do not connect to ownership. Ownership does not connect to consequences. A diagnostic should inspect how decisions are made, not just whether dashboards exist.
5. Leadership capacity
PE value creation often assumes that the existing team can absorb more complexity: add channels, integrate acquisitions, implement systems, recruit executives, tighten reporting, and still run the base business. Sometimes they can. Sometimes the CEO has two excellent lieutenants and four unresolved gaps. The diagnostic should be honest about management bandwidth.
The decision framework I use
I prefer a simple framework because the boardroom does not need another taxonomy. For each issue, I classify it across four dimensions: value impact, time to evidence, management capacity, and dependency risk.
Value impact
Does this lever materially affect EBITDA, revenue quality, retention, working capital, exit multiple, or diligence risk? If it does not connect to value, it belongs lower on the list. A cleaner CRM matters only if it improves forecast quality, sales execution, segmentation, handover, or buyer confidence.
Time to evidence
Some levers show signal in weeks. Pricing tests, sales pipeline inspection, cost leakage, reporting cleanup and delivery utilisation often reveal evidence quickly. Others, such as platform re-architecture or enterprise sales transformation, take longer. The diagnostic should distinguish quick evidence from long-term payoff.
Management capacity
A weak plan with a focused team may beat a brilliant plan assigned to people who are already saturated. I want to know who will own each initiative, what they must stop doing, and whether the executive team can make tradeoffs without waiting for the next board meeting.
Dependency risk
Some initiatives are blocked by data quality, hiring, vendor constraints, technical debt, customer contracts or channel conflict. A diagnostic that ignores dependencies becomes theatre. A useful one makes sequencing explicit.
The output should not be a list of 30 recommendations. It should be a ranked set of decisions: do now, validate next, defer, or stop.
How this differs from a standard portfolio company audit
A traditional audit tends to ask, “Is the company compliant, documented, and reasonably controlled?” That has a place. A value creation diagnostic asks, “Where can the sponsor and management team create more enterprise value from here?”
The difference matters. A compliance-style review may identify missing policies, weak documentation or system gaps. Useful, but often insufficient. A value creation diagnostic should pressure-test the investment thesis. If the thesis depends on enterprise expansion, the diagnostic should inspect product readiness, sales capability, onboarding friction, integrations, security posture, and referenceability. If the thesis depends on margin expansion, it should inspect delivery model, automation, utilisation, pricing, support volume and organisational design.
The mistake I see is treating every portfolio company audit as a checklist exercise. Checklists are helpful for coverage. They are not enough for judgement.
A short comparison of options
There are several ways to run this work. The right option depends on urgency, trust in management, and how much ambiguity the sponsor can tolerate.
- Internal operating partner review: fastest when the sponsor has domain depth and bandwidth. The risk is internal bias or limited time for primary investigation.
- Functional consultant assessment: useful for narrow questions such as pricing, sales compensation, ERP, cybersecurity, or procurement. The risk is over-optimising one function without seeing cross-functional tradeoffs.
- Big-firm diagnostic: strong for structured programmes, broad benchmarking and board-ready materials. The risk is cost, slower mobilisation, and recommendations that require another large programme to implement.
- Fractional operating advisor: useful when the sponsor wants experienced judgement, direct access, and a practical plan without creating a large consulting layer. The tradeoff is capacity: one senior advisor cannot inspect every corner of a complex enterprise at once.
- Management self-assessment: appropriate when trust is high and the question is minor. The risk is that teams often report symptoms in the language of their own function, not in the language of enterprise value.
My bias is to start with a focused diagnostic, then deepen only where the first pass shows real value or risk. You do not need a full transformation programme to learn that the first bottleneck is pricing discipline, a brittle data model, poor onboarding, or an overloaded CTO.
What the diagnostic deliverable should look like
The best deliverable is not the prettiest one. It is the one the CEO, CFO, operating partner and board can use the next Monday morning.
I would expect the output to include:
- Executive diagnosis: the handful of issues that actually matter to the thesis.
- Evidence base: interviews, KPI review, system observations, document review and, where relevant, technical or commercial inspection.
- Value levers: ranked by expected impact, confidence, timing and dependencies.
- Risk register: what could impair growth, margin, continuity, security, reporting, or exit readiness.
- Decision log: what the board or CEO must decide, by when, and with what information.
- First 30-100 days: concrete actions, owners, operating cadence and measures of progress.
I do not like diagnostics that end with “further analysis required” across every workstream. Some uncertainty is unavoidable. But the point of the exercise is to reduce ambiguity enough to act.
Signals that the diagnostic is working
A good diagnostic creates clarity quickly. You should see sharper conversations in the first week: fewer vague complaints, more specific tradeoffs, and a clearer distinction between strategic constraints and execution failures.
For example, “sales is underperforming” may become “pipeline stages are not comparable across regions, the ICP is too broad, and enterprise deals require product capabilities the roadmap has not funded.” “Technology is slow” may become “the roadmap is overloaded with customer-specific commitments, release ownership is unclear, and the reporting layer cannot support the board pack without manual work.”
Those reframes matter. They move the discussion from blame to decision.
When a value creation diagnostic is the wrong tool
There are times when this is not the right intervention.
- The company is in acute distress: if liquidity, covenant pressure, major customer loss or leadership breakdown is immediate, you may need crisis management, not a diagnostic.
- The board already knows the answer: if the decision has effectively been made, do not commission a diagnostic to legitimise it. Execute the decision and manage the risk.
- The sponsor wants benchmarking instead of judgement: benchmarking can be useful, but it rarely tells you what to do next in a specific company with specific constraints.
- Management is not willing to engage: a diagnostic conducted around the management team, rather than with them, usually produces defensive behaviour and weak adoption.
- The scope is secretly a full transformation: if the real need is a multi-quarter operating reset, call it that. A diagnostic can shape the programme, but it cannot replace it.
The wrong use of a diagnostic is to delay a hard conversation. The right use is to make that conversation better informed, more specific, and more actionable.
Common traps in PE value creation diagnostics
The first trap is over-scoping. Sponsors understandably want a full picture, but every additional workstream adds time and dilutes focus. I would rather inspect the five constraints most likely to affect the thesis than lightly touch 18 departments.
The second trap is mistaking data availability for operating maturity. A company can have dashboards and still lack decision discipline. Conversely, a company can have messy reporting but a strong operating spine. The diagnostic must look at behaviour, not just artefacts.
The third trap is underestimating technology as an operating constraint. In many mid-market assets, the technology estate quietly determines how fast the company can integrate acquisitions, launch products, serve larger customers, satisfy diligence, or automate reporting. This is not about fashionable tooling. It is about whether the operating model can scale.
The fourth trap is producing a recommendation without an owner. If nobody has the authority, time and incentive to move an initiative, it is not a plan. It is a wish.
How I’d approach this
I would start with the sponsor’s thesis and the management team’s current plan, then look for the few constraints that could materially change value creation over the next 100 days and the next 12 months. I would interview the CEO, CFO and relevant functional leaders, review the board pack, inspect the KPI model, examine customer and revenue signals, and go deeper on technology where it affects scale, reporting, security, integration or product velocity.
The output would be a ranked set of value levers, risks and decisions. Not a generic audit. Not a beauty parade of best practices. A practical operating view that tells the sponsor and CEO what to do now, what to validate next, and what to ignore for the moment.
If the company needs a board-ready plan after the diagnostic, I would usually point to a 100-Day Value Creation Plan. If the sponsor wants a standing second opinion across a portfolio company, with direct access as issues surface, a Fractional Retainer is often the cleaner model. In both cases, I stay close to the management team and the sponsor’s operating agenda, rather than dropping in a large delivery layer before the problem is properly defined.
Execution capacity can come later, including through DevriX where the agreed plan requires technical delivery. But the diagnostic itself should be senior, direct and decision-led. In private equity, the expensive mistake is not usually the lack of ideas. It is spreading attention across too many plausible initiatives while the real value constraint remains unresolved.