Operational transformation in PE-backed businesses: the 12-month value creation window

Why the first 12 months are disproportionately important

Private equity value creation plans are written at deal close. The EBITDA bridge is agreed, the workstreams are identified, and the investment thesis is documented. What happens next - in the 12 months that follow - determines whether that bridge is crossed or whether the gap grows.

The first year is when operational transformation either takes hold or stalls. Momentum built in the first 90 days is genuinely hard to build later. Delay in the first 90 days compounds. PE-backed businesses that outperform their VCPs typically have one thing in common: they started executing before the first board pack was written.

For US middle market businesses - typically $50m to $500m in revenue, often founder-led prior to acquisition - the operational gap between where the business is and where the VCP requires it to be is frequently wider than the deal model assumed. Operational due diligence captures a snapshot. The reality of building execution capability from inside the business is different.

The three phases of operational delivery

Operational transformation in PE-backed businesses moves through three phases. Understanding which phase you are in - and what the exit criteria for that phase look like - is more useful than a generic 100-day plan.

The failure point is most often at the transition from phase one to phase two. The diagnostic produces a prioritised list. The management team agrees it is right. And then nothing changes, because no one has the bandwidth, the programme management capability, or the mandate to actually deliver it.

The five most common portco transformation failure modes

1. No dedicated programme leadership inside the business

Transformation delivery is not a part-time activity for a senior leader who is also running their function. Portcos that attempt to run VCP workstreams without dedicated programme leadership consistently underdeliver. The workstreams compete with BAU, escalations happen slowly, and interdependencies are not managed.

The fix is either a dedicated internal programme lead or an interim resource - fractional COO, interim programme director - who owns delivery, not just reporting.

2. Wrong KPIs on the board pack

Board packs that report activity metrics (workstreams started, milestones hit) rather than outcome metrics (EBITDA impact, run-rate savings achieved, revenue per head) create an illusion of progress that masks delivery risk. By the time the outcome gap is visible, the portfolio is often two quarters behind plan with no recovery window before the hold period shortens.

The board pack should lead with the EBITDA bridge - what was planned, what has been confirmed, and what remains at risk. Everything else is context.

3. Management information is too slow or too unreliable

Transformation depends on being able to measure what has changed. In many middle market businesses, the management information infrastructure - the ERP, the reporting layer, the data quality - was built for a much smaller, simpler business. The VCP assumes data that does not yet exist in usable form.

Addressing the MI foundation is not a distraction from the VCP - it is a dependency for it. Businesses that invest in getting their data right in the first 90 days consistently deliver faster and more confident EBITDA realisation in the following nine months.

4. Organisational design lags the operating model change

Operating model changes that require new roles, restructured teams, or different reporting lines frequently stall because the people decisions are deferred. The process change is designed. The technology is procured. But the org chart has not changed, the incentives have not changed, and the people doing the work are still optimised for the old model.

5. Technology projects in the VCP are scoped as delivery projects, not as risk items

Technology projects - ERP implementations, system integrations, data migrations - are consistently the highest-risk workstreams in a VCP. They take longer, cost more, and have operational dependencies that affect other workstreams. Treating them as delivery projects rather than risk items means that when they slip - and they often do - the contingency has not been planned.

The leadership gap: when the management team is not enough

Middle market businesses often have excellent operational management. The founders and senior leaders who built the business understand it deeply and are credible with their teams. What they typically lack is not competence - it is experience of running a structured transformation on top of running a business.

This is where fractional or interim executive resource creates the most value. A fractional COO or interim programme director is not brought in to replace the management team - they are brought in to provide the delivery infrastructure, the escalation mechanism, and the programme leadership that the management team does not have spare capacity for.

The model that works best in middle market portcos is a combination: the existing management team retains ownership of the business and the EBITDA targets, and interim or fractional resource owns the transformation delivery mechanism. Clear boundaries, clear RACI, clear exit criteria.

Keeping EBITDA linkage visible throughout delivery

Every VCP workstream should have a direct line to the EBITDA bridge. Not indirectly - directly. If the workstream cannot be linked to a specific EBITDA line with a quantified expected impact and a confirmation date, it should not be in the VCP.

In practice, workstreams accumulate over the hold period that are useful but not EBITDA-linked. Strategic projects, capability building, compliance investments. These are not wrong, but they should be separate from the VCP workstreams that the deal model depends on. Mixing them creates a board pack that looks busy but does not tell the story of whether the EBITDA bridge is on track.

The programme governance structure should produce a monthly EBITDA confirmation - which workstreams have delivered confirmed run-rate savings or revenue, at what value, and with what confidence in sustainability. This is what an acquirer's due diligence team will reconstruct anyway. Building it during the hold period rather than retrospectively at exit saves significant time and reduces exit risk.

Exit readiness: what buyers look for in the ops team

Operational transformation in a PE-backed business is not just about EBITDA delivery during the hold period. It is about building a business that a buyer - strategic acquirer or secondary PE buyer - will pay a premium for.

Buyers in their due diligence will look for evidence that the operational improvements are structural rather than heroic. A business that has hit its EBITDA targets because one excellent executive was working 70-hour weeks is not the same as a business where the operating model, the incentive structures, and the management cadence produce that EBITDA reliably without extraordinary effort.

The operational indicators that command multiple expansion at exit include: documented and repeatable processes, reliable management information that the buyer can trust without restatement, a technology stack that is current and not a liability, and a management team that can articulate the business model clearly and demonstrate they own it.

Businesses that have invested in getting their operations right during the hold period - not just hitting the EBITDA number but building the infrastructure that generates it - typically achieve better exit multiples and cleaner due diligence processes. The operational work done in the first 12 months is still paying dividends at year four or five when the exit process opens.