The First 100 Days After an Acquisition: Commercial and Digital Integration Plan

The First 100 Days After an Acquisition: Commercial and Digital Integration Plan

The 100 day plan in private equity is the execution contract between the deal team’s assumptions and the operating reality you just bought. Get it wrong, and you spend months recovering from preventable fires: a CFO who never had real forecasting authority, a CRM that sales abandoned two years ago, a customer concentration nobody stress-tested. Get it right, and you enter your first board meeting with a baseline you trust, decision rights that function, and a management team that knows what they own.

I have worked on post-close integrations where the first 100 days determined whether the platform could absorb add-ons at pace, or whether it stalled for eighteen months fixing fo100-dayundational gaps. The difference is not luck. It is sequencing, ownership clarity, and knowing what must not break while you change everything else.

This article is a working playbook. It covers the phases, the checkpoint gates, and the specific deliverables that separate disciplined value creation from hopeful improvisation. At the end, you will find a sequencing table you can adapt for your next close.

What Must Not Break in the First Hundred Days

Before you optimize anything, identify the load-bearing walls. Every acquired company has two or three processes that, if disrupted, will crater revenue or destroy management credibility before you get a chance to improve them.

Common examples: the weekly sales pipeline review that keeps reps accountable, the invoicing cycle that maintains cash flow, the escalation path that keeps the largest customer from churning. These are not glamorous. They are often undocumented. But they hold the business together.

Your first task, before Day 1, is to map these critical processes with the outgoing owner or the CEO. Ask a simple question: “If we accidentally broke this in the next 90 days, what would be the commercial consequence?” Anything with a seven-figure downside or a key customer relationship at risk goes on a protected list. You do not touch those processes until you have redundancy or a tested replacement.

This is not about being conservative. It is about preserving the cash flow that funds your transformation. According to McKinsey’s research on post-merger integration, up to 70% of integrations fail to achieve their expected synergies, often because operational disruption undermines the base business while leadership chases growth initiatives.

The “Do Not Touch” Register

Create a one-page register listing each protected process, its owner, the risk if disrupted, and the earliest date you will revisit it. Share this with every workstream lead. It prevents well-intentioned consultants from “improving” something that keeps the lights on.

Do Not Touch Register | TABLE with columns: Process Name | Current Owner | Disruption Risk (Revenue Impact) | Protected

Days 0 to 30, establishing baseline and access

The first thirty days are about truth-finding, not transformation. Your diligence model contained assumptions. Now you validate them against actual data, actual systems, and actual management capability.

Commercial Baselining

Before you can measure improvement, you need a baseline you trust. This means reconciling the revenue figures in your model with what the finance team can actually produce from source systems. I have seen deals where the “ARR” in the CIM was a spreadsheet estimate that differed from the billing system by 15%. You cannot run a private equity value creation plan against a fiction.

In the first two weeks, produce a single-page revenue baseline: trailing twelve months by customer cohort, by product line, by geography. Compare it to the deal model. Document every variance above 5%. These variances become your early warning system.

System Access

You cannot govern what you cannot see. By Day 14, the operating partner or integration lead should have read access to the core systems: ERP, CRM, HRIS, and the financial reporting stack. Not admin access, just visibility. If the company resists, that resistance is diagnostic. It often signals data quality problems they do not want you to discover.

Create a system access matrix: system name, access level requested, owner who grants it, date granted, and any blockers. Escalate blockers to the CEO immediately. According to Bain’s research on integration best practices, delayed system access is one of the top three causes of integration timeline slippage.

Management Reporting

Most acquired companies have reports. Few have reports that answer the questions a new owner needs answered. In the first 30 days, establish the weekly and monthly reports you will use for portfolio company operating reviews. Do not accept the existing report package without examination. Ask: “What decision does this report enable?” If no one can answer, the report is noise.

By Day 30, you should have a one-page operating dashboard covering revenue (actual vs. plan), cash position, pipeline coverage, and headcount. Anything more complex can wait.

