The 100-Day Integration Playbook for PE Trade Roll-Ups

Why the First 100 Days Decide the Deal

Most PE trade roll-ups don't fail at acquisition. They fail at integration.

The math is straightforward: PE firms buy HVAC, plumbing, and electrical businesses at 4x–6x EBITDA. Exit multiples of 8x–12x — the source of actual PE returns — depend on demonstrating a unified, professionally-managed platform. That demonstration has to be credible by month 18, which means operational integration has to be complete by month 6. Which means the foundation has to be built in the first 100 days.

Every platform that hits 18-month integration drag — and most do — lost those 12 months somewhere in the first quarter. Not because they didn't work hard. Because they sequenced wrong. They let subsidiaries keep running their own QuickBooks files while "evaluating options." They defined KPIs for the platform deck without locking down definitions at the subsidiary level. They delayed the chart of accounts standardization because it felt disruptive.

The disruptive version is the 18-month version.

This playbook is the framework for front-loading that work.

The 5 Operational Layers That Must Standardize

Integration complexity in trade services concentrates in five layers. Skipping any one of them creates cascading visibility failures that don't surface until they're expensive.

Layer 1: Chart of Accounts

What "standardized" looks like: Every subsidiary uses an identical COA structure. Service revenue broken out by trade (HVAC install, HVAC maintenance, plumbing, electrical). Labor classified consistently (direct field, indirect field, back office). Material/equipment separate from subcontractor. A single intercompany elimination framework.

Cost of skipping it: You cannot produce consolidated financials. Full stop. Your portfolio CFO is manually reconciling spreadsheets. Your LP reporting is 3 weeks late. When a lender asks for trailing-12-month EBITDA across the platform, someone is building it in Excel at 2am.

Quick-win playbook:

1. Audit all existing COAs — identify the divergence points (most platforms have 4–7 critical mismatches)
2. Define the target COA with your platform CFO before Day 30
3. Map every subsidiary's existing accounts to the target
4. Migrate in your accounting system (QBO, Sage, Acumatica) — this is a 4–6 hour job per subsidiary if you've done the mapping
5. Do not allow exceptions for "how we've always done it" — one non-conforming entity destroys consolidated reporting for everyone

Layer 2: KPI Definitions

What "standardized" looks like: Platform-wide definitions for: revenue per technician per day, job gross margin (labor + materials only, no overhead allocation), maintenance agreement attach rate, average ticket, call booking rate, and technician utilization. Every subsidiary computes these identically. The platform dashboard shows comparable numbers, not numbers that require footnotes.

Cost of skipping it: You're comparing apples to motorcycles. One subsidiary's "gross margin" includes a non-cash amortization charge. Another excludes parts revenue because the owner always reported it separately. Your board deck shows margin improvement that doesn't actually exist — it's a reporting artifact. Worse, you can't identify which subsidiaries are actually underperforming vs. which are just reporting differently.

Quick-win playbook:

1. Run a KPI definition audit — pull last month's reports from each subsidiary and have your CFO compute the same 6 KPIs from each set. Note every divergence.
2. Write a one-page KPI dictionary. Not a 40-page data model. One page with field names, formulas, and exclusions.
3. Share it with every subsidiary GM/owner. Confirm they can compute it from their existing systems.
4. Lock it. This is not a living document. KPI definitions that change every quarter cannot be trended.

Layer 3: Payroll & HR Systems

What "standardized" looks like: All subsidiaries on a single payroll platform (or one per geography if state complexity requires it). Technician comp structures defined at the platform level — base vs. commission vs. spiff, overtime policy, benefits enrollment. A unified org chart in HRIS so headcount is reportable across the platform.

Cost of skipping it: You cannot compute labor cost per job consistently. A subsidiary running hourly technicians looks radically different from one running commission-only — not because the business is different, but because the cost accounting is different. You cannot benchmark technician productivity across the portfolio. When you acquire the 8th subsidiary, you're explaining your "platform" HR structure to a team that's using paper timesheets.

Quick-win playbook:

1. Inventory payroll platforms (most platforms have 3–5 different ones across 4 subsidiaries — Gusto, ADP, manual, QuickBooks payroll)
2. Select the target platform in the first 30 days — do not let subsidiaries evaluate independently
3. Migrate all subsidiaries to the target platform by Day 60 — this is operationally disruptive for 2 weeks and fine the other 10 weeks
4. Standardize technician job titles and comp structures — this is the political work; do it early while the relationship capital from close is still fresh

Layer 4: Dispatch & CRM

What "standardized" looks like: All subsidiaries using the same field service management platform (ServiceTitan, BuildOps, or equivalent). Job types, service categories, and opportunity stages defined platform-wide. Customer records deduplicated. Maintenance agreement tracking consistent across all entities.

Cost of skipping it: You cannot measure call booking rate, job close rate, or maintenance attach rate across the portfolio. Every dispatch system generates revenue data differently. You have no visibility into cross-sell opportunities across subsidiaries. Your acquisition thesis included cross-sell synergies — those synergies live in unified CRM data.

Quick-win playbook:

1. Standardize on one FSM platform — if the platform has a preferred partner, negotiate platform pricing (usually 30–40% below list for multi-entity deployments)
2. Define the job taxonomy before migration: every trade, every service type, every job category. This taxonomy drives revenue reporting forever. It cannot be an afterthought.
3. Migrate one subsidiary first (the most technically capable one) — use their implementation as the template for all others
4. Do not go live on a new FSM during peak season — sequence acquisitions and migrations around seasonality

Layer 5: Financial Close Cadence

What "standardized" looks like: Every subsidiary closes books by the 5th of the following month. Platform financial package published by the 10th. LP reporting out by the 15th. No exceptions, no "we're a little behind this month."

Cost of skipping it: You cannot run a portfolio. You're constantly waiting for one subsidiary to close so you can publish consolidated financials. Board meetings get postponed. Lenders see stale data. When the 9th subsidiary closes, the 3-week close that was annoying at 3 entities becomes a 6-week disaster at 9.

Quick-win playbook:

1. Set the close calendar on Day 1 — it is non-negotiable from the moment of acquisition
2. Identify the bottlenecks for each subsidiary (most common: inventory reconciliation, A/R reconciliation, payroll accrual timing)
3. Assign a platform finance resource to shadow each subsidiary's close for the first 3 months — not to do it for them, to understand the friction and fix it
4. Build a close checklist in your project management tool — same checklist, every entity, every month

The Week-by-Week 100-Day Plan

This is the actual sequencing. Not what you aspire to in the board deck. What the operating partner has to own.

The Integration Debt Trap

Here's what the 18-month integration drag actually looks like from the inside.

Platform closes acquisition 1 in January. Integration team is small; they let subsidiary 1 keep running QuickBooks while they focus on acquisition 2. Acquisition 2 closes in April — same pattern. By October, they have 5 subsidiaries, all on different systems, all with different close dates, all computing margin differently.

Now they need to standardize. But subsidiary 1's bookkeeper has been doing it "her way" for 8 months and resists change. Subsidiary 3's FSM data is so degraded it needs manual reconstruction. Subsidiary 4's COA is so idiosyncratic that the mapping exercise alone takes 6 weeks. And the platform is trying to do all of this simultaneously while managing normal business operations across 5 entities.

This is integration debt. It compounds.

RollForge is purpose-built for PE-backed trade service portfolios. Unified financial visibility across every acquisition — from Day 1.