Clients the acquirer already serves

Some of the clients an acquirer is buying are clients it already has. That matters twice: once for the price (revenue already in the acquirer's book is not new revenue) and once after close, when two account records for the same business have to become one without anybody's renewal falling between them.

Matching clients across two books sounds like a lookup. It is not: names are written differently, subsidiaries buy insurance in their own names, and two different businesses can have nearly the same name. This post follows the client match agent on two illustrative agencies — Riverbend Commercial Insurance after close and Ironwood Risk Partners before it — including a match a person should reject.

Use case card

Actors	Deal lead or integration lead (confirms or rejects each proposal)
Trigger	Analyze; the integration fit step
Agencies Illustrative	Riverbend: the acquirer already serves 6 of 550 clients, 2 matches to confirm. Ironwood: 6 of 526, 1 to confirm
Agents involved	Client match agent, integration planner
Data sources	The target's book export, the acquirer's client list, InsightPulse 360's company graph (illustrative stand-in in the demo)
Decisions and authority	Each match confirmed or rejected by a person; nothing merged automatically
Outcome	A confirmed overlap list for the price and for the account merge after close
What is measured	Clients already served; matches proposed, confirmed, rejected; new-to-acquirer clients

Four methods, in order

Each of the target's clients is tried against the acquirer's book; the first method that holds wins.

Method	When it holds	What happens
Exact	The names are the same once legal suffixes, punctuation and case are set aside (“Bluegate Logistics, LLC” = “BLUEGATE LOGISTICS”)	Matched
Website	The client's website domain is an acquirer client's	Matched
InsightPulse	Pulse resolves the client's domain to a company whose name — or whose parent's — is an acquirer client; the evidence cites Pulse and its date	Proposed for a person
Name similarity	Names at least 90% alike (token-sorted) in the same state	Proposed for a person, never confirmed

Personal-lines clients are matched only on exact name in the same state, because people's names collide.

flowchart TB C["Target client"] --> E{"Exact name?"} E -->|"yes"| MX["Matched"] E -->|"no"| W{"Same website?"} W -->|"yes"| MX W -->|"no"| P{"Pulse: same company
or parent?"} P -->|"yes"| PR["Proposed —
a person confirms"] P -->|"no"| F{"Names 90% alike,
same state?"} F -->|"yes"| PR F -->|"no"| N["New to the acquirer"] style PR fill:#e3f7ef,stroke:#10a37f

Two proposals on Riverbend

The Clients zone: proposed client matches, illustrative — Clients: a match through InsightPulse's company graph (the acquirer serves the parent) and one by name similarity, each waiting for a person to confirm or reject.

Oakvale Tool & Die LLC ($87.9K of premium) has no name in common with any acquirer client. InsightPulse resolves its website to Oakvale Tool & Die, whose parent is Oakvale Manufacturing Group — an acquirer client. The acquirer already serves the parent; the subsidiary is not new business. A person confirms it.

Larchmont Property Management LLC and the acquirer's Altamont Property Management Co are 91% alike by name in Ohio. That is a proposal, not a conclusion: the person checks the address or the FEIN and decides.

The one to reject

On Ironwood, the agent proposes Harlow Properties Inc → Marlow Properties Inc, 94% alike. One letter apart, and very likely two different businesses. This is exactly why name similarity never confirms itself: the engine can say the names are alike; only a person can say the businesses are the same. Rejecting it is an answer on the decision record like any other.

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.

Client overlap, from proposals to the merge Riverbend Commercial Insurance and Ironwood Risk Partners, illustrative.

Clients matchedclient_match_agentAnalyze

Every client in force tried by the four methods; already-served clients counted; proposals listed with their evidence.

Confirmation preparedclient_match_agentAnalyze

A prepared decision: confirm the proposed client matches.

Each proposal decidedDeal or integration leadReview

Confirm (check) or reject (cross) per row on the Clients zone; the Pulse evidence and the name scores shown.

Day-14 taskintegration_planner_agentPlan

Confirm the proposed client matches before accounts are merged.

Accounts mergedIntegration leadDay 14

Only confirmed matches are merged; rejected ones stay new clients.

sequenceDiagram participant RU as InsightRollup participant PU as InsightPulse 360 participant Ag as Client match agent participant IL as Integration lead RU->>Ag: Target clients and acquirer clients Ag->>PU: Resolve client domain (company, parent) PU-->>Ag: Company profile as of its date Ag-->>IL: Proposals with evidence IL->>RU: Confirm or reject each (decision record)

Agent	What it prepared	What it cites	Who decides
Client match agent	The acquirer already serves 6 of the target's 550 clients; 2 matches to confirm	526–550 distinct clients in force; Pulse profile as of its date	Integration lead
Integration planner	Day 14: confirm the proposed matches before accounts are merged	The client match finding	Integration lead

For the deal team

Matches come with their evidence, so confirming one takes a glance rather than a search.

For IT

Pulse is called through the diligence intelligence port; with no Pulse configured, an illustrative stand-in answers and says so.

For corp-dev leadership

Overlap revenue is known before the price, and no account is merged on a name alone.

Questions we get asked

What if we don't run InsightPulse?

Exact, website and name-similarity matching still run. The Pulse method finds subsidiaries the acquirer serves through a parent, which the others cannot.

Why not auto-confirm 99% matches?

Because the cost of a wrong merge is a client's renewal falling between two records. Exact and website matches are taken; everything else waits for a person.