A deal team's working day on an acquisition is spread across a data room, a spreadsheet per analysis, an email thread with the seller and a memo draft. The Acquisition Workspace puts the acquisition on one page: what the agents found and prepared, the book, the people, the carriers, the clients, the integration and the memo — with the stage strip across the top and the controls in the rail.

The hero

Acquisition Workspace · IC memo
The Acquisition Workspace for an illustrative agency at IC memo
The Acquisition Workspace for the illustrative Ironwood Risk Partners at IC memo: the stage strip, the headline figures from the book, and the first decision the agents prepared, with Accept, Reject and Ask.

Target number, focus and city; the stage; the lead, the expected close and the number of book rows; the seven-stage strip (Screening, Data received, Analysis, IC memo, Signed, Integration, Day 100); and six headline figures — book revenue, client retention (with revenue retention under it), organic growth, top producer, top carrier, renewals in 90 days. Under it, one line on where the acquisition stands, how many decisions wait, and Analyze.

Seven zones

ZoneWhat it holds
FindingsPrepared for you (the agents' decisions with Accept, Reject, Ask), the last Analyze run, and what the agents found with filters for high and critical, to review, approved and rejected.
BookRetention period over period, revenue by period and organic growth, revenue by line, the renewal calendar, what the revenue is made of, data quality and cross-sell.
ProducersRevenue, share, clients and retention per producer; key people; retention agreement status.
CarriersPremium and share per carrier, states, the acquirer's appointment status and the action.
ClientsMatches into the acquirer's book: to confirm, confirmed, new to the acquirer, rejected.
IntegrationAfter close: the retention tracker and the 100-day plan as tasks. Before close: the plan the planner proposes.
MemoThe valuation arithmetic and the valuation-support memo built from approved findings.
flowchart LR H["Hero: stage strip,
headline figures, Analyze"] --> F["Findings"] F --> B["Book"] --> P["Producers"] --> C["Carriers"] --> CL["Clients"] --> I["Integration"] --> M["Memo"] R["Rail: key facts,
acquisition controls,
data room"] -.-> F F -.->|"every citation"| RW["The rows behind it"]
Findings · prepared for you
Decisions the agents prepared for an illustrative agency
Prepared for you: the seller request, a client match to confirm, appointment requests, the 100-day plan, the practice leader's sign-off and the memo — each with Accept, Reject and Ask.

A prepared decision says which agent prepared it, its level (L1 draft here), whether it rests on the engines or the model, the lines of what it proposes, the facts behind it, and Accept, Reject and Ask. Ask questions the agent from those facts.

Workspace · controls
The key facts and acquisition controls rail, on illustrative data
The rail: key facts (seller's revenue, asking multiple, book revenue, book against seller) and the acquisition controls that fired, with who each refers to.

The rows behind every citation

The rows behind it
The rows behind a citation, on illustrative data
The rows behind it: a producer's revenue citation opened to the 367 book rows it rests on.

Every chip that says “N book rows” opens a drawer with those rows — row number, client, line, carrier, producer, effective date, premium, commission, type, status and any data issue.

For the deal team

One page per acquisition; the next thing to decide is at the top.

For IT

Built on the shared workspace kit (workspace-react), the same shell as InsightUW and InsightCW.

For corp-dev leadership

Every acquisition in the pipeline looks the same, so reviewing one takes minutes.

Keep reading