The title of this article asks how to ensure a successful acquisition announcement to customers, and the honest answer begins by shrinking the word ensure. No letter can ensure its own reception. What the writer of this document controls is narrower and more demanding: whether it answers the reader’s actual questions with facts that are settled, promises that are owned, and undecided matters marked as undecided. That is the whole of the craft — and it is enough, because the readers of this document are not an audience. They are counterparties.

A companion piece in this series covers the merger announcement itself — the document two organisations must both be able to sign, with employees as its first audience and completion stated as a projection rather than a fact. This article is about the sibling document: the letter written after, or alongside, the deal, addressed to the people who hold contracts with one of its parties. Its ground is not the transaction. It is the relationship the transaction has just rearranged, and the standard it is judged by is set by the people who will still be customers when the announcement is a memory.

The Reader Is a Counterparty

Begin with who is actually reading. A customer of an acquired company holds things: a subscription with months left on it, a contract with terms, a service their own work depends on, data sitting in the company’s systems, money paid in advance for things not yet delivered. The announcement lands in the middle of those holdings. The reader’s questions are therefore not the deal’s questions — who bought whom, at what logic, with what strategic rationale — but operational and personal ones. What happens to my service? To my price, and when? To the support route I use when something breaks? To my data? To my renewal, my terms, the people I deal with?

This series has a test for operational communication: it succeeds when the counterpart can act on it correctly. The customer letter is operational communication wearing an announcement’s clothes, and the test applies without adjustment. A letter that leaves the reader knowing the deal’s story but unable to answer what happens to their contract on Monday has failed at its only job, however warm its tone. A letter that answers the operational questions plainly — including by admitting which of them cannot yet be answered — has succeeded, however unglamorous it reads. Everything in the drafting follows from deciding which of those two documents you are writing.

There is a further asymmetry worth naming. The company writing the letter chose the transaction; the customer did not. The letter is therefore not a celebration the reader has been invited to share but a notification of a change in the reader’s own arrangements, made by other people, for reasons that are theirs. Documents written in that position owe the reader a particular discipline: the significant facts first, the company’s enthusiasm last or not at all, and no sentence that requires the reader to be pleased about a change before they have been told what it is.

Two Kinds of Sentence

Almost every sentence in an acquisition announcement to customers is one of two kinds, and the document’s honesty depends on keeping them visibly separate. The first kind is the fact: what is settled. Who has acquired whom. As of when. What has actually been decided — about the service, the price, the support route, the contract — stated precisely and without decoration. Where the transaction itself is still completing, the deal document’s grammar governs: completion is a projection with its conditions named, not an accomplished fact, and the customer letter inherits that discipline rather than relaxing it. Customers who are told a deal has happened when it has merely been agreed have been given a false fact at the foundation of everything else the letter says.

The second kind is the commitment, and it is where these letters usually fail. Everything a customer announcement says about the future — nothing will change, support will continue, your data stays where it is — is a promise. This series’ treatment of statements makes the point in general form: a commitment is the one thing such a document may legitimately promise, and a promise is a claim with an owner and a date on which it can be checked. An honest letter therefore makes only promises that someone identifiable can keep. It states their horizon where a horizon exists — for at least this period, until your renewal, through the current term — because a promise without a horizon is not reassurance but a fog the reader is asked to feel better inside. And it refuses promises whose keeping belongs to people who have not agreed to them, in integration meetings that have not happened yet.

Between the facts and the promises sits the third category, the one weak letters omit: the undecided. In any real acquisition, matters the customer cares about are genuinely unresolved on announcement day — pricing after the current term, the long-term shape of the product, whether their account team survives the integration. The honest sentence for each is short and complete: this has not yet been decided, and you will be told by a stated time, through a stated route. Readers do not punish that sentence. They punish its absence — the discovery, months later, that a silence they read as continuity was actually an undecided matter wearing continuity’s clothes. The undecided, marked plainly, is what makes the rest of the letter believable.

Reassurance Must Be Checkable

The original version of this article taught the document through example paragraphs, and its examples show the standard failure in its purest form. Customers were to be told there would be ‘no immediate changes to the products and services you know and love’, and that they would receive ‘the high level of service you’ve come to expect’. Both sentences are comfort, not information. ‘No immediate changes’ hides its meaning inside ‘immediate’ — a word that lets the sentence be true on the day it is sent and false by the quarter’s end. ‘The level of service you’ve come to expect’ cannot be checked against anything; it asks the reader to supply the standard and then trust it is being met. A factual claim wearing the costume of comfort is worse than no reassurance at all, because it spends the letter’s credibility on a sentence that was designed to be unverifiable.

