An acquisition is not finished at close. It is finished when the clients have moved, the carriers are appointed, the producers are signed and the systems are merged — and whether the revenue that was bought is still there. Most programmes track that in a project plan that knows nothing about the book.

This post follows the illustrative Riverbend Commercial Insurance, a middle-market commercial agency in Columbus, at day 40 after its close: the 100-day plan adopted as tasks, the retention tracker by producer and by client tier, and the appointment tasks that are now overdue.

Use case card
ActorsIntegration lead (owns the plan), deal lead, practice leader
TriggerClose recorded; the integration planner's prepared plan adopted
Agency IllustrativeRiverbend Commercial Insurance — closed Sep 19, 2026; 17 tasks, 6 done
Agents involvedIntegration planner, client match agent, carrier mapping agent
Stage gateDay 100 is recorded only when every task due by day 100 is done
Decisions and authorityAdopting the plan (integration lead, capped at ask first); task status (task owners)
OutcomeRevenue retained since close, tracked by producer and client tier, with the overdue work named
What is measuredRevenue retained; clients transferred, mapped, pending and lost; tasks done and overdue
Acquisition Workspace · integration
The workspace hero for an illustrative agency in integration
Riverbend Commercial Insurance (illustrative), closed and integrating: every stage to Signed checked off.
Home · integration lead
InsightRollup home for an integration lead, on illustrative data
Home for an integration lead: the acquisition integrating, the open tasks, revenue retained since close and what the agents prepared for them.

The plan the findings produce

The integration planner turns the findings into tasks across six areas — producers, clients, carriers, systems, finance, people — each with a day offset from close, an owner and a reason. Key producers produce day-0 retention agreements; renewals in the first 90 days produce a day-1 protection task; unappointed carriers produce day-30 appointments; data-quality rows produce a day-45 clean-up before migration; small carrier books produce day-90 moves at renewal; the largest cross-sell gap produces a day-100 review. Tasks tied to a high-severity finding are flagged high risk.

gantt title Riverbend 100-day plan (illustrative) dateFormat YYYY-MM-DD axisFormat %d %b section Producers Retention agreements (4) :done, p1, 2026-09-19, 1d section Clients Protect first-90-day renewals :done, c1, 2026-09-20, 1d Confirm client matches :active, c2, 2026-10-03, 14d Cross-sell review :c3, 2026-12-28, 1d section Carriers Appointments (3) :crit, k1, 2026-10-19, 14d Move small books at renewal :k2, 2026-12-18, 1d section Systems and finance Redirect commission payments :crit, f1, 2026-10-19, 14d Clean flagged rows :active, s1, 2026-11-03, 1d Migrate AMS data :s2, 2026-11-18, 1d
Workspace · Integration
The 100-day integration plan as tasks, on illustrative data
The 100-day plan as tasks: day, area, owner, due date and status, high-risk tasks flagged, overdue dates in red.

The retention tracker

Workspace · Integration
The retention tracker after close, on illustrative data
The retention tracker at day 40: revenue retained, clients transferred, mapped, pending and lost, by producer and by client tier.

At day 40: 97.1% of revenue retained; 635 clients transferred, 264 mapped, 172 pending and 36 lost. By producer, one producer's book has lost 16 clients and retains 93.8% — the lowest. By client tier (A is the clients bringing the first half of revenue), tier A retains 96.8%, tier B 97.9%, tier C 96.6%. Illustrative figures.

stateDiagram-v2 [*] --> Pending: client in force at close Pending --> Mapped: matched to an acquirer account Mapped --> Transferred: policy moved to the acquirer Pending --> Lost: did not renew Mapped --> Lost: did not renew Transferred --> [*]
Day 0 to day 40 Riverbend Commercial Insurance, illustrative.
1
Close recordedDeal leadDay 0

The move to Integration needs the close date.

2
Plan adoptedIntegration leadDay 0

Accepting the integration planner's prepared decision creates the tasks.

3
Retention agreements signedDeal leadDay 0

Four day-0 tasks done.

4
Letters and renewalsIntegration leadDay 1

Change-of-ownership letters (a dry run until a person sends them) and the renewal-protection task done.

5
Appointments and commissions overduePlanDay 30

Five tasks past their due date, shown in red on the plan and on the integration lead's home.

6
Tracker reviewedIntegration leadDay 40

The lowest-retaining producer's lost clients reviewed with them.

AgentWhat it preparedWhat it citesWho decides
Integration plannerA 17-task 100-day plan across producers, clients, carriers, systems, finance and peopleThe approved findings and engine figuresIntegration lead adopts
Client match agentConfirm 2 proposed client matches before accounts are mergedPulse evidence and name scoresIntegration lead
Carrier mapping agentAppointments with 3 carriersPremium by carrier and appointment statusIntegration lead

For the deal team

The integration plan comes from the deal's own findings, and the tracker shows which producer's clients are leaving.

For IT

Tasks carry their source finding and day offset; retention is recomputed from the transfer status of each client in force at close.

For corp-dev leadership

Revenue retained since close is a live number on the practice leader's home, not a quarterly estimate.

Questions we get asked

Can we add our own tasks?

Yes. The planner's tasks are a starting point: tasks can be added to the plan, and each task's status is kept on the Integration zone.

When is the acquisition 'done'?

When every task due by day 100 is done, the move to Day 100 is allowed and recorded.

Keep reading