Most product launches are announced, not explained. A date, a countdown, a photo, a "we're live!" post — and then silence, because nobody knew what problem the product solved or who it was for.
Launch copy has one job: give people a reason to care before you ask them to buy. That is true whether the launch is a new software feature or a new flavour of soap.
Write the one sentence first
Before any asset, write a single sentence: "[Product] helps [specific person] do [specific job] without [the usual cost]." If you cannot fill it in without jargon, you are not ready to write the launch — you are ready to talk to five customers.
Lead with the change, not the feature list
People do not buy features; they buy a different Tuesday. "Sync your calendar in one click" is a feature. "Stop copying meetings into two calendars" is the change. Put the change in the headline and the feature in the second paragraph.
The five assets you actually need
- Launch page — what it is, who it is for, what it replaces, price, and one clear action.
- Announcement email — three short paragraphs: the change, the proof, the link.
- One demonstration — a 40-second screen recording or three annotated screenshots. Not a brand film.
- A comparison paragraph — how it differs from what people use now, honestly.
- FAQ — the five questions support will get in the first week.
Sequence matters more than the day
A launch is a fortnight, not a morning: a week of quiet context (why we built this, who asked for it), one day of announcement, then two weeks of proof (how people are using it, what changed for them). The proof is where most of the sales happen.
Say what it does not do
Naming the limitation builds more trust than another benefit bullet. "It does not import from spreadsheets yet — that is next month" prevents a wave of support tickets and one-star reviews from people who assumed otherwise.
Measure the right thing
Vanity metrics (impressions, likes) tell you the announcement was seen. The numbers that matter are activation (did they complete the first meaningful action), time-to-first-value, and repeat use in week two. If activation is low, the copy promised something the product did not deliver quickly enough.
A short checklist
- One sentence, no jargon, tested on someone outside the company.
- Headline about the change, not the feature.
- One demonstration that takes under a minute.
- Price and limitations on the page.
- FAQ written from real support questions.
- Follow-up planned for day 7 and day 21, not just launch day.
Two questions worth settling early
How early should the page go live? A week before the announcement, with a waitlist. It gives search engines time to index the page and gives you early signal on which headline people click.
What if the launch slips? Say so on the page and in the email. A moved date is a small annoyance; a silent date that passes is a trust problem you will spend months repairing.
An example announcement email
Subject: Stop copying meetings into two calendars
Body: "For the last year, the most common support question we got was how to stop double-booking. As of today, Calendar Sync connects your work and personal calendars in one click, and updates both directions every five minutes.
It does not yet handle recurring events created in the other calendar — that lands next month, and we will email you when it does.
It is included in every plan. Connect a calendar and tell us what breaks."
Three paragraphs: the change, the honest limitation, the action. No brand film, no countdown, no exclamation marks. The limitation paragraph is what makes the rest believable.
