L3Lesson 25Free

Create the email follow-up version

Send the deck with context and ask

After this, you'll be able to create a follow-up email and deck note and use it to move a deck from rough material toward a presentable file.

Before you start

Complete Make audience-specific variants first.

The idea

The follow-up email tells the recipient why the deck matters, what changed, and what action is requested. This lesson asks you to make a follow-up email and deck note, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.

Follow-up email, deck note, and next action are disconnected after the meeting. — The first move: turn the lesson input into a follow-up email and deck note.

Here is the before and after: Before, the deck lands with a vague note and the recipient has to infer the ask. After, the email frames the file, highlights the decision, and gives the next step. For example, if you are preparing a sales presentation, the artifact should name the audience, slide job, proof, speaker note, or export check where that detail matters. A reviewer should be able to tell whether the deck is closer to being presented, sent, or handed off.

Now try it: Ask Claude to write the follow-up email in three lengths: short, standard, and executive. Make one choice before asking Claude to write: which audience, which decision, which proof, which slide job, or which delivery mode matters most right now. That choice keeps the deck from becoming a generic presentation outline.

Create the email follow-up version runtime mapThe deck works when a follow-up email and deck note connects the input, the check, and the next step.

Messy inputThe raw pitch deck material before the lesson shapes it.
a follow-up email and deck noteThe thing you can inspect, edit, and reuse.
Review checkThe delivery check that catches a weak assumption.
Next stepThe output moves into the next lesson instead of sitting alone.

The lesson is done when the artifact moves the deck toward a real room, reader, or file handoff.

Try it (14 min)

Watch out for

Writing a long email that repeats the whole deck.
Sending the deck without a clear request.
Forgetting to mention changes after a revision.

Paste this into Claude

Write the email that sends this deck. Include context, one-line summary, why it matters, what to read first, requested action, deadline, and attachment or link note. Deck decision and audience: [paste].

If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

What a good response looks like

Finished Artifact:
- a follow-up email and deck note
- Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention.
- Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything.

Reality Check:
- The artifact names the user, input, decision, owner, or proof it depends on.
- The weakest assumption is visible.
- The next step can be completed in one sitting.

What good looks like

The email names the deck purpose.
The requested action is specific.
The deadline or timing is clear.
The deck link or attachment note is included.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why a follow-up email and deck note matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

What a good response looks like

Transfer Check:
- What changed: the second example has a different audience, input, or delivery context.
- What stayed the same: a follow-up email and deck note still needs a source, a review check, and a next step.
- Before trusting it: inspect the delivery check that would catch a wrong assumption.
- Next action: run the check once, then carry the revised artifact into the next lesson.

What good looks like

You explained the lesson idea from memory before applying it again.
The second example changes the artifact instead of copying the first answer.
The delivery check names a real risk.
The next action can be done in one sitting.

When this breaks

Fails when the ask is vague because the recipient does not know what to do next.
Breaks when the email over-explains because the deck becomes secondary.

AI can help with this

Paste the exercise prompt into Claude with your real deck context. Ask Claude to interview you one question at a time, produce a follow-up email and deck note, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.

The follow-up package links the decision, deck, note, and requested next step.

You can now

You can explain a follow-up email and deck note in one sentence.

You can name the source material or decision it depends on.
You can name the assumption that still needs checking.
You can point to the check that proves it is ready for the next deck step.

Key takeaways

Deck delivery includes the message around the file, not only the file itself.

The email should frame the deck.
The ask must be explicit.
Length should match the recipient.
Revision notes prevent confusion.

Was this helpful?

Up nextFact-check claims and numbers

Make audience-specific variants Fact-check claims and numbers

← Back to Slides & Pitch Decks

Write the email that sends this deck. Include context, one-line summary, why it matters, what to read first, requested action, deadline, and attachment or link note. Deck decision and audience: [paste]. If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

Finished Artifact: - a follow-up email and deck note - Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention. - Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything. Reality Check: - The artifact names the user, input, decision, owner, or proof it depends on. - The weakest assumption is visible. - The next step can be completed in one sitting.

Without rereading the lesson, explain why a follow-up email and deck note matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

Transfer Check: - What changed: the second example has a different audience, input, or delivery context. - What stayed the same: a follow-up email and deck note still needs a source, a review check, and a next step. - Before trusting it: inspect the delivery check that would catch a wrong assumption. - Next action: run the check once, then carry the revised artifact into the next lesson.