Section 1
The information vacuum is the real risk
Deal teams optimise for confidentiality, and for good reasons. The cost is that the people whose retention determines whether the deal works are the last to learn anything. What they do in the meantime is rational: they assume redundancy, they assume the acquirer's systems win, and they update their CVs. A useful narrative accepts that you cannot say everything and commits instead to a rhythm. State what is decided, state what is genuinely not decided yet, and state the date by which the open questions will be answered. The second of those is the hardest and the most valuable. Leaders who claim certainty they do not have lose credibility the first time a decision reverses, and after that nothing they say lands. The internal mechanics of that telling are covered in [How to Lead Organizational Change Through Storytelling](/blog/how-to-lead-organizational-change-through-storytelling).
Section 2
Two companies, two versions of the same event
The acquirer usually experiences the deal as expansion and the acquired company experiences it as an ending. Communications written from the acquirer's point of view read as celebration to one audience and as an obituary to the other. The practical fix is to write separate messages for each side rather than one release with the logo of both. The acquired team needs to hear what is being preserved and why the business was worth buying in its current form. Customers need to hear who their contact is next week. Investors need the strategic logic. One message that tries to serve all three usually serves none, and the acquired team reads the omissions closely.
Section 3
The commitments that survive contact with integration
Make few promises and keep them narrow, dated and verifiable. No changes to compensation before a named date is a commitment. Nothing much will change is not, and it will be quoted back to you the first time something does. Public-facing messaging carries the same discipline, as [How Storytelling Sparked Viral Marketing Campaigns](/blog/how-storytelling-sparked-viral-marketing-campaigns) shows in a different context.
Section 4
The first hundred days in practice
Set the communication cadence before close and keep it after. A short written update every two weeks, sent by the same person each time, does more for trust than an elaborate town hall in week one followed by silence. People calibrate on consistency, not production value. Give the acquired team a route to ask questions that does not require asking their manager in public. Then answer the uncomfortable ones directly, including the ones where the answer is that roles will change. Founders and senior staff who stay should be visible in the telling, because their continued presence is evidence, and evidence outperforms assurance in a period when everyone is watching for a signal.
Section 5
Judging whether you are ready to communicate
You are ready to open the conversation if you can name what is decided, what is open, and when the open items close, and if your leadership team gives the same answer to the three questions employees will ask most: my job, my manager, my tools. You are not ready if the only honest version of the plan is one you are unwilling to say aloud, because it will leak in a worse form. The deeper failure mode is a story maintained for months after it stopped being true. Integration plans change. Saying so costs less than being discovered. Where the change involves replacing systems the acquired team built, [How to Build Custom AI Bots for Your Business](/blog/how-to-build-custom-ai-bots-for-your-business) is a reminder that the tooling debate is rarely just technical.