You are looking at a portfolio company audit because something needs a sharper second opinion. Maybe the business has missed two monthly packs in a row. Maybe the CTO says the platform is fine but product releases keep slipping. Maybe the CEO has a credible growth story, but EBITDA quality, systems maturity and management cadence do not quite line up. In my experience, this search usually starts when the sponsor needs clarity without turning the company upside down.
A useful portfolio company audit is not a forensic fishing expedition and it is not a generic operational review. It is a focused assessment of where enterprise value is being protected, leaked or left on the table. For a mid-market company, that often means looking across commercial operations, finance processes, technology, data, people, delivery cadence and the operating rhythm between management and the board.
The aim is not to produce a thick report. The aim is to give the sponsor and management team a short list of decisions they can act on.
What buyers actually mean by portfolio company audit
When a sponsor, operating partner or CEO searches for portfolio company audit, they may mean one of several different things. The phrase is broad, and that is why many audits become bloated. The first job is to define the question.
1. Is the company operating as reported?
This is the classic sponsor concern. The board materials show progress, but the underlying machine feels brittle. Revenue is growing, yet customer support is strained. Product velocity is promised, yet every release appears to create regressions. Hiring is approved, yet capacity never improves. The audit needs to reconcile narrative with operating reality.
2. Where is value leaking?
In a portfolio company, leakage rarely sits in one place. It can be buried in manual finance work, custom delivery, weak pricing discipline, founder-led sales, data inconsistency, technical debt, vendor sprawl, slow procurement, or an underpowered management layer. A good audit makes those leaks visible and ranks them by impact, effort and urgency.
3. What will break at the next stage of growth?
A company can be perfectly serviceable at £10m or £20m of revenue and still be unfit for the next chapter. The systems, leadership cadence and product architecture that carried the business so far may not support expansion into new geographies, enterprise customers, integrations, acquisitions or heavier reporting demands. The question is not whether the business works today. The question is what becomes fragile when volume, complexity or scrutiny doubles.
4. Is management being realistic?
This is sensitive, but common. Sponsors do not always need an adversarial review. They need an independent operator to test assumptions. Are the hiring plans credible? Is the product roadmap commercially anchored? Are technology estimates padded, optimistic or simply unknown? Is the CEO avoiding a difficult reorganisation? A portfolio company audit can create a neutral fact base before the board pushes harder.
The right scope for a portfolio company audit
The audit should match the decision at hand. If the sponsor is preparing an add-on acquisition, the review will look different from a post-close stabilisation audit. If the issue is margin compression, it should not become a broad technology survey. If the issue is a stalled software platform, it should not become a generic HR diagnostic.
I usually separate scope into five practical lanes.
- Operating cadence: board packs, management meetings, KPIs, ownership, escalation paths, forecast discipline and decision latency.
- Commercial engine: pipeline quality, customer concentration, pricing, renewals, sales process, marketing attribution and customer success handoffs.
- Technology and product: architecture, release process, security posture, technical debt, roadmap governance, build-versus-buy decisions and engineering leadership.
- Finance and data: close process, management accounts, unit economics, data integrity, reporting stack, ERP or CRM reliability and manual workarounds.
- People and execution capacity: leadership bench, role clarity, incentives, delivery model, hiring bottlenecks, dependency on founders or single points of failure.
The scope does not need to cover all five lanes equally. In fact, it should not. The sharper version identifies the two or three lanes most likely to change the investment outcome in the next 90 to 180 days.
A decision framework for sponsors and CEOs
Before commissioning a portfolio company audit, I would work through five questions. They prevent the work from becoming a consultancy-shaped distraction.
Question 1: What decision will this audit inform?
If there is no decision, there is no audit. The decision might be whether to replace or support a functional leader, whether to approve a technology investment, whether to pause an acquisition, whether to reset the 100-day plan, or whether to intervene before covenant pressure builds. Write the decision down before agreeing the work.
Question 2: What is the time horizon?
A pre-close or urgent board concern may need a five-day readout. A post-close operating review might need two to four weeks. A deeper transformation assessment may need a retained advisory relationship over a quarter. The shorter the window, the more ruthless the scope has to be.
Question 3: What evidence is available?
Useful evidence includes board packs, monthly management accounts, CRM exports, product roadmaps, engineering tickets, architecture diagrams, customer churn data, support queues, staff org charts, vendor lists and recent investor updates. If the company cannot provide basic artefacts quickly, that is itself a signal.
Question 4: Who needs to hear the answer?
An audit for the deal team reads differently from an audit for the CEO. An audit for the board differs from one designed to help a CTO prioritise. Decide whether the output is a board memo, a red-amber-green risk register, a 100-day action plan, or a working session with management.
Question 5: What level of disruption is acceptable?
There is always a tradeoff. The least disruptive audit relies heavily on documents and short interviews. It is faster and politically easier, but it may miss cultural and execution problems. A more intrusive audit includes workshops, system access, staff interviews and deeper evidence sampling. It creates a better picture but consumes management time and can feel like a vote of no confidence if poorly positioned.
What I would inspect first
In a mid-market portfolio company, I start with operating rhythm because it reveals how the company really works. If the leadership team cannot define its top five priorities, if KPIs change every month, or if the same unresolved issues appear in three board packs, the problem is rarely confined to one function.
Then I look for single points of failure. These can be technical, commercial or human. A founder who approves every enterprise deal is a single point of failure. A legacy developer who alone understands billing logic is another. So is a spreadsheet that drives revenue recognition with no documented owner. These weaknesses may not appear on a financial statement until they become expensive.
Next, I examine the relationship between growth plans and operational capacity. Many companies carry a gap between what the investment case assumes and what the current operating model can absorb. The sales plan assumes enterprise expansion, but implementation is still bespoke. The product plan assumes integrations, but the platform lacks clean APIs. The finance plan assumes faster close, but reporting is stitched together manually.
Finally, I look at management honesty. Not moral honesty, but operating honesty. Does the team surface bad news early? Do leaders understand tradeoffs? Are estimates grounded in evidence? Do they distinguish between symptoms and root causes? A management team that can describe its constraints clearly is usually easier to back than one that insists every issue is temporary.
Short comparison of portfolio company audit options
There is no single best format. The right option depends on the question, timing and political context.
Internal sponsor review
- Best when: the sponsor already has strong functional expertise and the issue is narrow.
- Strength: fast, low cost and already tied to the investment thesis.
- Tradeoff: may inherit existing assumptions and can be discounted by management as investor pressure.
Big consultancy diagnostic
- Best when: the company needs a broad transformation programme, multiple workstreams and heavy documentation.
- Strength: structured process, capacity and benchmarking language.
- Tradeoff: expensive, slower to mobilise and often produces more slides than decisions.
Functional specialist audit
- Best when: the problem is clearly in one area, such as cybersecurity, ERP, pricing, sales compensation or cloud spend.
- Strength: depth and technical precision.
- Tradeoff: can miss cross-functional causes. A technology issue may actually be a governance issue; a sales issue may be a product packaging issue.
Fractional operating partner or independent advisor
- Best when: the sponsor needs judgement, prioritisation and a practical operating view without deploying a large team.
- Strength: closer to board and management decisions, less theatre, more direct recommendations.
- Tradeoff: capacity is limited. You are buying senior judgement, not a bench of analysts.
My own model sits in that last category. I take a small number of personal advisory engagements and work alongside sponsors, operating partners and CEOs. If execution capacity is needed after the plan is agreed, DevriX can be relevant, but the audit itself should be led by judgement rather than headcount.
When a portfolio company audit is the wrong tool
A portfolio company audit is useful when there is a decision to make and uncertainty to reduce. It is the wrong tool in several situations.
- When the board already knows the answer: If the decision has effectively been made, do not commission an audit to create political cover. Be direct with management.
- When the issue is purely financial compliance: If the concern is statutory audit, fraud investigation or tax treatment, use the appropriate accounting, legal or forensic specialists.
- When the company is in crisis execution mode: If payroll, production, security or customer delivery is already failing, you may need interim leadership or a turnaround plan, not another assessment.
- When management will not engage: A sponsor can force access, but a hostile management team will reduce the quality of the evidence. In that case, the first issue is governance and alignment.
- When the scope is too broad to matter: An audit that asks for everything usually produces a report that changes nothing.
The most common misuse I see is commissioning an audit because the sponsor feels uneasy but has not named the actual worry. Unease is a legitimate signal, but it needs translation into a testable question.
What the output should look like
I prefer concise outputs. A good portfolio company audit should give the board and management team a shared fact base, not a library. The core output usually includes:
- Executive diagnosis: the three to five issues that matter most.
- Risk register: ranked by severity, likelihood, timing and owner.
- Value creation opportunities: the few initiatives that can improve growth, margin, resilience or exit readiness.
- Decision points: what the sponsor or board must approve, stop or escalate.
- 90-day action plan: owners, milestones and evidence of progress.
The language should be plain. If a CTO needs replacing, say that carefully and evidence it. If the platform is stable enough but the roadmap governance is weak, say that too. If the finance systems are ugly but adequate for the next 12 months, do not turn them into a transformation programme for the sake of neatness.
How I’d approach this
If you came to me with a portfolio company audit question, I would start by narrowing the decision. Are we testing a risk before an investment committee? Are we diagnosing a missed plan? Are we preparing a 100-day reset? Are we giving the CEO a practical second opinion before the next board meeting?
For a discrete issue, I would usually recommend a short written assessment: review the artefacts, interview the right operators, identify the root causes and give you a clear memo with options. That is often the cleanest next step through a Written Brief.
If the company needs ongoing judgement rather than a one-off audit, I would structure a light retained relationship: regular management sessions, board-level readouts, priority tracking and a standing second opinion for the sponsor. That fits a Fractional Retainer.
The point is not to audit for the sake of auditing. The point is to protect the investment thesis, reduce avoidable surprises and give management a short list of moves that will actually change the company’s trajectory.