Sponsor-backed platform · ~$95M add-on acquisition · two operating brands

Integrating an acquisition without stalling either business

An integration architecture built before close held both businesses' service levels through the transition and captured synergy nine months early.

Disciplines deployed: FOUNDATION → SIMPLIFY → LEAD → GROW
Measurement window: 12 months from close
Measures reported: 4

Condition 05 of eight

A major transition is approaching

Succession, exit or integration is on the horizon. Value walks out with the people who held it in their heads.

All eight conditions

Present reality

A prior add-on had consumed eighteen months of executive attention and lost key people. The next acquisition was already under LOI, with an integration plan that existed only as a task list.

Constraint

Integration was scoped as a project to be run after close instead of an operating model to be decided before it, so every consequential question arrived as a surprise with a deadline.

Intervention — architecture installed

Pre-close integration architecture — target operating model, decision rights across both brands, retention design for named critical roles, and a gated integration cadence with evidence required at each gate.

FOUNDATION → SIMPLIFY → LEAD → GROW

Mapped to the operating system

What was architected inside each discipline, and the measured consequence. Disciplines held out of scope are shown with the reason — nothing is implied by omission.

1. FOUNDATION
Build
Loaded in this engagement
Target operating model and decision rights across both brands decided before close, not after.
Result: Executive hours a week on integration escalations 26 → 7 (−19 hrs).
FOUNDATION →
2. SIMPLIFY
Focus
Loaded in this engagement
One way of working chosen per core process — neither brand's habit adopted by default.
Result: Service level held within 1 pt through transition, against an 11-pt drop on the prior add-on.
SIMPLIFY →
3. LEAD
Execute
Loaded in this engagement
Gated integration cadence with evidence required at each gate, and retention design for named critical roles.
Result: Retention of named critical roles at 12 months 64% → 96% (+32 pts).
LEAD →
4. GROW
Scale
Loaded in this engagement
Commercial synergy sequenced behind the operating model so cross-sell was offered only where delivery could carry it.
Result: Full synergy capture in 12 months against 21 on the prior add-on (−9 months).
GROW →

ARC™ — the renewal loop around all four

The integration architecture is now the platform's standard playbook, re-read after each add-on.

ARC™ →

Measured result — what moved, and by how much

Sponsor-backed platform · ~$95M add-on acquisition · two operating brands — measured change over 12 months from close
Measure	Before	After (12 months from close)	Change
Time to full synergy capture	21 months (prior add-on)	12 months	−9 months
Retention of named critical roles at 12 months	64% (prior add-on)	96%	+32 pts
Service level through transition	dropped 11 pts (prior add-on)	held within 1 pt	no material dip
Executive hours per week on integration escalations	26 (prior add-on)	7	−19 hrs

Before → after, measure by measure · 12 months from close

Time to full synergy capture
−9 months
Before21 months
After12 months
Standardized against Time to full synergy capture — Capture measured against the signed synergy register.
Retention of named critical roles at 12 months
+32 pts
Before64%
After96%
Standardized against Retention of named critical roles — Named role list fixed before close in both transactions.
Service level through transition
+10 pts
Before−11 pts
After−1 pts
Standardized against Service level held through change — Worst monthly deviation from pre-close service level.
Executive hours per week on integration escalations
−19 hrs
Before26 hrs
After7 hrs
Standardized against Leader hours per week on operational escalation — Calendar-sampled over four consecutive weeks.

The integration architecture is now the platform's standard playbook for the next acquisition, owned internally.

Transfer — what the client now owns

The platform's operating leaders own the integration architecture and run the gates themselves on subsequent add-ons.

Compass leaves business architects, not dependency.

Client identities, brands, and locations are withheld under confidentiality. Metrics are client-reported and measured over the window shown; they describe those engagements and are not a projection of results for any other enterprise.

Start with your own present reality

Every engagement above began with an honest read of the architecture already producing the results. Score yours, or schedule a conversation.

Schedule a callGovernance readiness diagnostic