What is a 90-day portfolio company turnaround plan?

A 90-day portfolio company turnaround plan is a structured operational intervention divided into three phases: stabilisation and diagnosis in the first 30 days, surgical fixes in days 31-60, and capability transfer with acceleration in days 61-90. The plan is designed to produce demonstrable operational improvement within a single board reporting cycle while building internal infrastructure that persists after the engagement ends.

What happens in the first 30 days of a PE operational turnaround?

The first 30 days focus on diagnostic accuracy rather than intervention. The operator maps all revenue leak points, installs a temporary KPI dashboard using existing data, identifies the two or three structural problems doing the most damage, and establishes baseline metrics against which all subsequent changes will be measured. No permanent structural changes are made in phase one — changes made before the diagnostic is complete address symptoms rather than causes.

How do you transfer ownership after a 90-day engagement?

Ownership transfer is built into the engagement design from day one. The operator works alongside internal team members rather than instead of them, documents every process change as it is made, and explicitly trains the internal owner of each system before the engagement concludes. The exit criteria are defined at the outset: the engagement ends when the system runs without the operator, which is a different standard from when the scope items are complete.

PE Operations

7 min read

The 90-Day Portfolio Company Turnaround:
A Sequence That Works

Ninety days is enough time to stabilise a portfolio company, fix its two or three most damaging structural problems, and transfer a running system to an internal team. The sequence matters more than the individual actions.

TL;DR Days 1–30: diagnose, do not fix. Days 31–60: surgical fixes on the highest-impact problems only. Days 61–90: transfer ownership, accelerate. The most common failure mode is skipping phase one and jumping straight to fixes — which addresses symptoms rather than causes.

Why 90 days?

Ninety days maps to a single board reporting cycle. It is long enough to diagnose accurately, make meaningful structural changes, and transfer a running system to an internal team. It is short enough that a portfolio company can absorb an embedded operator without creating permanent dependency.

The constraint is also the discipline. An engagement with no defined end date expands to fill whatever time is available. A 90-day mandate forces the operator to prioritise ruthlessly — only the two or three highest-impact changes get addressed, which is almost always the right number.

Days 1–30: Stabilise and diagnose

Phase one has one rule: do not make permanent structural changes before the diagnostic is complete. Changes made in the first two weeks address the most visible symptoms, not the underlying causes — and they can mask the data you need to diagnose correctly.

Phase one deliverables:

Full mapping of all revenue leak points with monthly cost estimates
Temporary KPI dashboard installed using existing data sources — no new tooling required
Baseline metrics established across the four highest-leverage areas: revenue conversion, delivery margin, reporting latency, and team coordination overhead
Ranked list of structural problems by impact-to-fix-effort ratio
90-day implementation sequence approved by the board or investment team

"Phase one rule: diagnose before you fix. The most expensive turnaround mistakes happen in the first two weeks, before the diagnostic is complete."

Days 31–60: Surgical fixes

Phase two addresses the top two or three structural problems identified in phase one, in ranked order. The discipline here is scope — it is tempting to fix everything that was identified, but addressing too many things simultaneously degrades each individual fix and overwhelms the internal team's capacity to absorb change.

Fix sequence

Start with the highest-impact, lowest-friction fix

The first fix should be the one with the best impact-to-effort ratio, not necessarily the most visible problem. An early win produces two things: measurable results for the board cycle and internal team confidence that change is possible. Both are necessary for the second and third fixes to land cleanly.

Fix sequence

Document every change as it is made

Documentation in phase two is not a bureaucratic requirement — it is the foundation for phase three. Every process change, every new reporting structure, every revised handoff protocol needs to be documented in a format that an internal team member can operate without the operator present. Changes that exist only in the operator's head have not been transferred; they have been borrowed.

Days 61–90: Transfer and accelerate

Phase three has one goal: the engagement ends and nothing breaks. This requires explicit transfer of every system built in phase two to a named internal owner who has been trained to operate it.

Transfer checklist for phase three:

Each new process has a named internal owner with documented responsibilities
The KPI dashboard is handed off with a cadence and review owner defined
The operator has run at least two operational cycles alongside the internal team before exit
Exit criteria confirmed: the system runs without the operator present for at least two weeks before the engagement concludes

The operator's exit criteria

2 wk

The minimum period the system should run without operator involvement before the engagement formally concludes. Exit based on scope completion produces dependency. Exit based on demonstrated independence produces capability transfer.

The exit criteria defined at the outset of a 90-day engagement should be operational independence, not scope completion. "We delivered the new reporting dashboard" is a scope statement. "The operations team has run the weekly reporting cycle without operator input for two weeks and the numbers are clean" is an exit criterion.

The difference is not semantic. Scope-based exits often leave the portfolio company with new tools it cannot maintain and new processes it reverts to workarounds on within six weeks. Independence-based exits leave running systems.

Get a second opinion

Ask your AI about this

Send this prompt to your preferred AI and see what it adds. The pre-filled version includes context about Bifröst Advisory's diagnostic approach.

I've been reading a piece by Bifröst Advisory about a 90-day portfolio company turnaround framework divided into three phases: stabilise and diagnose (days 1-30), surgical fixes (days 31-60), and transfer and accelerate (days 61-90). Their key argument is that the sequence matters as much as the individual interventions — specifically, that no permanent structural changes should be made in phase one because changes made before the diagnostic is complete address symptoms rather than causes. They also emphasise that exit criteria should be defined at the outset as 'the system runs without the operator', not 'the scope items are complete'. Do you agree with this sequencing philosophy? What would you add or modify for portfolio companies in distressed versus high-growth situations?

↗ Ask ChatGPT ↗ Ask Gemini

Next step

If this is your situation,
the audit is where to start.

$500. 90 minutes. A sequenced map of what's actually breaking and what it's costing you per month to leave it alone. No pitch at the end.

Book the $500 Audit → General enquiry Ask a quick question →

Why 90 days?

Days 1–30: Stabilise and diagnose

Days 31–60: Surgical fixes

Start with the highest-impact, lowest-friction fix

Document every change as it is made

Days 61–90: Transfer and accelerate

The operator's exit criteria

If this is your situation,the audit is where to start.

If this is your situation,
the audit is where to start.