# Product launch announcement email

> Use when you are launching something and the draft keeps turning into a feature list.

## Fill in before running

- `{{PRODUCT_NAME}}`
- `{{WHAT_IT_DOES}}`
- `{{AUDIENCE_AND_NON_AUDIENCE}}`
- `{{OLD_WAY}}`
- `{{PRICE_AND_AVAILABILITY}}`
- `{{PROOF}}`
- `{{NEEDS_FACT}}`

## Prompt

```
You are a product marketing copywriter. Write a launch announcement email.

Product: {{PRODUCT_NAME}}
What it does, in plain terms: {{WHAT_IT_DOES}}
Who it is for and who it is not for: {{AUDIENCE_AND_NON_AUDIENCE}}
What people had to do before it existed: {{OLD_WAY}}
Price and availability: {{PRICE_AND_AVAILABILITY}}
Proof I can cite, such as beta results or named users: {{PROOF}}

Output: subject, preheader, body of 150-250 words, one primary call to action, and one secondary link for people who want detail.

Structure:
1. What is now possible that was not before, in the first two sentences.
2. The old way and its cost, briefly.
3. What it does, in three plain statements. Not a feature list.
4. Who it is for, and one honest sentence about who should skip it.
5. Price, availability and the call to action.

Rules:
- No launch cliches: "thrilled to announce", "excited to share", "introducing the future of".
- No em dashes. No "it is not just a tool, it is a workflow" constructions. No closing paragraph restating the opening.
- Do not invent benchmarks, adoption numbers or quotes. Write {{NEEDS_FACT}} where one is needed.
- Keep the who-should-skip sentence in. Do not soften it into a benefit.
```

## Getting a better result

- The "who should skip it" line raises trust and cuts refund and churn traffic from bad-fit buyers.
- Lead with the new capability, not with the fact that you built something.
- If you have no proof yet, say the product is new rather than letting the model invent traction.

---

From the QuQi prompt library - https://www.quqi.io/prompts/product-launch-announcement