Most founders have a fundraise announcement half-written before the round closes. Almost none of them have anything prepared for the other major event that ends a startup’s independent life: getting acquired. That gap shows up constantly in how badly these announcements read, and it’s entirely avoidable.
The timeline that guarantees a bad announcement
Acquisition talks run under tight confidentiality, often until hours before signing. The founder who hasn’t thought about the public version of the story until that point is now trying to write it - explain years of work, reassure employees, answer customers who found out from a press release - inside a 48-hour window shared with lawyers finalizing the deal itself. What comes out is almost always generic: “excited to join forces,” a quote that could belong to any acquisition, no real answer to the one question everyone is actually asking, which is why.
Employees and customers need different answers, fast
A funding announcement mostly needs to satisfy one audience: outside observers deciding whether to be impressed. An acquisition announcement needs to satisfy three audiences simultaneously, each asking something different. Employees want to know if their jobs survive the transition. Customers want to know if the product they rely on is changing. Investors and the broader market want the strategic logic. A founder improvising all three answers in the same news cycle will shortchange at least one of them, and it’s usually the employees, who find out their own fate from the same press release as everyone else.
The founders who announce this well prepared it in advance
The pattern among acquisitions that land well isn’t luck - it’s that someone on the founding team treated “how would we explain this if it happened” as a document worth drafting long before any term sheet existed, the same way a company drafts a crisis communication plan for an outage it hopes never happens. That draft doesn’t predict the buyer or the price. It forces the founder to work out, with no deadline pressure, what they’d actually want employees to hear first, what customers need reassured about immediately, and what the honest version of “why” sounds like before the real one has to be written overnight.
What belongs in that draft
Three things, roughly: an employee-facing version written for people worried about their job, not investors; a customer-facing version that answers the product question directly instead of in acquisition-speak; and a founder’s own honest paragraph on why the outcome makes sense, written in a moment with no deal pressure attached. None of it gets published until it’s needed. All of it means that when the moment arrives, the founder is editing a document they’ve already thought through, not inventing one under the worst possible time constraint a startup will ever face.