Add-On Acquisitions
High-stakes financial decisions requiring trust, structured diligence, and coordinated stakeholders.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Executive Outcome Alignment
Align the buyer, the seller, and portfolio stakeholders on strategic acquisition objectives, target criteria, success metrics, and key integration risks.
Discovery Questions
Starting Where You Are
- How many add-on acquisitions has your team completed in the last 24 months?
- Tell me about the most recent close, focusing on timeline, key handoffs, and one surprise your team encountered.
- Name the person who led day-to-day integration and the function they represented.
- List the three metrics your team watches in the first 90 days after close.
- Share a concrete example of an acquisition that exceeded expectations and what changed because of it.
- Estimate how much management time, in hours per week, acquisitions typically consume for your leadership team in the first three months.
What Breaks First When Integration Stresses Operations
- If an add-on reduced your customer retention by 3 percentage points this quarter, would you still push the integration forward?
- Describe which operational process—billing, order fulfillment, support—would feel the impact first and why.
- When a recent integration caused a spike in support tickets, how long did elevated tickets remain above baseline?
- Who on your operations team is authorized to pause customer-impacting changes if metrics deteriorate?
- Choose the scenarios that most worry you during integration.
- Which single operational constraint, if unresolved, would make you stop pursuing an acquisition right now?
Are We Aligned on Why This Acquisition Matters
- If the deal met revenue targets but required two quarters of margin compression, would leadership accept that trade-off?
- Outline the top two strategic objectives from your 3-year plan this acquisition must support.
- Who will be accountable to the board for tracking acquisition ROI, and what cadence of reporting do they already produce?
- List the three KPIs that must move within 12 months for you to call the acquisition successful.
- Which metric would make you walk away immediately if the target could not meet it in the first year?
- Rate your appetite for short-term disruption from this acquisition
The Price, The Deal, The Boundaries
- Suppose the seller required a price 15% above your target cap, would you withdraw of pursue with adjusted terms?
- Identify the purchase agreement clauses your CFO considers non-negotiable.
- Name the retention and incentive mechanisms you typically deploy to keep acquired leaders and critical staff.
- Estimate the valuation multiple range you would consider for targets of your usual size.
- Choose which deal boundaries are deal breakers for you.
- Specify the approver who must clear any above-capacity price increase for the deal to proceed immediately.
Integration Risks That Keep You Up at Night
- Would replacing a core system to enable integration be acceptable, and under what budget conditions?
- Provide the parts of your tech stack that must remain untouched during migration.
- Identify who owns API access and the credentials needed to migrate customer and billing data.
- On a scale from 'not ready' to 'clean and deduplicated', how mature are your customer data hygiene practices?
- Are there regulatory or contractual approvals that could block transfer of customer contracts?
- Declare the technical constraint that, if unresolved within 30 days of LOI, would terminate the project.
The Alternatives You Are Weighing
- Assuming your current approach were delivering the plan, what would have to be true for you to keep it rather than partner externally?
- Provide the internal teams that have proposed executing add-ons without outside support.
- Share the incumbent vendors or advisors you currently use for deals of this size.
- Would staying with your incumbent partner require changes for you to meet the timeline and targets we discussed?
- What single condition would cause you to reject external help and proceed with an internal-only approach?
- Select the alternative solutions you are actively evaluating.
- How much confidence do you have in each alternative's ability to preserve customer relationships?
Can You Deliver On Day One — Readiness and Constraints
- Assume access to named systems and data is delayed by 10 business days after signature, can your integration timeline remain intact?
- Identify the systems that must be reachable with API or SFTP to complete a typical migration.
- Who will supply credentials and where will they be stored during migration?
- Estimate the headcount and skill mix you can assign to integrations over the next six months.
- Are there existing vendor contracts that limit how you transfer data or customers?
- Which single resourcing gap, if not filled within two weeks of LOI, would prevent you from starting integration?
- Select the compliance or regulatory gates that could delay close.
- Describe your emergency rollback process for the first 30 days after launch.
Close the Loop — Decision Drivers and Next Steps
- If a pilot proves the uplift you expect, what remains that could stop you from signing the deal within a week?
- Which approvals, signatures, or board votes must occur before you can commit?
- Name the internal champion who will drive week-to-week decisions through closing.
- What is your target closing window from LOI to signed agreement?
- Which single remaining question, if answered positively today, would let us move to a mutual commit this week?
- Select how soon you'd like a follow-up planning workshop.
-
Integration Strategy Session
Walk through how the add-on acquisition program will deliver growth, retention, and operational outcomes using the buyer's portfolio context and realistic target scenarios.
Solution Experience
- Integration Strategy Session
- Confirm the current state and its cost
- You confirm the demonstrated scenarios remove the main sources of integration disruption you described.
- Provide three representative target profiles with last 12 months of revenue, contribution margin, and headcount by function.
- You agree on the success metrics and go/no-go criteria that will be used to advance a target to Acquisition Scope.
- Walk through two realistic target scenarios and P&L impact
- Deliver a scenario-modeled P&L and integration risk register for the selected pilot target within five business days.
- Map the integration playbook to your operating model
- You commit to one pilot target to move into scoped diligence with named owners and timelines.
- Confirm the approval authority and maximum investment threshold required to proceed to Acquisition Scope.
- Validate success metrics and go/no-go criteria
- Forced validation, confirm this maps to what you meant
- Integration Strategy Session
- Integration Strategy Deck
- Integration Strategy Solution Brief
- meeting
- slides
- document
-
Acquisition Scope
Define deal boundaries, target selection filters, valuation assumptions, integration responsibilities, retention plans, and measurable deliverables.
Scope Configuration
- Source and Outreach to Target Sellers
- Deliver Screened Target Pipeline
- Execute Financial and Operational Due Diligence
- Negotiate and Finalize Purchase Terms
- Draft and Execute Letter of Intent
- Manage Transaction Closing and Funds Transfer
- Migrate Acquired Company CRM Records
- Consolidate Accounting and Reporting Systems
- Onboard Key Employees and Transfer Benefits
- Execute First-100-Day Integration Playbook
- Run Customer Transition and Contract Notifications
- Integrate IT Systems and Data Migrations
Scope Questions
Source and Outreach to Target Sellers
- Do you have an existing target criteria list (for example revenue range, geography, NAICS codes) to drive outreach?
- How many broker or intermediary relationships should be included in active outreach per quarter?
- Which outreach channels should be prioritized (for example broker CRM introductions, direct-owner email, trade show contacts)?
- Who will be the named owner for inbound outreach responses and lead qualification (provide name and contact role)?
- When do you expect the first outbound campaign to launch and what target list size should it include (for example month and number of targets)?
Deliver Screened Target Pipeline
- What is the primary screening metric you require on each target profile (for example trailing twelve months revenue, gross margin, recurring revenue percent)?
- Specify the minimum revenue and EBITDA ranges we should filter on for the pipeline (for example $1-5M revenue, $250-500K EBITDA).
- Provide the scorecard fields you want in each target profile (for example revenue growth, tech stack, top 10 customers percentage).
- List the red flags that should exclude a target from the screened pipeline (for example active litigation, >30% customer concentration, unresolved regulatory findings).
- Are there any geographic or regulatory jurisdictions we must exclude from the pipeline (for example non-qualified countries or states with compliance issues)?
Execute Financial and Operational Due Diligence
- Will you require a forensic quality of earnings (QoE) report or a standard adjusted EBITDA analysis for targets?
- Estimate the depth of vendor contract review needed (for example top 20 supplier contracts, all master services agreements, change-of-control clauses).
- Confirm which financial periods should be covered by diligence (for example last 12 months, fiscal year-end trailing twelve months, three-year trend).
- Identify the operational systems we must access for diligence (for example your source CRM exports, order management database, inventory SKU master).
- Describe the cost synergy tests we should run on payroll, overlapping SG&A, and shared procurement categories (for example vendor repricing potential, headcount overlap count).
Negotiate and Finalize Purchase Terms
- Which valuation assumptions should guide term negotiation (for example target EBITDA multiple range, working capital peg, earnout hurdles)?
- What is the maximum cash consideration you are willing to approve before requiring investment committee escalation?
- Specify the preferred deal structures to propose (for example asset purchase, stock purchase, membership interest sale).
- Provide the target indemnity cap and survival period ranges you want to negotiate (for example cap = 100% of purchase price, survival = 12-24 months).
- Who on your team is authorized to approve negotiated term sheets up to defined thresholds (provide name and approval limit)?
Draft and Execute Letter of Intent
- Do you require the LOI to include exclusivity and standstill clauses?
- List the conditions precedent that must appear in the LOI (for example satisfactory due diligence, regulatory approvals, third-party consents).
- When should the exclusivity period in the LOI start and what duration (in days) is acceptable?
- What signatures and witness requirements do you expect on the executed LOI (for example authorized signer, notary, witness on schedules)?
- Identify any third-party notification templates you want attached to the LOI (for example broker fee letter, landlord consent notice).
Manage Transaction Closing and Funds Transfer
- What escrow or holdback mechanics should be included in the purchase agreement and escrow instructions (for example escrow amount, release conditions)?
- Describe the wire and bank account verification process you require for final funds transfer (for example template wire instructions, KYC checklist, bank confirmation steps).
- Confirm which closing deliverables you require in escrow (for example executed purchase agreement, officers' certificates, resignations, consents).
- What evidence will validate that funds transfer and closing are complete (for example cleared wire confirmation, released escrow statement)?
- Who will be the authorized signer and provide the bank-sourced signature verification letter at closing (provide name and title)?
Migrate Acquired Company CRM Records
- How many contact, account, deal, and activity records must be migrated from the source CRM export (provide counts by object if available)?
- Indicate the record types that require historical activity migration (for example past 24 months of calls, invoices, support tickets).
- What mapping rules should be applied between source CRM fields and the integration endpoint (for example account ID, custom tag fields, lead source)?
- What acceptance criteria will confirm the CRM migration is complete (for example 99% account match rate, zero orphaned deals, reconciled activity samples)?
- Choose the de-duplication strategy you prefer for CRM records (for example match on email+company, fuzzy name match, manual review threshold).
Consolidate Accounting and Reporting Systems
- Indicate the target chart of accounts file or mapping example you will provide for general ledger mapping.
- What reconciliation tolerance thresholds should apply to accounts payable / accounts receivable roll-forwards (for example <0.5% variance, <$5,000 absolute)?
- Explain the deferred revenue and subscription ID mapping required to align recurring revenue in consolidated reporting.
- What evidence will validate consolidated reporting is accepted by finance (for example closing pack, trial balance match, variance analysis signed off)?
- Name the person who will provide historical P&L and balance sheet source files and point contacts for GL mapping (include file path or SFTP user if available).
Onboard Key Employees and Transfer Benefits
- Are you able to provide an employee census file export (for example payroll ID, hire date, compensation, benefits election) for the acquired company?
- What notice or offer letter templates should be used for new employment contracts and benefits enrollment?
- Name the payroll provider category and benefits carrier types that require cutover coordination (for example payroll provider export, medical carrier enrollment files, 401(k) vendor).
- How will you handle accrued vacation and final payroll runs for transferring employees (for example cutoff payroll period and payout rules)?
- Detail the benefits enrollment artifacts that must be migrated (for example plan IDs, employee elections file, COBRA notices).
Execute First-100-Day Integration Playbook
- What are the critical day-one operations we must preserve (for example billing runs, customer support SLAs, fulfillment cutoffs)?
- Define the 30/60/90 milestones that must be in the playbook with owners (for example CRM cutover day+30, pricing harmonization day+60).
- Please list the individuals assigned to handle customer escalations and the 24-hour response process during integration (name and role).
- Explain the contingency steps if the CRM cutover misses its data migration window (for example fallback to dual-write, manual order entry procedures).
- What communication templates should be included for customer-facing emails and service desk scripts during the first 100 days?
Run Customer Transition and Contract Notifications
- Detail the customer contract types that require assignment or consent notifications (for example material statements of work, master service agreements, reseller agreements).
- When should customers receive transition notices relative to close (for example immediate, 7 days after close, at first billing)?
- Define the customer segments that should receive white-glove outreach versus standard email notification (for example top 10 accounts, regulated customers).
- How will you handle contract assignment that triggers change-of-control consent requests for strategic customers (for example pre-notify, request consent, escrow solution)?
- What customer-facing SLA or billing changes should be included in notification templates (for example invoice remittance changes, new support hours)?
Integrate IT Systems and Data Migrations
- Are API documentation and service accounts available for the systems to be integrated (provide SFTP/API endpoint list)?
- Select the data flows that must be real-time versus batch (for example order creation, inventory sync, customer status).
- What authentication and rate-limit expectations exist for the APIs to be used (for example OAuth tokens, 1000 requests per minute)?
- What rollback plan will you accept if a data migration introduces duplicate invoices or inventory mismatches (for example freeze, reconciliation script, reverse batch)?
- Estimate the monitoring and alert thresholds to be configured post-migration (for example failed sync rate >1%, unmatched SKUs >0.1%).
-
Mutual Commit
Finalize commercial terms, approval authorities, governance cadence, investment thresholds, and closing conditions required by both parties.
Agreement Modules
- Purchase Agreement
- Disclosure Schedules
- Escrow & Holdback Agreement
- Transition Services Agreement (TSA)
- Key Employee Retention Agreements
- Closing Conditions & Deliverables Checklist
- Approval & Signatory Matrix
- Governance & Post-Closing Oversight Agreement
- Tax Allocation & Contingent Liability Agreement
- Regulatory Filings & Consents Plan
-
Deployment
Operationalize integration with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — named owners, diligence and systems access, integration windows, and customer/employee communication plans — before execution begins.
Pre-Deployment Questions
Environment and access
- Which buyer systems and endpoints will the integration touch? (select all that apply — choosing these lets us size connectors and test scope)
- For each system you selected, when will production-level integration access be available? (enter a date per system or 'not available' — so we can schedule initial API/tests)
- How will required integration credentials/service accounts be provisioned?
Data and configuration
- Which data domains must be migrated or continuously synchronized at cutover? (select all that apply)
- Is the authoritative source (system of record) confirmed for each selected data domain? If not, list domains still needing a decision.
- Has the field‑mapping and dedupe approach for core domains been approved, and who owns mapping sign‑off? (so we can schedule test migrations)
People and ownership
- Who is the named overall integration owner (name and role)? (deployment team will escalate to this person)
- Are named owners assigned for these workstreams: technical integrations, data migration, business continuity/rollback, customer communications, employee retention/onboarding? If unassigned, write 'unassigned' next to the workstream.
Timing and constraints
- Are there approved integration windows or operational blackout periods that restrict cutover dates/times? If yes, list them with timezones; if none, enter 'none'.
- Are there mandatory approvals, compliance gates, or third‑party sign‑offs required before execution? Select the nearest authority (we will request expected clearance date in a follow-up field).
-
Integration Configuration
Lock exact configuration values the deployment team will use: system mappings, migration steps, data handoffs, and retention/incentive mechanics.
Configuration Details
Integration Configuration — Systems & Instances
- Primary source system type for customer and account records (select one). Options reflect the source where the migration job will read data: "source CRM org", "source ERP system", "SFTP-hosted CSV exports", "data lake / object store", "Other (specify in next question)"
- Exact source system instance identifier (enter the non-secret instance name the migration job will target; examples: "prod-crm-01", "erp-prod-3", "s3://bucket-name/path"). Enter exactly as it appears in your environment.
- Primary target system type for customer and account records (select one). This tells the deployment which connector to configure: "buyer production CRM org", "buyer production ERP", "buyer data warehouse / analytics", "platform integration endpoint", "Other (specify in next question)"
- Exact target system instance identifier (enter the non-secret instance name the migration job will write to; examples: "crm-prod-west", "dw.cluster.company", "integration-endpoint-v2"). Enter exactly as it should appear in connector settings.
Integration Configuration — Credentials & Secure Handoffs
- Credential owner email for the source system (format: name@domain). This is the person the deployment team will contact to request non-secret identifiers and to coordinate secret exchange via your secrets manager.
- Which secrets manager will be used to exchange vaulted credentials for connectors? Select one: "your secrets manager (e.g., HashiCorp Vault)", "buyer corporate secrets manager (e.g., enterprise vault)", "platform-managed secrets vault", "Other (we will coordinate secure channel at kickoff)"
Integration Configuration — Field Mappings, Migration Cadence & Retention
- Exact source field name for the customer unique identifier (enter the case‑sensitive field/column name as it appears in the source; example: "AccountId" or "customer_id"). This value will be used verbatim in the mapping table.
- Exact target field name for the customer unique identifier (enter the case‑sensitive field/column name as it should be written to the target; example: "account_id" or "customer_uid"). This value will be written verbatim into the target mapping configuration.
- Preferred migration cadence for initial cutover (select one). Default behavior matters for scheduling and rollback plans: "One-time full cutover (single migration window)", "Phased by business unit (seed + parallel run per BU)", "Phased by record type (customers first, then transactions) with delta sync", "Continuous incremental sync (no planned cutover)"
- Maximum allowed migration throughput (numeric). Enter the upper limit the deployment should target in records per hour for bulk migration jobs. Default is 5000 (enter a whole number).
- Retention period for historical transactional data to be migrated into the target (enter number of years). Default is 7 (enter a whole number). This value configures archive vs. live-target cutoffs.
- Key-employee retention bonus duration to configure in post-close retention mechanics (enter number of months). Default is 12 (enter a whole number). This numeric value will be used verbatim in the retention plan artifact.
-
Integration Execution
Execute the integration plan with named owners, a Gantt of milestones, dependency tracking, and escalation paths to protect core business performance.
-
-
Sustain & Value Realization
Monitor EBITDA, retention, and customer-satisfaction KPIs, validate realized synergies, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (Weeks 1-4)
- First Outcomes Measurement Review (Weeks 4-10)
- Acceptance Gate — 90-Day Outcome Decision
- Quarterly Value Realization Review
Issues & Enhancements
- Product/ops to update the shared enhancement request channel and notify stakeholders of planned delivery windows.
- Validate and certify the financial data sources feeding the acceptance gate report.
- Restate acceptance criteria and required signatory
- Produce a documented acceptance decision for the acquisition integration with the named signatory recorded.
- Create a binding remediation plan with owners and dates for any conditional or failed criteria.
- Confirm the incumbent system decommissioning or retention approach and the archival status of legacy data.
- Publish the signed acceptance record and distribute to governance stakeholders.
- Open remediation tickets for any conditional items with owners, milestones, and review dates.
- Execute incumbent system contract closeout or convert to read-only and archive data per the agreed schedule.
- KPI dashboard review versus Acquisition Scope targets
- Confirm whether realized EBITDA contribution and customer satisfaction are sustained against the Acquisition Scope run-rate.
- Maintain a prioritized backlog of enhancement requests with owners and delivery windows.
- Agree the monitoring cadence and data owners for the next quarter.
- Owner to close the top 3 backlog items impacting retention or CSAT within the agreed quarter.
- Finance to publish the quarterly EBITDA reconciliation versus Acquisition Scope projections.
- Re-confirm scope, success criteria, and owners
- All deployment completion items are confirmed done or have named owners and resolution dates.
- Top 3 operational blockers are triaged with owners and committed resolution dates.
- Agreement on the data sources and cadence for the first outcomes measurement.
- Publish the deployment completion checklist annotated with owners and resolution dates.
- Deliver the adoption and system-health logs to the review team within 5 business days.
- Create escalation path documentation and distribute to named owners.
- Present first-period results against Acquisition Scope targets
- Determine whether consolidated EBITDA and 90-day retention are trending toward the Acquisition Scope targets or require remediation.
- Name owners and delivery dates for the top corrective actions needed before the acceptance gate.
- Confirm data validation steps so the acceptance gate can rely on the presented figures.
- Produce a variance pack showing line-item drivers for EBITDA delta and retention cohort behavior.
- Implement the agreed retention initiatives for acquired accounts and report weekly adoption metrics.
- Present final outcome data against each criterion
- Realized synergies validation
- Deployment and migration validation
- Variance analysis and root-cause diagnosis
- Document pass/fail and capture formal acceptance decision
- Early adoption signals and usage patterns
- Open issues and enhancement request backlog
- Operational blockers impacting financials or retention
- Blocker triage and immediate remediation plan
- Agree corrective actions, owners, and dates
- Operational risk and escalation review
- Agree remediation plan for any failed or conditional criteria
- Next steps and short-term checkpoints
- Incumbent system wind-down and data archival check
- Next quarter monitoring plan and checkpoints