You are likely reading this because a portfolio company is no longer behaving like the investment memo said it would. Growth has slowed, margin is under pressure, delivery is inconsistent, technology spend feels opaque, or the management team is asking for capital without a clean operating case. That is where operational due diligence consulting gets searched, budgeted and debated.
In my experience, the phrase is often used imprecisely. Some sponsors mean a pre-acquisition operating review. Some mean a post-close portfolio company audit. Some mean technology diligence with a broader operating lens. Some mean a second opinion before approving a 100-day plan, ERP programme, sales reorganisation or engineering expansion.
The useful question is not whether you need consultants. The useful question is what operating decision needs to be made, how much confidence is missing, and whether the current team can produce the answer without marking its own homework.
What buyers actually mean by operational due diligence consulting
When a PE sponsor, operating partner or mid-market CEO searches for operational due diligence consulting, they are usually looking for one of five outcomes.
- Investment risk clarity: What could break the thesis operationally, technically or commercially after signing?
- Value creation confidence: Which initiatives can actually move EBITDA, cash conversion, retention or delivery quality in the next 100 days?
- Management team calibration: Is the team describing reality accurately, or are the narratives polished but untested?
- Capability mapping: Where are the gaps in systems, process, data, leadership, hiring, product, engineering, sales operations or finance operations?
- Decision support: Should the sponsor approve budget, replace a leader, delay an integration, accelerate automation or change the operating cadence?
That is why I prefer the phrase portfolio company audit when the asset is already owned. The word diligence can imply a deal process. Audit forces a harder lens: what is working, what is not, what is material, what is noise, and what should happen next.
Good operational diligence does not merely list problems. It ranks tradeoffs, tests whether the fixes are executable, and tells the board which decisions cannot wait.
The output should not be a 90-slide museum piece. It should become a working operating agenda. I normally look for a heat map, a small number of quantified value levers, a sequencing plan, a management capability view, and the uncomfortable questions that need board-level attention.
Where a portfolio company audit differs from classic diligence
Pre-close diligence is constrained by time, access and deal politics. It often happens in two to four weeks, sometimes less. You review data rooms, interview management, test the investment thesis and flag red risks. It is valuable, but it is not the same as operating inside the asset.
A portfolio company audit is different. The sponsor already owns the problem. Access is broader. The operating cadence is visible. You can inspect board packs, budget variance, customer churn patterns, sales handoffs, engineering throughput, hiring bottlenecks, support escalations, procurement controls and system ownership. You can compare what the management team says against what the business does every week.
The tone also changes. Pre-close work asks, should we buy this and at what price? Post-close audit asks, how do we make this company perform better with the people, capital and time we actually have?
That distinction matters because operational due diligence consulting can become too generic if the scope is not tied to the asset's stage. A founder-led software business with £8 million of revenue and messy delivery needs a different review from a multi-site services company with procurement leakage and weak branch-level reporting. A carve-out needs different questions from a buy-and-build platform. The playbook is not the same.
A practical decision framework
When I advise sponsors or CEOs on whether to commission an operational review, I use a simple decision framework. It is not academic. It is designed to avoid over-scoping and to get to the decision that matters.
1. Define the board decision first
Start with the decision, not the diagnostic. Are you deciding whether to fund a £1 million systems programme? Replace a CTO, COO or revenue leader? Pause an acquisition? Rebuild the 100-day plan? Approve a hiring plan? Move from founder-led operations to a professional management cadence?
If the board decision is vague, the review becomes vague. The better brief is: within 10 working days, assess whether the proposed CRM and sales operations rebuild is the right constraint to attack, what risks are hidden, and what the first 90 days should include.
2. Identify the value levers
I usually map diligence around a short value creation bridge. Revenue quality, gross margin, operating expense control, cash conversion, customer retention, pricing discipline, delivery capacity and systems scalability are common levers. Not every company needs all of them.
For a B2B services company, utilisation, scope control and account expansion may matter more than automation. For a SaaS company, churn, product velocity, technical debt and sales conversion may dominate. For an eCommerce business, margin, inventory, performance marketing efficiency and platform reliability may be the real battleground.
3. Separate symptoms from constraints
Most operating reviews find a long list of symptoms: delayed reporting, weak dashboards, too many meetings, slow delivery, unclear ownership, poor forecasting, customer escalations and leadership fatigue. The job is to find the binding constraints.
A reporting problem may really be a data model problem. A sales problem may really be an ICP and pricing problem. An engineering problem may really be a product governance problem. A margin problem may sit in discount authority, not delivery efficiency. The point of operational due diligence consulting is to prevent the sponsor from funding the wrong cure.
4. Test management capacity
Even a strong plan fails if the team cannot absorb it. I look at decision velocity, span of control, role clarity, second-line leadership, hiring discipline and weekly operating rhythm. A company can usually handle two or three serious change initiatives at once, not twelve.
This is where a RACI, 30/60/90-day cadence and weekly KPI pack still earn their keep. They are not fashionable, but they expose whether ownership is real. If no executive can name the owner, metric, deadline and dependency for an initiative, the initiative is not managed. It is hoped for.
5. Decide the intervention level
The final question is proportionality. Does the company need a written second opinion, a five-day focused diligence sprint, a 100-day plan, interim technology leadership, or a fractional operating partner beside the team for several months?
I am biased toward smaller, sharper interventions first. If the question can be answered with ten interviews, board pack review and a written brief, do that. If the situation has cross-functional implications and execution risk, move into a retained advisory relationship. Do not buy a transformation programme when the immediate need is judgement.
What should be examined in an operational review?
A sensible portfolio company audit usually covers seven areas. The weighting changes by sector and investment thesis.
- Strategy and operating model: Is the company organised around the value creation plan or around historical habits?
- Leadership and cadence: Who makes decisions, how fast, using which data, and with what accountability?
- Revenue operations: Pipeline quality, forecasting, pricing, handoffs, customer segmentation and account ownership.
- Delivery and service quality: Capacity planning, margin leakage, project controls, customer success and escalation handling.
- Technology and data: System architecture, technical debt, cyber basics, integration risk, reporting reliability and vendor dependency.
- Finance operations: Budgeting, working capital, controls, unit economics, management information and variance discipline.
- People and organisation: Role clarity, hiring plan, incentive alignment, management bench strength and retention risk.
The key is to connect these areas rather than inspect them in isolation. Technology debt may be hurting finance reporting. Weak product governance may be creating support cost. Poor sales qualification may be destroying delivery margin. A good advisor follows the operating chain until the economics make sense.
A short comparison of options
There are several ways to buy this kind of help. None is universally right.
Large consulting firm
The advantage is breadth, brand comfort and process maturity. If the sponsor needs a board-safe report across multiple workstreams, a large firm can be appropriate. The tradeoff is cost, seniority dilution and the risk of a generic methodology. You may get a capable team, but not always the senior operator doing the work.
Specialist diligence boutique
A boutique can be faster and more focused. Many are excellent in specific sectors, including software, healthcare, industrials or multi-site services. The tradeoff is scope discipline. Some boutiques are built for pre-deal diligence and may not stay close enough to the messy post-close operating reality.
Fractional operating partner or board advisor
This is where I tend to sit. The sponsor or CEO gets a senior second opinion, direct challenge, operating pattern recognition and continuity from diagnosis into the first execution decisions. The tradeoff is capacity. I take a small number of personal engagements at a time; I am not selling a bench of consultants.
Internal operating team
If the sponsor has experienced operating partners with available time and domain depth, internal review may be the best answer. The tradeoff is independence and bandwidth. Internal teams can be too close to the original thesis, too busy with other assets, or politically constrained when the conclusion points at management capability.
Functional expert
A CTO, CRO, CFO or supply chain specialist can be ideal when the problem is clearly bounded. The tradeoff is that functional experts sometimes optimise their domain rather than the full enterprise constraint. If the board has not isolated the problem, start broader before going deep.
When operational due diligence consulting is the wrong tool
There are times when this is not the right answer.
It is the wrong tool when the board has already made the decision and only wants a report to justify it. That creates theatre, not diligence.
It is the wrong tool when the business needs urgent crisis management. If payroll is at risk, a system is down, cyber containment is active, or customers are churning today because service is failing, you need an operator in the seat, not a diagnostic exercise.
It is the wrong tool when the scope is too broad for the decision window. A full enterprise review in five days will become superficial. A five-day sprint can answer a focused question. It cannot responsibly redesign the operating model, validate every system, review every contract and assess every leader.
It is also the wrong tool when the sponsor is unwilling to act on uncomfortable findings. Operational reviews frequently reveal that the issue is not the dashboard, the CRM or the project plan. It may be decision avoidance, founder dependency, weak middle management or a value creation plan that was too optimistic. If those topics are off limits, the review will underperform.
What the deliverable should look like
I like deliverables that are usable in the next board meeting and still useful six weeks later. That normally means:
- An executive view: the two or three decisions that matter now.
- A red, amber, green heat map: not for decoration, but to force prioritisation.
- Evidence trail: interviews, documents reviewed, metrics checked and assumptions made.
- Value levers: where money, risk or time is being won or lost.
- Initiative sequencing: what happens in the first 30, 60 and 90 days.
- Ownership model: named accountable leaders, not committees.
- Risks and dependencies: what can derail the plan and what needs sponsor support.
For technology-heavy companies, I add architectural risk, platform scalability, security basics, engineering process, product governance and data reliability. For services companies, I spend more time on utilisation, delivery margin, handoffs and client concentration. The format should follow the economics of the asset.
Common mistakes sponsors make
The first mistake is buying a broad review when the real need is a sharp second opinion. A written assessment can sometimes save weeks of debate if the question is clear.
The second mistake is treating operational diligence as a procurement exercise. The cheapest review is not cheap if it misses the constraint. The most expensive review is not valuable if it produces generic recommendations the team cannot execute.
The third mistake is separating diligence from operating cadence. If the audit identifies ten initiatives but the company has no weekly operating rhythm, no clean KPI pack and no escalation model, the work will die in the gap between insight and execution.
The fourth mistake is ignoring technology as an operating system. In most mid-market companies, technology is no longer a back-office topic. It shapes customer experience, reporting quality, sales conversion, hiring productivity and margin. That does not mean every review is a tech review, but it does mean technology cannot be left until the end.
How I would approach this
If you are a sponsor, operating partner or CEO trying to decide what kind of operational due diligence consulting you need, I would start with the decision on the table. Send the investment thesis, last two board packs, current KPI pack, budget versus actuals, management organisation chart and the specific question keeping you from acting.
From there, I would usually recommend one of two routes. If the question is bounded and you need a fast independent view, I would use a Written Brief: concise, direct, and designed to support a board or sponsor decision. If the issue is broader and you need an ongoing second opinion beside the management team, a Fractional Retainer is the better fit.
For situations that are clearly tied to a transaction, a focused diligence sprint may be appropriate. For owned assets, I normally prefer a portfolio company audit that turns into a 30/60/90-day operating agenda. My role is not to sell a transformation army. I sit alongside the sponsor and management team, challenge the assumptions, identify the constraints, and help turn the review into decisions that can actually be run.