SOCIAL

Launch announcement sequence

Use when a product or feature ships and you need a run of posts rather than one shout on launch day.

launch-announcement-sequence.md

Download .md

You are planning a social sequence around a launch.

What is launching: {{WHAT_IS_LAUNCHING}}
Who it is for: {{AUDIENCE}}
The problem it solves, in plain terms: {{PROBLEM}}
Launch date: {{LAUNCH_DATE}}
Platform: {{PLATFORM}}

Produce a sequence of 7 posts across the two weeks around launch: three before, one on the day, three after.

Output a table: # | Timing relative to launch | Purpose | Hook line | Body outline (3 bullets) | CTA.

Purposes must include at least: naming the problem without mentioning the product, showing the old workaround, the launch post, one post about a real limitation of what shipped, and one post answering the objection you expect most.

Rules:
- Only the launch-day post may lead with the product name.
- The limitation post must be honest and specific. If you do not know a limitation, write [NEEDS INPUT: what does it not do].
- No countdown posts, no "something big is coming", no teaser with no content.
- No claims about speed, savings or results unless I gave you the figure. Otherwise write [NEEDS FIGURE].
- No em dashes, no "in today's fast-paced world", no "it's not just X, it's Y".

After the table, write the launch-day post in full at {{WORD_COUNT}} words.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{WHAT_IS_LAUNCHING}}
{{AUDIENCE}}
{{PROBLEM}}
{{LAUNCH_DATE}}
{{PLATFORM}}
{{WORD_COUNT}}

Getting a better result

The limitation post consistently outperforms the launch post; do not delete it to keep things upbeat.
Write the problem line yourself in the words a customer used, not the words your team uses.
If the model asks for a figure, get the real one rather than dropping the claim - vague launches convert badly.

Questions about this prompt

When is a sequence better than one launch post?

When something ships and the plan is a single shout on the day. One announcement reaches whoever happens to be online that morning. This spreads seven posts across two weeks and spends most of them on the problem rather than the product, which is what reaches people who had not framed it as a problem yet.

What do I need in front of me?

What is launching, the audience, the date, the platform, and the problem written in the words a customer used rather than your team's. You also need one real limitation, because the sequence includes a post about what it does not do and will otherwise hand you back [NEEDS INPUT] in that row.

What comes back, and which post matters most?

A table of seven posts with timing, purpose, hook line, body outline and CTA, then the launch-day post written in full. Protect the limitation post. The tips say it consistently outperforms the launch post, and it is also the one most likely to be cut in review for being off-message.

What is the mistake?

Filling a [NEEDS FIGURE] with a rounded guess about speed or savings. The prompt refuses to invent those for good reason, and an unsupported launch claim is the line people quote back at you. Get the real number from whoever measured it rather than dropping the claim, since vague launches convert badly.