Write an Email That Gets Answered
Write a short email with one clear ask that gets answered.
Busy people delete vague emails. This Cookbook helps you name the reader, lock one ask, lead with the point, and revise until the message is short enough to answer. Enter only facts you know about the person, the ask, and the deadline. Every step is told to invent nothing about their calendar or motives. You leave with a send-ready email and a simple checklist.
- Made for
- Anyone who needs a clear reply from a busy person: managers, landlords, clients, or teammates
- You leave with
- reader brief, full short email with subject, revised send-ready email, and a pre-send checklist
- Time
- about 28 minutes
- Steps
- 3 guided steps
- Requires
- any AI you already use (a free chat account is usually enough); sample answers included where available
- Completed runs
- 389 (demo metric)
- Average rating
- 4.8 / 5 (demo metric)
Also in Start Here Selected by SousMeow Recently Added Under 30 Minutes
Have an account? Sign in.
Stages
3 stages in sequence-
11 step
Aim
Name the reader and the single ask before any sentences.
-
21 step
Draft
Write a scannable subject and a short body in one pass.
-
31 step
Send-ready
Revise for clarity and pack a pre-send checklist.
Workflow steps
3 steps · completed in orderStage 1: Aim
-
1
Name the reader and the one ask
Lock who this is for, what you want them to do, and what they already know.
Vague emails hide the ask. This step forces one reader and one action before sentences appear. Common mistakes: writing to "whoever handles this," stacking three asks, inventing how busy or annoyed they feel. Need help if the AI invents motives? Paste again and ban mind-reading. You are ready when a stranger could repeat your ask in one sentence.
- Exactly one ask You could underline a single action. Nothing else sneaks in.
- Reader is named specifically Not "the team" or "whoever." A real recipient from your facts.
- No invented emotions Nothing claims how they feel or what they will definitely do.
Stage 2: Draft
-
2
Write subject and short email
Produce subject options and a complete short email a busy reader can answer in one pass.
People decide from the subject and first lines. Common mistakes: cute subjects, burying the ask, stacking side requests, inventing ticket numbers. Need help if the body grows past a screen? Paste again and cap the body near 120 words. You are ready when skimming only the subject and first sentence still reveals the ask.
- Subject states the point A stranger skimming the inbox knows the topic without opening.
- Ask appears early A reader who stops after three lines still has the request.
- One primary ask only No bonus favors or stacked questions.
Stage 3: Send-ready
-
3
Revise for clarity and pack a checklist
Tighten wording, keep the voice honest, and finish with a pre-send checklist.
First drafts often hedge. This step removes fog without turning rude. Common mistakes: passive voice sneaking back, new asks appearing, checklist items that need research you do not have. Need help if the revise gets sharper than your tone choice? Paste again and restore the selected tone. You are ready when you would hit send today.
- Still one ask Revision did not smuggle a second request.
- Changes are specific You can see what got cut or rewritten.
- Checklist is send-day practical Every item is something you can verify in one minute.
Your information
7 details, answered once- Who receives this email? Name and role if you know them. One busy human, not a whole department.
- How do you know each other? Tenant, coworker, client, stranger via form. Mention prior contact if it is real.
- What is the one thing you want them to do? One action. If you have two asks, pick the one that unlocks the rest.
- Why does this matter now? A real consequence or deadline. Skip drama. Stick to facts.
- Facts they need to act Unit numbers, dates, links, amounts. One per line. Only what is true.
- Tone How this should sound in their inbox.
- Your name and sign-off details Name, optional role, phone or unit. Exactly as it should appear.
Finished files
What you export when every step is approved
One Markdown file per approved step, plus kit.html (opens in any browser, offline)
and a README of what you approved.
kit.htmlOffline HTML reader for every approved step01-name-reader-and-ask.mdName the reader and the one ask02-subject-and-short-draft.mdWrite subject and short email03-revise-and-checklist.mdRevise for clarity and pack a checklistREADME.mdManifest of what you approved