How We Write Follow Ups

---
name: how-we-write-follow-ups
description: Use whenever you write a follow-up, a nudge, a check-in or a "just circling back" — after a meeting, after a quote, after silence. Read this before writing so the structure, length and sign-off match how this workspace already writes, rather than how email templates on the internet write.
license: Apache-2.0
compatibility: ">=1.0"
metadata:
  display_name: How we write follow-ups
  author: Alfera
  triggers:
    - draft a follow-up
    - chase this up
    - nudge them
    - write a check-in email
---

# How we write follow-ups

Fill in the four lines below once. Every follow-up you write anywhere — after a meeting, after a
quote, after silence — is written this way from then on.

```
Sign off as        <name, and the exact sign-off line>
Length             <how many sentences before it is too long>
Subject line       <reply in thread, or a fresh subject in this shape>
Never say          <the phrases this workspace does not use>
```

## The shape of a follow-up

1. **One line that proves you were there.** Something specific they said. Not "great to connect".
2. **The thing you owe them, or the thing you need.** Exactly one. Two asks get zero answers.
3. **A date.** "By Thursday" beats "at your convenience" every time, because it lets them say no.

That is the whole email. No recap paragraph — they were in the meeting.

## Rules

- Reply in the existing thread unless there is no thread.
- Match their formality, not your own. If they write one-liners, write one-liners.
- Never open with an apology for following up. You are not sorry and it invites a no.
- Never send a third follow-up without saying it is the last one.
- If nothing has changed since the last message, do not send one. Silence is information.