Verified against ChatGPT · 2026-07-28
Write a genuine thank-you or follow-up note
Writes a short thank-you or follow-up note (after an interview, a meeting, a favor, a referral) that references one specific detail from the interaction, so it doesn't read as an obviously templated courtesy message.
The prompt
Ready to copy — highlighted parts are example details you can swap.
TASK: Write a short thank-you / follow-up note for the situation below.
WHO IT'S TO: The hiring manager who interviewed me for a product design role
WHAT HAPPENED: A 45-minute interview where we talked through my portfolio and their team's current redesign project.
ONE SPECIFIC THING WORTH MENTIONING: She mentioned the team is struggling to get engineering buy-in on design changes, and I have a relevant story about solving exactly that at my last job.
WHAT I WANT THIS NOTE TO DO: Reinforce that I understand their actual problem and would be useful solving it, and keep myself top of mind before their decision.
REQUIREMENTS:
- Reference the specific detail above in the first two sentences — the note should be recognizably about this exact interaction, not swappable with any other thank-you note
- Keep it to 120 words
- Match tone to the relationship: professional but warm, not stiff
- If the goal includes a next step (staying in touch, confirming a next meeting, asking a follow-up question), state it clearly in one sentence near the end, not buried
- No generic closing filler ("Thanks again for your time and consideration") — end on the specific note instead
Write the note. Then suggest one alternative subject line if this is being sent as an email rather than a handwritten note.Customize the highlighted detailsoptional — the prompt above already works
Why this works
The specific-detail variable is the entire mechanism here — a thank-you note fails the moment it reads as swappable with any other thank-you note, and the only reliable way to stop an LLM from defaulting to that generic register is to hand it one real, concrete detail and require it to appear in the first two sentences, not buried at the end. This mirrors the cold-outreach prompt's trigger-fact requirement: specificity is doing the same job in both, anchoring the message in something true rather than letting the model fall back on template phrasing. Separating "what happened" from "what I actually want this note to accomplish" also matters, since a thank-you note that's purely polite reads differently from one that's quietly doing follow-up work (staying top of mind, reinforcing fit) — naming the goal explicitly lets the model write toward it instead of defaulting to pure courtesy.
What you get back
Hi Maria, Thank you for walking me through the redesign project yesterday — the engineering buy-in challenge you described is exactly the kind of problem I enjoy solving. At my last role, I ran into the same resistance and got past it by bringing engineers into the design review a stage earlier, which cut pushback significantly by the time changes were proposed. I'd love the chance to bring that same approach to your team. Happy to share more detail on how that process worked if it would be useful before your next round of decisions. Thanks again for the thoughtful conversation. Best, [Your name] Alternative subject line: Following up on the redesign challenge
Verified against
ChatGPT GPT-5.1 · 2026-07-28
Claude Claude Sonnet 4.5 · 2026-07-28
Changelog
- 2026-07-28 — Required the specific detail to land in the first two sentences after early drafts buried it near the end, undermining the whole point.
- 2026-07-09 — Initial version published.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
