Agency-code architecture — consolidate, separate, or dual-code.

Once the purchase agreement is signed and the carrier-continuity negotiation is done, one operational question sits between the acquirer and the carrier's ledger: which agency code does the acquired book write under? The premium map sized the contingency prize, the continuity provisions secured the history — but neither pays out unless the post-close code structure is built to capture it. Get this wrong and you can give back most of the synergy the deal was priced to capture, even after winning every prior negotiation.

§ 01 · The three pathsConsolidate, separate, or dual-code.

Under a consolidation structure, the acquired book migrates into the acquirer's existing code with each carrier — all new business, renewals, and servicing flow through one unified code, and the carrier sees a single larger agency. The upside is tier velocity: every dollar of acquired premium stacks onto the existing volume track record, pushing the combined book into higher contingency tiers faster than either book reaches alone. The tier-jumping math that justified the acquisition only actually plays out if the codes consolidate. The downside is contagion: whatever loss ratio the acquired book carries blends into the acquirer's loss ratio on day one, and a hidden concentration or a bad pending claim can push the combined book across the carrier's 60% disqualification gate — zeroing the contingency on the entire combined agency, not just the acquired piece.

Under a separation structure, the acquired agency keeps its original code with each carrier; the acquirer owns the entity, but the carrier relationships stay distinct — two books, two tier positions, two contingency calculations under common ownership. The upside is isolation: a loss-ratio problem in the acquired book stays contained, and the acquirer's existing tier position is protected. Separation also preserves optionality — a book whose economics turn out worse than diligence suggested can be wound down or restructured without dragging the core agency's carrier relationships with it. The downside is forgone synergy: two smaller books qualifying separately at lower tiers produce less contingency than one combined book at a higher tier, plus the overhead of two billing codes, two commission flows, and two relationship cycles per shared carrier. A dual-code structure runs both in parallel through a 12–24 month transition with a pre-defined migration path, buying clean post-close data before the one-code commitment — at the cost of disciplined internal accounting and active carrier communication.

§ 02 · The four variablesWhat actually drives the call.

The first variable is loss-ratio differential. If the acquirer runs a clean 45% book and the target sits at 58%, consolidation exposes the contingency line to blended risk and separation or dual-code makes sense; if both books are inside the cushion zone — both in the low 50s or below — consolidation is safer and the tier-velocity case wins. The second is combined tier delta: if consolidation jumps the acquirer from a lower tier to a materially higher one across the top three carriers, the synergy justifies some contagion risk, but if the combined book stays in the same tier the acquirer already held, consolidation adds only integration work and separation becomes the stronger default. The third is the carrier-continuity outcome — what the carrier actually agreed to. A clean continuity grant makes consolidation attractive; reset terms shift the calculus toward starting fresh under a separate code or running dual-code to build post-close history first. That negotiation is covered in successor in interest.

The fourth variable is integration readiness — how operationally mature the acquirer is. Consolidation demands disciplined servicing systems, clean commission accounting, and the ability to run a larger book under one code without dropping service quality. An acquirer with modest infrastructure and first-time integration experience should favor separation or dual-code for the first twelve months, then consolidate once the book is stable; a sophisticated acquirer with a repeatable integration playbook can consolidate on day one. Read together, the four variables produce three viability tests: consolidation is viable when both books sit in the cushion zone, the combined volume materially shifts tier placement, continuity was cleanly granted, and the integration muscle exists. Separation is viable when the acquired loss ratio is materially worse, the combined book risks the 60% gate, or the carrier insisted on reset terms. Dual-code is viable when optionality and learning time matter more than immediate synergy capture — the typical profile for a first-time or modest-infrastructure acquirer.

§ 03 · Ring-fencingThe surgical fourth option.

There's a fourth move that sits alongside the three main paths, and it's the one the most sophisticated acquirers use when a specific segment carries the risk: ring-fencing. It's a targeted form of separation — most of the acquired book consolidates cleanly into the acquirer's code, but a specific concentrated account, problem segment, or high-loss-ratio slice stays under the original code, or moves to a different carrier entirely, until it can be remediated, non-renewed, or wound down. Ring-fencing captures the tier-velocity upside of consolidation while protecting the combined book from a known contamination source. It's the right answer when diligence has identified a specific problem — a single large account with a claim history, a concentrated industry segment, a producer whose book carries a chronic loss ratio — but the rest of the acquired book is clean. The reason most acquirers never consider it is that they frame the architecture decision as a binary. It isn't binary; it's a portfolio question, and the loss-ratio drivers worth ring-fencing are exactly the ones surfaced in loss-ratio blending.

§ 04 · The disciplineA valuation lever, not an integration task.

Most acquirers over-weight integration simplicity and under-weight carrier economics. The post-close code architecture is routinely handed to the operations team as a systems-integration task rather than treated as a valuation lever inside the broader carrier-mapping strategy — which is how the same acquirer can negotiate a clean continuity provision and then give the contingency back by consolidating a book that should have been ring-fenced. The discipline is simple to name and harder to execute. Run the carrier-level contingency math both ways — combined and separate — before close, with the model showing year-one, year-two, and year-three contingency under each architecture. Identify ring-fencing candidates in diligence, not after close: concentrated accounts, problem segments, and inherited loss-ratio drivers should be flagged and scoped before the LOI. Match architecture to integration capacity — don't consolidate on day one unless the operational muscle is there; dual-code with a pre-defined migration plan is the safer default for most acquirers. And revisit the decision at the twelve-month mark: dual-code should be a transition, not a steady state — if the book has performed, consolidate; if it hasn't, keep it separated permanently. Run that discipline and the architecture stops being where synergy quietly leaks and becomes the last lever that locks in everything the premium map promised.

◆