Launch planning
Before you pitch your launch, find the story
A launch date gives you a deadline. It does not give a journalist a story. Here is how to tell whether yours is ready to leave the room.

You know how much work went into the launch. The reader does not. They have not sat through the product decisions, watched early versions fail or heard the customer conversation that made the idea click.
That gap is where a useful launch story begins. Before writing an announcement, work out what has changed for someone outside the company. Then make it possible for another person to understand and check it.
Start with the change
Finish this sentence without using your company name: “Until now, this group of people had to do this. Now they can do this instead.”
This is a working prompt, not a claim to publish without checking. If the sentence depends on “first”, “only” or “best”, put those words aside and describe the actual difference. A smaller, precise change is easier to explain than a sweeping promise.
A hypothetical scheduling service might launch a shared booking page. “We are transforming appointment management” says little. “A customer can book two related appointments without calling the shop” gives a reader something concrete to consider. That sentence still needs to be true in the product.
Choose one useful angle
Write three possible headlines for your own use: one about the product, one about the problem and one about the people affected. Under each, answer “Why would this publication's readers care?”
Choose the angle with the strongest evidence. Avoid combining every benefit into one pitch. The launch is the occasion; the angle is the reason to read.
Before selecting a publication, read its recent work. Look for the questions it explores, the people it serves and the detail it expects. A relevant connection is more useful than a flattering opening line.
Make a small evidence folder
Build a folder that lets a person check the central claims without another meeting:
- A plain description of what is launching, who can use it and when it is available.
- A working product link, demonstration or screenshots of the actual experience.
- The source, date and scope behind every number you intend to quote.
- Permission for any customer name, quotation, photograph or example you plan to share.
- A short founder biography containing facts you can stand behind.
- One contact who can answer questions and arrange access.
Keep private customer information out of the shareable version. If something is not ready to disclose, describe that boundary clearly. Polished assets cannot substitute for an answer to a basic product question.
Prepare the awkward answers
Ask a colleague to challenge the announcement. What does the product cost? What does it not do? Who is it unsuitable for? What happens after the introductory offer? Which parts exist today, and which are still planned?
Answer in language you would be comfortable seeing quoted. Separate what exists from what you hope to build. If a claim needs a qualification to be accurate, keep it attached when shortening the copy.
This also reveals dependencies. If nobody can confirm the price, the materials are not ready. If a customer has not approved their quotation, prepare a version without it.
Decide whether to send
Can someone outside the team explain the change back to you? Can they find support for the central claim? Can a journalist try the thing, speak to someone relevant or see a useful demonstration? Is someone available to respond afterwards?
If an answer is no, narrow the story or move the outreach. You can still publish a clear update for customers while preparing a stronger press angle.
When the answers are yes, write a short pitch: the change, its relevance to this audience, the evidence and an easy next step. Keep the full background ready for the person who asks.
Coverage remains an editorial decision. Making the story understandable, checkable and worth a closer look is the part you can own.