Days 0-30 Priorities | 4-step horizontal process: Step 1 "Commercial Baseline (Revenue by cohort, variance to model)" →

Days 31 to 60, decision rights and integration architecture

With a baseline established, the second month focuses on governance. Who decides what, at what threshold, with what approval chain? Ambiguity here is the source of most post-close dysfunction.

Decision Rights Framework

A post acquisition integration fails when every decision escalates to the board, or when decisions happen in silos without coordination. You need a decision rights matrix, often called a RACI or RAPID, that specifies:

  • What decisions the CEO owns unilaterally
  • What requires board notification
  • What requires board approval
  • What the operating partner can direct without CEO involvement

Be specific. “Strategic decisions require board approval” is useless. “Any customer contract above $500K annual value requires board notification before signing” is actionable.

Publish this framework by Day 45. Review it with the CEO and the board chair. If there is disagreement, surface it now, not during a time-sensitive negotiation.

Post Merger Integration Plan Structure

If you are executing a post merger integration strategy following an add-on or a platform combination, Days 31 to 60 are when you finalize the integration plan architecture. This includes:

  • Workstream definition (finance, technology, commercial, HR, legal)
  • Workstream leads and their decision authority
  • Integration dependencies (what must complete before something else can start)
  • Synergy targets with owners and measurement dates

The post-merger integration checklist I use covers revenue, data, and customer systems in detail. The key principle: every synergy target needs an owner, a baseline, a target, and a measurement date. “We will achieve $2M in procurement savings” is not a plan. “CFO owns $2M procurement savings, baseline spend is $8M, target is $6M by Q4, measured via AP analysis” is a plan.

Communication Plan

Employees, customers, and vendors are all watching. By Day 45, you need a communication cadence that prevents rumor from filling the vacuum. This does not mean oversharing. It means structured updates at predictable intervals.

A basic communication plan includes:

  • Weekly all-hands email from the CEO (5 minutes to read, focused on one or two updates)
  • Monthly town hall with Q&A
  • Customer communication for any changes that affect them (pricing, contacts, contracts)
  • Vendor notification for payment term changes or new procurement processes

HBR’s research on change management shows that consistent communication reduces employee anxiety and improves retention during transitions. The goal is not inspiration. It is predictability.

Decision Rights Matrix | TABLE with columns: Decision Type | Example | Owner | Approval Required | Threshold ,  rows: "Hi

Days 61 to 100, execution rhythm and checkpoint gates

The final forty days are about proving the operating model works. You are not just planning anymore. You are running the business under the new governance, catching failures early, and preparing for the first board meeting with credible evidence.

Checkpoint Gates

A 100 day plan in private equity needs explicit checkpoints, not just a final review at Day 100. I use three gates:

  • Day 30 Gate: Baseline validated, system access complete, protected processes documented
  • Day 60 Gate: Decision rights published, integration workstreams staffed, synergy owners assigned
  • Day 90 Gate: First full month of reporting under new cadence, initial synergy tracking, any red flags escalated

Each gate has exit criteria. If you do not meet them, you do not proceed with the next phase’s initiatives. This prevents the common failure mode of launching growth projects before foundational work is complete.

Acquisition Integration Validation

By Day 75, you should be running the business under the new operating model, not the legacy one. This is when you validate whether the integration plan is working:

  • Are the new reports being produced on time?
  • Are decisions flowing through the rights matrix without bottlenecks?
  • Are the synergy workstreams on track against their targets?
  • Has any “do not touch” process required emergency intervention?

Document what is working and what is not. This becomes input for the Day 100 board presentation.

First Board Meeting Preparation

The Day 100 board meeting is your first real accountability moment. Come prepared with:

  • Baseline vs. model variance analysis (what we thought vs. what we found)
  • Decision rights framework (how we are governing)
  • Synergy progress (early indicators, not final results)
  • Risk register (what could go wrong, what we are doing about it)
  • Next-quarter priorities (what we will focus on now that foundation is set)

