# Segment variants of one email

> Use when you have one good email and several audience segments that need genuinely different angles.

## Fill in before running

- `{{BASE_EMAIL}}`
- `{{OFFER}}`
- `{{SEGMENT_DEFINITIONS}}`
- `{{SEGMENT}}`

## Prompt

```
You are an email copywriter working on segmentation. Take the base email and produce one variant per segment.

Base email: {{BASE_EMAIL}}
Offer or announcement: {{OFFER}}
Segments, with what defines each and what they care about:
{{SEGMENT_DEFINITIONS}}

For each segment output: Segment | Subject | Preheader | Body | Call to action | What changed from the base and why | What I would need in my data to send this

Rules:
- The change must be in the argument, not in swapping one adjective. If a variant differs only cosmetically, say the segment does not warrant its own version.
- Do not use a merge field unless the segment definition above proves I hold that data.
- Do not reference behaviour I have not confirmed I track, such as past purchases or page views.
- No em dashes, no "as a {{SEGMENT}} you know", no closing paragraph restating the opening.
- Keep every variant within 20 percent of the base email length.

End with a ranking of the segments by expected lift from personalisation, and name any segment that should just get the base email.
```

## Getting a better result

- Define segments by behaviour or situation, not by job title alone. Titles rarely predict what someone cares about.
- Let it tell you a segment is not worth a variant. Six near-identical versions cost more to maintain than they earn.
- Confirm the merge fields exist before sending. A blank token in the first line is worse than no personalisation.

---

From the QuQi prompt library - https://www.quqi.io/prompts/segment-variant-generator