You acquired a book. Now there are two ways of doing everything.

The deal closes, the clients are papered, the accounts transfer, and the revenue shows up where it should. On paper the acquisition is done.

Inside the firm there are now two onboarding processes, two filing conventions, two ideas about what belongs in the CRM, and two groups of people each convinced their way is the sensible one. That condition can persist for years, and it quietly costs more than the premium paid for the book.

Why it does not resolve on its own

Nobody decides to run two operations. It happens because integrating them is nobody’s explicit job, both ways work well enough to avoid a crisis, and asking a team to abandon a process they built feels like a judgement about them rather than about the process.

So the two systems persist, and the cost shows up indirectly. Staff cannot cover for each other. Reporting requires reconciliation. A client who moves between advisors gets a visibly different experience. Every new hire has to be told which of the two ways applies to them.

Two ways of doing something is not twice the work. It is twice the work plus the cost of deciding which one applies, every time.

Pick the process, not the firm

The move that makes this tractable is separating the decision from the politics. Do not ask whose process wins. Document both, compare them step by step, and choose per step against something neutral: how long it takes, how often it fails, and how much of it needs a person.

The result is usually a third process that borrows from both, which is easier for everybody to accept than a verdict, and is generally better than either. Every firm has somebody who owns the process today, which is one of the standards we design against, and a change that takes something away from that person without giving them anything back does not survive the first quarter. That is a design problem rather than a personality problem, and we treat it as one.

What to settle first

• Which system holds the authoritative client record, before anybody migrates anything
• One filing convention and one naming rule, applied to both back files, which is also what an examiner is looking for
• One onboarding path, because it is the process most visible to a client and the one new staff learn first
• Which of the two firms’ integrations survive, and who owns each one by name

The document architecture is worth doing early even though it feels like the least urgent, because every month it waits is another month of files landing in two conventions.

If more acquisitions are coming

A firm that intends to acquire again should treat the first integration as the template rather than a one-off. Once the combined process is documented, the next book is being merged into something written down, which turns a negotiation into an onboarding. Firms that skip this end up with three ways of doing everything, and the arithmetic does not improve.