Sector analysis · Private equity
Operational drag in portfolio companies: measuring the EBITDA gap
The thesis is sound, the management team is capable, and EBITDA realization still lags the model. The explanation is frequently sitting inside the portfolio company's own operations, in a layer no financial report is built to show.
In brief
- Hidden operational drag — rework loops, manual dependencies, workflow variation and fragmented automation — is estimated to consume 15 to 25% of EBITDA, routinely.
- Financial reporting is an outcome indicator. By the time a process problem is visible in EBITDA it has been running for weeks or months.
- Typical findings include 22% of orders passing through manual review, 18% rework in approval routing, and one region executing a single process through 39 distinct variants.
- Operational readiness precedes AI readiness: automation applied over a workflow carrying a 32% rework rate reproduces that rework at scale.
- Deployment is read-only and runs in two to three weeks, with initial findings in two to four — a timeline compatible with a hold period rather than a consulting calendar.
1What the gap consists of
Operating partners know the pattern. The numbers look close. The thesis is solid. Quarter after quarter, EBITDA realization lags the model, and market conditions, integration delays and talent gaps absorb the blame.
Hidden operational drag is estimated to consume between 15 and 25% of a company's EBITDA, across industries and company sizes.1 Financial reports, executive dashboards and periodic reviews are built to show outcomes rather than execution. They establish what happened. They do not establish why, or where.
Business process intelligence addresses that specific gap: continuous, data-driven visibility into how work genuinely moves across ERP, CRM, procurement and finance systems — not how it is documented. Most organisations know what their order to cash process should look like. Fewer know the following.
For an investor, the difference between seeing execution reality and seeing designed process is the difference between catching margin leakage early and discovering it once it is already in the numbers.
2The four forms leakage takes
Behind every portfolio company is a web of processes determining how efficiently the business runs. Over time those processes drift: manual dependencies accumulate and workarounds become standard practice. What stays hidden tends to fall into four categories.
| Form | How it appears in operations | Why reporting misses it |
|---|---|---|
| Rework and duplicate effort | Tasks repeated because upstream exceptions were not caught | Creates cost with no corresponding line item |
| Workflow variation | One procurement process executed differently across seven entities | Makes standardisation and benchmarking unreliable |
| Manual dependencies | Approvals and reconciliations that should be automated and are not | Consumes labour hours booked as normal capacity |
| Bottlenecks and cycle time | Fulfilment averaging 2.7 days against a designed 1.4 | Delay buried in an exception path nobody monitors |
Collectively these produce leakage that is slow, quiet and cumulative. The challenge is not that leadership is unaware problems exist. It is that without execution data, identifying what those problems are and where they originate is extremely difficult — and imprecise problems attract imprecise remedies.
3Why financial metrics lag the problem
Financial metrics are outcome indicators. By the time a process problem appears in EBITDA it has been operating for weeks or months. A rework loop adding cost to every order processed does not wait for the quarterly close to begin doing damage.
What financial reports cannot explain is mechanism. They cannot identify which workflows generate delay, where rework repeats, or that two regions execute the same process in fundamentally different ways with one taking three times as long. They cannot show that an exception path is triggered by 11% of orders and adds two days to every cycle it touches.2
Without execution visibility, portfolio teams are improving performance by reading the scoreboard rather than watching the game. The score establishes that you are losing. It does not establish why.
4Value creation moves to the execution layer
Value creation in private equity has been led by financial engineering and strategic transformation. Both have produced real results and both face diminishing returns as markets grow more competitive.
Execution is where strategy either becomes results or is absorbed by the machinery of operations — where synergies realize on schedule or slip, and where margin improvement persists or fades. Delivering faster synergy realization, durable margin improvement and stronger exit valuations consistently requires visibility at that layer.
What that produces is a shift from reactive problem solving to identifying performance issues before they reach the P&L — which matters most in a hold period, where the time available to compound an operational improvement is finite and known in advance.
5Operational readiness precedes AI readiness
Most companies are implementing AI before they understand the processes they intend to automate. They know they want AI but are not always clear which processes are stable enough, where the exceptions sit, or how manual dependencies are currently handled.
The result is predictable: organisations automate inefficiency rather than efficiency. Applied over a workflow carrying a 32% rework rate, automation reproduces that rework faithfully and at higher volume.3
The sequencing implication for diligence
A portfolio company's AI roadmap is difficult to assess without knowing the stability of the processes it targets. Execution data provides that input, which makes it as relevant to pre-investment diligence as to post-close value creation — though the evidence base for AI-driven results specifically remains thin, and claims about it should be treated with more caution than claims about visibility itself.
6Deployment constraints that fit a hold period
Historically, this level of visibility required lengthy engagements and months before any insight was delivered. That model does not fit how private equity operates. Four constraints define what does.
- Two to three weeks to deploymentVisibility on a timeline compatible with a value creation plan rather than a consulting calendar.
- Read-only, non-disruptiveConnection to source systems with no changes to existing infrastructure and no write access to production.
- Cloud or on-premisePortfolio estates are mixed; the deployment model has to accommodate that rather than dictate it.
- EBITDA-anchored outputFindings expressed in margin terms rather than as process documentation, because that is the language the investment committee uses.
Initial findings identifying major bottlenecks, rework patterns and workflow variation are typically delivered within two to four weeks. A structured analysis of a single high-volume workflow frequently surfaces a material annualized opportunity — though the size of that opportunity varies widely by company and should be treated as a finding to be validated, not a number to be underwritten.4
Operational inefficiencies do not announce themselves. They accumulate quietly, eroding margin and reducing the scalability buyers price at exit. What cannot be seen cannot be optimised, and what cannot be optimised cannot be maximised.
7Common questions
What is business process intelligence in a portfolio context?
The capability to see how operational workflows actually execute across portfolio companies — capturing activity across ERP, CRM, procurement and finance systems and translating it into evidence about efficiency, bottlenecks, rework and margin impact.
How does it differ from management reporting?
Reporting shows outcomes after the period closes. Process intelligence operates at the execution layer, extracting event-level data and revealing variation, rework and bottlenecks as they occur.
Why do these inefficiencies go undetected?
Because dashboards and management packs are designed to measure outcomes. A rework loop adding cost to every transaction does not appear as a distinct line item; detecting it requires reading operational event logs directly.
Can it be implemented without disrupting operations?
Yes. Platforms in this category operate read-only, connecting to source systems without requiring infrastructure changes. Initial visibility is typically achieved within two to three weeks.
How quickly does EBITDA impact become visible?
Findings arrive within two to four weeks. Realised impact takes longer, since it depends on the intervention being made and measured against the pre-intervention baseline.
—References
- Estimates of EBITDA consumed by hidden operational drag across industries and company sizes. [Full citation to be confirmed before publishing.] ↩
- RE-ViVE deployment analyses across portfolio operations: manual review rates, approval rework rates, workflow variant counts, exception path frequency and fulfilment cycle times. Figures aggregated; client identities withheld. ↩
- RE-ViVE analysis of workflows carrying elevated rework rates prior to automation. ↩
- RE-ViVE engagement data on time to initial findings for single high-volume workflow analyses. ↩
Deployment figures are drawn from RE-ViVE engagements and described in aggregate. Opportunity sizes surfaced during analysis are estimates requiring validation against the company's own baseline before being relied upon.
Related reading
RE-ViVE deploys read-only across cloud and on-premise estates, with initial findings in two to four weeks. To scope an analysis on one portfolio company,request a walkthrough.