Platform Performance Partners · Module D Framework
100-Day Capacity Framework
Where 100-day plans actually break in PE-backed MEP platforms — and how to course correct before the board sees it
"Most 100-day plans in PE-backed HVAC and MEP platforms are structurally sound on paper. They break at the same five capacity choke points — and those choke points don't fail in isolation. They reinforce each other."
PPP entry point
Pre-close — stress testing the plan before acquisition
Day 1 — setting realistic field capacity expectations
Day 60 — course correcting before the board sees it
The Core Insight
What this framework is built on
"The plan fails not because it was wrong at the model level — but because no one stress-tested it against the field's actual absorption capacity before execution began."
100-day plans are written by investors, advisors, and finance teams at the model level — revenue assumptions, headcount ratios, integration milestones, margin targets. They are then handed to field operators who are expected to execute them at the labor level. The gap between those two levels is where the plan dies. The five capacity choke points are not strategic failures. They are structural execution failures that every PE-backed MEP platform encounters — and they compound each other when left unaddressed past day 60.
The 100-Day Execution Window
Days 1–30
Setup & orientation
Leadership assessed, data gathered, quick wins identified. Choke points are forming but not yet visible.
Low visibility
Days 31–60
First execution pressure
Initiatives launch. Capacity strain begins. Dispatch, billing, and mid-management gaps start showing.
Strain emerging
Days 61–80
PPP entry point
Choke points visible but board hasn't seen the damage yet. This is the correction window — the last opportunity to course correct.
Correction window
Days 81–100
Board readout
Results are measured. Missed milestones are explained. Without correction, narrative replaces structural fixes.
Board visibility
The Five Capacity Choke Points — All Compound Each Other
CP1
Dispatch & field supervision capacity
The execution layer cannot absorb new volume at the rate the plan assumes
Breaks first
What breaks
Dispatch load exceeds scheduler capacity
Supervisor span of control too wide for integration pace
Technician utilization drops while overtime rises
Why it compounds
Overloaded dispatch creates routing waste
Supervision gaps allow rework and callbacks to accumulate
Field morale drops — turnover risk increases
Early warning signal
Overtime creeping past 15% of labor hours in weeks 3–5
Callback rate rising without root cause identified
Dispatch queue consistently behind by end of day
CP2
Billing & closeout velocity
Revenue is being earned in the field but not captured in time to support the plan's cash assumptions
Breaks fast
What breaks
Days-to-invoice extends beyond plan assumption
Job closeout incomplete — missing scope notes, materials
WIP grows while cash conversion slows
Why it compounds
Cash flow pressure forces reactive decisions
Incomplete closeouts make margin analysis unreliable
Finance team loses confidence in field reporting
Early warning signal
Days-to-invoice trending above 12 days by week 4
More than 15% of jobs missing closeout documentation
WIP balance growing faster than revenue recognition
CP3
Management bandwidth at the mid-level
The layer between field and CEO has no capacity left — decisions queue up or get absorbed by leadership
Compounds fast
What breaks
Service managers and branch leads overwhelmed
Decision escalation reaches CEO for operational matters
Integration tasks layered on top of run-rate responsibilities
Why it compounds
CEO bandwidth compresses — mirrors CEO churn pattern
Integration milestones stall without mid-level ownership
Run-rate operations degrade as integration gets priority
Early warning signal
CEO calendar shows operational meetings 3+ days per week
Mid-level managers reporting to CEO rather than managing up
Integration task owners not identified below CEO level
CP4
Technology & system absorption
Software rollouts and system changes consume field capacity the plan did not account for
Slow burn
What breaks
Field productivity drops during system transition
Dual-system operation creates data inconsistencies
Training time not accounted for in labor capacity plan
Why it compounds
Productivity disruption amplifies dispatch and billing strain
Reporting gaps during transition hide other choke points
Field resistance to new systems slows adoption timeline
Early warning signal
Productivity metrics dropping in weeks following go-live
Support tickets and workarounds increasing
Field staff reverting to prior processes informally
CP5
Pricing discipline at the field level
Margin assumptions in the plan are not enforced at the estimate-to-job handoff where they are actually won or lost
Hidden leak
What breaks
Quoted vs. realized gross margin variance grows
Field-level price exceptions not tracked or approved
Scope changes absorbed without change order discipline
Why it compounds
Margin erosion invisible until period close reporting
Field team learns that exceptions are tolerated
EBITDA misses accumulate before structural fix occurs
Early warning signal
Quoted-to-realized GM variance greater than 3 points
Change orders not being issued for scope additions
Sales team discounting without approval tracking
Capacity Scorecard — Day 60 Assessment Tool
Choke point
On track
Strain
Breaking
Not assessed
CP1 — Dispatch & field supervision
CP2 — Billing & closeout velocity
CP3 — Mid-level management bandwidth
CP4 — Technology & system absorption
CP5 — Pricing discipline at field level
On track
Under strain — monitor weekly
Breaking — immediate intervention
Not yet assessed
The Day 60 Entry — What PPP Does and How
What we assess in days 60–70
01Score all five choke points against observable field data — not management reports
02Map which choke points are compounding each other and in what sequence
03Identify the one or two structural fixes that break the compounding chain
04Build the board narrative — what is fixable before day 100 and what is a 90-day correction
05Deliver a Go / Course Correct / Escalate recommendation with named owners
How we do it — not a survey
01Direct field observation — dispatch floor, job closeout process, supervisor interactions
02Targeted data pulls — overtime %, callback rate, days-to-invoice, GM variance
03Structured interviews — CEO, service managers, dispatch, billing lead
04Decision audit — trace three recent escalations from origin to resolution
05Output: capacity scorecard + correction priority map + board-ready summary
Diagnostic Questions for PE Sponsors at Day 60
Q1
Which of the five choke points was identified as a risk in the original 100-day plan — and which ones were not?
Probe: If none were identified, the plan was written at the model level only. That is the structural gap.
Q2
At day 60, how many of the plan's milestones are on schedule — and who owns each one at the operator level?
Probe: Milestones without a named owner below CEO level are not owned — they are aspirational.
Q3
What is the current overtime rate and days-to-invoice compared to plan assumptions?
Probe: If these numbers are not known precisely at day 60, the field-to-finance translation is broken.
Q4
Is the board readout at day 100 going to show structural corrections or narrative explanations?
Probe: Narrative explanations at day 100 signal that the plan's structural failures were not addressed — they were managed.
Q5
If the same 100-day plan were handed to the next add-on acquisition, which choke points would break in the same place?
Probe: If the answer is "all of them," the platform has a repeatable execution model problem — not a one-time integration challenge.
PPP Position — How This Framework Is Used
How Platform Performance Partners uses this in an engagement
"We don't review 100-day plans at the model level. We stress-test them against the five capacity choke points that every PE-backed MEP platform hits — and we do it before the board has to ask why the plan missed."
Pre-close: validate whether the platform's field capacity can absorb the plan's assumptions before the deal closes
Day 1: set realistic expectations with the incoming CEO about which choke points are present and which need structural attention first
Day 60: the primary entry point — score all five choke points and build the correction plan before the board readout
Outputs connect directly to Board Readout Framework slides 4, 7, 8, and 9 — field execution, cadence, root cause, and stabilization plan
Platform Performance Partners · 100-Day Capacity Framework · Module D Confidential · Internal Use · Version 1.0