M&A Integration: Day 1 / 30 / 100 / 365
A 12-15 month, event-anchored M&A integration playbook synthesising McKinsey, BCG, Bain, Deloitte, EY, and PwC PMI methodologies plus T2D3 proprietary IP for $25M-$250M ARR B2B SaaS acquirers running tuck-in or mid-sized acquisitions. Stands up the IMO charter, decomposes the deal thesis into OKRs, executes 8 functional workstreams (Finance / IT / HR / Legal / GTM / Product / CS / Facilities) under a single Integration Management Office, delivers Day 1 readiness with zero customer or payroll incidents, hits Day 30 stabilization, Day 100 operating-model cutover, and Day 365 synergy capture (>=50% public synergy run-rate, >=85% top-talent retention, <=3% Top-100 customer churn). Reference methodology: https://www.mergerintegration.com/. Total scope: 8 modules, 37 sections, 224 tasks, ~2310 hours canonical effort across the 12-15 month engagement (4-6 FTE-equivalents at peak). Wave 2 playbook with cross-references to upstream pricing-packaging and sales-methodology playbook artifacts. Scoped to tuck_in and mid_sized acquisitions; merger-of-equals deals routed to forthcoming ma-merger-of-equals v2 playbook per Decision 5.
M1 - Pre-Close Planning & IMO Stand-Up
Stand up the institutional spine of the integration before Day 1. Without an IMO charter signed by both CEOs, an Integration Thesis mapped to OKRs, and clean-team synergy validation, every downstream workstream operates without authority. Section deliverables: charter, OKR map, workstream charters, clean-team output, retention pool, base risk register. T2D3 stage T2/D1; STOP Standardize.
M1.S1 - IMO Stand-Up
Stand up the Integration Management Office: charter, director appointment, decision-rights matrix, cadence design, tooling stack. Without an IMO charter signed by both CEOs, every downstream workstream operates without authority.
Author IMO Charter (mission, mandate, scope, decision rights)
The IMO Charter is the institutional constitution of your integration: it grants authority, fences scope, and defines what "won" looks like. In a B2B SaaS post-merger integration,…
Ratify charter - both CEOs sign
The charter has no force until the two people who control the combined org commit to it personally. Ratification is not a formality — it is the moment the acquirer and target…
Appoint IMO Director (CHRO-eq independence)
The IMO Director is the single most consequential appointment in the integration. This person runs the daily operating rhythm, arbitrates between workstream leads, and is the face…
Build decision-rights / RACI matrix
In a post-merger integration the most expensive delays are not technical — they are decisions nobody is clearly empowered to make. Two leadership teams now share one org, and any…
Design IMO cadence (daily / weekly / monthly / quarterly)
Cadence is the heartbeat of the integration. Without a designed rhythm, the IMO either over-meets (burning the leaders you most need executing) or under-meets (letting red risks…
Select tooling stack (issue tracker, dashboard, doc repo)
The IMO runs on shared information, and in the chaos of integration that information fragments fast — one lead's spreadsheet, another's email thread, a third's private Slack DM. A…
Dry-run cadence simulation (Day -30)
A cadence that has never been run is an assumption, not a system. The Day -30 dry run is where you discover — while it's still cheap — that the weekly RAG meeting produces no…
Stand up IMO team (PMO, analysts, change mgmt)
The IMO Director cannot run an eight-workstream integration alone. A properly staffed IMO team gives the Director the program-management muscle to drive cadence, the analytical…
Author board-update / steering-committee pack template
The board and Steering Committee govern the integration at the strategic altitude, and they govern through one artifact: the periodic update pack. A standardised steering-pack and…
M1.S2 - Deal-Thesis-to-OKR Mapping (T2D3 IP)
T2D3 PROPRIETARY IP layer. Decompose the public deal thesis into discrete commitments, map each to O1/O2 objectives, translate every synergy item into a Key Result with quantitative target + date + named owner. The political contract converted to an audit-ready synergy-capture system.
Decompose public deal thesis into discrete commitments
The deal got approved on a thesis — the story the board, investors, and regulators saw at sign about why the combined company is worth more than the parts. But a thesis is a…
Map each commitment to an O1 / O2 objective
A classic integration failure is treating PMI as a single goal — "capture the synergies" — and quietly neglecting the base business while everyone chases the upside. This task…
Translate each synergy item into a KR with target + date
This is the T2D3 proprietary deal-thesis-to-OKR mapping template — the step that converts an objective into something you can manage weekly. Each synergy item sorted under O1 or…
Establish acquirer T2D3-stage baseline + target
Before you translate a deal thesis into commitments, you must know what growth stage the acquirer is operating from — because the stage dictates the kind of synergy ambition that…
Pressure-test thesis against bottom-up workstream estimates
A deal thesis built top-down — boardroom ambition divided across synergy buckets — is a hypothesis, not a plan. This task converts each Key Result into a number the people who…
Stakeholder readout - Steering Committee
The deal-thesis-to-OKR map only becomes binding when the people who own the capital and the customers ratify it. This 90-minute Steering Committee readout — both CEOs, both CFOs,…
M1.S3 - Workstream Charters
Confirm 8-workstream taxonomy (Finance/IT/HR/Legal/GTM/Product/CS/Facilities), appoint named workstream leads, author per-workstream charter template, complete all 8 charters, map cross-stream dependencies, compile master Day-1 mandatories.
Confirm 8-workstream taxonomy (Finance/IT/HR/Legal/GTM/Product/CS/Facilities)
The workstream taxonomy is the org chart of the integration itself — every Day-1 mandatory, every synergy KR, and every dependency hangs off one of these lanes. Get it wrong and…
Appoint named lead per workstream
A workstream without a named, accountable owner is a wish. This task puts a single senior decision-maker on each of the 8 lanes — and the seniority bar is deliberately high: the…
Author per-workstream charter template
The workstream charter is the contract between the IMO and each lane lead — it converts "you own Finance integration" into a concrete, reviewable mandate. A single shared template…
All 8 workstream charters drafted + signed
This is where the integration plan stops being the IMO's document and becomes the workstream leads' document. Each of the 8 leads drafts and signs their own charter against the…
Map cross-stream dependencies (DAG)
Integrations don't fail one workstream at a time — they fail at the seams, where one lane's milestone silently depends on another's. This task makes those seams explicit by…
Compile master Day-1 Mandatories list across workstreams
Day 1 is a continuity event, not a transformation event — and the master mandatories list is the single artifact that proves the combined company can operate the morning after…
M1.S4 - Clean Team & Synergy Validation
Stand up clean team under legal firewall, transfer data room to IMO knowledge base, validate cost and revenue synergies bottoms-up, run customer overlap analysis (Top-100), run tech-stack overlap analysis. Gated to mid-sized+ deals or where customer.has_clean_team is true.
Stand up clean team under legal firewall
Before close, the acquirer and target are still legally competitors, and antitrust law (HSR / FTC, and foreign equivalents) prohibits them from sharing competitively-sensitive…
Transfer data room -> IMO knowledge base
The due-diligence data room is a legal repository — organised for deal evaluation, gated by counsel, and full of material that workstream leads either can't see…
Bottoms-up cost synergy validation
Cost synergies are the most credible line in any deal thesis — they're inside the combined entity's control and don't depend on customers behaving. But the boardroom number is…
Bottoms-up revenue synergy validation
Revenue synergies are the most over-promised, under-delivered line in any deal model. The IMO clean team must rebuild the announced number bottoms-up — from named accounts, real…
Customer overlap analysis (combined Top-100)
When two B2B SaaS companies merge, the customers buying both products are simultaneously your biggest opportunity and your biggest exposure. A dissatisfied overlap account can…
Tech-stack overlap analysis (combined SaaS apps)
Two SaaS companies merging means two of nearly everything — two CRMs, two billing systems, two data warehouses, two of every point tool. A $50M ARR target typically runs 60–120…
M1.S5 - Retention & Severance Pre-Plan
Identify ~2% critical talent (talent-to-value), size retention bonus pool against deal value, design retention bonus structure (T2D3 IP), author severance protocol, plan retention conversations Day 1 -> Day 30. Mid-sized+ deals require formal retention pool.
Talent-to-value exercise - identify ~2% critical talent
In post-merger integration, value walks out the door faster than it can be captured — the cross-sell ramp, the institutional knowledge of the target's Top-100 accounts, and the…
Size retention-bonus pool against deal value
A retention pool is the insurance premium on the deal thesis — too small and your critical talent (the ~2% just identified) gets poached during the most fragile window; too large…
Design retention-bonus structure (lump / milestone / installment)
This is T2D3 proprietary IP: the retention-bonus design framework that turns a sized pool into a behavioral instrument. The structure you choose determines what you are buying. A…
Author severance protocol + Q&A
Severance is the mirror image of retention — the same integration that keeps the critical ~2% will, in any deal with cost-synergy redundancy, exit a population of employees. How…
Plan retention conversations (Day 1 -> Day 30)
A retention bonus on paper retains no one if the conversation around it lands badly. Critical talent decides whether to stay in the first days after announcement, when uncertainty…
M2 - Day 1 Readiness
Ensure the legal-and-operational handover is boring - no payroll incidents, no IT outages, no customer surprises. Day 1 KPI is 100% mandatories ready, top-100 customers contacted within 24h, 0 critical incidents. T2D3 stage T2/D1; STOP Templatize.
M2.S1 - Legal Day 1 vs Operational Day 1
Confirm Legal Day 1 (regulatory clearances + close mechanics), define Operational Day 1 (same date or staged), Day-3 readiness check, Day-1 final rehearsal (war-room test). Sign-off section.
Confirm Legal Day 1 (regulatory clearances + close mechanics)
Legal Day 1 is the day ownership legally transfers — when the deal closes, the purchase price moves, and the target becomes the acquirer's property. Everything in the integration…
Define Operational Day 1 (vs Legal - same date or staged)
If Legal Day 1 is when ownership transfers, Operational Day 1 is when the combined company begins to *run* under one operating model — unified leadership, customer-facing…
Day -3 readiness check (FTC clearance, signing path)
Three days out, the IMO runs a go/no-go readiness check focused on the deal-existential gate: regulatory clearance and the signing path. This is distinct from the operational…
Day -1 final rehearsal (war-room test)
The Day -1 rehearsal is where you discover the last-mile gaps that no checklist surfaces — the email distribution list that's missing a region, the SSO bridge that wasn't tested…
M2.S2 - Mandatories Confirmation
Each of 5 functional workstreams (Finance, IT, HR, Legal, GTM) confirms its Day-1 mandatories list as GREEN before Steering Committee approves close-execution. Closes with Deloitte-style Day One certification per workstream.
Finance Day-1 mandatories (cash controls, signing authority)
On Operational Day 1 of a B2B SaaS merger, Finance has exactly one job: continuity, not transformation. Payroll must run, vendors must get paid, customers must get billed, and the…
IT Day-1 mandatories (IAM, SSO bridge, break-glass)
The single most important IT principle for Operational Day 1 is the one teams most often violate: Day 1 is continuity, not cutover. Per mergerintegration.com's M&A Day-1 task set…
HR Day-1 mandatories (payroll, benefits, org chart)
HR carries the most emotionally charged Day-1 mandatories in a B2B SaaS merger: this is the day every employee asks "do I still have a job, will I still get paid, and who do I…
Legal Day-1 mandatories (contracting authority, change-of-control filings)
Legal's Day-1 mandatories are the guardrails that keep the combined entity inside the law from the first hour. The moment Legal Day 1 transfers ownership, two things must already…
GTM Day-1 mandatories (customer ownership, sales rules)
In a B2B SaaS merger, customers are the asset that walks — and Day 1 is when they decide whether the deal is reassuring or alarming. The GTM Day-1 mandate, per the NMS Day-1 to…
Deloitte-style "Day One certification" sign-off per workstream
The Day One certification is the formal gate that converts a sea of scattered mandatories into a single, accountable go/no-go decision. Per Deloitte's M&A integration-plan…
M2.S3 - Day-1 Comms Kit Execution
Author the full Day-1 comms kit: employee FAQ (75-question template, T2D3 IP), customer Day-1 email + FAQ, partner email, press kit, manager talking points + reverse Q&A, Day-1 welcome packet, mailbox / hotline staffing.
Author employee FAQ (75-question template)
The employee FAQ is the most-read document of the entire integration — and the one that most directly governs talent retention, the variable that makes or breaks deal value. Per…
Customer Day-1 email + FAQ
The Day-1 customer email is the single highest-leverage retention act in a B2B SaaS merger. It protects the O2 "hold the base" commitment and the Bain ≤3% incremental Top-100…
Partner Day-1 email
The partner Day-1 email is a deliberately separate artifact from the customer email because partners sit in a different legal and economic relationship to the combined entity.…
Press kit (release, FAQ, exec quotes, logos)
The press kit is the external-narrative control system for Day 1. The moment the embargo lifts, journalists, analysts, competitors, and prospects will form their first impression…
Manager talking points + reverse Q&A
Managers are the highest-trust communication channel in any merger — employees believe their direct manager over a CEO email or a corporate FAQ. That makes the manager an asset or…
Day 1 Welcome Packet (CEO note, vision, infographic)
If the employee FAQ is the channel for reducing uncertain news, the Day 1 Welcome Packet is its emotional counterweight — the channel for delivering the good news and making…
Day-1 mailbox / hotline staffing plan
In the first 72 hours after close, employees, customers, and partners all generate questions the standard org chart isn't yet wired to answer. A dedicated Day-1 mailbox…
M2.S4 - Day 1 Run-of-Show
Hour-by-hour run-of-show, war-room staffing, P0 incident protocol, Day-1 pulse check (employee + customer signal). Pre-cutover sign-off + Day-1 governance section.
Author Day-1 run-of-show (hour-by-hour)
Day 1 is the most-watched day of the entire integration: every employee, customer, and partner forms a first impression of the combined company in a single news cycle. A precise…
War-room staffing (Day 1 + Day 2)
The first 48 hours after close are when small operational failures — a payroll glitch, a customer escalation, a system that didn't cut over cleanly — can metastasize into…
Incident protocol (P0 outage / customer escalation)
During the Day-1/Day-2 window, the combined company faces elevated risk of outages, customer escalations, and regulatory queries — all while reporting lines are still settling. A…
Day-1 pulse check (employee + customer signal)
The IMO cannot manage what it cannot measure, and Day 1 sets the baseline against which all subsequent integration health is judged. A structured 17:00 pulse check captures four…
M3 - Workstreams (Finance / IT / HR / Legal / GTM / Product / CS / Facilities)
Execute per-function integration in coordinated parallel under the IMO's authority. M3 has 8 sections - one per function - and is the largest module. GTM section explicitly cross-references upstream playbooks pricing-packaging (for tier rationalisation, discount governance, billing migration) and sales-methodology (for MEDDPICC reconciliation and Command-of-the-Message harmonisation). T2D3 stage T2/D1; STOP Templatize -> Optimize.
M3.S1 - Finance Workstream
Combined close calendar, chart-of-accounts mapping, ERP cutover plan, revenue recognition harmonisation, treasury consolidation, AR/AP cutover, tax structure review, audit alignment, finance org design, budget rebuild, finance systems rationalisation.
Author combined close calendar (monthly + quarterly + yearly)
A merger collides two finance organizations that each have their own close conventions — cutoff dates, sub-ledger sequencing, intercompany eliminations, reporting deadlines. Until…
Chart-of-accounts mapping (target -> acquirer schema)
The chart of accounts is the skeleton of financial reporting, and the acquirer and target almost never share one. Mapping the target's COA to the acquirer's schema is the…
ERP cutover plan (target -> acquirer or unified)
The ERP cutover is the single highest-stakes move in the Finance workstream because it gates billing, AR/AP, treasury, and revenue recognition simultaneously — a botched cutover…
Harmonise revenue recognition policy (ASC 606)
Two SaaS companies can both be ASC 606-compliant and still recognize revenue differently — diverging on how they identify performance obligations, allocate transaction price, and…
Treasury / banking consolidation
Treasury consolidation is where some of the cleanest, fastest cost and capital synergies live — duplicate bank relationships, idle cash trapped in too many accounts, redundant FX…
AR/AP cutover with no payment-disruption window
The AR/AP cutover is the most operationally unforgiving step in finance integration: a single missed window means customers don't get invoiced (cash stops) or vendors don't get…
Combined tax structure review (entity-level optimisation)
A merger creates a one-time window to re-engineer the combined entity's tax structure — and the value at stake is real cash, not accounting cosmetics. Optimising entity structure,…
Combined-co audit alignment (auditor selection, schedule)
In a B2B SaaS post-merger integration, audit alignment is the quiet workstream that protects the combined entity's ability to close the books, satisfy lenders, and stay fundable.…
Finance team org design (combined CFO org chart)
Designing the combined finance org is where cost synergy meets capability retention. Two finance functions arrive with overlapping controllerships, two FP&A teams, and often two…
Combined annual budget rebuild
The combined annual budget rebuild is where the deal thesis stops being a slide and becomes a number people are accountable for. You are not stapling two budgets together — you…
Finance-systems rationalisation (FP&A, BI, treasury tools)
Two SaaS companies merging will own two of nearly everything in the finance-tech stack: two planning tools, two BI platforms, two treasury workbenches, often two ERPs feeding…
M3.S2 - IT & Data Workstream
Application inventory + rationalisation, IAM/SSO unification, data platform integration, IT cutover runbook (T2D3 IP), security posture alignment, network/VPN bridge, collaboration tools merge, endpoint/MDM merge, IT vendor consolidation, IT org design, cybersecurity incident response, combined CMDB.
Application inventory + rationalisation (keep/consolidate/retire)
The first job of the IT & Data workstream is to see the full picture: a complete, deduplicated inventory of every SaaS application running across both companies. Until that…
IAM / SSO directory unification
Identity is the substrate of the merger. Until employees from both companies live in one directory with consistent access, nothing else integrates cleanly: you can't grant…
Data-platform integration sequencing (warehouse, lakehouse)
A merger creates two analytics universes that must converge before the combined company can trust a single number — for the synergy dashboard, the board model, churn-signal…
IT cutover runbook (T2D3 IP) - sequencing + dependencies + rollback
This is T2D3 proprietary IP and the operational heart of the IT workstream: the comprehensive runbook that turns the keep/consolidate/retire inventory into a safe, ordered set of…
Security posture alignment (SOC2, ISO, HIPAA)
In B2B SaaS, security posture is a revenue asset, not just a control function — customers' procurement and vendor-risk teams gate renewals and expansions on SOC 2 / ISO 27001 /…
Network / VPN bridge between acquirer + target
The network bridge is the plumbing that lets two previously separate companies actually work as one — shared services, cross-company access to applications, and the connectivity…
Collaboration tools merge (email, Slack/Teams, calendar)
Collaboration tools are the most visible, most emotional systems in an integration — they are where employees experience "are we one company yet?" every single day. When the…
Endpoint / MDM merge (laptops, mobile devices)
Merging endpoint and mobile-device management is how the combined company gains uniform control over the riskiest attack surface in any SaaS business: the laptops and phones…
IT vendor consolidation
IT vendor consolidation is one of the most reliable cost-synergy levers in a B2B SaaS post-merger integration: the combined entity inherits two overlapping portfolios of…
IT team org design (CIO org chart)
Designing the combined CIO org chart is where the IT integration stops being a list of tool decisions and becomes a durable operating model. Org ambiguity is a top driver of…
Combined cybersecurity incident response plan
A merger doubles the attack surface and the number of people with privileged access overnight — and threat actors actively target companies mid-integration, when IAM is in flux…
Combined CMDB / asset management
You cannot rationalize, secure, or cut over what you cannot see. A combined CMDB (configuration management database) / IT asset management record is the single source of truth…
M3.S3 - HR & People Workstream
Org design Band 3+, Syntropy job-family redundancy decisions (T2D3 IP), payroll cutover, benefits harmonisation, comp-plan harmonisation rubric (T2D3 IP), equity treatment, HRIS merge, policy handbook merge, onboarding harmonisation, performance-management process merge.
Org design Band 3+ (VP and above)
Combined-co org design for Band 3+ (VP and above) is the most politically charged and value-determinative people decision in the integration. The leadership layer sets the tone…
Syntropy job-family redundancy decisions (T2D3 IP)
This is T2D3 proprietary IP: applying the Syntropy job-family taxonomy to make redundancy decisions defensibly, capability-first, across the combined workforce. The common failure…
Payroll cutover (no missed pay date)
A missed or late paycheck is the single fastest way to destroy trust in a newly combined company — it converts goodwill into resignations and, in many jurisdictions, into legal…
Benefits harmonisation (medical, dental, 401k)
Benefits harmonization is where employees most directly feel the merger in their wallets and their families' security, so it carries outsized retention weight relative to its…
Comp-plan harmonisation rubric (T2D3 IP)
This is T2D3 proprietary IP: a scoring rubric that turns compensation harmonization from a political tug-of-war into a defensible, criteria-based decision. Compensation is the…
Equity treatment (acceleration, replacement awards, lock-ups)
Equity is the retention lever with the longest reach and the highest legal sensitivity in a SaaS acquisition. For the target's early employees and executives, unvested equity is…
HRIS merge (Workday/Bamboo/Rippling/Gusto)
The HRIS merge is the systems backbone behind every people decision in the integration: payroll cutover, benefits enrollment, org-chart publication, and headcount reporting all…
Policy handbook merge (PTO, remote, code of conduct)
The policy handbook merge sets the day-to-day rules of the combined company — PTO, remote/hybrid, code of conduct, expense, and travel — and employees notice these differences…
Onboarding harmonisation (combined-co experience)
A merger doubles the population of "new" employees overnight — not just literal new hires, but every target-company employee learning the combined-co's systems, benefits, and…
Performance-management process merge
Two SaaS companies almost never run performance management the same way: one does annual ratings on a 1–5 scale with stack-ranked calibration, the other does continuous check-ins…
M3.S4 - Legal & Compliance Workstream
Change-of-control vendor + customer contract review, IP transfer, regulatory notifications, litigation/claims inventory, data-privacy policy merge (GDPR/CCPA), MSA template harmonisation, export-control / sanctions screening for combined entity.
Change-of-control vendor contract review
Many vendor, supplier, and software contracts contain change-of-control (COC) clauses that fire automatically at close — granting the counterparty a consent right, a termination…
Change-of-control customer contract review
The mirror image of vendor COC review, and higher-stakes: a change-of-control clause in a customer contract can give a major account a contractual exit, a renegotiation right, or…
IP transfer (patents, trademarks, copyrights)
In a B2B SaaS deal the intellectual property — patents, trademarks, copyrights, and trade secrets — is often the asset being bought. Yet legal ownership does not transfer cleanly…
State/foreign regulatory notifications
Federal antitrust clearance (HSR/FTC) is the headline gate, but a B2B SaaS combination also triggers a long tail of state-level and foreign regulatory notifications that must be…
Combined litigation + claims inventory
At close the acquirer inherits the target's legal liabilities — open litigation, threatened claims, and regulatory inquiries — and must now manage them as one combined portfolio.…
Data-privacy policy merge (GDPR, CCPA)
A B2B SaaS combination merges two bodies of personal data — customer contacts, end-user records, employee data — each governed by its own privacy posture under GDPR, CCPA/CPRA,…
Master Services Agreement template harmonisation
The acquirer and target each sell on their own paper — distinct MSAs, order forms, and SOW templates with different liability caps, indemnities, data-protection terms,…
Export-control / sanctions screening (combined entity)
The combined entity inherits the union of both companies' export-control and sanctions exposure — and combination can create new obligations neither party had alone. A B2B SaaS…
M3.S5 - GTM Workstream (cross-referenced to upstream playbooks)
Top-100 customer list with risk score, exec sponsor assignment, Day-1 Top-100 comms, 30-day check-in cadence, NPS/churn tracking, territory/quota redesign, pricing harmonisation (cross-ref pricing-packaging), discount governance merge, billing-system harmonisation runbook (T2D3 IP), brand decision tree (T2D3 IP), domain decision, cross-sell motion design, MEDDPICC reconciliation (cross-ref sales-methodology), Command-of-the-Message reconciliation, marketing tech stack merge, customer-comms decision tree (T2D3 IP), sales enablement + cert program, RevOps tooling merge.
Build Top-100 combined-co customer list with risk score
In M&A, customers vote with their renewal — and the target's continuing base is the hold-the-base (O2) commitment the whole deal thesis rests on. The single most leveraged…
Assign named exec sponsor per Top-100
A risk score is inert until someone is accountable for acting on it. The companion move to the Top-100 list is assigning a single named executive sponsor per Top-100 account — one…
Day-1 customer comms (email + call) for Top-100
The single biggest controllable churn risk in any B2B SaaS PMI is the silence that follows a deal announcement. Customers are roughly three times more likely to leave after a…
30-day Top-100 check-in cadence
Day-1 outreach buys goodwill; the 30-day check-in is where you convert that goodwill into measured retention. Merger anxiety peaks not at announcement but a few weeks in, when…
NPS delta + churn-signal tracking (RevOps build)
What gets measured gets defended. The most cited PMI failure is sentiment decay that nobody saw until renewals slipped — one major US bank's post-merger NPS fell from 11.5 to zero…
Territory + quota redesign (combined-org coverage)
When two SaaS sales orgs combine, the fastest way to destroy both revenue synergy and rep retention is to leave overlapping coverage unresolved. Two reps calling the same logo,…
Pricing harmonisation (cross-ref pricing-packaging.define-v1-packaging-tiers)
Two SaaS price books are rarely compatible — the target almost always sells different tiers, value metrics, and effective ACVs than the acquirer. Left unharmonised, the combined…
Discount governance merge (cross-ref pricing-packaging.discount-governance-policy)
Harmonised list prices mean nothing if the two sales teams approve discounts by different rules. The target's reps almost always operate under looser norms — and the moment…
Billing-system harmonisation runbook (T2D3 IP, cross-ref pricing-packaging.billing-migration-runbook)
Industry practice splits into cold cutover (single entity, all data migrated and validated in a short controlled window of a few hours) and phased migration (multi-entity /…
Brand decision tree (T2D3 IP) - preserve / sub-brand / endorsed / merge
Decision criteria to score before choosing:
Domain + website decision (rebrand timing)
The domain and website are where the brand decision (the M3.S5 brand decision tree) becomes irreversible in public — and where a rushed redirect can vaporize organic traffic and…
Cross-sell motion design (combined-org accounts)
Cross-sell is the headline revenue synergy in nearly every SaaS deal thesis — and the one that most reliably under-delivers, because reps default to selling what they've always…
MEDDPICC reconciliation (cross-ref sales-methodology.meddpicc-qualification-rubric)
A combined sales org with two different qualification standards produces one unforecastable pipeline. If the acquirer scores deals on MEDDPICC and the target qualifies on gut…
Command-of-the-Message reconciliation (cross-ref sales-methodology.command-of-the-message-map)
After a merger, two sales teams walk into the same combined-org accounts telling two different value stories. Customers hear inconsistency; reps freelance positioning; and the…
Marketing tech stack merge (HubSpot/Marketo/Pardot decision)
In post-merger integration, the marketing-automation platform is the system of record for demand generation — it owns nurture flows, lead scoring, attribution and the contact…
Customer-comms decision tree (T2D3 IP) - segment -> message -> channel -> timing
This is T2D3 proprietary IP and the spine of GTM customer continuity. Bain's research on keeping customers first in integration shows that uncertainty, not the deal itself, drives…
Combined sales enablement + certification program
Revenue synergies in the deal thesis assume sellers can carry the combined portfolio — cross-sell the target's products into acquirer accounts and vice versa. That doesn't happen…
RevOps tooling merge (CRM, CPQ, forecasting)
The CRM is the revenue system of record — pipeline, ownership, forecast and the data every synergy KR is measured against. Running two CRMs past the operating-model cutover means…
M3.S6 - Product / R&D Workstream
Roadmap rationalisation (combined-co priorities), tech architecture decision, engineering org structure, shared platform decisions (auth/analytics/payments), product feature overlap analysis (sunset/merge/co-exist), PM process merge, research/UX function merge, design system merge.
Roadmap rationalisation (combined-co priorities)
Two SaaS companies arrive at close with two roadmaps built for two strategies — and finite combined engineering capacity. If you simply concatenate them, R&D spreads thin, the…
Technical architecture decision (target -> acquirer or unified)
This is the single most consequential — and most expensive-to-reverse — decision in the Product/R&D workstream. Do you migrate the target's codebase onto the acquirer's platform,…
Engineering org structure (combined CTO org chart)
Architecture decisions are inert until there's an org that can execute them. Two engineering teams arrive with two reporting structures, two sets of leads competing for the same…
Shared platform decisions (auth, analytics, payments)
Even when two products stay separate, the shared services beneath them — authentication, analytics, payments — are where real product synergy lives or dies. A single sign-on lets…
Product feature overlap analysis (sunset / merge / co-exist)
When two SaaS products combine, overlapping features are both a cost synergy (stop maintaining two of the same thing) and a churn risk (sunset a feature a customer depends on and…
PM process merge (PRD, sprint, release cadence)
Two product orgs ship the same product only when they share the same operating rhythm. If one team runs two-week sprints with lightweight PRDs and the other runs monthly releases…
Research / UX function merge
Research and UX are easy to overlook in a PMI — they don't run payroll or hold pipeline — but they are how the combined product feels coherent to customers rather than like two…
Design system merge (or hybrid)
The design system is the shared vocabulary of the combined product UI — tokens, components, patterns. When two SaaS companies merge, two design systems mean two visual languages,…
M3.S7 - Customer Success Workstream
CS team merge, support tooling decision, support tier harmonisation (response SLA, severity), CS playbook merge (onboarding/EBR/renewal), renewal process merge, NPS survey harmonisation, customer health score merge, combined CS KPI dashboard.
CS team merge (named owners per book)
In M&A integration, customer success is the workstream that holds O2 — the base — and the single biggest churn driver post-close is ambiguity over who owns the account. A target…
Support tooling decision (Zendesk / Intercom / unified)
Support tooling is where customer continuity (O2) meets cost-synergy capture. The two companies almost certainly run different help desks — Zendesk on one side, Intercom on the…
Support tier harmonisation (response SLA, severity)
When two SaaS companies merge, their severity definitions and response SLAs almost never line up — one calls a partial outage P1, the other P2; one promises Enterprise a 1-hour…
CS playbook merge (onboarding, EBR, renewal)
Beyond org charts and tooling, the operating motions that CS teams run — how a customer is onboarded, how a quarterly business review is structured, how renewal and expansion are…
Renewal process merge
The renewal is where churn risk becomes a number, and in the post-close window it is the most fragile moment in the customer lifecycle. A target customer whose renewal falls in…
NPS survey harmonisation (combined-co instrument)
NPS is the headline O2 metric — the deal thesis and the board pack both commit to maintaining customer NPS at or above pre-deal levels, and the IMO Charter's mission anchor…
Customer health score merge
A customer health score is the early-warning system for churn, and in M&A it is how the IMO sees ARR-at-risk before it becomes lost revenue against the O2 hold the base…
Combined-co CS KPI dashboard
The CS workstream's contribution to the deal thesis only becomes governable when it is visible on one dashboard. Up to this point the merge has produced unified owners, tooling,…
M3.S8 - Facilities & Real Estate Workstream
Site rationalisation (close/consolidate/keep), lease decisions (terminate/sublet/renegotiate), combined-co signage and badging, remote/hybrid policy merge, equipment and asset transfer. Gated when target has physical offices.
Site rationalisation (close / consolidate / keep)
Real-estate consolidation is one of the most reliable cost synergies in a B2B SaaS merger — combined headcount rarely needs every office, and overlapping metros create immediate,…
Lease decision (terminate / sublet / renegotiate)
Once site rationalisation says close or consolidate, the lease decision is where the synergy is actually realised — or quietly evaporates. A site you no longer need still carries…
Combined-co signage + badging
Signage and badging are the physical, daily-felt expression of the brand decision — they are where the abstract choice (preserve / sub-brand / endorsed / merge-into-master)…
Remote / hybrid policy merge
Remote and hybrid policy is where facilities economics and people retention collide most visibly. Two SaaS companies will almost always have different defaults — one fully remote,…
Equipment + asset transfer
Physical equipment and fixed-asset transfer is the Facilities & Real Estate workstream's most error-prone Day-30 deliverable: assets move between sites while the combined entity…
M4 - Day 30 Stabilization
Absorb shocks from Day 1, lock in operating rhythm, prevent silent regressions. Day 30 KPIs: 90% top-talent in seat; 100% Top-100 30-day check-ins completed; cultural pulse survey baseline set; synergy tracker baseline live. T2D3 stage T2/D1; STOP Optimize.
M4.S1 - Day-30 Workstream Status
Day-30 RAG review per workstream, Day-30 incident retrospective, Day-30 integration budget burn report, Day-30 board update, Day-30 plan rebaseline. Recurring 30-day cadence section.
Day-30 RAG review per workstream
The Day-30 RAG (Red/Amber/Green) review is the earliest credible signal of integration health — early enough to course-correct, late enough that real friction has surfaced. Per…
Day-30 incident retrospective
The Day-30 incident retrospective aggregates every P0-P3 incident logged across all 8 workstreams in the first month and asks the question a single-workstream view cannot: are…
Day-30 integration budget burn report
The Day-30 integration budget burn report tracks integration cost — the one-time spend on consultants, retention bonuses, system migrations, severance, and rebranding — against…
Day-30 board update
The Day-30 board update is the first formal credibility signal the deal sends to the board and investors after close. It reuses the standardised board-update template authored in…
Day-30 plan rebaseline (where reality diverges)
By Day 30 the pre-close integration plan has met reality, and reality has won in places. The rebaseline is the disciplined act of resetting the plan where bottom-up evidence now…
M4.S2 - Top-100 30-Day Check-In Cadence
Conduct 30-day check-ins for all Top-100 (CSM-led 30-min calls; agenda: how's the integration landing, any concerns, what would you change). NPS delta measurement (baseline vs Day-30), churn signal review, customer-comms decision-tree messages at Day-7 + Day-30.
Conduct 30-day check-ins for all Top-100
The combined entity's Top-100 customers carry the majority of ARR and the entire O2 "hold the base" commitment — and they are precisely the accounts most likely to read a merger…
NPS delta measurement (baseline vs Day-30)
NPS delta — the change in Net Promoter Score from the pre-Day-1 baseline to Day 30 — is the most sensitive instrument for detecting customer-sentiment damage before it converts…
Churn signal review (any at-risk Top-100?)
The churn signal review is where the soft signals from the 30-day check-ins and the NPS delta get converted into hard, account-level action. Mergers create a window of elevated…
Send Day-7 + Day-30 customer-comms decision-tree messages
Customer reassurance after a merger is not a single email — it is a cadenced sequence, and the Day-7 and Day-30 touches are the two that hold the relationship through the…
M4.S3 - Initial Cultural Pulse
Launch initial cultural pulse survey (Day 14 or 21), analyse pulse survey results (acquirer vs target cohort), cultural fault-line readout to Steering, perception workshops (Bain-style: self/other/assumed). 12 items mapped to Bain three fault lines.
Launch initial cultural pulse survey (Day 14 or 21)
Culture is the most-cited cause of merger failure and the least-measured. The initial cultural pulse survey, fielded at Day 14 or 21, captures the first quantitative read on how…
Analyse pulse survey results (acquirer vs target cohort)
A pulse survey only creates value once it is analysed for the cohort gap. The raw scores are noise; the signal is the delta between acquirer-origin and target-origin employees on…
Cultural fault-line readout to Steering
By Day 30 the initial cultural pulse has surfaced where the acquirer and target diverge in lived behaviour — and culture, not synergy spreadsheets, is what sinks most deals (Bain…
Perception workshops (Bain-style - self / other / assumed)
Most post-merger cultural friction is built on inaccurate stereotypes rather than real value conflict — each cohort acts on a caricature of the other ("they're bureaucratic,"…
M4.S4 - Synergy Tracker Baseline
Build synergy tracker (T2D3 IP - per-KR rows: baseline, target, weekly actual, corrective action, proof link), set baseline run-rate (combined-co Day 30), author corrective-action protocol, stand up proof-link evidence store.
Build synergy tracker (baseline / target / weekly actual)
The synergy tracker is the single source of truth that connects the deal thesis to reality — without it, synergy capture drifts on vibes and Steering discovers a miss a quarter…
Set baseline run-rate (combined-co Day 30)
Synergy capture is meaningless without a credible starting line. The Day-30 baseline run-rate freezes the combined-co's financial state before integration effects accrue, so every…
Author corrective-action protocol (when actuals miss)
A synergy tracker that flags red but triggers nothing is theatre. The corrective-action protocol pre-commits the combined-co to what happens when weekly actuals miss — before…
Stand up proof-link evidence store
Synergy claims that can't be traced to a source document don't survive an audit, a board challenge, or an investor diligence — and 42% of deals already fail to convert diligence…
M5 - Day 100 Operating-Model Cutover
Lock in the operating model. Day 100 is when boards expect signal; this module's deliverables are the credible board narrative. KPIs: 20-30% synergy run-rate captured, <=50% integration cost burned, 90%+ critical talent in seat, NPS +/-5 of baseline, cultural index >=3.0/5. T2D3 stage T2/D1/D2; STOP Optimize -> Productize.
M5.S1 - Operating-Model Cutover
Execute ERP cutover, CRM cutover, HRIS cutover, billing cutover, support tooling cutover, Day-100 ops cutover readout. Each cutover follows the IT cutover runbook with dry-runs, validation queries, rollback plan, freeze windows.
Execute ERP cutover
The ERP cutover is the highest-stakes move of the Day-100 operating-model phase: it gates billing, AR/AP, treasury, and revenue recognition simultaneously, so a botched cutover…
Execute CRM cutover
The CRM cutover is where revenue operations live or die: accounts, contacts, open opportunities, and activity history all move at once, and a single lost opportunity or scrambled…
Execute HRIS cutover
The HRIS cutover carries an absolute, bright-line constraint that no other system migration shares: payroll cannot break. A late or wrong paycheck during integration does more…
Execute billing-system cutover
The billing-system cutover is where customer trust meets cash collection: subscriptions, payment methods, and dunning rules all migrate, and any error shows up as a wrong invoice,…
Execute support tooling cutover
The support tooling cutover is the customer-facing tail of the Day-100 operating-model migration: tickets, the knowledge base, and customer interaction histories all move, and the…
Day-100 ops cutover readout
The Day-100 readout is the gate that closes the operating-model cutover phase: it tells Steering, in one disciplined session, whether the combined-co is now running on one…
M5.S2 - Day-100 KPI Review
Synergy capture readout, talent retention scorecard, customer NPS delta, cultural index second pulse, Day-100 board update. The Day-100 board signal sets investor narrative for the rest of Y1. Sign-off section.
Synergy capture readout (Day 100)
The Day-100 synergy capture readout is the first public, board-grade proof point that the deal thesis is real. Day 100 is when investors and the Steering Committee stop accepting…
Talent-retention scorecard (Day 100)
The Day-100 talent-retention scorecard measures whether the value embedded in people — the ~2% critical talent identified in M1.S5 — has actually stayed. Talent flight is the most…
Customer NPS delta (Day 100)
The Day-100 customer NPS delta answers the O2 question: did we hold the base? In B2B SaaS, the target's continuing-customer relationships are a non-trivial commitment in the deal…
Cultural index (Day 100, second pulse)
The Day-100 cultural index is the second pulse since the Day-14/21 baseline, and movement matters more than the absolute score. Culture is where most B2B SaaS mergers quietly fail…
Day-100 board update
The Day-100 board update is the public credibility milestone of the integration — the moment the board, investors, and lenders form their narrative for the rest of Year 1. Per…
M5.S3 - Brand & Pricing Launch
Execute brand decision (rebrand/sub-brand/endorsed), launch combined-co website, update pricing page, refresh marketing collateral, issue Day-100 press release with synergy proof points. Gated on brand decision != preserve.
Execute brand decision (rebrand / sub-brand / endorsed)
Executing the brand decision turns the brand-architecture decision-tree output into live, customer-facing reality across every touchpoint at once. The choice — full rebrand,…
Combined-co website launch
The combined-co website launch is the most visible Day-100 deliverable — the front door every customer, prospect, partner, and analyst checks first. It must execute the brand…
Pricing page update (combined-org tiers)
The pricing page update publishes the harmonised combined-org tiers to the market — the visible end of the pricing-harmonisation work and a direct lever on the revenue-synergy…
Marketing collateral refresh
The marketing collateral refresh propagates the brand decision and combined value proposition into every asset the revenue team uses in front of buyers. After the website and…
Press release at Day 100 (synergy proof points)
The Day-100 press release converts integration progress into a public, on-the-record narrative anchored to synergy proof points. Where the Day-1 release announced intent, the…
M5.S4 - Comp-Plan Harmonisation Launch
Launch harmonised comp plans, redesigned quotas + territories, sales certification program, rep-by-rep redline meetings (HR + manager). Mid-sized+ deals require full comp-plan + quota + cert + redline; tuck-ins use abbreviated approach.
Launch harmonised comp plans
Launching harmonised comp plans is the moment two different sales-incentive systems become one — and the single most trust-sensitive event in GTM integration. Reps don't read the…
Launch redesigned quotas + territories
Launching redesigned quotas and territories completes the GTM operating-model cutover: it assigns who owns which accounts in the combined org and what each rep is now expected to…
Launch sales certification program
When two B2B SaaS sales forces merge, the single fastest way to stall the revenue-synergy thesis is to put reps in front of customers before they can credibly sell the combined…
Rep-by-rep redline meetings (HR + manager)
A merged comp plan, new quota, and redrawn territory are existential to a salesperson's income — and a mass-email rollout of those changes is the single most reliable way to…
M6 - Day 365 Synergy Capture & PMO Wind-Down
Deliver the deal thesis. Capture >=50% public synergy run-rate by Month 12 (KR1.1). Wind down the IMO into BAU governance - STOP P / Productize. KPIs: synergy >=50%; cultural index >=3.5; talent retention >=85%; integration cost <=6% of deal value. T2D3 stage D1/D2.
M6.S1 - Synergy Realisation Reporting
Month-12 synergy readout vs deal thesis, validate cost synergies (audit trail), validate revenue synergies (cross-sell pipeline + ARR), integration cost final tally vs budget, investor / public synergy-realisation report.
Month-12 synergy readout (vs deal thesis)
The Month-12 synergy readout is the moment the integration is judged against the public deal thesis decomposed at M1.S2 — the version the board, investors, and regulators saw at…
Validate cost synergies (audit trail)
By Month 12 the IMO will have claimed a cost-synergy number all year; this task makes that number audit-quality — defensible to the board, the auditor, and any future investor…
Validate revenue synergies (cross-sell pipeline + ARR)
Revenue synergies are the hardest part of any deal thesis to prove because they lag — per DealRoom, typical Year-1 capture is only 10–20% of the committed cross-sell value. That…
Integration cost final tally (vs budget)
Synergies tell only half the value story; the other half is what it cost to capture them. The Month-12 integration-cost tally closes the loop by reconciling every dollar of…
Investor / public synergy-realisation report
This is the external credibility artifact of the entire integration — the report that goes to investors, the board, and (for public acquirers) the market, declaring how much of…
M6.S2 - Cross-Sell Motion Activation
Launch cross-sell motion (combined-org accounts), roll out acquirer products to target customers, roll out target products to acquirer customers, design and launch cross-sell SPIF, build cross-sell pipeline tracking dashboard.
Launch cross-sell motion (combined-org accounts)
The cross-sell motion is where the revenue-synergy thesis becomes real. Cost synergies are largely internal and capturable in Year 1; revenue synergies depend on getting the…
Roll out acquirer products to target customers
This is one of the two directional plays inside the cross-sell motion (M6.S2): selling the acquirer's products into the target's installed base. It is often the higher-confidence…
Roll out target products to acquirer customers
This is the second directional play of the cross-sell motion (M6.S2): selling the target's products into the acquirer's installed base. It is frequently the strategic reason for…
Cross-sell SPIF design + launch
A SPIF (Sales Performance Incentive Fund) is the short-term, surgical incentive that overcomes a sales force's natural inertia toward selling what it already knows. After a…
Cross-sell pipeline tracking dashboard
The cross-sell pipeline dashboard is the instrument panel for the entire revenue-synergy thesis. Without it, the cross-sell motion (M6.S2), the directional roll-out plays, and the…
M6.S3 - IMO Wind-Down
Check IMO sunset criteria (95% synergies / culture +/-2 points), design BAU governance (post-IMO, T2D3 IP), transfer residual issues to function leads, IMO team redeployment, IMO archives handover. Formal wind-down sign-off section.
Check IMO sunset criteria (95% synergies / culture +/- 2 points)
The Integration Management Office is a temporary institution, and the discipline of PMI is knowing when to dissolve it. An IMO that lingers past its purpose becomes a parallel…
Design BAU governance (post-IMO)
The most common wind-down failure is dissolving the IMO without naming its successor. The sunset criteria define the trigger; BAU governance is the destination. If you simply…
Transfer residual issues from IMO to function leads
At wind-down, the IMO's central issue tracker is never empty — there is always a tail of open items: a half-finished vendor consolidation, a deferred data-migration cleanup, an…
IMO team redeployment / next-deal capture
The IMO team — the Director, program managers, data analyst, and change-management specialist — has spent a year becoming the company's most integration-literate talent. At…
IMO archives handover (templates + lessons + decisions)
When the IMO dissolves, its accumulated knowledge either becomes durable corporate IP or evaporates with the team. The archives handover is the act that makes a one-time…
M6.S4 - Lessons Learned
Workstream-lead retrospectives (8 x 2h), lessons-learned document for next deal, template updates (charter, runbook, decision tree). Roll-up / synthesis section.
Workstream-lead retrospectives (8 x 2h)
The retrospective is where tacit integration knowledge gets converted into transferable lessons. Each of the 8 workstreams — Finance, IT & Data, HR & People, Legal & Compliance,…
Lessons-learned document for next deal
Eight workstream retrospectives produce raw material; this task synthesises them into a single, decision-grade lessons-learned document that the next IMO will actually open on Day…
Template updates (charter, runbook, decision tree)
Lessons learned are inert until they are baked into the templates the next deal starts from. This is the step that closes the loop on the synergy muscle: the IMO Director takes…
M6.S5 - Year-1 Board Retrospective
Author Year-1 deal-thesis-vs-reality narrative, Year-1 board deck (synergy / talent / customer / culture), Year-1 board session (90-min), investor / public Year-1 narrative. Final board-level sign-off section.
Author Year-1 deal-thesis-vs-reality narrative
This is the single most important credibility artifact of the entire integration: an honest reckoning of what the deal promised at sign versus what it actually delivered at Day…
Year-1 board deck (synergy / talent / customer / culture)
The Year-1 board deck is the formal close-out of the deal at the governance level — the document that tells the board whether the acquisition created the value it underwrote. It…
Year-1 board session (90-min)
The Year-1 board session is the live forum where the integration is formally judged and the IMO's mandate is closed out. It is not a status read-out — the deck does that…
Investor / public Year-1 narrative
The final integration deliverable is the external story: how the combined company frames Year 1 to investors, analysts, customers, and the market. Internally you graded the thesis…
M7 - Culture & Communications (cross-cutting)
Hold the cultural-integration index >=3.5/5 by Month 12 (KR2.3). Apply Pain-Claim-Gain to employee narrative and customer comms. McKinsey 7S diagnostic at 90 days. T2D3 stage T2/D1; STOP Standardize -> Optimize.
M7.S1 - Pain-Claim-Gain Employee Narrative
Articulate employee Pain (uncertainty, identity, comp), author Claim (commitments to skills, comp, role), author Gain (combined-co growth, opportunity, mission), roll out narrative on Day 1 / 30 / 100 / 365 cadence, coach managers on PCG narrative use.
Articulate employee Pain (uncertainty, identity, comp)
The Pain-Claim-Gain (PCG) employee narrative is T2D3 proprietary IP, and its credibility lives or dies on the Pain step. In a B2B SaaS merger, the announcement detonates a cloud…
Author Claim (what we commit to)
With employee Pain surfaced, the Claim is the second beat of the Pain-Claim-Gain narrative: a precise, time-bound commitment from combined-co leadership answering each Pain…
Author Gain (what employees get from combined-co)
The Gain is the third and forward-looking beat of the Pain-Claim-Gain narrative: once you have acknowledged the fear (Pain) and stabilized it with commitments (Claim), Gain…
Roll out narrative (Day 1 / 30 / 100 / 365 cadence)
A Pain-Claim-Gain narrative authored once and dropped on Day 1 decays within weeks — anxiety regenerates as new ambiguities surface, and a single town hall cannot carry an…
Coach managers on PCG narrative use
Front-line managers are the single highest-trust communication channel in any merger — employees believe their own manager over a CEO email by a wide margin. But a manager who is…
M7.S2 - 90-Day Cultural Diagnostic (T2D3 IP)
T2D3 PROPRIETARY IP. Design McKinsey 7S diagnostic instrument (12-item x 2-cohort), launch at Day 90, analyse acquirer x target x combined target, author fault-line interventions per Bain three categories, readout to combined leadership team.
Design McKinsey 7S diagnostic instrument
Culture clash is the most-cited reason mergers underdeliver, yet it is rarely measured — most acquirers manage it on gut feel until attrition spikes. This task, T2D3 proprietary…
Launch 7S diagnostic at Day 90
The 90-day mark is the deliberate launch window for the McKinsey 7S cultural diagnostic: early enough that integration interventions can still change trajectory, late enough that…
Analyse 7S results (acquirer x target x combined target)
Raw 7S survey data is inert until it is read as a three-way comparison — legacy-acquirer cohort vs. legacy-target cohort vs. the combined-target ideal. The analytical payload of…
Author fault-line interventions per Bain three categories
A cultural diagnostic that ends at a scorecard changes nothing — the value is in the interventions it triggers. This task converts the analyzed 7S deltas into concrete, owned…
7S readout to combined leadership team
The cultural diagnostic only changes the organization if the combined leadership team owns its findings and commits, by name, to acting on them. This 60-minute readout is that…
M7.S3 - Pain-Claim-Gain Customer Comms
Articulate customer Pain (disruption, uncertainty, billing change), author Claim (no service disruption, named contact, transparency), author Gain (better product, broader capability, value), roll out customer PCG narrative on Day 1 -> 365 cadence.
Articulate customer Pain (disruption, uncertainty, billing change)
The same Pain-Claim-Gain discipline applied to employees applies to customers — and in B2B SaaS the stakes are revenue itself. The moment a deal is announced, every customer…
Author Claim (what we commit to customers)
With customer Pain surfaced, the customer Claim is the stabilizing commitment combined-co makes to each Pain dimension — and in B2B SaaS it is, quite literally, a retention…
Author Gain (what customers gain from combined-co)
The Gain is the third leg of the Pain-Claim-Gain (PCG) customer narrative and the only one customers actually care about: not why you merged, but what they get out of it. In B2B…
Roll out customer PCG narrative (Day 1 -> 365 cadence)
A great Pain-Claim-Gain narrative is worthless if it lands once and goes silent. The integration year is a trust-decay curve: customers re-evaluate at every support ticket,…
M7.S4 - Engagement & Pulse Cadence
Engagement survey cadence (Day 14 / 60 / 180 / 365), pulse tracker dashboard (combined-co), stand up integration ambassador program, monitor cultural fault lines monthly. Recurring cadence section.
Engagement survey cadence (Day 14 / 60 / 180 / 365)
Culture is the silent killer of M&A value — Bain's Cultural Integration research attributes a large share of failed deals to people and engagement erosion that leadership never…
Pulse tracker dashboard (combined-co)
A survey cadence only creates value if its signal is visible at a glance to the Steering Committee. The pulse tracker dashboard consolidates engagement, eNPS, and retention…
Stand up integration ambassador program
Surveys tell you what changed; ambassadors tell you why. The integration ambassador program recruits frontline employees from both legacy companies to give the IMO unfiltered,…
Monitor cultural fault lines monthly
Cultural fault lines are the predictable seams where a merged organization cracks under stress: us-vs-them tribalism, clashing decision norms (consensus vs. command), pay/title…
M8 - Risk & Issues Log (cross-cutting)
Capture every risk and issue, route to owner, drive to closure. Per Umbrex IMO playbook - central tracker captures severity, timestamp, owner, root-cause hypothesis, mitigation steps, closure. No spreadsheet workarounds permitted. T2D3 stage T2/D1; STOP Templatize -> Productize.
M8.S1 - Register Stand-Up
Design register schema (severity, owner, root-cause, closure), configure register tooling (Jira/Asana/native), distinguish risk (not yet) vs issue (occurred), load initial risks from M1 charter + workstream charters, train owners on register use. Recurring risk-log governance.
Design register schema (severity, owner, RC, closure)
The Risk & Issues Register is the IMO's central nervous system: every fear, blocker, and incident across all eight workstreams lands in one place with one shared grammar. A sloppy…
Configure register tooling (Jira / Asana / native)
A schema on paper is inert; the register only becomes the IMO's operating reality once it lives in a tool everyone uses daily. Configuring the register tooling means implementing…
Distinguish risk (not yet) vs issue (occurred)
The single most common register failure is collapsing risks and issues into one undifferentiated pile — which means everything gets the same (wrong) treatment. Per…
Load initial risks from M1 charter + workstream charters
An empty register on Day 1 is a lie — the integration's biggest risks were already named in the M1 IMO charter and the eight workstream charters before close. Loading them is a…
Train owners on register use
A register is only as honest as the people who feed it. Training risk and issue owners — the workstream leads and their delegates across M3-M8 — converts the tooling from a PMO…
M8.S2 - Severity-Based SLA Operations
Roll out P0 protocol (15min triage / 6h resolution / CEO auto-notify), P1 protocol (1h triage / 24h resolution / Steering daily), P2/P3 protocol (same-day triage / 5d / monthly batch), author escalation playbook (one-step rule), weekly RAG audit of register.
P0 protocol rollout (15min triage / 6h resolution / CEO auto-notify)
A P0 is an integration emergency — customer-facing outage, data loss, a regulatory breach, a top-account about to churn, a key leader resigning. These are the events that destroy…
P1 protocol (1h triage / 24h resolution / Steering daily)
In post-merger integration, P1 issues are the second-most-severe class in the IMO register — material to synergy capture or the customer base but not the existential, CEO-wakes-up…
P2/P3 protocol (same-day triage / 5d / monthly batch)
Most of an integration's issue volume is not P0/P1 — it is the long tail of P2 (functional friction that slows a workstream but doesn't threaten synergy or the customer base) and…
Author escalation playbook (one-step rule)
An SLA without an escalation path is a deadline nobody enforces. The escalation playbook is the mechanism that converts a missed clock into action by someone with more authority —…
Weekly RAG audit of register
The issue register only creates value if someone reads it as a whole on a fixed rhythm. The weekly RAG (Red/Amber/Green) audit is that read — the standing 60-minute review where…
M8.S3 - Issue Closure & Audit Trail
Author issue-closure criteria (root-cause + remediation + audit), quarterly audit of closed issues, pattern analysis (recurring root causes), handover register to BAU governance at IMO sunset.
Author issue-closure criteria (root-cause + remediation + audit)
The most common failure in an integration risk log is the premature close — an issue marked "done" because the symptom went away, not because the cause was fixed. That's how the…
Quarterly audit of closed issues
Closure criteria only hold if someone checks that they were actually applied. The quarterly audit of closed issues is the back-stop control: a periodic spot-check that samples…
Pattern analysis (recurring root causes)
Individual issues get resolved; recurring issues need to be designed out. Pattern analysis is the systemic layer of the risk log — it mines the accumulating set of closed issues…
Handover register to BAU governance at IMO sunset
When the IMO meets its sunset criteria (95% synergies captured, culture index within ±2 points, no critical Day-365 incidents), it dissolves — but the risk and issues register…