The Joins Nobody Owns: A First-Fortnight Integration Review for UK Acquirers

On the morning after completion, the combined logo appears: two names, an ampersand, a slightly revised shade of blue. It is the cheapest change in the entire transaction and the most ambitious one. It asserts that two organisations are now a single business. Whether that assertion holds depends less on the synergy model than on a set of decisions that rarely reach the board pack: which system holds the client record, whose signature releases a purchase order, which job titles survive the transition, and whose bank details appear at the foot of the invoice.

Where the value actually leaks

Deal models are built at the level of cost lines. Headcount, property, procurement, duplicated licences — these are the numbers that justify the multiple, and they are real. But the friction that erodes value in the first year is usually transactional rather than structural. Two firms can hit every cost synergy on the schedule and still lose a long-standing client because a quotation took nine days instead of three, or because a delivery note went out under the wrong entity and the client's finance team queried it.

The joins are small, unglamorous and — crucially — owned by nobody. Each side assumes the other is deciding. The result is a period of weeks in which both legacy systems operate, both approval routes are technically valid, and staff choose whichever is more convenient. Habits formed in that window tend to persist.

A diagnostic, not a programme

The five questions below are not an integration plan. They are a diagnostic, designed to be asked in the first two weeks, while people are still paying attention and before defaults harden into policy. Half a day with the right people is usually enough.

1. Whose CRM is the record of truth on day one — and who has write access?

The question is not which system will be used eventually. It is which system a salesperson opens on the Monday morning after completion. If the answer is 'both, for now', expect two pipelines, two forecast numbers and a board that cannot reconcile them within a month. A related test: did the acquirer have reliable visibility of the target's pipeline before signing? If not, the same opacity will persist after.

2. Whose approval route does a mid-value purchase order follow?

Choose a real, unglamorous example — forty thousand pounds of stock, a software renewal, an urgent facilities repair — and walk it through both legacy routes end to end. Note who signs, at what threshold, and how long each step takes. If the honest answer is that the finance team will improvise until a policy is written, the improvisation will become the policy.

3. Which job titles survive, and who tells the clients?

Titles are cheap to change and expensive to get wrong, particularly in professional services where a client-facing title is part of the product. Decide who is called what before the first joint pitch, and agree — in advance — who communicates the change to which clients. Clients tolerate a change of structure; they dislike discovering it from a signature block.

4. Whose invoice template, bank details and payment terms go out on Monday?

This is the least strategic question on the list and the one most likely to cause immediate damage. A payment sent to a dormant account. A remittance advice addressed to a company the client has never traded with. A VAT number that no longer matches the letterhead. Reconcile legal entity names, bank details, VAT registrations, remittance addresses and payment terms before the first combined invoice leaves the building.

5. Who owns the join?

Each of the questions above needs a named individual with the authority to decide across both entities, and a date by which the decision will be made. A steering committee is not an owner. If no single person can settle the CRM question by a stated date, the join will drift until someone lower down settles it by accident.

Reading the pattern

The answers matter individually, but the pattern matters more. If nearly every answer is 'the acquirer's way', you are buying a book of clients and calling it a merger; that may be the intent, but it should be stated rather than assumed. If nearly every answer is 'to be confirmed', the announcement has run ahead of the work. The most common and most fragile outcome is a split: the acquirer's finance systems, the target's client systems, and no agreed rule for where the boundary sits.

A simple discipline helps. Score each of the five red, amber or green, assign a thirty-day action to every red, and review the whole set at the first post-completion board meeting.

The quiet cost of printing side by side

Firms that never resolve these questions rarely fail dramatically. They operate two of everything, tolerate a longer decision cycle, and explain the overhead as 'integration costs' for longer than the integration lasts. The letterhead says one thing; the operating reality says two. Gradually the ampersand becomes decorative — a piece of design rather than a description.

The first fortnight is the cheapest moment to decide. After ninety days, the joins will have been set by default rather than by choice, and unpicking a default is considerably more expensive than making a decision.

The ampersand is a promise about a join. The first fortnight is when a business decides whether to keep it.