Event ·Creator ·Friendly
Get the RSVP from people who will actually turn up.
Write a plain-text invitation to [THE EVENT], happening [WHERE AND WHEN]. Words only — no HTML, no layout notes.
The reader is deciding whether to give up an evening and a journey. Write for that decision.
Rules:
- 110 to 160 words.
- Say what actually happens there in the first two sentences. Not the theme, not the vibe — what people will be doing in the room.
- Include the end time as well as the start. Someone weighing up childcare or a train needs both, and leaving the end time out costs more RSVPs than any other omission.
- Name [WHO IT SUITS] in one sentence, and be willing to exclude. A room of people who came because it sounded vaguely relevant is worse than a smaller room.
- Cover [THE PRACTICALITIES] in one short paragraph. Cost, numbers, whether there is food, whether to bring anything.
- One ask, written as an ordinary sentence with the link inside it.
- Do not describe the atmosphere. Do not promise networking.
- Never invent a number, statistic, capacity or attendee count beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.
Write a subject line under 45 characters naming the event and the city or the date. Return subject, preheader, body, sign-off.
Event ·Spartan
Turn a registration into an attendance.
Write a plain-text reminder to someone already registered for [THE EVENT], happening [WHEN EXACTLY]. Words only — no HTML, no layout notes.
They have already decided. This email exists so they turn up.
Rules:
- 50 to 90 words. Shorter than the invitation by a clear margin.
- Put [HOW TO GET IN] in the first three lines — the join link, the door, the room number. This is the reason the email exists and it should be findable in a search two minutes before the start.
- Repeat [WHEN EXACTLY] with the timezone, even though it was in the invitation. People check the reminder, not the invite.
- State [WHAT TO BRING OR DO] in one line. If nothing is needed, say so explicitly.
- Do not re-pitch. No agenda, no speaker bio, no benefits, no "here is what you will learn". They registered.
- Do not ask them to invite anyone else. That is a different email and it dilutes this one.
- Never invent a number, statistic, attendee count or detail beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.
Write a subject line under 40 characters naming the event and the time. Return subject, preheader, body, sign-off.
Event ·SaaS ·Professional
Get the registration. Attendance is a different email's problem.
Write a plain-text webinar invitation for [THE SESSION], running [WHEN]. Words only — no HTML, no layout notes.
The single action this email drives: registering.
Rules:
- 100 to 150 words.
- Lead with [WHAT THEY LEAVE WITH] — what the attendee can do afterwards that they cannot now. An agenda is not a reason to attend; an outcome is.
- Put [WHEN] on its own line, with the timezone. A reader deciding whether to register is really deciding whether they are free, and making them hunt for the time loses them.
- Name [WHO IS RUNNING IT] in one clause. Credentials in a full sentence read as insecurity.
- Say [THE RECORDING] explicitly. A large share of registrations come from people who already know they cannot make it, and hiding the recording policy costs those sign-ups for nothing.
- Three bullet points maximum if you use any at all, and only for what is covered.
- One ask, written as an ordinary sentence with the link inside it.
- Never invent a number, statistic, attendance figure or testimonial. Where a figure belongs and I have not supplied it, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.
Write a subject line under 45 characters naming the outcome or the topic, not the format. Return subject, preheader, body, sign-off.