Applies to
PE sponsors evaluating VCP progress
Operating partners translating model to field
CEOs accountable to plans their operating model cannot support
Board members reviewing forecast variance
The Core Insight
What this framework is built on
"The VCP is not owned by one person. It is seen differently by three — and the gap between how each of them sees it is exactly where execution breaks down."
The PE sponsor sees a financial model with assumptions. The CEO sees a mandate with targets. The operating partner — if there is one — sees an execution gap that nobody mapped. None of them are wrong. But when all three are operating from a different version of the plan, the result is predictable: forecast misses at days 60–90, narrative explanations at the board level, and a value creation timeline that quietly extends. This framework maps where the VCP disconnects from field reality, who owns each layer, and what alignment actually looks like in practice.
The Three-Party Ownership Gap — The Root of VCP Misalignment
What they see
"Hit the EBITDA target, integrate the add-ons, hit the milestones — or the board conversation gets uncomfortable."
The gap
Accountable to targets the current operating model cannot support without structural changes nobody has defined or funded
What they see
"The field can't absorb this plan at this pace. Dispatch is already strained, pricing discipline is inconsistent, and mid-management is overloaded."
The gap
This view is either not present at all, or arrives too late — after the first forecast miss has already happened
The result: Three parties, three versions of the plan, zero translation between model-level assumptions and field-level execution capacity. The forecast miss at day 60–90 was not a surprise — it was structural.
The Four VCP Disconnections — Where the Model Loses Contact with the Field
Model assumption
Revenue per tech based on top-quartile comparable
Utilization assumed at 75–80% of available hours
Growth assumed through tech productivity increase
Field reality
Current dispatch structure limits effective utilization to 55–65%
Routing inefficiency consumes 2–3 billable hours per tech per day
Supervisor span too wide to support productivity improvement at scale
Model assumption
Gross margin targets at 35–40% on service work
Pricing discipline assumed consistent across all branches
Change order capture assumed at 85%+ of scope additions
Field reality
Quoted vs. realized GM variance of 4–8 points on average
Field-level price exceptions not tracked or approved centrally
Change order discipline inconsistent — scope absorbed without billing
Model assumption
Cross-sell synergies realized within 12 months of close
Back-office consolidation reducing overhead by $X
Procurement leverage improving material costs by Y%
Field reality
No named owner for cross-sell execution below CEO level
Back-office systems still separate — consolidation timeline undefined
Procurement still decentralized — leverage not being captured
Model assumption
Overhead ratios improve as platform scales
Management leverage increases with add-on acquisitions
Field productivity improves as systems standardize
Field reality
Platform is not yet at the scale where those ratios apply
Each add-on requires more management bandwidth — not less
System standardization is a 12–18 month effort — not a 90-day assumption
VCP Misalignment Visibility Timeline
Pre-close
Hidden in assumptions
Disconnections exist in the model but no one has stress-tested them against field capacity. The plan looks sound.
Not visible yet
Days 1–45
Gaps forming quietly
Execution begins. Dispatch strain, pricing exceptions, and integration delays start accumulating — but metrics look stable.
Forming silently
Days 60–90
First forecast miss
EBITDA variance appears. Board asks why. CEO explains with narrative. The structural gap is now visible — but still fixable.
Sponsor visible
Days 90–180
Compounding damage
Without structural correction, second and third misses follow. CEO credibility erodes. VCP timeline extends. Exit delayed.
EBITDA damage
VCP Field Stress Test — Model vs. Reality Check
Revenue per tech / month
$18,000–$22,000
Validate against current dispatch structure — most platforms run $12,000–$16,000 without routing redesign
Technician utilization
75–80%
Pull actual billable vs. available hours — industry average in unoptimized platforms is 55–65%
Gross margin — service
35–42%
Compare to quoted vs. realized GM by job type — variance of 4–8 points is common without pricing enforcement
Change order capture rate
85%+
Audit last 30 jobs — most platforms without formal CO discipline run 40–60%
Days to invoice
7–10 days
Pull actual billing cycle data — platforms without closeout discipline average 14–21 days
Integration synergy timeline
6–12 months
Map named owners for each synergy — if no owner exists below CEO level, add 6–12 months to every assumption
What Misalignment Looks Like vs. What Alignment Looks Like
✕Model assumptions never stress-tested against field capacity
✕Sponsor, CEO, and operating partner each have a different version of the plan
✕Synergies assumed — no named owner at operator level
✕Forecast misses explained with narrative not structural correction
✕CEO held accountable to a plan the operating model cannot support
✕Exit timeline extends — value creation erodes
→Model assumptions stress-tested against actual field capacity pre-close
→Sponsor, CEO, and operating partner operating from one field-validated plan
→Every synergy has a named owner and a 90-day execution milestone
→Forecast variance addressed structurally within 30 days of first miss
→CEO mandate calibrated to what the operating model can actually deliver
→Value creation timeline protected — exit on schedule
Diagnostic Questions for PE Sponsors & Operating Partners
Q1
When was the VCP last reviewed against actual field operating data — not management reporting?
Probe: If the answer is "never" or "at close," the plan has never been field-validated. Every assumption is theoretical.
Q2
Can the CEO name the three operating model changes required to hit the EBITDA target — and who owns each one?
Probe: If the answer is the EBITDA target itself rather than structural changes, the CEO is managing to the number rather than fixing the model.
Q3
Which synergies in the VCP have a named owner below CEO level and a defined 90-day milestone?
Probe: Count them. Any synergy without a named owner and a near-term milestone is an aspiration, not a plan.
Q4
What is the current revenue per tech per month — and how does it compare to the VCP assumption?
Probe: If this number is not known precisely, field-to-finance translation is broken. The VCP is being managed at the P&L level, not the operating level.
Q5
If the first forecast miss at day 60–90 was structural — not situational — what changed operationally after that conversation?
Probe: If nothing changed structurally, the second miss is already predictable. Narrative explanations without structural corrections are a leading indicator of continued EBITDA erosion.
PPP Position — How This Framework Is Used
How Platform Performance Partners uses this in an engagement
"We don't review the VCP at the model level. We stress-test it at the field level — against the actual dispatch capacity, pricing discipline, and management bandwidth that will be asked to execute it."
Pre-close: stress-test every VCP assumption against field capacity before the deal closes — identify the gaps before they cost EBITDA
Post-close: translate the model-level plan into field-level execution milestones with named owners at the operator layer
Day 60–90 entry: when the first forecast miss triggers the conversation — identify whether the miss is situational or structural and build the correction plan
Outputs connect directly to Board Readout Framework slides 6, 8, and 9 — financial visibility, root cause, and the 90-day stabilization plan