Checkable reassurance looks different, and it is not colder — it is merely specific. It names the thing that is not changing, the period the statement covers, and the route by which the reader can test it or ask about it. Your current plan and price continue until your renewal date. The support team you use today remains your route, at the same contact points. Your data remains held under the terms of your existing agreement. Each sentence can be true or false, and the reader will know which, in due course, from their own experience — which is precisely why such sentences reassure and the fog sentences do not. The template below replaces the original’s examples on that principle: every value is a bracketed placeholder, and every line is built to be checked.

Template — announcement to customers: [Acquired organisation] has been acquired by [acquiring organisation], [effective date — or: the transaction is expected to complete on (date), subject to (conditions, named as categories)]. For your [service / subscription / contract]: [the specific element that is not changing, and the period it covers]. [The specific element that is changing, and from when]. [The matter that has not yet been decided, and the date by which you will be told]. Your route for questions about your own arrangement is [named team or contact, and how to reach them]. We will write again [when / on what trigger] with [the next specific thing you will be told].

The placeholders are the lesson. An example written with invented company names and glossy outcomes teaches the writer to reach for the gloss; a template whose every slot demands a settled fact or an owned promise teaches the opposite habit. If a slot cannot be filled honestly — the period not yet agreed, the change not yet decided — the template does not permit inventing one. It permits the undecided sentence, which exists for exactly that slot.

Tone: Plain Beats Positive

The original advised writers to ‘keep the tone positive and forward-looking’, and the advice deserves to be retired by name. The merger piece in this series ruled the same instruction out for staff announcements, and the ruling applies here word for word: positivity as a drafting instruction is how readers learn to distrust a document. A customer who reads that a change to their own contract is ‘an exciting new chapter’ learns something immediate and accurate — that the letter is written for the writer’s comfort, not for theirs — and discounts every factual sentence that follows accordingly. Excitement is the acquiring company’s emotion. It has no standing in a notification addressed to someone whose arrangements have been changed by it.

The honest tone is plain, complete and early, and it is not a lesser thing. Customers forgive bad news delivered straight — a price change with a date and a reason, a service ending with its migration path — far more readily than good news that evaporates. The reason is structural: customers keep the letter. They compare it against what subsequently happens to their service, their invoices and their support tickets, over months and years, and the comparison is the relationship. Publics read every message with all of their stakes at once, and a customer is the stakeholder with the best evidence: their own bills. A letter that survives that comparison is worth more than any tone. A letter that fails it becomes the exhibit in every later dispute about what was promised.

One Record, at the Depth Each Stake Requires

An acquisition produces several documents at once: the deal announcement, the staff announcement, the customer letter, the public release. This series’ discipline for all of them is the same: they are one factual record at different depths. Segmentation is legitimate — customers need operational depth the public release does not carry; staff need employment depth the customer letter does not — and this series has defended it as an accuracy exercise, different depths of the same facts for different audiences. What may never differ between the documents is the facts themselves. A customer who reads in the press release that the service will be ‘enhanced’ and finds in their letter that it is being discontinued has not received two depths of one record. They have received two records, and they will believe the worse one.

Sequencing follows from the same principle, and it is a duty rather than a courtesy. Customers must not learn of operational changes to their own service from press coverage of their supplier. The letter that arrives after the headlines has already failed, whatever it says, because its lateness is itself a fact about how the company orders its obligations. Channels, likewise, are a delivery matter and not a strategy: the document must actually reach the counterparties — through account contacts, direct notice to the addresses on the contracts, in-product notification where the service is software — because posting the announcement on a website is publication, not notification. A customer who never saw the letter was not told, in any sense a relationship recognises.

The Follow-Up Is Part of the Document

The announcement is not the end of the communication; it is the first entry in a file the customer keeps. The letter itself creates the obligations that follow: the questions arriving at the named route must be answered by people who know the reader’s arrangement; the matters marked undecided must be returned to when they are decided — on the date the letter promised, not when the integration team gets round to it; and anything the letter got wrong must be corrected in the open, to the same audience, with the correction marked as a correction. The post-event record discipline this series applies to event announcements — the follow-up states what actually happened — applies here across a longer arc: the follow-ups state what actually happened to the promises.

That is the honest meaning of a successful acquisition announcement to customers. Not that trust was built — trust is the customer’s conclusion, drawn later, from the comparison between the letter and the life that followed it. Not that loyalty was maintained, or the transition made seamless, or the outcome ensured. The announcement’s success is narrower, checkable, and entirely within its writer’s control: the facts were settled and stated, the promises were owned and dated, the undecided was marked as undecided, and the document reached the people whose arrangements it described — in time for them to act on it. A letter that does those things has done everything a letter can. The rest belongs to what the company does next, which is where it always belonged.