Prompt · Follow-up

Follow-up after a first meeting

Get agreement on the record and the next step owned by someone.

Email type
Follow-up
Business
Agency
Tone
Professional
Length
90-130 words

The follow-up email prompt

Write a plain-text follow-up after a meeting with [WHO WAS THERE], covering [WHAT WAS AGREED]. Words only — no HTML, no layout notes.

This email becomes the record. Write it so that if someone reads it in six weeks, they know what was decided.

Rules:
- 90 to 130 words.
- Open with one sentence naming what was agreed at the highest level. Not "thanks for your time" — that can go at the end in four words or not at all.
- Then [WHO DOES WHAT], as a short list. Each line is an action, an owner and a date. Put my own actions first; leading with theirs reads as an invoice.
- Include [THE OPEN QUESTION] explicitly, with who is expected to resolve it. Unwritten open questions are the ones that surface as a disagreement two months later.
- Do not summarise the discussion. Nobody rereads a recap of a conversation they were in.
- Do not pitch, do not attach a proposal unless one was asked for, and do not suggest a next meeting unless one was agreed.
- Never invent a number, date, figure or commitment that was not in my notes. If something is unclear, write it as an open question rather than resolving it in the email.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the project. Return subject, body, sign-off.

What to fill in first

[WHO WAS THERE]
Who you met and what the meeting was about.
[WHAT WAS AGREED]
The substance. Paste your notes in raw and let the model organise them.
[WHO DOES WHAT]
Each action, its owner and its date. Include your own, first.
[THE OPEN QUESTION]
Anything left unresolved. Writing it down is how it gets resolved rather than forgotten.

When to send it

Within a few hours, same day at the latest. The value of this email decays fast: sent within the hour it sets the record while everyone still agrees on what happened, and sent three days later it becomes one participant’s version of events.

What to change first

[WHO DOES WHAT]. Most follow-ups summarise the conversation and leave the actions implied, which is how a good meeting produces nothing. An action with a name and a date attached is the entire deliverable of this email — and putting your own first is what makes the list read as a commitment rather than a demand.

What good output looks like

Subject: Onboarding rebuild, next steps

Agreed we start with the onboarding flow rather than the whole app, with a view to a second phase in the new year.

From me, by Friday: a scope and a fixed price for phase one, plus the two examples we talked about.

From you, by the 20th: the analytics access, and confirmation from Priya that the January budget can carry phase two.

Still open: whether the existing design system stays. You were going to check who owns it now.

The prompt writes the words. Bring them here and the studio builds the campaign — branded, dark-mode safe, and ready to import.

Generate your own

In the studio

A model writes copy. It does not write email.

Production HTML that survives Outlook, dark mode and a Gmail clip is a different job from writing the words. Describe the send once and export it to Mailchimp, Klaviyo, ActiveCampaign or MailerLite.