Professional Services
›
Corporate Development & Strategy
›
M&A & Integration
Acquisition Integration
Decisions that reshape organizational direction, structure, and partnerships.
Accenture
McKinsey
BCG
Kearney
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, deadlines, constraints, and what 'run-rate synergies' look like within 90 days.
Alignment Questions
Start Here: Who’s carrying this 90‑day baton?
- Tell us your role and the individual who will own delivering the 90‑day run‑rate synergies.
- Acquirer (legal entity) and Target (legal entity) — provide names and the business lines being absorbed.
- Has the purchase agreement been signed and are there any outstanding material conditions?
- When is close (or anticipated close)?
- Are other integrations from your portfolio currently in flight that will compete for the same people or tooling?
- In one sentence, what is the single most important thing you need to have true at Day 90?
Are We Quietly Banking on Miracles?
- What are you assuming will simply work out on its own in the first 90 days — that, if it didn’t, would break the plan?
- How confident are you in the current 90‑day synergy estimate?
- List the top three assumptions behind the synergy numbers (e.g., immediate vendor conversions, zero revenue attrition, swift ERP cutover).
- Which of those assumptions have you validated with real data or target subject-matter reviews?
- If those assumptions fail, what is the near‑term consequence for cash flow, reporting, or the deal thesis?
What's Actually Running Under the Hood?
- How likely is it that an unknown systems dependency in the target will force a parallel run longer than 90 days?
- Which of the following core systems does the target use? (pick all that apply)
- Which systems are heavily customized, on legacy stacks, or supported by one vendor/consultant?
- Do you have admin access, test environments, and data extracts available for each critical system pre‑close?
- Which integrations (APIs, EDI, payroll runs, bank feeds) connect the target to customers, suppliers, or regulatory systems?
- Roughly how many months of transactional data and master records must be migrated/validated for financial consolidation?
Who's Going to Walk Out the Door First?
- Who at the target, if they left in the next 30–60 days, would make the 90‑day plan impossible?
- Please list the top five roles or named individuals we must retain through Day 90 and why each is critical.
- Which retention levers are available or already promised (pick all that apply)?
- Have you already communicated equity treatment, reporting lines, or role changes to key staff? If so, what was the reaction?
- Are there contractual or regulatory obligations (e.g., visa sponsorship, union rules) that raise the risk of losing people post‑close?
- If we had to design a minimal retention package today, what are the non‑negotiables it must include?
Which Contractual Landmines Are We Ignoring?
- Which vendor or customer contract clause, if triggered by change of control, could erase the projected savings?
- Approximately how many of the target’s top 20 vendor contracts contain change‑of‑control, assignment, or automatic termination clauses?
- Do any customer contracts restrict assignment or permit contract termination or repricing upon a change of control?
- What are typical notice periods and mandatory cure windows in the target’s vendor/customer contracts?
- Are any agreements subject to third‑party consents (e.g., landlords, licensors, regulators)?
- Who will lead contract conversions and negotiations post‑close (names/roles)?
If Your CFO Only Cares About One Number…
- If you could only deliver one measurable proof point at Day 90 that would prove the deal is on plan, what would it be and why?
- Which of these synergy categories must be realized in 90 days? (pick up to three)
- For each selected synergy category, specify the metric we’ll report and the acceptance criteria (e.g., $X saved, Y% cost reduction, Z systems decommissioned).
- Which financial close deliverables are required at Day 1 versus Day 90? (pick all that apply)
- How will synergy realization be tracked and who approves the reported numbers?
What Would a Realistic Day One and 90‑Day Runbook Actually Look Like?
- Which Day One capability are you most tempted to compromise on to hit timelines (even if it increases risk)?
- Select the non‑negotiable Day One capabilities we must guarantee (pick all that apply).
- What cutover windows are acceptable for finance close, billing, and order processing (choose all that apply)?
- Do we have documented fallback controls and rollback triggers for each critical process? If not, where are the gaps?
- What specific data extracts, reconciliations, and validations must be completed before cutover (list prioritized items)?
- Which external vendors require advance notice or parallel onboarding steps for Day One (e.g., payment processors, EDI partners)?
Who Decides When Things Go Off the Rails?
- If a critical milestone slips by 72 hours, who has the authority to reassign resources or pause the cutover, and what will they do?
- Document the RACI for decisions during pre‑close and the first 90 days (names/roles for Responsible, Accountable, Consulted, Informed).
- What governance cadence do you want for the first 90 days?
- Which KPIs should appear on the governance dashboard (pick all that apply)?
- What is the escalation path for commercially-critical decisions (names/roles and expected SLA to resolve)?
- What budget contingency is available for emergency external resources (e.g., third‑party engineers or migration specialists)?
Final Readiness Pulse — If We Start Today, Where Do We Begin?
- If we had to start work today, what single blocker must be removed immediately to make meaningful progress?
- On a scale of 1–10, how ready is your organization to execute the Day One plan and initial 90‑day runbook?
- List the top three open risks that should be our first mitigation priorities.
- What internal resources (number of people and estimated hours/week) can you commit immediately to support cutover and migrations?
- Preferred start date for pre‑close readiness engagement or immediate advisory support.
- What documents, system accesses, or stakeholder introductions should we request first (list top 5 items)?
-
Current State Mapping
Document the target’s ERP/CRM architecture, vendor contracts, people risks, and integration blockers that threaten the 90‑day plan.
Current State
Start Here — The quick snapshot that gets us moving
- Who is the legal acquirer and the target entity for this integration, and who will be our primary integration contact?
- How many days remain until close (or since close, if already closed)?
- What is the numeric 90‑day run‑rate synergy target (cash savings or EBITDA uplift)?
- Which internal teams are currently assigned to support integration activities?
- In one sentence—what would success at Day 90 look like for you?
If Day 90 Misses, What Breaks First?
- If we miss the 90‑day target, which business outcome will be impacted first and why?
- How likely do you think each of those outcomes are on a scale of 1–5? (1 = Very unlikely, 5 = Very likely)
- Give an example of a recent integration or operational change that caused unexpected downstream disruption—what happened?
- Which stakeholders (roles or names) will feel the pain first if the plan slips?
- How would missing Day 90 change your appetite for scope trade‑offs versus schedule concessions?
Where Your Technology Actually Lives (and who controls it)
- Which system is the current source of truth for financials, and which for customer data? List product names and hosted vs on‑prem.
- Can the target’s ERP/GL and CRM be exported or migrated without vendor‑level consent or downtime? If known, specify constraints.
- How many distinct production databases, ERPs, or CRMs will need to be consolidated or integrated?
- Describe any heavy customizations, home‑grown modules, or bespoke reporting the target relies on (names/functions).
- Who currently administers each system (internal team, MSP, vendor)—and how long have they owned it?
Contracts That Can Turn Projected Savings Into Surprises
- Which vendor or customer contracts contain change‑of‑control clauses, early termination fees, or assignment restrictions that could affect Day One or 90‑day savings?
- How many contracts require notice or renegotiation within the next 90 days (estimate)?
- Are there any material auto‑renewals, evergreen clauses, or confidentiality provisions that limit our ability to convert contracts to buyer paper?
- Who owns vendor relationships today and who will be authorized to negotiate or sign amendments?
- If you had to prioritize contract workstreams for the first 30 days, which three would you pick and why?
Who's Irreplaceable (and How Fragile Are They?)
- Which named individuals or roles are critical to revenue, ops, or systems continuity, and what would be the immediate impact if they left within 30–60 days?
- Do key employees have equity, retention agreements, or other incentives that are unresolved at close?
- How have you communicated ownership, reporting lines, or compensation changes to target employees so far?
- Which roles are single points of failure (one person knows how everything works)? List role and how long they’ve been in post.
- What retention levers are available (cash bonuses, equity acceleration, role guarantees) and how fast can they be implemented?
Hidden Tech Debt and Quiet Workarounds — the stuff that stretches timelines
- What manual workarounds, spreadsheets, or undocumented processes currently glue systems together?
- Are there single‑vendor APIs or third‑party services we rely on that have limited transferability?
- How complete is your system and process documentation (0–100%) for core functions that must be live Day One?
- Who on the target side can walk a stranger through critical end‑to‑end processes (finance close, order‑to‑cash, payroll)?
- If we needed to accept a pragmatic Day One workaround, what three tasks would you be willing to accept as manual for the first 30 days?
Will We Actually Get the Keys (data access, admin rights, exports)?
- Which of the following will require legal or vendor sign‑off before we can extract data or change configuration?
- For each critical system, what is the expected timeline to grant admin access and full data export capability?
- Are there security, compliance, or data residency rules that will restrict migration or require specialized handling?
- Who approves cross‑domain access requests (IT security, legal, CIO), and what is the typical approval SLAs?
- If access is delayed, what contingency do you consider acceptable (e.g., limited exports, read‑only access, third‑party extraction)?
Decision Speed — Who Can Trade Scope for Time?
- If a critical blocker appears in week two, who has the authority to sign a scope concession that preserves the 90‑day deadline?
- What governance cadence and escalation path do you want for the first 90 days (weekly, twice weekly, daily war room)?
- What acceptance criteria must be met for consolidated financials and core systems to be considered 'Day One acceptable'?
- If we propose a temporary carve‑out or dual‑stack approach, what minimum KPIs would convince you it’s an acceptable trade?
- How quickly do you expect the integration advisory team to be embedded and making decisions (days from engagement)?
Lessons From the Field — What We Should Copy or Avoid
- Think of a past integration that either accelerated well or derailed—what single decision made the difference?
- Which playbook artifacts or templates do you already have (integration runbook, cutover checklist, vendor amendment templates)?
- How comfortable are you reusing a standard, repeatable 90‑day migration playbook vs. building one from scratch?
- What internal resistance or political dynamics have historically slowed integrations in your org?
- If we proved a small, reversible approach in the first 14 days, what would you want us to demonstrate to earn broader buy‑in?
Immediate Next Moves — Where to Apply Focus in Week One
- From our conversation, which three items should be top of list for the first 7 days?
- Which stakeholders do you want present in a Day‑0 kickoff (names/roles)?
- What would you consider a non‑starter that would require pausing integration until resolved?
- How would you like us to report progress—format and cadence (dashboard, email, weekly review)?
- Are there any documents, login credentials, or contracts you can share in the next 48 hours to accelerate our first assessment?
-
-
Outcome Discovery
Define measurable 90‑day success signals, priority synergies, and the non‑negotiable Day One capabilities.
Discovery Questions
Quick Orientation — Why We're Here (5 minutes)
- Tell us briefly: what specifically triggered this 90‑day plan for the current acquisition?
- Who are you and which role will own hitting the 90‑day run‑rate synergies?
- How soon is close (or when did close occur)?
- What would you most like us to solve first in the next 30 days?
- In one sentence, what would make you say the 90‑day plan was a clear success?
If 90 Days Fails, What Actually Breaks?
- If we miss the 90‑day run‑rate, what is the single biggest negative outcome you fear?
- How would that outcome show up in the next quarterly board update or LP call?
- Who outside your immediate integration team feels the impact first (finance, sales ops, procurement, legal, portfolio CFO, others)?
- How would missing the 90‑day target change leadership’s appetite for future add‑on deals?
- How worried should we be—what's your confidence today that the 90‑day promises are realistic?
Where the Money Actually Lives — Baselines and Believability
- Your model promises run‑rate synergies. Which three line items together represent most of that value?
- For each of those top items, how were savings quantified in the deal model (example: FTE reductions, contract repricing, license rationalization)?
- What evidence did you see in diligence that made those savings credible? If none, what assumptions feel the weakest?
- Do you currently have access to the target's transaction‑level data (AP aging, vendor spend, customer contracts, payroll) to validate those assumptions?
- Which of these would you prioritize for verification in week 1: vendor master, customer contract terms, payroll detail, GL structure, or another dataset?
The People Who Make or Break Day One
- If your top technical or commercial lead left in 30 days, which specific capability or revenue stream would be at immediate risk?
- Who are the 5–10 people whose retention is non‑negotiable for Day One, and why (role, domain knowledge, customer relationships)?
- How clear is communication to target employees about equity, reporting lines, and benefits today?
- What incentives or communications have you already planned to keep those key people through 90 days?
- Have you encountered cultural friction in past integrations that we should anticipate here? Tell a specific example if yes.
Systems — Can We Migrate Without a Six‑Month Parallel?
- What makes you doubt the target's ERP/CRM can be absorbed within 90 days?
- Describe any single integration blocker you’ve seen in diligence (e.g., bespoke billing engine, multi‑entity GL mapping, EDI relationships).
- Where are the single points of failure for Day One financial close—data, reconciliations, intercompany mappings, or something else?
- Which vendor contracts have explicit change‑of‑control clauses or auto‑renewals that could block conversion within 90 days?
- What cutover windows (weekends, month‑end, fiscal close) are we allowed to use—are there hard blackout dates?
Non‑Negotiable Day One — What Must Be Live
- If Day One only delivered three capabilities, which three would be absolutely non‑negotiable to avoid business disruption?
- For each must‑have capability, what acceptance criteria would prove it’s working (e.g., AR aging within X days, invoices issued within Y hours)?
- Which stakeholder will sign off on Day One acceptance for finance, sales, and operations?
- Are there regulatory or customer commitments that legally require continuity on Day One (contractual SLAs, data residency, billing terms)?
- If a Day One capability is degraded, what is an acceptable temporary manual workaround (hours of delay, manual reconciliations, temporary billing process)?
Priority Synergies — What We Should Tackle First
- Which synergy category feels highest‑value and least risky to realize in 90 days: procurement, G&A, revenue ops, or systems consolidation?
- What fraction of modeled synergies are tied to vendor contract conversions versus people or processes (percentage estimate)?
- Which vendor categories could be consolidated quickly (telecom, cloud, office suppliers, SaaS) and which will take time?
- Are there quick governance levers (price floors, delegated approvals, procurement templates) you can deploy immediately to lock savings?
- Which synergy requires executive escalation to unlock (CPO, CFO, CEO), and who is that person?
What’s Getting in the Way — Hidden Assumptions and Dangerous Bets
- What assumption in your 90‑day plan would you call the riskiest if it proved false?
- How dependent is the plan on a single individual’s knowledge or external vendor timelines?
- What contingency exists if a critical vendor refuses conversion or delays notice periods?
- How much flexibility do you have to reallocate integration headcount from other active deals if we need more hands?
- Which internal stakeholders historically under‑indexed on integration commitments and may slow decisions now?
Escalation, Governance, and Fallbacks — Who Decides When Things Go Wrong
- At what point or trigger would you want executive escalation to intervene (X days behind, Y% of synergies missed, major customer at risk)?
- Who should be on the rapid‑decision forum (names/roles) that can approve tradeoffs on Day One issues?
- What consequences or incentives are acceptable to link to synergy milestones (earnbacks, holdbacks, performance fees)?
- What fallback controls should be pre‑positioned (manual journal templates, temporary billing flows, escrowed funds) if automated conversion fails?
- How often do you want status updates and in what format (daily standup, weekly dashboard, executive memo)?
How We'll Measure Success — KPIs, Ownership, and Reporting
- What are the top 5 KPIs that would demonstrate the 90‑day plan is on track (be specific with targets where possible)?
- For each KPI, who is the accountable owner and what data source will we trust for measurement?
- What cadence of reconciliation do you need between the integration tracker and the FP&A model (daily, weekly, monthly)?
- If KPIs show we are off track at day 30, what immediate corrective actions would you expect to see?
- Do you want our team to run the KPI dashboard or hand over to internal ops immediately after Day One?
Decision Time — Comfort, Tradeoffs, and Immediate Asks
- If you had to rate your comfort with the plan right now on a scale of 1–10, what is the number and why?
- What one tradeoff are you willing to accept to hit 90 days (higher short‑term cost, temporary manual work, deferred vendor savings)?
- What immediate access do we need this week to accelerate certainty (data rooms, admin credentials, target leadership time)?
- Who else should join our next call to unblock decisions (name/role)?
- What's the single deliverable from us that would make you feel more confident in 72 hours?
-
Solution Experience
Translate constraints into a practical Day One and 90‑day runbook using real portfolio scenarios to confirm feasibility.
Experience Meetings
- Current-State Synthesis & Consequence Framing
- Portfolio Scenario Workshop — Day One Simulation
- 90-Day Runbook Design — Synergy Milestones & Acceptance Criteria
- Technical Migration Feasibility — ERP & CRM Cutover Plan
- People & Contract Continuity — Retention, Vendor & Customer Conversion
- Publish a data readiness checklist and assign owners for each feed and data conversion mapping.
- Define measurable acceptance criteria for each milestone and module.
- Establish KPI definitions, reporting cadence, and escalation triggers for governance.
- Confirm resource plans and external dependencies to be tracked in the runbook.
- Publish the 90-day milestone tracker with owners, acceptance criteria, and target dates.
- Baseline synergy targets and attach the measurement methodology and data sources.
- Assign owners to each escalation trigger and document the governance flow.
- Compile the resource RACI and identify hiring/contractor gaps to fill within 7 days.
- Confirm Technical Current State in One Sentence
- Select and document the migration approach for each scenario with evidence from portfolio precedent.
- List all data and integration dependencies with owners and timelines.
- Produce a cutover runbook skeleton with rollback controls and test gates to validate the future state.
- Obtain explicit technical owner validation or a clear list of blockers to close.
- Deliver a draft cutover runbook (sequence, owners, validation checks) for review within 48 hours.
- Opening & Objectives
- Schedule integration and end-to-end test windows and assign test case owners.
- Document any remaining technical blockers with mitigation plans and target close dates.
- One-sentence People & Contract Current State
- Agree a prioritized retention plan for critical roles with committed timelines and owners.
- Produce a vendor/customer conversion sequence with acceptance criteria and legal/negotiation owners.
- Finalize Day One communications and people checklist to mitigate immediate attrition risk.
- Obtain owner validation that people and contract plans materially protect the quantified consequence.
- Publish a retention tracker with named owners, retention levers, timelines, and success metrics.
- Create a vendor conversion matrix listing at-risk contracts, notice periods, and conversion actions with assigned negotiators.
- Draft Day One and 30/60/90 communication templates and finalize recipient lists.
- Escalate any non-remediable contract threats to the Mutual Commit agenda with recommended commercial mitigations.
- Produce and gain sign-off on a single-sentence current-state description.
- Quantify consequences in dollars, days, or headcount risk to create urgency.
- Agree a single-sentence future-state outcome that will guide all runbook proof points.
- Confirm scope: systems, contracts, and key roles for Day One and 90-day work.
- Circulate the signed one-sentence Current State and Future State to all attendees.
- Deliver a consolidated consequence worksheet (financial impact, timeline delay, retention risk) with source data and assumptions.
- List outstanding data gaps (systems access, contract copies, employee roster) and assign owners to close within 48 hours.
- Schedule the first Scenario Workshop with required scenario owners and system SMEs.
- Recap: Current State, Consequence, Future State
- Produce an owner-assigned Day One runbook for each scenario with minute-level critical steps.
- Surface and document concrete mitigations for every identified constraint, tied to portfolio precedent where available.
- Define fallback controls and escalation criteria to protect the Day One outcome.
- Obtain explicit owner confirmation or a list of required changes for validation.
- Finalize and publish the Day One runbook drafts per scenario with named owners and timestamps.
- Capture mitigation evidence (historical cutover notes, vendor responses, test results) and attach to the runbooks.
- Schedule a Day One dry-run (tabletop rehearsal) date and assign participants.
- Log residual risks with likelihood/impact and assign owners for risk mitigation plans.
- Restate Future State & 90-day Success Signals
- Agree a week-by-week 90-day milestone map with named owners for each deliverable.
- Select & Describe Scenarios
- One-sentence Current State
- Key Role Mapping & Retention Risk Assessment
- Migration Approach Options & Recommended Path
- Milestone Mapping (Weeks 0–13)
- Contract Change-of-Control Review
- Data Dependencies & Conversion Scope
- Consequence Mapping (Money / Time / Risk / People)
- Run Day One Tabletop per Scenario
- Acceptance Criteria by Module
- One-sentence Future State
- KPI & Reporting Cadence
- Blocker Identification & Evidence-linked Mitigations
- Cutover Runbook Skeleton & Rollback Controls
- Vendor & Customer Conversion Plan
-
Solution Scope
Specify modules—pre‑close readiness, Day One plan, systems migration, vendor conversions, retention—and acceptance criteria.
Scope Configuration
- General Ledger Cutover to Acquirer ERP
- CRM Data Migration and Sales Cutover
- Customer Contract Novation and Re-papering
- Vendor Contract Consolidation and Renegotiation
- Accounts Payable and Receivable Migration
- Payroll and Benefits Transition
- Inventory and WMS Cutover with SKU Mapping
- Weekend Systems Cutover Execution
- Identity and Access Management Merger
- Customer Billing System Migration and Invoice Cutover
- Procurement Spend Consolidation and PO Conversion
- Execute Retention Bonuses and Offer Letters
Scope Questions
General Ledger Cutover to Acquirer ERP
- Do you require a full GL cutover to the acquirer's ERP within 90 days?
- Which ledger system does the target currently use?
- How many legal entities, charts of accounts, and currencies must be consolidated?
- Are there open periods, recurring journals, or complex allocations that require parallel reconciliation?
- What is an acceptable reconciliation tolerance or acceptance criteria for Day One (e.g., trial balance match, AR/GL variance)?
- Who will own GL cutover tasks and approvals on the buyer and target side (names/roles)?
CRM Data Migration and Sales Cutover
- Do you plan to migrate the target's CRM data into the acquirer's CRM or run dual systems temporarily?
- Which CRM platforms are involved (target and acquirer)?
- Approximately how many accounts/contacts/opportunities and custom objects need migration?
- Are there complex territory, quota, or sales ownership rules that must be preserved or remapped?
- What acceptance tests indicate successful sales cutover (e.g., lead routing, opportunity history, salesperson access)?
- Which stakeholders must approve CRM behavior on Day One and who will be the business owner for post-cutover issues?
Customer Contract Novation and Re-papering
- Do target customer contracts contain change-of-control, assignment, or consent clauses that require novation?
- How many customer contracts and contract templates need review and re-papering?
- Are there priority customers that must be re-documented before Day One to avoid revenue disruption?
- Do you require legal drafting, signature workflows, and CRM updates as part of repapering?
- What acceptance criteria will confirm success (e.g., X% of revenue novated, signed amendments logged)?
- Who are the internal approvers and external parties (e.g., customers, counsel) required for contract novation?
Vendor Contract Consolidation and Renegotiation
- Do vendor contracts include change-of-control, auto-renewal, or termination-for-convenience clauses that could affect 90‑day synergies?
- How many vendor agreements and spend categories will be in scope for consolidation?
- Which vendor categories are highest priority (e.g., hosting, SaaS, logistics, manufacturing)?
- Do you want vendor renegotiation to include unified pricing, PO conversion, and assignment to the acquirer?
- What acceptance criteria determine success (e.g., X% cost reduction, contracts assigned, no service interruptions)?
- Who will be responsible for vendor communications, legal reviews, and procurement approvals?
Accounts Payable and Receivable Migration
- Do AR/AP ledgers need to move into the acquirer's systems or be managed via a temporary integration?
- What is the monthly volume/value of invoices and payments (AP) and invoices/receipts (AR)?
- Are there locked billing cycles or customer-specific invoicing rules that prevent immediate migration?
- What cutover day acceptance tests will be used (e.g., invoice delivery, cash application match, vendor payment run)?
- Do you require AP/AR automations (PO matching, remittance advice, lockbox mappings) to be configured during migration?
- Who owns exceptions and dispute resolution post-migration?
Payroll and Benefits Transition
- Will payroll processing move to the acquirer's provider or stay with the target's provider through a transition period?
- How many employees and jurisdictions are in scope for payroll and benefits?
- Are there outstanding equity, severance, or benefit obligations requiring communication before Day One?
- Do you require benefits vendor conversions, enrollment windows, and employee communications included in the plan?
- What payroll acceptance criteria are required (e.g., correct net pay, tax filings, benefit enrollment confirmations)?
- Who are the HR and payroll contacts on buyer and target sides and who will sign off on final payroll runs?
Inventory and WMS Cutover with SKU Mapping
- Is the target using a WMS/ERP for inventory that must be migrated or integrated?
- How many SKUs, locations, and open shipments/POs are in scope for Day One?
- Are there serialized items, lot tracking, or regulatory compliance requirements (e.g., expiry dates) to preserve?
- Do you require physical inventory counts, SKU mapping, and warehouse process training as part of cutover?
- What acceptance metrics indicate success (e.g., inventory accuracy %, successful outbound shipments)?
- Who will be the operations and warehouse owners responsible for cutover and post-cutover reconciliation?
Weekend Systems Cutover Execution
- Do you intend to perform a consolidated weekend cutover for core systems (GL, CRM, Billing) or staggered cutovers?
- What is the preferred cutover window (dates/times) and are there blackout periods to avoid?
- What rollback/fallback controls and exact criteria must be in place to abort and return to pre-cutover state?
- Which teams and named SMEs must be on-call for the cutover (IT, Finance, Sales, Legal, Ops)?
- Do you need runbooks, automated scripts, and test rehearsals included in the weekend execution plan?
- What acceptance checks will be executed at cutover completion (e.g., end-to-end transaction test, report validation)?
Identity and Access Management Merger
- Will the target be moved into the acquirer's identity provider (IdP) and SSO domain on Day One?
- Which identity platforms and authentication methods are in use (e.g., Azure AD, Okta, LDAP)?
- Approximately how many user accounts, service accounts, and privileged accounts must be migrated or reconciled?
- Are there regulatory or security controls (MFA, conditional access, SSO) that must be enforced immediately?
- What roll-forward acceptance tests are required (e.g., user login, app access, privileged account audit)?
- Who is the security/IT owner for IAM decisions and emergency access during cutover?
Customer Billing System Migration and Invoice Cutover
- Do invoices and billing need to be migrated to the acquirer's billing system or left on legacy with integrations?
- How many active billing customers, billing frequencies, and billing templates are in scope?
- Are there complex billing rules (usage billing, proration, multi-currency) that require custom mapping?
- What customer notice and collections workflows must be in place to avoid revenue disruption at cutover?
- What acceptance criteria confirm a successful billing cutover (e.g., invoices issued, payment processing validated, customer portal access)?
- Who will own billing exceptions, customer disputes, and refunds post-cutover?
-
Mutual Commit
Finalize commercial terms, governance, timelines, and escalation tied to measurable synergy milestones.
Agreement Modules
- Commercial Term Sheet
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Synergy Milestone Schedule & Acceptance
- Governance Charter & RACI
- Payment Schedule & Holdback Release
- Escalation & Dispute Resolution Protocol
- Transition Services Agreement (TSA) / Temporary Operations
- Data Processing Agreement (DPA) & Security Addendum
- Retention & Key Talent Incentive Agreement
- Change Order / Scope Amendment Process
- Final Acceptance & Handover Checklist
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Verify data access, cutover windows, vendor notice plans, retention communications, and fallback controls before execution.
Readiness Questions
Quick Check: What’s the one outcome you can’t miss in 90 days?
- In one sentence, what does ‘hitting run‑rate synergies in 90 days’ look like for your team?
- How confident are you today that the 90‑day target is achievable?
- Which target systems must be consolidated or reporting to the parent ERP/GL within 90 days?
- What is the firm deadline (close date, reporting period, or investor milestone) driving this 90‑day requirement?
- Who is the single accountable leader day‑to‑day for delivering the 90‑day plan?
If We Don’t Move Fast, What Breaks First?
- Which of the following failures do you fear most if the 90‑day plan slips?
- How quickly would that failure materialize—days, weeks, or months—if migration is delayed?
- Which customer or contract commitments are most likely to be impacted by a missed Day One?
- How would a missed deadline affect your investor or board narrative on the deal?
- Which metric below best measures the first real sign that the plan is failing?
Who Holds the Keys (and Can We Get Them on Time)?
- Tell us why we might not be handed full admin or export access to the target systems before Day One.
- Which platforms require credentials or data extracts for migration? Select all that apply.
- Are there known security approvals, legal NDAs, or data protection reviews that will delay access?
- If approvals are required, how long do you estimate the approval cycle will take?
- Do you have test or read‑only accounts available today for migration rehearsal?
Vendor Paper & Change‑of‑Control: Is a Clause Quietly Crushing Synergies?
- Which vendor or supplier relationships are likely to trigger a change‑of‑control review or pricing reset?
- Do you have a current inventory of contracts with change‑of‑control, consent, or assignment clauses?
- How many vendor contracts require 30/60/90‑day notices that might force pre‑close renegotiation?
- Who on your team owns vendor notice, consent, and procurement conversion conversations?
- Which vendors are critical for Day One operations (select up to five)?
People Risk: Which Roles Will Make or Break Day One?
- Name the top three people or roles whose departure would prevent a successful Day One.
- How many key employees are at high risk of leaving in the first 60 days given current communications?
- Have you communicated equity, reporting lines, or role stability to those key people yet?
- Do you have retention offers or incentives budgeted and approved for critical talent?
- Who is responsible for day‑one org chart and reporting confirmations?
Cutover Windows & Operational Rhythm: When Can We Safely Switch the Switch?
- What single operational constraint most restricts your cutover window (billing cycles, month end, events, peak season)?
- Which of these windows are acceptable for a full cutover?
- Are there blackout dates in the next 90 days where any migration is strictly prohibited?
- How many cross‑functional resources (IT, finance, ops, sales, support) can be allocated exclusively during your preferred cutover window?
- Would you be open to a staged cutover (critical systems first, others later) if full Day One proved infeasible?
Fallback Controls and War Rooms: Do You Have a Plan B That Actually Works?
- What would you say is the single weakest fallback control in your current Day One plan?
- Which rollback criteria would trigger pausing or reversing a cutover?
- Do you have manual workarounds documented for key processes (billing, order entry, payroll) if automation fails?
- Who is your escalation owner for an emergency decision during cutover (name and role)?
- How often do you want dry‑run rehearsals before the final cutover?
Signing Off: Who Gets the Go/No‑Go and What Do They Require?
- Who must sign the final Day One readiness checklist (names and titles)?
- What minimum acceptance criteria must be met for a go decision (select top three)?
- Which stakeholder is most likely to veto go based on perceived risk rather than data?
- What format do you prefer for a go/no‑go briefing (war room call, slide pack, live demo, checklist)?
- If we identify a single critical blocker today, how quickly can your team commit resources to resolve it?
-
Deployment Enablement
Schedule and execute cutovers, migrations, contract conversions, and retention activities with clear owners and tracking.
-
Validation Checklist
Confirm consolidated financials, migrated systems, converted contracts, and retained key staff meet acceptance criteria.
Validation Questions
Quick Deal Snapshot — Bring Me Up to Speed
- Tell me the short deal facts we should all know right now (target name, approximate revenue, planned close date).
- Who on your side is the day‑to‑day owner for hitting the 90‑day run‑rate synergies?
- How many active integrations is your internal team managing alongside this one?
- Which one synergy in the deal model matters most to you to realize within 90 days (pick one)?
- Right now, how confident are you that the 90‑day target is realistic?
Who Really Holds the Keys?
- If one person at the target walked out tomorrow, could the 90‑day consolidation plan collapse?
- Which specific decision roles at the target must be involved for Day One to work (pick all that apply)?
- Who at the buyer will have final authority on integration tradeoffs (names or titles)?
- Which role(s) currently lack a clear post‑close reporting line and create the biggest decision bottleneck?
- How comfortable is the buyer’s leadership with delegating integration authority off the operating team?
What's Creaking Under the Hood?
- Which single system or integration, if not migrated on schedule, would force a months‑long parallel run?
- Which core systems does the target use today (select all that apply)?
- How customized are those systems (degree of code/config customization)?
- Do you currently have admin access, exports, and historical GL detail available for the target pre‑close?
- Roughly how complex is the data we’d need to migrate (transactions/month, SKUs, active customers)? Please give ballpark numbers.
- Are there third‑party middleware, EDI partners, or outsourced providers that mediate critical flows?
Contracts: Time Bombs or Smooth Transfers?
- Which single contract type is most likely to trigger renegotiation or loss of savings on change of control?
- Approximately how many vendor or customer contracts require counterparty consent or novation to transfer?
- How many contracts have near‑term renewal, termination, or automatic pricing reset windows inside the next 90 days?
- Who owns contract conversions today and will they be available to execute pre/post close (Legal, Procurement, Integration, Other)?
- Are there any bilateral contracts where the counterparty has already indicated they will not permit assignment or will demand material concession?
- Please list or upload the top 5 contracts you believe are most at risk (names, counterparties, and why).
If the Worst Happens — What's Your Fallback?
- If the primary migration fails on Day One, what is the single control that keeps customers invoiced and payroll paid for the next 72 hours?
- Which processes are mission‑critical to maintain without interruption (select all that apply)?
- Are approved cutover windows and outage tolerances already agreed with critical customers and vendors?
- How long would it take to stand up the documented fallback reconciliation and reporting (hours/days)?
- What manual workarounds are you willing to accept temporarily (extra headcount, manual journals, delayed close) if migration slips?
People: Who's At Risk, Who's Motivated?
- Which five people at the target, if they resigned in the first 60 days, would most jeopardize the 90‑day targets (names or functions)?
- Have retention offers, equity clarifications, or stay bonuses been planned or communicated to key staff?
- How certain are you about the messaging and timing we can use to reduce attrition risk (equity treatment, reporting lines, role clarity)?
- Which cultural or reporting mismatch do you anticipate will most stress key contributors (management style, targets, comp structure, remote vs office)?
- What early warning signals should we track for potential departures (reduced responsiveness, missed milestones, raised concerns)?
What Would Perfect 90 Days Look Like?
- If you received a flawless 90‑day report tomorrow, what three accomplishments would it show?
- Which of the following measurable success signals would you require to declare the 90‑day plan a win (select all that apply)?
- For each selected success signal, what is the numeric target or acceptance criteria (percent, $ amount, or hard flag)?
- Which Day One capabilities are non‑negotiable (minimal viable operations we must have at open)?
- What governance cadence will you accept for milestone reviews (frequency, attendees, format)?
Objections, Hidden Costs, and What You Haven't Said
- What's the single unstated reason you believe this integration could fail that you haven't shared yet?
- Which internal stakeholder groups are most likely to push back on consolidation, and why?
- What budget or headcount limits would force you to scale back the 90‑day plan?
- Are there regulatory, tax, or data residency constraints that could prevent full consolidation within 90 days?
- What would make you pause or cancel the integration after close (e.g., material contract loss, key exec departure, unexpected liabilities)?
Agreeing the First Move — What We Need in the Next 48 Hours
- What are the three things we must see or receive in the next 48 hours to credibly scope a 90‑day runbook?
- Which of the following immediate data and documents can you provide now (select all that apply)?
- Who needs to be on a 30‑minute kickoff call this week to unblock access and decisions (names or roles)?
- How would you like us to report early risk signals (format and cadence)?
- Any immediate red flags we should prioritize before we accept the engagement (list them briefly)?
-
-
Success
Review achieved synergies, document learnings, and maintain a shared channel for issues and continuous improvement.
Success Reviews
- Synergy Validation Review
- Lessons Learned & Playbook Update Workshop
- Run‑Rate Sustainment & Monitoring Setup
- Issues Triage & Continuous Improvement Cadence
- People Retention & Knowledge Handoff
Issues & Enhancements
- Establish a persistent, documented channel and weekly cadence for ongoing triage.
- Create 2–3 annotated example scenarios demonstrating playbook use for common edge cases.
- Schedule peer review with two portfolio CFOs/operators before publishing the playbook update.
- Define Future State KPI One-Sentence
- Operationalize measurable monitoring that proves sustained run‑rate synergies.
- Assign clear data ownership and delivery SLAs for KPI feeds and dashboards.
- Establish escalation thresholds and a scheduled governance cadence for ongoing oversight.
- Provision the KPI dashboard with live data feeds and share access with governance within 7 business days.
- Publish the KPI calculation guidebook and data ownership RACI.
- Schedule recurring monthly run‑rate review meetings and calendar invites for the governance group.
- Publish the weekly triage agenda template and assign rotating facilitator.
- Review Open Issues Log
- Clear ownership and SLAs for all open issues impacting run‑rate synergies.
- Opening & Objectives
- Ensure every resolved issue is captured for playbook improvement and traceability.
- Create the shared 'Integration Issues' channel and onboard all owners with notification rules.
- Update the issues register with remediation dates and expected KPI impact for each item.
- Retention Outcome Summary
- Ensure critical people risk is mitigated and that retained employees have a concrete onboarding and retention plan.
- Close knowledge gaps through scheduled handoffs and deliverable artifacts.
- Assign owners for ongoing people engagement and escalation if additional attrition risk appears.
- Issue final retention confirmations and schedule 1:1 check-ins for critical staff over the next 30 days.
- Deliver a complete knowledge transfer packet (SOPs, access lists, vendor contacts) for each function within 7 business days.
- Assign an HR/business lead to monitor attrition indicators and report any early warning signs weekly.
- Validate realized synergies against the 90‑day targets with documentary evidence.
- Obtain formal acceptance or assign remediation owners and timelines for shortfalls.
- Produce a clear decision record that changes contractual or payout triggers where applicable.
- Publish the finalized synergy realization report with supporting evidence and distribute to governance.
- Owner(s) of each remediated synergy to submit corrective action plans within 7 business days.
- Prepare a single-page executive sign-off document for signatures by integration and finance leads.
- Recap of Objectives and One-Sentence Future State
- Turn tacit integration knowledge into explicit playbook changes that reduce repeat risk.
- Prioritize a minimal set of high‑impact updates deliverable before the next acquisition.
- Assign accountable owners and timelines to finalize playbook artifacts.
- Deliver updated '90‑day runbook' with new gating criteria and checklists within 10 business days.
- Triage & Prioritize
- Exit & Stay Interview Insights
- What Worked — Proof Points
- Agree Core KPIs & Acceptance Thresholds
- Current State (one-sentence)
- What Failed — Root Cause Analysis
- Financial Consequence Summary
- Assign Resolutions & SLAs
- Role Mapping & Gaps
- Dashboard & Data Ownership
- Escalation Rules & Cadence
- Variance Review by Synergy Bucket
- Finalize Retention & Onboarding Actions
- Set Communication Channel & Cadence
- Brainstorm Playbook Corrections
- Knowledge Transfer Deliverables
- Root Cause Attribution
- Handoff & Training Plan
- Prioritize & Define Minimum Viable Playbook Updates
- Continuous Improvement Loop
- Acceptance & Remediation Decisions
- Assign Owners & Deadlines
- Confirm Next Steps & Sign-off