Value creation in a deal is not a slogan; it is a dated, costed, and evidenced plan to expand revenue, lift CM2, accelerate cash, and mitigate risk within the hold period. In commercial due diligence, your job is to separate underwritable synergies from wishful thinking, translate them into driver‑level edits in the model (Chapter 14), and hard‑wire governance so they actually show up in the P&L. This chapter focuses first on revenue synergies—the ones that excite Investment Committees and unsettle competitors—and then (later in the chapter) on cost, working‑capital, and strategic value levers. Throughout, we keep to the same segmentation used in Chapters 6–13 and the same definitions of realized price and CM2, so numbers travel cleanly from thesis to term sheet to Day‑1 plans.
15.1 Revenue Synergy Identification Guide
Revenue synergies are not “+5% on top.” They are specific motions—cross‑sell, up‑sell, bundling, channel and geo extension, price power from a stronger value proposition, and new logos unlocked by credibility or ecosystem—that you can evidence, price, and staff. The output of this guide is a portfolio of Revenue Synergy Cards with attach rates, timing, cost, owners, and risks, and a consolidated Synergy Bank you can plug into the driver model.
Principles to anchor before you start
- No averages. Work by segment × route‑to‑market × region × product family (Chapter 6)
- Commercial physics. Tie every dollar to a customer action (conversion, attach, re‑rating) and to operating constraints (capacity, SLOs, compliance).
- Risk‑adjusted math. Present base/low/high, clear gates, and probabilities. Cannibalization and churn risk are defaults, not caveats.
- Clean‑team and antitrust. Pre‑close, share only aggregated, non‑customer‑identifiable data. No coordination on pricing, customer allocation, or go‑to‑market execution until approvals.
- Hold‑period discipline. If it cannot move cash inside your horizon, it belongs in “strategic options,” not in the base synergy case.
Step‑by‑step identification (from blank page to a defendable synergy bank)
1) Fix the scope and success criteria
Write one sentence that constrains ambition: “We will underwrite only those revenue synergies that (i) clear legal/antitrust and customer‑consent gates, (ii) show evidence of right‑to‑win, (iii) lift CM2 (not just revenue), and (iv) produce cash within 18–36 months.” Confirm segmentation and the model hooks you will use (attach rate, conversion uplift, realized‑price bps, cycle‑time deltas, CAC/payback changes).
2) Assemble the evidence pack (request once; reuse everywhere)
- Customer & product masters for both firms: top‑200 accounts, segments/tiers, current SKUs/modules, active routes, contracts (terms, MFN, exclusivities, non‑solicits), renewal dates.
- Commercial telemetry: win/loss and reason codes, discount distributions, price fences, CPQ rules, billing/entitlement accuracy, expansion/cross‑sell history, cohort retention (Chapter 6.3).
- Channel & ecosystem: partner tiers and certifications, marketplace listings and ranks, attachments of “must‑have” integrations (Chapters 7.1, 12.2).
- Operational constraints: capacity ladders and SLOs (10.2–10.3), onboarding/implementation throughput, regulatory/attestation status (11.1, 12.3).
- Pricing and unit economics: pricing pages and deal desks, realized price corridors (8.2), CM2 by segment/channel (13.2).
- Legal & policy gates: antitrust counsel memo, clean‑team protocol, data‑sharing limits, channel/marketplace policy constraints (11.4).
3) Name the revenue synergy families (and what proves each)
- Cross‑sell: sell Company B’s SKUs to Company A’s installed base (and vice versa). Proof: overlap accounts, use‑case adjacency, integration readiness, lighthouse references, entitlement/billing ability to invoice accurately at launch.
- Up‑sell/rate‑card re‑rating: move accounts to higher‑value tiers/bundles on renewal. Proof: WTP evidence, feature usage/telemetry, cohort uplift from pilots, price fences and DOA ready (8.2).
- Bundling & packaging: combined offer with clearer value narrative and higher realized price. Proof: A/B price tests, attach of complementary modules, churn hazard unchanged in trials.
- Geo expansion: take proven offers into regions using the other party’s footprint. Proof: regulatory/certification readiness, in‑country data/service levels, partner coverage, localized content.
- Channel leverage: push through the other party’s channels (distributors, resellers, marketplaces, hyperscaler co‑sell). Proof: partner capacity and incentives, listing eligibility, private‑offer mechanics.
- Ecosystem lift: integration catalog closes competitive gaps and improves win rate. Proof: connector attach in new wins, time‑to‑integration < target, co‑marketing slots.
- Brand/credibility effects: larger balance sheet and references increase conversion and shorten cycles. Proof: win‑rate and velocity lifts in like‑for‑like segments after announcement (normalize for competitor reaction).
- Innovation acceleration: near‑term launches become sellable earlier due to combined assets. Proof: Stage‑gate evidence from Chapter 12.4 (lighthouse, SLO impact, entitlement accuracy).
4) Build the Cross‑Sell & Up‑Sell Heatmap (qualify before you quantify)
For each segment × route × region, rate the motion on a 0–5 Right‑to‑Win scale using evidence. Score against: problem/fit, proof (references/telemetry), integration/entitlement readiness, channel reach, legal/consent status, and capacity headroom. Anything <3 is upside only or a strategic option; do not load it into the base case.
5) Quantify with simple, auditable equations
Use the smallest number of moving parts; keep units clear. Examples:
- Cross‑sell revenue (for a given segment/channel):
Eligible base (accounts or seats) × Attach rate × Adoption curve × Realized net price.
CM2 contribution = Revenue × CM2% − Incremental CTS (implementation/support) − Incremental CAC/program spend. - Up‑sell/re‑rating:
Renewal base × Adoption share × ΔRealized price (bps) × Retention factor (1 − churn hazard uplift). - Channel leverage:
Partner‑sourced pipeline × Win‑rate uplift × Realized price × CM2% − MDF/commission. - Geo expansion:
In‑region footprint (eligible TAM share × access via channel) × Conversion × Realized price − localization/serve CTS. - Brand/velocity:
Pipeline coverage × ΔStage conversion × ΔCycle time → time‑phased bookings change → revenue recognition per model rules.
6) Bake in cannibalization, churn hazard, and capacity limits
- Cannibalization: if bundle A replaces high‑margin SKU X, subtract displaced CM2.
- Churn hazard: apply uplift factors where price re‑ratings or migrations risk attrition (use elasticity and VoC from Chapters 6.4 and 8.2).
- Capacity/SLO: cap bookings where implementation, support, or platform reliability (12.1) would be breached; include SLA credits if you push too fast (10.3).
7) Convert to risk‑adjusted economics (rNPV) and timing
For each initiative, compute risk‑adjusted cash flows by stage:
- rNPV
- Use evidence‑based stage gates: sellable narrative signed off, entitlement/billing accuracy ≥99.5%, partner listing live, certification complete, capacity rung booked (10.2).
8) Map to model hooks (Chapter 14)
Create a Synergy‑to‑Model Map so finance can update one set of cells:
- Attach rate uplift (by segment/channel).
- Realized price delta (bps) and discount guardrail edits.
- Stage conversion and cycle‑time improvements; seller productivity.
- Channel/partner mix share shift; take‑rate changes.
- Implementation throughput; support contact rate deltas and minutes per contact for CTS.
- Working‑capital side effects (prepay mix, DSO for new channels, processor reserves for marketplaces).
- One‑time integration spend and recurring opex to sustain the motion.
9) Design the front‑line motion (what people will actually do)
- Cross‑sell blitz: account mapping (top‑100, named owners on both sides), joint discovery scripts, mutual NDAs where needed, three lighthouse offers with fixed “land” scopes, 30‑day pilot SLAs, success metrics, and reference harvesting.
- Re‑rating plan: renewal calendar with 120‑/90‑/60‑day tasks, new fences and DOA, CPQ templates, customer‑ready value calculators, and guardrails for vulnerable cohorts.
- Bundle launch: SKU and entitlement harmonization, FAQs and objection handling, price realization dashboards (8.2), and billing dry‑run tests (zero credits tolerated).
- Channel leverage: partner enablement kit in 2 pages, MDF offers, demo/POC environment, private‑offer mechanics, and certification path with dates.
- Geo play: localization checklist (content, tax, privacy, routing), support schedule, in‑country partners, data residency statement (12.3).
- Ecosystem motion: connector catalog with two “must‑have” integrations prioritized, listing/certification plan, and a migration toolkit to lower switching friction.
10) Codify risks and dis‑synergies (and cost them)
- Customer conflict or MFN clauses → require carve‑outs or renegotiations; treat as timing gates.
- Channel conflict (distributors vs. direct; marketplace delist risk) → scenario a downgrade and haircut revenue in that route; add policy covenants (11.4).
- Forced migrations → add churn hazard and CTS spikes; delay re‑rating until support burden normalizes.
- Cultural/comp plan friction → unless incentives change, cross‑sell rarely happens; bake comp plan changes into opex and timing.
- Quality or SLO drift during integration → add SLA credits and NRR hits (10.3, 12.1).
Turn each into Revenue‑at‑Risk (RaR) and Margin‑at‑Risk (MaR) corridors and subtract from rNPV.
Copy‑ready templates (paste straight into your workspace)
A) Revenue Synergy Card (one per initiative × segment/route/region)
- Name & owner; why now (deal‑thesis link).
- Mechanism: cross‑sell / up‑sell / bundling / channel / geo / ecosystem / brand / innovation.
- Right‑to‑win (0–5) and evidence links (references, telemetry, certifications, partner status).
- Math: eligible base; attach/adoption; realized‑price delta; CM2%; incremental CTS/CAC; timing.
- Risks: cannibalization, churn hazard, channel conflict, capacity/SLO, legal/policy gates.
- Gates: entitlement/billing accuracy, listing/certification, capacity rung booked, DOA/fences live.
- Economics: ΔRevenue, ΔCM2, ΔCash (L12M, Y1, Y2); rNPV; confidence label (H/M/L).
- First 90 days: top 3 actions with cost and date; KPIs; exit criteria for promotion or kill.
B) Cross‑Sell & Up‑Sell Heatmap (fields to fill)
- Segment × route × region; overlap count; integration readiness; consent/contract status; partner reach; capacity headroom; Right‑to‑win score; priority flag (P1/P2/P3).
C) Bundle Canvas (fields to fill)
- Target jobs and segments; included SKUs/modules; fences and surcharges; list and target realized price; value narrative; migration path; billing/entitlement mapping; support SLAs.
D) Channel Leverage Plan (fields to fill)
- Target partners/marketplaces; listing/certification gaps; private‑offer mechanics; co‑sell alignment; MDF and spiffs; compliance thresholds (return, late‑ship, chargeback); pipeline targets.
E) Synergy‑to‑Model Map
- Parameter cells: attach, conversion, cycle time, realized price bps, channel share, implementation throughput, support minutes/contact, DSO/processor reserve deltas; one‑off and run‑rate costs.
Metrics, governance, and incentives (make it real)
- KPI set: attach rate by segment; NRR uplift; realized price vs. corridor; bookings from partner/marketplace; time‑to‑first‑$; implementation throughput; billing credits (should be ≈0); CM2 per order/account.
- Cadence: weekly stand‑up for the top three initiatives; monthly “Synergy Bank” review with CFO and CRO; quarterly re‑estimates (rNPV and confidence labels).
- Incentives: comp plan changes (cross‑sell credit, renewal re‑rating credit, partner‑sourced credit); spiffs with sunset dates; exec bonuses tied to ΔCM2 and cash, not just bookings.
- Controls: antitrust guardrails; price fence governance; CPQ/doa enforcement; policy/watchlist from Chapter 11.4 baked into playbooks.
Early‑warning indicators (by motion)
- Cross‑sell: attach < target in first 30 accounts; implementation backlog > capacity rung; rising support contact rate on new bundles.
- Re‑rating: discount depth creeps up; billing credits or entitlement errors appear; churn early‑warning (Chapter 6.4) flashes on targeted cohorts.
- Channel: penalty or delist warnings; paid placement dependence rises; partner pipeline stalls versus enablement calendar.
- Geo: delays on residency/attestations; translation/compliance gaps; first‑response times miss targets.
- Ecosystem: connector attach < plan; certification slips; migration friction (hours/cutover) higher than modeled.
Red flags—and the immediate response
- No entitlement/billing readiness → move synergy to upside only; fix CPQ/billing/entitlement as a Day‑1 condition; do not run a bundle without invoice accuracy ≥99.5%.
- Capacity/SLO thin → cap pilots; add a reliability/capacity sprint to the 90‑day plan; reflect SLA credits and NRR drag in the model.
- Channel conflict → freeze direct offers in contested tiers; renegotiate reseller carve‑outs; model delist risk and set policy covenants.
- Price‑led synergy with weak VoC → run two pricing tests immediately; hold re‑rating out of the base until evidence shows realized price holds without churn spike.
- Gun‑jumping risk → route all pre‑close actions through counsel and the clean‑team; keep any joint customer contact to publicly available information and approved scripts.
90‑day lift plan (moves that change cash fast)
- Top‑100 cross‑sell: joint account mapping, 30‑day lighthouse offers, reference harvesting; attach dashboard live.
- Re‑rating pilots: two fences + DOA live, renewal calendar sequenced, value calculators in reps’ hands, first 20 renewals coached.
- Channel enablement: publish two listings/certifications; activate private offers; run first partner webinar; MDF tied to pipeline and win‑rate metrics.
- Bundle readiness: SKU and entitlement harmonized; billing dry‑run pass; customer comms and FAQs out; support scripts loaded.
- Capacity lock: book first capacity rung (10.2); publish SLOs and error‑budget gates (12.1).
- Controls: clean‑team protocol enforced; pricing fence governance and CPQ rules pushed; watchlist (11.4) monitored weekly.
72‑hour sprint plan (from blank page to an underwritable synergy bank)
- Day 0: Freeze scope, segmentation, legal guardrails; issue a single evidence request; draft Heatmap skeleton and Synergy‑to‑Model Map.
- Day 1: Fill Heatmap with right‑to‑win scores; create 8–12 Revenue Synergy Cards for P1 motions; run quick math (attach, adoption, realized price bps, CM2).
- Day 2: Quantify cannibalization, churn hazard, and capacity caps; compute rNPV corridors; draft front‑line motions and 90‑day actions; wire parameters into the model (Chapter 14).
- Day 3: Publish the Synergy Bank with owners, costs, and dates; set KPIs and cadence; propose term‑sheet protections (indexation, channel policy covenants, certification CPs, earnouts tied to NRR or realized price).
Acceptance criteria for a decision‑grade revenue synergy assessment
- Cross‑Sell & Up‑Sell Heatmap complete with evidence‑based right‑to‑win scores.
- 8–12 Revenue Synergy Cards with attach/adoption, realized price bps, CM2, timing, risks, gates, and owners.
- Cannibalization, churn hazard, and capacity/SLO caps quantified; rNPV corridors computed; model hooks wired (14.1).
- 90‑day plan issued with costs and dates; KPI dashboard defined; clean‑team and antitrust guardrails documented.
- Investment Committee can see which dollars depend on which gates, who owns them, and what happens to cash and CM2 if a gate slips.
Use this guide and “revenue synergy” becomes a precise set of customer moves—evidenced, gated, and priced—not a percentage you hope will appear after close.
15.2 Cost Synergy Estimation Template
Cost synergies are not a percentage haircut on expenses. They are specific, durably repeatable cost removals—in COGS, Cost‑to‑Serve (CTS), and SG&A—that you can price, phase, and govern. In commercial due diligence, your task is to (i) baseline cost with the same segmentation used for revenue and margin, (ii) identify concrete levers (procurement, footprint, operations, tech, cloud, support, G&A), (iii) quantify run‑rate savings and one‑time costs, (iv) haircut for execution risk and dis‑synergies, and (v) wire the result directly into the driver‑based model (Chapter 14) and the CM2 logic (13.2). Treat savings as changes in drivers (rates, volumes, yields, minutes, bps) rather than as line‑item decrements. That is how they survive scrutiny—and how they show up in cash.
Freeze definitions and guardrails (before any math)
- Run‑rate vs. in‑period savings: Run‑rate = steady‑state monthly reduction once the lever is fully live; In‑period = the portion realized in calendar time (ramp‑up and slippage matter).
- Gross vs. net: Always present savings net of: implementation costs, stranded fixed cost, inflation/market drifts, and reinvestment required to protect service levels.
- Scope and segmentation: Same cuts as Chapters 6–13 (product family × route‑to‑market × region × customer tier). Separate COGS, CTS, and SG&A.
- Clean‑team and antitrust: Pre‑close, only aggregated and anonymized data can be shared; no joint vendor negotiations or price coordination without counsel and a signed clean‑team protocol.
- Hold‑period discipline: Only include savings that turn into cash inside the horizon (typically 18–36 months). Put the rest into “strategic options.”
Step‑by‑step: from blank page to an underwritable cost‑synergy bank
1) Baseline the cost—build one spend truth
Create a clean, comparable spend cube for both companies:
- By category: direct materials/components, freight/inbound duty, manufacturing conversion, packaging, 3PL/warehouse, parcel/LTL, payment processing & fraud, cloud/compute/storage/egress, third‑party APIs/data, support/success/BPO, software/SaaS licenses, contractors, facilities & utilities, insurance, audit/advisory, marketing programs, HR/benefits, IT/telecom, travel.
- By vendor: top‑200 suppliers, rate cards, rebates, step‑down discounts, term sheets, auto‑renew dates, termination penalties.
- By site and function: plants/DCs/call centers, seat counts, utilization, fixed vs. variable split, lease terms, maintenance schedules.
- By unit driver: $/lb, $/shipment, $/order, $/API call, minutes/contact, $/user/month, $/kWh, $/sq ft.
Normalize for constant currency, organic perimeter, and seasonality. Reconcile to GL totals and the CM1/CM2 tree (13.2).
2) Identify the synergy pools (what typically pays fast)
- Direct procurement (materials & services): price harmonization to best‑in‑class, supplier rationalization, volume aggregation to unlock tier breaks and rebates, indexation alignment, should‑cost and VA/VE redesign, dual‑sourcing for bargaining power.
- Logistics & network: carrier rationalization, multi‑lane re‑bids, DIM/packaging optimization, mode shifts, DC consolidation, slotting/picking productivity, cross‑dock and pool‑distribution where density allows.
- Manufacturing & operations: footprint consolidation (close/mothball/repurpose sites), changeover and batch‑size optimization, labor productivity, yield/scrap improvement, energy and maintenance programs, automation where payback <24 months.
- Cost‑to‑Serve / post‑purchase: returns/refurb loop efficiency, policy fixes (restocking, free‑shipping thresholds), support deflection (self‑serve, knowledge base), entitlement and billing accuracy to eliminate credits.
- Cloud, data & software (“FinOps”): reserved/savings plans, right‑sizing, de‑duping environments, storage lifecycle policies, egress avoidance patterns, API plan optimization, SaaS/license rationalization (remove overlaps, consolidate tiers).
- SG&A overlaps: finance, HR, legal, IT help desk, facilities, audit/advisory, insurance, duplicate public‑company costs (if take‑private), overlapping management layers.
- Sales & marketing efficiency (handle with care): agency consolidation, ad‑tech/tool stack simplification, event portfolio rationalization. Only book savings that do not degrade conversion, win rate, or NRR—pair with 9.1/9.3 diagnostics.
- Payment rails & fraud: blended bps reduction from volume tiers, chargeback program optimization, fraud tooling to reduce losses and manual review minutes.
- Insurance & benefits: brokerage consolidation, captive structures, benefit plan harmonization (flag retention and wage/benefit dis‑synergies explicitly).
3) Quantify each lever with simple, auditable equations
Use driver math; avoid opaque percentages.
- Procurement (rate card):
Savings = Volume_consolidated × (Old rate − New rate) × Coverage% − Lost rebates + Rebate uplift.
Implementation cost = sourcing event cost + testing/qualification + dual‑running. Timing = contract notice + ramp weeks. - Yield & scrap (manufacturing):
Savings/month = (Scrap_baseline − Scrap_target) × Material_cost_per_unit × Units − Rework/QA added cost. - Labor productivity (ops/support):
Savings = FTE_reduction × Fully loaded cost × Realization% − Severance/retention − Backfill contractors.
Realization schedule: 0% (Month 0) → 50% (Month X) → 100% (Month Y) after notice and handover. - Freight & parcel:
Savings = Shipments × Avg weight/zone mix × (Old $/shipment − New $/shipment) − Accessorial drift.
Add packaging/DIM fixes: ΔDIM × Rate_card × Shipment count. - Cloud & APIs:
Savings = Usage × (On‑demand rate − Reserved rate) × Reserved coverage% + Rightsizing delta − Commitment premiums.
API plan: Calls × (Old $/call − New $/call) − overage minimums. - Returns/refurb:
Savings/order = (Return_prob_baseline − Return_prob_target) × (Reverse_log_cost − Recovered_value) + ΔSupport minutes × rate. - Payment fees:
Savings = Card‑processed VRR × Δbps − Additional reserves/holdback cost (cash drag is separate). - Facilities & footprint:
Run‑rate savings = Fixed costs eliminated (rent, utilities, security) − stranded overhead retained.
One‑time costs = lease break fees + make‑good + relocation/move + asset write‑offs + IT cutover.
Every equation must carry units, coverage, ramp, and confidence (H/M/L).
4) Build the realization curve (cash, not just run‑rate)
For each lever, specify monthly phasing with gates:
- Procurement: RFP/negotiation (30–90 days), notice periods (30–180), vendor onboarding and QA (2–8 weeks).
- Footprint: board approval, works‑council/union process, notice, lease exit, move/commissioning (often 6–18 months).
- Cloud/IT: commit purchase (instant), re‑platforming (4–16 weeks), decommission legacy (8–24 weeks).
- People: org design, notices, knowledge transfer (4–16 weeks), severance/retention payouts timing.
- Policy/CTS: comms and policy change (2–6 weeks), system/checkout updates (2–8 weeks), effect on demand/NRR monitored.
Use S‑curves or step functions; avoid straight lines unless justified.
5) Net it down—implementation costs and unavoidable offsets
- One‑time: severance and retention, program management/IMO, legal and advisory, IT integration, lease exits/make‑goods, relocation, dual‑run costs, certification/validation, change management and training.
- Stranded cost: overhead that persists after consolidation (e.g., corporate utilities, insurance minima); model the bleed‑off plan or keep it as a residual.
- Inflation drift: commodity, energy, wage changes that partially offset savings.
- Reinvestment: reliability or quality spend to protect service levels; FinOps tooling; QA staffing during consolidation.
6) Dis‑synergies and risk haircut (treat as first‑class citizens)
- Service‑level degradation: higher contact rates, SLA credits, OTIF penalties.
- Wage/benefit harmonization: upward adjustments due to parity, union or statutory rules.
- Supplier power: fewer vendors can mean worse terms or exposure to single‑source risk.
- Channel/partner friction: loss of MDF, co‑op funds, or tier benefits.
- Attrition & morale: productivity dip during transition.
Convert to Margin‑at‑Risk (MaR) corridors and subtract from savings.
7) Turn savings into risk‑adjusted NPV (rNPV)
For lever i with monthly net savings Si,tS_{i,t}Si,t, probability pip_ipi of clearing each gate, and discount rate rrr:
- rNPVi=∑t(Si,t×∏g≤tpi,g)/(1+r)t − one‑timei\text{rNPV}_i = \sum_t \left( S_{i,t} \times \prod_{g \le t} p_{i,g} \right) / (1+r)^t \;-\; \text{one‑time}_irNPVi=∑t(Si,t×∏g≤tpi,g)/(1+r)t−one‑timei.
Rank by ΔCM2/$, ΔCash/$, and time‑to‑impact.
8) Wire the savings into the model (Chapter 14 hooks)
- COGS: material rate deltas, yield/scrap factors, labor rates and hours, inbound freight, energy/utilities.
- CTS: parcel/LTL rate cards, return probability and reverse‑log cost, support minutes and rate, payment bps, cloud/API unit costs and reserved coverage.
- SG&A: headcount/FTE by function with ramp, SaaS/license seats × $/seat/month, facilities fixed costs, audit/insurance.
- Working capital side‑effects: DIO/DSO/DPO changes from vendor and policy moves; processor reserves.
- One‑time costs & capex: severance, lease exits, integration spend, automation capex (with depreciation or direct cash impact).
Copy‑ready templates (use verbatim)
A) Cost Synergy Card (one per lever × segment/channel)
- Name & owner; business rationale (why it exists).
- Baseline & unit driver: current rate/volume/yield; source link.
- Mechanism: rate reduction, vendor consolidation, yield, labor productivity, footprint, cloud/IT, CTS policy, SG&A overlap, insurance/benefits, payment bps.
- Math: formula with units; coverage%; monthly ramp; run‑rate at steady state.
- Economics: ΔCM1/ΔCM2, ΔOpex, ΔCash by month (Y1/Y2), one‑time costs, stranded cost.
- Risks/offsets: MaR, dis‑synergies, service guardrails.
- Gates & dates: approvals, notices, certifications, works‑council, IT cutover.
- Confidence (H/M/L); dependencies (legal, vendor, system).
- KPIs: unit cost trend, contact rate, SLA credits, error budgets, savings realized vs. plan.
B) Spend Cube Request (clean‑team friendly fields)
- Vendor, category, site/function, GL account; 24‑month monthly spend; rate card terms and tiers; volumes and units; rebates; start/end dates; termination penalties; contacts; currency.
C) Procurement Event Plan (for each major category)
- Category & scope; market structure & benchmarks; strategy (consolidate vs. split); lotting; should‑cost; timeline; governance; risks; fallback; savings & rNPV.
D) Footprint Decision Guide
- Demand by region (3‑year), site cost curve, SLO targets, labor availability, logistics cost to serve, lease terms, automation options, capex, one‑time costs, time to close/open, regulatory/works‑council steps, stranded cost plan.
E) FinOps Savings Card (cloud & APIs)
- Baseline usage by service; on‑demand vs. reserved share; $/unit; commitment plan; right‑sizing actions; decommission plan; savings math; risk (lock‑in, performance); owner & dates.
F) SG&A Consolidation Stack
- Function, baseline FTE & cost, overlaps, retained model, systems to keep/retire, TSA scope and duration, severance/retention, compliance (SOX, payroll, benefits), ramp and controls.
G) Synergy‑to‑Model Map
- Exact driver cells in 14.1 for COGS, CTS, SG&A, working capital, one‑time costs; version and change log.
Governance, tracking, and “quality of savings”
- Synergy Bank: a single list of levers with run‑rate and in‑period cash, one‑time costs, probability bands, owners, and dates.
- Quality of Savings (QoS): book only savings that hit P&L and cash; exclude budget cuts that reappear as service loss or backlog.
- Controls: GL cost centers and project codes to capture savings and one‑time costs; monthly variance review led by the CFO/IMO; independent verifier sign‑off.
- Cadence: weekly top‑five lever stand‑up; monthly bank refresh; quarterly rNPV re‑score.
Industry nuances you must account for
- Healthcare & life sciences: cGMP validation and QA overhead; change‑control costs; GPO contracts; device/clinical quality risks.
- Fintech & payments: processor reserve/holdback side‑effects; PCI scope; fraud loss elasticity to tooling spend.
- SaaS & data: cloud vendor commit terms, egress penalties, multi‑tenant isolation limits; de‑duping SaaS while protecting entitlement/billing accuracy.
- Retail/CPG & marketplaces: OTIF/compliance penalties; returns policy economics; paid placement vs. take‑rate; seasonality locks on network changes.
- Industrial & distribution: union/works‑council processes; safety and warranty exposure; duty regime shifts with footprint moves.
- Energy‑intensive: hedging for power/fuel; carbon/EPR overlays (11.2) that affect net savings.
Early‑warning indicators (monitor weekly/monthly)
- RFP/contract slippage vs. plan; vendor pushback or price‑increase notices.
- Works‑council/union delays; retention risk on critical roles.
- SLA credits, contact rate, OTIF drift during CTS or footprint changes.
- Cloud on‑demand share rising; API overage bills; postponed decommissions.
- Stranded cost not bleeding off; lease‑exit negotiations stall.
- Inflation or FX offsets eroding promised savings.
Red flags—and immediate responses
- Savings depend on service cuts. Response: move to upside‑only; add deflection/automation first; enforce SLO guardrails.
- No GL tie‑out. Response: halt claims; implement cost‑center tracking; reconcile to 13.2 bridges.
- Footprint closures with no stranded‑cost plan. Response: add a bleed‑off schedule; delay booking run‑rate.
- Cloud “savings” without commits deployed. Response: execute reservation now; publish coverage; set unit‑cost dashboards.
- Headcount reductions without process redesign. Response: implement standard work/automation; freeze FTE claims until throughput proof.
90‑day cost‑synergy lift plan (moves that change cash fast)
- Procurement quick wins: re‑bid top five categories; align to best‑in‑class rate cards; sign two rebate programs; lock indexation where favorable.
- Logistics: consolidate carriers; launch packaging/DIM fixes; renegotiate fuel/GRI surcharges on key lanes.
- FinOps: convert top services to reserved/savings; right‑size two largest workloads; downgrade or remove three overlapping SaaS tools.
- CTS policy: update free‑shipping threshold; roll out return triage; publish knowledge base and deflection flows for top five contact drivers.
- Payment fees: negotiate blended bps with processor(s); tighten chargeback program; deploy 3‑D Secure where ROI positive.
- Footprint & people: decide site rationalization (go/no‑go) with a dated plan; finalize org design for back office; communicate retention packages.
- Controls: GL tracking live; synergy dashboard launched; IMO cadence running.
72‑hour sprint plan (from zero to a defendable cost‑synergy bank)
- Day 0: Freeze definitions; stand up the spend cube; publish clean‑team protocol; reconcile to GL and CM2 tree.
- Day 1: Identify pools and draft 12–18 Cost Synergy Cards; quantify with unit math; set ramps and gates; estimate one‑time costs.
- Day 2: Haircut for dis‑synergies and MaR; compute rNPV corridors; wire hooks into the 14.1 model (COGS, CTS, SG&A, WC, one‑times).
- Day 3: Publish the Synergy Bank with owners and dates; set KPIs and governance; propose term‑sheet translations (TSAs and pricing/commit terms with critical vendors; carve‑outs; indemnities for known exits; covenants on service levels and inventory).
Term‑sheet levers to protect realization
- TSAs: precise scope, service levels, and price caps for back‑office and IT; taper plan.
- Vendor & platform contracts: preserved rates or step‑downs; indexation clauses; termination/assignment consents; API plan continuity.
- Footprint: landlord consents; make‑good caps; environmental/waste liabilities allocated.
- People: retention pools approved; severance funded; works‑council timing in CPs.
- Covenants: service‑level floors; inventory and lead‑time covenants during network changes; FinOps coverage milestones.
- Indemnities/escrows: known lease exits, early‑termination penalties, E&O/WIP exposures.
Acceptance criteria for a decision‑grade cost‑synergy assessment
- Spend cube reconciled to GL and the CM1/CM2 tree; constant‑currency and organic perimeter.
- 12–18 Cost Synergy Cards with unit math, ramps, one‑time costs, MaR haircuts, and confidence labels.
- Savings wired into the driver model (14.1) across COGS/CTS/SG&A/WC; cash and run‑rate shown; bridges reconcile to 13.2.
- Governance live: Synergy Bank, GL tracking, KPIs, cadence, and independent verification.
- Term‑sheet protections drafted for critical dependencies (TSAs, vendor terms, consents, covenants).
- Investment Committee can see who owns which dollars, when they land, what could slip, and how that would be mitigated.
Use this template and “cost synergy” becomes a portfolio of priced, phased, and governed changes to rates, yields, minutes, and fixed costs—visible in CM2 and cash, not just on a slide.
15.3 Integration Feasibility Checklist
Integration feasibility is the bridge between your synergy thesis and cash in the bank. It tests whether you can legally, safely, and economically combine (or tightly coordinate) the two businesses without breaking service levels, customer trust, or regulatory obligations. It also decides how much to integrate (full fusion vs. federation vs. interface), when to integrate (Day‑1, first 90 days, and beyond), and what it will cost in one‑times and execution capacity. Your output should be a single, decision‑grade view: a readiness heatmap, gated cutover plan, TSA blueprint, and a risk‑adjusted cost/benefit that plugs into the driver‑based model (Chapter 14). Treat this like an engineering safety case: define the minimum evidence needed to proceed, and refuse to make value promises that the integration cannot deliver within the hold period.
Start with the integration thesis (minimum viable integration)
Before you inventory tasks, answer three questions: Why integrate at all? How much is enough? What cannot break? Anchor on the value drivers you underwrote in Chapters 15.1 and 15.2 and choose the operating posture per domain:
- Fuse (single system/process/org now) when synergy depends on one way of working (e.g., one CPQ & billing engine to realize price, one warehouse network to reduce CTS, one PLG funnel to lift conversion).
- Federate (shared standards, separate stacks/orgs) when regulatory licenses, reliability, or time‑to‑cash argue for controlled autonomy.
- Interface (APIs, data pipes, or commercial agreements) when integration risk is high relative to value, or when you need an option to pivot.
Document these choices in your Integration Blueprint with the target state for each domain: Legal entities, People/Org, Product & Pricing, GTM & Channels, Operations & Supply Chain, Technology & Data, Finance & Tax, Risk & Compliance.
The feasibility checklist (workstream by workstream)
1) Legal, antitrust, and pre‑close guardrails
- Antitrust/merger control status, gun‑jumping boundaries, clean‑team protocol, scope of competitively sensitive data allowed pre‑close.
- Change‑of‑control notifications/approvals: sector regulators, data protection authorities, financial services, telecom, healthcare, defense/export.
- Entity strategy: keep/separate for licenses and customer contracts, tax nexus, and labor law.
- IP and OSS posture: assignments, third‑party consents, open‑source license compatibility, patent encumbrances.
- Cross‑border constraints: CFIUS/local equivalents; sanctions exposure; beneficial ownership updates.
2) Customer, contract, and commercial policy constraints
- Assignment/novation and consent clauses; MFN/price‑protection; exclusivity and non‑compete limits; notice periods; co‑terminus requirements.
- Service credits and SLAs transferability; support entitlements harmonization without breaching contracts.
- Key‑account plans and “no surprises” comms (timing and content pre‑ vs. post‑close).
- Channel/partner agreements: reseller/distributor veto rights, tiering consequences, MDF/coop cadence, vendor‑of‑record constraints.
3) Platform and marketplace policy compliance
- Take‑rates, penalties, and policy thresholds; multiple‑seller policies; brand registry/GS1 and listing ownership.
- On‑time in‑full (OTIF), late‑ship and return thresholds; listing migration/delist risk; private‑offer mechanics (cloud marketplaces).
- Evidence that combined offer meets rank/quality thresholds; paid‑placement dependency and caps.
4) Technology, data, and security (commercial lens)
- Target architecture: keep/migrate/retire for CPQ, billing/entitlement, payment rails, CRM/marketing ops, data warehouse/CDP, support stack, product/engineering toolchain, cloud & network.
- Identity & access: SSO/IAM strategy, customer identity merge, partner portals, least‑privilege mapping.
- Data migration: scope, data model mapping, data quality & dedupe, test cutovers, rollback plan; data residency & cross‑border flows.
- Privacy & security: DPAs, records of processing, DPIAs, SOC2/ISO 27001 alignment, HIPAA/PCI where applicable; incident response integration and breach notification logic.
- Reliability and SLOs: error budgets, capacity headroom, DR/BCP alignment; change‑freeze windows and deployment cadence.
- Third‑party dependencies: API plan terms, quota/overage risks; cloud commitments and FinOps savings plan.
5) Product, pricing, and packaging
- SKU/module mapping and de‑duplication; bundle design; price‑fence and guardrail harmonization; list vs. realized price corridors (Ch. 8.2).
- Entitlement and metering: feature flags, usage measures, seat definitions, migration grants.
- Migration plans: grandfathering, re‑rating rules at renewal, discount unwind cadence; communications and value calculators.
- Regulatory labeling/UDI (healthcare, devices), export controls, accessibility/localization requirements.
6) Go‑to‑market and channel operations
- Org design: seller/CSM coverage, territories, comp plans (credit for cross‑sell/re‑rating), partner account mapping.
- Funnel tooling: CRM objects and pipelines, stage definitions, attribution model, forecast hygiene.
- Enablement: playbooks, demos/POC environments, certifications; partner contracts and incentives aligned to the combined offer.
- Conflict policy: direct vs. channel and marketplace rules; escalation path; price parity where required.
7) Operations and supply chain
- Network design: DC/plant footprint, routing logic, carrier contracts, inventory positioning, S&OP cadence; quality system harmonization.
- Capacity ladders and bottlenecks (10.2); service SLOs and penalty ladders (10.3).
- SKU and packaging harmonization; EPR/packaging compliance by country; labeling and customs/tariff impacts.
- Returns/refurb loops and warranty policy integration; field service coverage.
- Vendor terms and assignments; VMI/consignment status; critical single‑source risk and mitigation.
8) Finance, tax, and treasury
- ERP/ledger consolidation, chart‑of‑accounts mapping, revenue recognition policies, close cadence, consolidation eliminations.
- Order‑to‑cash and procure‑to‑pay process design; credit & collections policy; deductions handling; processor reserves.
- Payroll, benefits, and statutory tax registrations; indirect tax/VAT, nexus, and exemptions; transfer pricing policy.
- Banking, liquidity, and controls (SOX if applicable); borrowing‑base integration for ABL.
9) People, culture, and change
- Org structure and decision rights (RACI); span of control targets; leadership selections and succession.
- Retention and severance plans; works‑council/union processes and timing; immigration/relocation constraints.
- Culture risks and rituals: communications cadence, values, manager toolkits, listening posts.
- Training: role‑based curricula for sellers, CSMs, support, finance, ops, and engineering.
10) Program governance and economics
- Integration Management Office (IMO) with workstream charters, RAID log, decision forums, and budget.
- Synergy tracking “bank”: each initiative with ΔRevenue/ΔCM2/ΔCash, one‑time costs, probability, owner, and date.
- TSA strategy and economics (see below); cutover decisioning (big‑bang vs. phased vs. “strangler”).
- Model hooks connected to 14.1; term‑sheet protections drafted for residual risks (indexation, covenants, CPs, indemnities, earnouts).
Go/No‑Go gates (evidence thresholds before each cutover)
Define Definition of Done checklists per domain. Do not proceed on hope.
- Customer & revenue:
- Entitlement/billing dry‑run accuracy ≥99.5% for affected SKUs or tiers.
- CPQ quotes match price fences and discount DOA; zero invoice credit defects in pilot.
- Cross‑sell playbooks tested with ≥10 lighthouse accounts; attach rate within ±20% of plan without discount creep.
- Technology & data:
- Data migration test: accurate records ≥99.9%; dedupe precision/recall ≥95/95; rollback tested.
- SLO headroom ≥15% at constraint; DR tested; on‑call runbooks merged.
- IAM/SSO cutover tested; least‑privilege confirmed for crown‑jewel data.
- Operations:
- DC or carrier switch simulated; pick/pack and routing KPIs within ±5% of baseline; returns loop working.
- Service desk: contact rate delta <10% for two weeks in pilot; CSAT ≥ baseline.
- Finance:
- Close calendar dry‑run; order‑to‑cash and procure‑to‑pay cycle time within thresholds; collections and deductions tooling live.
- Tax and payroll compliance verified in new entities/regions.
- Regulatory & policy:
- Change‑of‑control approvals/notifications complete; platform policy compliance confirmed; certifications live.
If any gate fails, pause and reroute the synergy to upside‑only until fixed.
TSA (Transition Service Agreement) scoping and exit
- Scope and service levels for IT (hosting, identity, email/collab, ERP), finance (close, AP/AR), HR (payroll/benefits), facilities, customer support, and security.
- Price caps and glidepath to avoid TSA cost creep; explicit termination milestones and penalties for slippage.
- Shadow‑run periods and acceptance criteria; runbook for TSA exit per service.
- Risks: hidden tool dependencies, license transferability, capacity gaps after exit; mitigation with staged insourcing or managed services.
Cutover strategy and playbooks
- Big‑bang for small surface areas with high coupling (e.g., brand switch, email domains).
- Phased for systems with long tails (CRM objects, billing catalogs, data warehouse).
- Strangler pattern for high‑risk code or platform migrations: route new traffic to the new system while draining old.
- Always define: blackout windows, roll‑forward and rollback criteria, smoke tests, hypercare staffing, and communication templates.
Copy‑ready templates (paste straight into your workspace)
A) Integration Feasibility Heatmap (0–5 scale per domain)
- Domains: Legal/Regulatory; Customer/Contracts; Platform/Channels; Technology & Data; Product/Pricing; GTM & Channels; Operations & Supply Chain; Finance & Tax; People & Culture; Security/Privacy; TSA & Cutover; Economics & Model Hooks.
- For each: current score, top three blockers, earliest achievable gate date, owner, confidence.
B) Integration Blueprint Canvas (per domain)
- Target state (Fuse/Federate/Interface), value driver(s) unlocked, must‑not‑break constraints, systems/processes to keep/migrate/retire, gating approvals, one‑time cost, run‑rate effect, start/finish dates.
C) Regulatory & License Transfer Tracker
- Obligation; jurisdiction; trigger (change of control/assignment); authority/counterparty; required deliverables; notice/approval SLAs; status; owner; critical path link.
D) Data & Identity Migration Card
- Datasets in scope; record counts; quality score; mapping & dedupe rules; test plan and metrics (accuracy, precision/recall); privacy/legal gates; IAM changes; rollback/runbook; cutover date; owner.
E) Billing/Entitlement Readiness Test
- Catalog alignment; price fences and DOA; taxation rules; invoice formats; credit/collections flow; meter integrity; test cohort results; defect log and burn‑down; acceptance criteria (≥99.5% accuracy).
F) TSA Scope Worksheet
- Service, in‑scope systems/processes, volumes/SLAs, price and escalator, exit milestones, shadow‑run criteria, termination triggers, residual risk plan, owner.
G) Cutover Playbook (one per system/process)
- Strategy (big‑bang/phased/strangler), dependencies, blackout windows, smoke tests, rollback plan, hypercare staffing, comms templates, success metrics.
H) Org & Comp Alignment Canvas
- Org chart target; decision rights (RACI); comp & incentive changes; retention/transition plan; works‑council or union steps; training plan and completion KPIs.
I) Synergy‑to‑Integration Map
- For each underwritten synergy/cost lever: integration dependency (gate), planned cutover, one‑time costs, ΔCM2/ΔCash impact month, model cell(s) to toggle.
Industry‑specific nuances to test explicitly
- SaaS/usage: entitlement and billing accuracy, tenant migrations, API plan limits, SOC2/ISO posture, data residency, SLOs and incident response merge; hyperscaler marketplace listings and private‑offer mechanics.
- E‑commerce/DTC & marketplaces: seller of record, brand registry, listing migration, returns policy, paid placement dependencies, OTIF thresholds, duty/tax engines.
- Fintech & payments: PCI scope, processor reserve/holdbacks, scheme compliance, fraud tooling integration, KYC/KYB & AML policy harmonization.
- Healthcare & life sciences: QMS alignment (cGMP/ISO13485), UDI/labeling, clinical/real‑world evidence claims, HIPAA & regional equivalents, device software validation and change control.
- Industrial & field service: safety and certification transfers, warranty policy, field force scheduling and parts logistics, export controls.
- Public sector: security accreditation (FedRAMP/StateRAMP/IRAP), data residency, subcontracting clauses, small‑business set‑aside constraints.
Economics: one‑time costs and cash plan
- One‑times: severance/retention, IT migration and licenses, TSA fees, rebranding, facilities moves and make‑goods, certifications/validations, dual‑running, change management and training.
- Cash timing: month‑by‑month phasing, working‑capital impacts (inventory re‑positioning, processor reserves, DSO/DPO shifts), capitalized vs. expensed items.
- Risk haircut: probability‑weighted gates; Margin‑at‑Risk from SLA credits, returns, paid placement, and channel penalties during transition. Feed all into Chapter 14.
Early‑warning indicators (watch weekly in integration command center)
- Billing/entitlement defects; invoice credit rates; discount creep vs. DOA.
- SLO burn rate or OTIF slippage; contact rate spikes; SLA credits issued.
- Project plan slippage on regulatory/consent items; unexpected platform policy notices.
- Data migration test failure rates; IAM access exceptions; security incidents.
- TSA cost burn above plan; shadow‑run defects not burning down; stranded‑cost accumulation.
- Key‑talent attrition; training completion gaps; rumor levels in engagement surveys.
Red flags—and immediate responses
- Gun‑jumping risk or antitrust red lines → lock down joint comms and planning to counsel‑approved clean‑team scope; shift synergy to upside‑only until clearance.
- Billing/entitlement not ready → postpone price/pack changes; keep catalogs separate; fund a 30‑day fix; protect revenue with customer guarantees.
- Capacity/SLO thin → cap migrations; add a reliability sprint; staff hypercare; reflect SLA credits and NRR drag in the model.
- Consent & license delays → ring‑fence affected books; maintain dual brands; sequenced migrations by jurisdiction; propose CPs/escrows in the term sheet.
- TSA sprawl → set hard exit milestones; add price caps; stand up managed services as bridge; prioritize highest‑cost TSAs for early exit.
- Culture/retention risk → trigger retention packages; simplify decision rights; double the manager comms cadence; pause non‑critical changes in affected teams.
90‑day integration lift plan (moves that change cash fast)
- Day‑1 controls: brand/comm templates, support routing, order acceptance, credit & collections continuity, security and access baselines.
- Cross‑sell readiness: CPQ and entitlement alignment for top three offers; seller/CSM enablement; ten lighthouse accounts live.
- CTS improvements: shipping/returns policy harmonization; carrier rationalization on top lanes; knowledge base and deflection flows deployed.
- FinOps & IT: reserved/savings plans live; top two workloads right‑sized; duplicate SaaS tools rationalized.
- Network quick wins: packaging/DIM fixes; lane re‑bids; duty/tax engine alignment for cross‑border.
- TSA exits: schedule shadow‑runs for two highest‑cost services; publish exit acceptance criteria; staff backfills.
- People: org and comp decisions announced; retention letters out; role‑based training completion to ≥90%.
72‑hour sprint plan (from blank page to a defendable feasibility view)
- Day 0: Freeze integration thesis and posture (Fuse/Federate/Interface) by domain; issue a single evidence request; draft the Heatmap and Blueprint shells.
- Day 1: Fill Heatmap with 0–5 scores and blockers; complete Regulatory Tracker and TSA Scope; draft Data & Billing Readiness Cards; pick cutover strategies.
- Day 2: Run gate tests (pilot or dry‑run metrics); quantify one‑times and MaR haircuts; wire integration dependencies into the 14.1 model; propose term‑sheet protections (CPs, covenants, indemnities, earnouts).
- Day 3: Publish the Integration Blueprint, Go/No‑Go gates, TSA plan, and 90‑day lift; stand up the IMO cadence, KPI set, and early‑warning dashboard.
Acceptance criteria for a decision‑grade integration feasibility
- Integration Blueprint complete with target posture per domain and “must‑not‑break” constraints.
- Heatmap scored 0–5 with dated gates, owners, and confidence; top blockers and critical path clear.
- Go/No‑Go checklists defined and measured in pilots/dry‑runs (billing/entitlement ≥99.5%, SLO headroom ≥15%, data accuracy ≥99.9%, etc.).
- TSA scope priced with exit milestones; cutover strategies selected with rollback plans; hypercare staffed.
- One‑time cost and MaR haircut quantified; model hooks wired; term‑sheet protections documented.
- IMO governance lives with RAID log, cadence, KPI dashboard, and synergy bank linkage.
- Clean‑team and antitrust guardrails documented; regulatory/consent tracker active.
- Investment Committee can see what integrates when, what it costs, what could break, and which protections are in place.
Run this checklist and “integration” stops being a vague promise. It becomes a gated, evidence‑led program that protects customers and service levels while converting your synergy thesis into risk‑adjusted cash within the hold period.
15.4 Value Capture Roadmap Guide
A value capture roadmap turns a deal thesis into a dated, resourced, and governable program that moves revenue, CM2, and cash within the hold period. It connects your synergy bank (15.1–15.2), integration feasibility (15.3), and the driver‑based model (14.1–14.4) into one operating plan the CFO, CRO, COO, and CTO can run. The roadmap is not a Gantt chart; it is a sequence of decisions and proofs—what must be true by when, who owns it, what it costs, and how dollars will show up in the bridge from last actuals to Year‑1 and Year‑2. Build it like an engineering program: explicit gates, measurable acceptance criteria, small batches, and fast feedback loops.
Principles that keep the roadmap real
Work from cash backwards. Every initiative must show how it changes a driver in the model, how that driver moves revenue or CM2, and how quickly that shows up in cash. Plan by constraints, not by wish lists—capacity rungs, SLO floors, regulatory approvals, platform policies, and customer consents set the pace. Make risk‑adjusted plans; present base/low/high with probabilities. Govern with a single source of truth: one synergy bank, one dependency map, one set of definitions, one cadence. Wire incentives to ΔCM2 and cash, not just bookings or cost lines. And above all, protect the franchise: no roadmap is worth a broken SLA, regulatory breach, or antitrust misstep.
Step‑by‑step build of a decision‑grade value capture roadmap
1) Start with a value tree, not a task list
Translate the deal thesis into a value tree with four trunks: Revenue, CM2, Working Capital, and Risk/Option Value. Under each trunk, place the specific levers you have already sized (attach rate uplift, realized price bps, take‑rate reductions, freight and cloud unit costs, returns policy, support deflection, DSO/DIO/DPO shifts). Quantify the Year‑1 and Year‑2 targets for each branch and link every branch to a single KPI and model cell. The tree is your north star; if a proposed activity cannot be placed on a branch, it is not in scope.
2) Consolidate the synergy bank into a program backlog
Pull the Revenue and Cost Synergy Cards into one backlog with uniform fields: ΔRevenue/ΔCM2/ΔCash by month, run‑rate, one‑time cost, confidence (H/M/L), gates from the integration feasibility work, owner, and earliest start and finish dates. Normalize all dollars to constant currency and organic perimeter. Add unit drivers (price bps, minutes, $/unit, calls per active, return rate) so you can audit realization later.
3) Prioritize by value density, feasibility, and sequencing logic
Score each initiative on risk‑adjusted NPV per month of execution capacity; right‑to‑win evidence; dependency count; and time‑to‑first‑cash. Prefer moves with high value density (ΔCM2 or cash per week of effort) and low dependency complexity. Separate quick wins (≤90 days, no structural dependencies) from enablers (catalog harmonization, entitlement/billing accuracy, certification, reserved cloud coverage) that unlock multiple dollars later. Sequence by constraints: staffed squads, capacity ladders, SLO floors, regulatory approvals, platform policy thresholds, TSA exit windows.
4) Plan the work in waves with explicit gates and acceptance criteria
Define Wave 0 (Day‑1 readiness) for stability and controls; Wave 1 (first 90 days) for quick wins and lighthouse proofs; Wave 2–3 (Quarters 2–4) for structural synergies; and Wave 4+ for options outside the hold‑period core. Each wave needs entry and exit criteria written as tests: billing dry‑run accuracy ≥99.5%; realized price fence live with DOA; returns triage deployed; carrier re‑bids signed; reserved cloud coverage ≥X%; OTIF ≥ threshold; SLA credits ≤ bps cap; DSO drift ≤ target; top‑100 cross‑sell attach ≥ target band.
5) Build the capacity plan and squad roster
Value capture fails when calendars pretend people are infinitely divisible. Define squads with named leaders, skills, and weekly capacity. Cap squad WIP to two to three concurrent initiatives. Pair each squad with a finance partner who owns baseline, measurement, and GL tagging. Agree on the “no heroics” rule: you cannot launch new playbooks unless hypercare capacity is booked and SLO error budgets allow it.
6) Map dependencies and the critical path
Create a single dependency map across domains: product/catalog, data, CPQ/billing, channel listings and marketplace policies, network/ops, compliance, and people/comp. Mark hard gates in red, soft dependencies in amber. Identify the critical path to the three biggest dollars; time‑box discovery for any unknowns. No ghost dependencies: every dependency must have an owner and a date or it does not exist.
7) Instrument measurement and attribution before you launch
Decide how you will prove dollars. Lock a benefits attribution method per lever: counterfactuals (A/B or geo‑splits), holdouts on renewals for re‑rating, pre/post with matched cohorts for support deflection, contract‑level realized price audits for pricing, parcel invoice audits for freight, cloud provider bills for FinOps, and processor statements for payment bps. Create a benefit ledger with GL project codes and dashboards that show realized vs. plan at the unit‑driver level. If you cannot measure it, you cannot book it.
8) Wire the roadmap to the model and scenarios
For every initiative, point to the exact assumption cells in the driver model that move (attach, price bps, take‑rate, returns %, shipping rate card, cloud on‑demand share, contact rate/minutes, DSO/DIO/DPO, processor reserve, channel mix). Pre‑build “go/no‑go toggles” per gate. When an initiative clears its gate, finance flips the toggle; the base and scenarios update and the valuation range refreshes. This keeps IC and lenders aligned in real time.
9) Set governance, cadence, and decision rights
Stand up a weekly Value Review (30–45 minutes) with the CEO, CFO, CRO/COO/CTO, IMO lead, and squad leads. Focus on dollars, gates, and risks; avoid status theater. Run a monthly Wave Gate where you promote, pause, or kill initiatives based on evidence. Publish decision rights: who can launch, pause, or change scope; who approves discount guardrail edits; who releases capacity or budget; who flips model toggles.
10) Align incentives and change management
Update comp plans so sellers receive credit for cross‑sell and re‑rating; success teams are rewarded for NRR uplift; operators for CM2 and SLO adherence; finance for cash and measurement quality. Add time‑boxed SPIFFs with sunset dates for early attachment. Train managers to coach the new plays; publish scripts, objection handling, and value calculators. Keep antitrust and clean‑team rules visible in all playbooks.
11) Connect to term‑sheet protections and TSA exit
Translate residual risks into structure: indexation clauses for price‑cost risk; inventory/service covenants during network changes; certification conditions precedent for geo/channel plays; indemnities for known exits; earnouts tied to realized price or NRR. Set TSA exit milestones with acceptance tests and price caps. Your roadmap dates should match these commitments.
12) Publish the 30/60/90 and 13‑week cash plan
Day‑1 is about stability: brand and comms, order acceptance, credit and collections continuity, security, and support routing. The first 13‑week cash plan shows when procurement, freight, FinOps, fee reductions, and working‑capital moves land; finance updates it weekly and explains variances by driver, not by department.
Copy‑ready templates to accelerate your build
Value Capture Roadmap Canvas (one page per initiative)
- Name and owner; branch of the value tree (Revenue / CM2 / Working Capital).
- Mechanism and unit driver(s) (e.g., +150 bps realized price; −8% parcel $/shipment; −3 minutes/contact; −10 days DSO).
- Economics: ΔRevenue, ΔCM2, ΔCash by month; run‑rate; one‑time cost; confidence (H/M/L).
- Gates and dependencies: from integration feasibility; earliest start/finish; critical path link.
- Measurement plan: counterfactual or audit method; GL tags; dashboard tile ID.
- Risks and MaR corridor; mitigations and owners.
- Model hooks: exact assumption cells and toggles; scenario interactions.
- First 30/60/90 actions; hypercare plan; acceptance criteria.
Wave Plan Template (for Wave 0–3)
- Objectives and target dollars; entry and exit gates with acceptance tests; squads and capacity; dependency milestones; hypercare staffing; communications and customer/partner touchpoints; risks and contingency triggers.
Benefits Ledger and Attribution Log
- Initiative; unit driver; baseline and current; source system; realized $ vs. plan this month and LTM; attribution method; auditor/verifier sign‑off; model toggle status; variance notes.
KPI Tree & Instrumentation Plan
- For each branch: lead metrics (e.g., attach demo‑to‑close, discount guardrail compliance, return reason mix, contact rate, cloud on‑demand share) and lag metrics (NRR, CM2%, CAC payback, cash); data owner; refresh cadence; thresholds for RAG.
Owner One‑Pager
- Purpose and “why now”; three weekly moves; risk/decision backlog; help needed; next gate date; definition of done.
Communications Plan Checklist
- Internal: Day‑1 note, weekly value digest, playbook updates, manager toolkits, office hours.
- External: key‑account briefings, partner enablement, marketplace listing updates, policy notices, migration offers and guarantees.
- Legal guardrails: antitrust and clean‑team reminders on every page.
Operating mechanics that make the roadmap work
Run a short weekly Value Review with three artifacts only: the Synergy Bank sorted by ΔCash next 90 days, the Dependency Map with red/amber gates, and the Benefits Ledger showing realized vs. plan at unit‑driver level. Decisions: promote, pause, kill; release or reassign capacity; flip model toggles; update scenario weights if early‑warning indicators move. Keep a tight hypercare loop for any change that touches customers, billing, or SLOs—pre‑staff, instrument, and give teams a measured exit.
Early‑warning indicators to wire into the dashboard
Monitor leading signals that threaten value: realized price erosion vs. fences; rising contact rate or SLA credits; return/chargeback spikes; parcel or cloud on‑demand share drifting up; processor reserve hikes; DSO tail growth; marketplace penalty warnings; gate slippage for certifications or consents; TSA burn above plan; attrition in key squads. Each indicator should have a predefined flip rule and a play: tighten discount guardrails, cap paid placement, defer a bundle, add a reliability sprint, reallocate squad capacity, or trigger a term‑sheet protection.
Red flags—and the immediate response
If dollars depend on unproven behavior (e.g., “customers will accept a re‑rating without elasticities or VoC”), move the initiative to upside only and run a pilot with a holdout. If billing/entitlement readiness is below threshold, freeze bundle or price changes; fix accuracy before launch. If capacity is over‑subscribed, reduce WIP and sequence; do not borrow against SLOs. If measurement is ambiguous, install instrumentation and GL tags before claiming savings—no metrics, no money. If TSA exits slip, escalate to owners, trim scope, and stand up managed services as a bridge.
90‑day value lift plan (moves that change cash fast)
In the first quarter, bias towards levers with short proof cycles and clean measurement. For revenue: cross‑sell to top‑100 mapped accounts with fixed‑scope lighthouse offers; re‑rate renewals where fences and DOA are live; publish a realized price dashboard and enforce discount guardrails. For CM2: re‑bid parcel lanes and deploy packaging/DIM fixes; move priority cloud workloads to reserved/savings plans; tighten returns triage and support deflection. For cash: enforce terms on top‑20 accounts, triage retail deductions weekly, launch SCF or early‑pay where APR is favorable, right‑size weeks of supply on non‑KVIs. Instrument everything, book GL codes, and update the model within 24 hours of gate clearance.
72‑hour sprint plan (from analysis to a board‑ready roadmap)
Day 0: Publish the value tree and the consolidated synergy bank; freeze definitions and acceptance tests; stand up the dependency map. Day 1: Prioritize by risk‑adjusted NPV per month of capacity; assign squads; draft Wave 0–1 with gates and owner one‑pagers; wire model hooks and toggles. Day 2: Finalize measurement plans and GL tags; set the weekly Value Review and monthly Wave Gate; load early‑warning indicators into the KPI dashboard. Day 3: Issue the 30/60/90 plan and 13‑week cash cadence; align incentives; publish the communications plan; secure term‑sheet protections and TSA exit milestones.
Acceptance criteria for a decision‑grade value capture roadmap
The value tree is complete with quantified targets and one KPI per branch. A single synergy bank lists initiatives with ΔRevenue/ΔCM2/ΔCash by month, run‑rate, one‑times, confidence, owners, and gates. Wave 0–3 are dated and gated; squads and capacity are assigned; dependencies and the critical path are explicit. Measurement and GL tagging are live; a benefits ledger and dashboards track unit drivers and dollars; model hooks and toggles are wired; scenarios refresh when gates clear. Governance is in place with weekly Value Reviews and monthly Wave Gates; incentives and comms are aligned; legal and TSA constraints are embedded. IC can see what lands when, who owns it, how it is measured, and what happens to cash and headroom if a gate slips.
Build the roadmap with this rigor and you will replace optimism with operating truth: a small set of high‑density initiatives, sequenced by constraint, measured at the unit level, and wired to the model—so value creation becomes a managed flow of auditable dollars, not a slide buried in the appendix.