Do not oversell. Boards respect operators who surface problems early. They lose confidence in operators who hide them.

100-Day Checkpoint Gates | 3-tier vertical timeline: "Day 30 Gate: Baseline validated, System access complete, Protected

100-Day Plan Sequencing Table

Below is a working template you can adapt for your next post-close integration. Each row includes the deliverable, the owner, key dependencies, and the exit criteria that must be met before moving forward.

Phase Deliverable Owner Dependencies Exit Criteria
Pre-Day 1 Protected Process Register Operating Partner CEO input, outgoing owner input Register signed off by CEO, shared with all workstream leads
Days 0-14 System Access Matrix Integration Lead IT cooperation, legal review of access terms Read access to ERP, CRM, HRIS confirmed for operating team
Days 0-30 Commercial Baseline Document CFO Finance team capacity, system access TTM revenue by cohort reconciled to model, variances documented
Days 0-30 Weekly Operating Dashboard CFO Data access, report template agreement Dashboard produced for two consecutive weeks without errors
Day 30 Gate 1 Review Operating Partner All Day 0-30 deliverables All exit criteria met, or exceptions documented with remediation plan
Days 31-45 Decision Rights Matrix CEO + Operating Partner Board chair alignment Matrix published, reviewed with CEO and board chair, no open disputes
Days 31-60 Integration Workstream Charters Integration Lead Synergy targets from deal model Each workstream has lead, scope, dependencies, synergy target, measurement date
Days 31-60 Communication Plan CEO HR and legal review Cadence published internally, first all-hands completed
Day 60 Gate 2 Review Operating Partner All Day 31-60 deliverables All exit criteria met, or exceptions documented with remediation plan
Days 61-90 First Full Reporting Cycle CFO Dashboard operational Monthly close completed under new process, board pack draft produced
Days 61-90 Synergy Tracking Report Integration Lead Workstream leads reporting Initial synergy indicators documented, on-track or at-risk status assigned
Day 90 Gate 3 Review Operating Partner All Day 61-90 deliverables All exit criteria met, board meeting materials in draft
Day 100 First Board Meeting CEO + Operating Partner All prior gates passed Board presentation delivered, Q2 priorities approved, risk register reviewed
100-Day Plan Dependencies | Flow diagram showing: "Protected Process Register" feeds into "System Access + Baseline" fee

What separates successful post-close execution

The 100 day plan in private equity is ultimately about converting deal thesis into operating evidence. You entered with assumptions about revenue quality, management capability, and synergy potential. You exit the first hundred days with validated data, functioning governance, and a management team that knows what they own.

The operators who succeed at this share a few characteristics. They protect the base business while building the new one. They establish decision rights before they need them. They measure against baselines, not aspirations. And they surface problems early, before small issues become board-level crises.

The sequencing table above is a starting point, not a final answer. Adapt it to your deal, your platform, and your management team’s capacity. But do not skip the gates. The discipline of explicit checkpoints is what separates a post merger integration plan that delivers from one that drifts.

The first hundred days after close are not a grace period. They are the foundation for everything that follows: the add-on integrations, the growth initiatives, the eventual exit. Get the baseline right, establish governance that functions, and prove the thesis has legs. For a live post-close engagement, DevriX can run the first-100-days commercial and digital integration.


Mario Peshev is a 5x CEO and operator, founder of DevriX and Growth Shuttle, global value creation advisor, angel investor, and author of “MBA Disrupted.”

His original background in engineering rode the wave of IT entrepreneurship in the last 25 years, from product and service entrepreneurship through acquiring and selling businesses, to investing in global startups like beehiiv, doola, the Stacked Marketer, Alcatraz, SeedBlink.

Peshev spent over 10,000 hours in consulting and training contracts for mid-market and enterprise organizations like VMware, SAP, Software AG, CERN, Saudi Aramco since 2006. His books and guides are referenced in over 50 universities in North America, Europe, and Asia.


Follow Mario on social:

Latest Editions:

Latest Answers: