In professional services, the most important asset is not something you can acquire in the way the rest of the business can be acquired. The largest part of the value lies in the relationship between an advisor, accountant, lawyer or consultant and the client who has been calling them for years. That relationship does not automatically transfer with the deal. It can weaken, shift to a competitor, or never have been properly transferred in the first place because no one knew exactly who owned the contact. Compare that to a sector where the product exists separately from the person, and the difference becomes clear: here, integration is to a large extent an integration of trust, and trust cannot be forced through a plan.
Every merger in this sector should raise the question of whether integration is the right choice, and that is not a formality. Two firms with overlapping services can, through merging, actually lose clients who had deliberately chosen two smaller, specialized parties. An advisory firm absorbed into a larger brand can lose the very reason clients once chose it: the personal name, the small scale, the specific expertise. Sometimes the answer is that the brands should continue to exist side by side, with only the back office — administration, procurement, systems — merged. That choice should be made in advance, not justified afterwards.
The most common reason integrations get stuck in this sector is not a poorly integrated IT system. It is the advisor who leaves, taking part of their clients with them, within the period that the integration has not yet been completed. Retention agreements and earn-outs soften this risk, but do not resolve the underlying question: what happens to a client file when the person managing it leaves before the handover to a colleague has been completed? Anyone who does not map this out in advance per client group only discovers it once it has already happened.
A second sticking point is the difference in service model. One firm works with fixed subscriptions, the other bills by the hour. One firm records everything in a case management system, the other keeps it in the heads of three senior people. These differences cannot be smoothed over in a week, and trying to do so can break more than it fixes.
A synergy baseline for a merger of advisory firms or service providers does not start with cost items, but with client concentration: what share of revenue runs through which advisor, and what is the risk if that advisor leaves. The baseline makes that risk explicit instead of hiding it in an optimistic synergy figure.
The Day 1 plan for this sector answers a different question than in a product company: not which factory keeps running, but which advisor is still speaking to which client today, and with what message. Ambiguity on this point on day one is often the moment a client decides on their own to look elsewhere.
The Day 100 plan sets out when and how the transfer of client relationships takes place, and who acts as a safety net if the original advisor is no longer there. The decision list in the integration office forces the choice of whether service models are merged, continue to exist side by side, or whether one firm adopts the model of the other. Dependencies become visible: the CRM system tied to the billing system, the case management tied to a specific package. Benefit tracking follows not just cost savings, but also client retention, because that is the first place value leaks away in this sector.
This tool structures the questions and records the agreements. It does not prove experience with previously executed integrations in professional services, and it does not guarantee the retention of clients or advisors. It makes the risks visible, so that the choice of whether and how to integrate is made deliberately rather than along the way.
The bottleneck of people-bound value is not unique to professional services. In education, a similar dependency exists on individual teachers and their relationship with students, as described in where an integration gets stuck in education. In financial services, an additional layer of supervision and licensing is added on top, described in where an integration gets stuck in financial services. And in the IT sector, the risk lies specifically with technical staff and client contracts tied to specific engineers, as elaborated in where an integration gets stuck in the IT sector. The pattern is recognizable every time: value lies in people, and people cannot be integrated the way a system can.
If the core of the risk is that too much work sits in the heads of too few people, a logical follow-up question is what share of that work can actually be documented and made transferable. The work scan from FTE TO AI calculates per task what share of the work can be taken over by AI, and for a merging advisory firm that is relevant information apart from the integration itself: it reveals which case knowledge, reporting or client communication can become less dependent on one specific person. That does not reduce the risk of departure, but it does expose where the vulnerability is greatest.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.