What Can You Say Without Legal Risk?
Strategic rationale, customer impact, and what stays the same, usually safe at a high level. Deal terms belong in filings, not interviews. You can explain why you bought or sold, what capability the combined company gains, and what customers should expect in the next twelve months. You cannot discuss purchase price, earnout triggers, or integration details that have not been publicly disclosed.
Legal teams often default to boilerplate because it is safe. The problem is that boilerplate produces no coverage, editors pass on stories where the CEO sounds like they are reading an 8-K. Work with counsel on three or four approved talking points that have a human spine, then stay inside those boundaries on air.
What Should the CEO Sound Like?
A steward explaining a bet, not a lawyer reading disclosures. Plain language about why you bought and what capability you added. If you acquired a company, talk about the gap in your product that their team fills. If you were acquired, talk about what the combination lets you build that you could not build alone. Founders who explain the logic like they would to a board member produce segments editors actually run.
Avoid the temptation to oversell the synergy. Buyers and editors have heard "best-in-class platform" before. Specificity wins: name the customer problem, name the capability you gained, and name what does not change for existing accounts. That is the interview editors want, and the one your customers will find when they search.
What Kills Acquisition Coverage?
Boilerplate-only answers. Editors need a human explanation of the integration story, not a recitation of press-release language. "We are excited to join forces" tells them nothing. "Our enterprise customers asked for X, and this acquisition gives us Y within two quarters" gives them a headline.
Evasiveness kills coverage too. If you dodge every question about customer impact or employee continuity, the segment either does not air or airs with a skeptical frame. Prepare honest answers at the strategic level, even if you cannot share operational details yet. Confidence without specifics reads better than silence with a smile.
How Do You Structure the Integration Story?
Start with the customer problem, not the deal. Why did this acquisition happen now? What were customers asking for that you could not deliver alone? Then move to capability: what does the combined company do that neither could do separately? Finish with continuity: what stays the same for existing accounts, support channels, and product roadmaps in the near term.
That three-part structure, problem, capability, continuity, works for broadcast segments, MSN features, and the clips your team will repurpose on LinkedIn. It also maps cleanly to what legal teams can approve because it stays at the strategic level without wandering into undisclosed terms.
Can One Interview Serve Customers and Investors?
Yes, if you anchor on the integration narrative rather than deal mechanics. Customers care about product survival and support. Investors care about strategic logic and market position. Both audiences respond to a clear explanation of why the combination makes sense and what it enables, told by a founder who sounds like they believe it.
One 30-minute conversation, coached around approved talking points, can become a syndicated feature, broadcast clips, and social assets your account teams forward for months. The interview is not a one-time PR event. It is the source material for every channel that needs to answer the question people are Googling after your deal closes.
Act while the milestone is news
Executive Visibility Package
Guaranteed CNBC, Bloomberg, and MSN.com coverage plus a month of content from one 30-minute interview, built for raises, launches, acquisitions, and major hires.
