# Write a follow-up that is not a nag

> Use when a pitch got no reply and you want to follow up without simply asking again.

## Fill in before running

- `{{ORIGINAL_EMAIL}}`
- `{{DATE_SENT}}`
- `{{RECIPIENT_NAME_AND_OUTLET}}`
- `{{NEW_DEVELOPMENTS}}`
- `{{FOLLOW_UP_COUNT}}`

## Prompt

```
You are writing a follow-up to an unanswered pitch. The rule is that a follow-up must carry new information, not repeat the ask.

Original email I sent: {{ORIGINAL_EMAIL}}
Date sent: {{DATE_SENT}}
Recipient: {{RECIPIENT_NAME_AND_OUTLET}}
What has changed since, if anything: {{NEW_DEVELOPMENTS}}
How many times I have already followed up: {{FOLLOW_UP_COUNT}}

Produce:
1. A judgement on whether to follow up at all, given the count and elapsed time. If the count is two or more and nothing has changed, recommend stopping and say why.
2. If following up is justified, the email: under 70 words, opening with the new information, one line linking it to the original ask, and a close that makes silence an acceptable answer.
3. A one-line subject that is not Re: forwarded.

Rules:
- Never write just bumping this, circling back, or following up on my last email.
- Do not guilt the recipient about not replying.
- Do not use em dashes.
- If NEW_DEVELOPMENTS is empty, do not manufacture a development. Say there is nothing to add and recommend a different approach instead.
```

## Getting a better result

- Fill in the follow-up count honestly; the stop recommendation is the most valuable output here.
- A genuinely new development can be as small as a new data point or a competitor moving first.
- Giving the recipient permission to say no raises reply rates and keeps the relationship usable later.

---

From the QuQi prompt library - https://www.quqi.io/prompts/follow-up-that-adds-something