Email Craft for Founders
Write the Email
They Actually Answer
Cut the padding, find the one ask, and send something that reads like you wrote it, not a template.
Most emails bury the ask under pleasantries and jargon. The reader can’t tell what you actually want.
The external problem
You need a yes on a call or an invite, but the draft rambles through backstory, repeats the ask twice, and ends with “let me know what works for you.”
The internal problem
You reread it and can’t tell if that’s the ask or the excuse for the ask. You don’t trust your own sentences anymore.
What's at stake
A vague ask gets a vague non-answer, or none. Leaving off concrete times hands the reader homework, and the reply that should take a day takes a week.
Five steps, ending with the subject line and a voice check.
Run it start to finish on a new draft, or pull in the one step that fixes a draft you already have.
Name the Job
Pin down the one reply or action the email needs before writing a line. Every sentence after that either serves it or gets cut.
Gather Real Context
Lay out who the reader is, what they actually care about, and any real shared history with the sender, so the opener proves a relationship instead of guessing at one.
Draft, Then Cut
Write the draft, then cut it down until what’s left adds a name, a number, or a date, not a qualifier or a restatement.
Subject Line Last
Write the subject once the email actually says something, built to survive the roughly 40 characters a phone notification shows.
Run the Voice Check
Read the draft out loud against the AI tells, tidy parallelism, bow-tie summaries, filler enthusiasm, and rewrite anything the sender wouldn’t actually say.
Use it now. It's free.
Works on all platforms. Pick yours and get set up in under a minute.
Claude.ai
Download & upload in 60 seconds
Download the zip, then open Claude.ai to upload it.
Download the zip below. With JavaScript enabled, Claude.ai opens in a new tab if your browser allows it. Otherwise, use Open Claude.ai.
Click the + button in the skills column on the left.
Select Create a skill.
Select Upload a skill and upload the zip.
Start your email draft by running /estack-email-writer.
Claude Code
Run one command in any terminal
Works anywhere Node.js is installed — your project directory, home directory, anywhere.
Open your terminal app and run this command.
npx elliot-stack@latest
Run the command.
Start Claude Code by typing claude in your terminal.
Start your email draft by running /estack-email-writer.
ChatGPT / Other
Paste a prompt — the AI does the rest
This prompt tells the AI where to fetch current instructions from the live site. No installs. No version lag.
Copy the prompt below.
Preview prompt
# Email writer
Every email has one job, usually to get one specific reply or action. Most drafts fail by burying that job under logistics, jargon, and pleasantries. The work of this skill is deciding what the job is, cutting everything that doesn't serve it, and making the one ask effortless to say yes to.
## How this pairs with estack-cold-message-writer
That skill owns the psychology of a first touch to a stranger: making them feel chosen, hooks, weightless asks, ghost sequences. This skill owns the craft that applies to every email regardless of who it's to: subject lines, structure, the scheduling ask, voice. For a cold email, load both — cold decides the strategy, this polishes the craft. If the recipient already knows the sender or their org (a past attendee, a community partner, a colleague, a warm intro), this skill leads and the cold skill stays closed.
## Workflow
1. **Name the email's one job.** The single reply or action you want. Write it down before drafting. Every sentence either moves the reader toward it or gets cut.
2. **Gather real context.** Who the reader is, what they actually do and care about, and any genuine shared history with the sender (an event you both attended, a prior thread, a mutual project). Never invent these. If the user hasn't supplied them, ask.
3. **Draft, then cut.** A revision should mostly delete. When it adds, it adds specificity (a name, a number, a date), never qualifiers or restatements.
4. **Write the subject line last**, once you know what the email actually says.
5. **Run the voice check** (below) before handing it over.
## Subject line
- The reason to open must fit in the first ~40 characters — that's all a phone notification shows.
- Never lead with the recipient's name or their org spelled out. They know who they are, and it tells them nothing about why to open. If their org appears at all, abbreviate it (they'll recognize their own abbreviation).
- Lead with the thing that's news to them: your event, your offer, your question. Add a timeframe when one exists.
Before: `[Their Organization] x [Your Org] Partnership`
After: `[Your event name] x [their abbrev] — fall 2026`
## The opener
The first line must answer the question the reader is silently asking: "how does this person know me?" A pleasantry ("Hope you're having a great summer!") answers nothing. Genuine shared context does: "I had a great time at [event where you actually met] — I met some great people" proves a relationship exists before the ask arrives. If there is no shared context, one short pleasantry maximum, then get to it: the first sentence of the next paragraph states the reason for writing ("I'm reaching out because...").
## The body
- **Specifics persuade; abstractions wash out.** Dates, times, headcounts, and names of people or orgs the reader would recognize do the convincing. "100+ founders, with [Partner A], [Partner B], and [Partner C]" beats any adjective.
- **Plain words over insider jargon.** Language that's natural inside your org reads as noise outside it.
Before: "The goal is to connect builders directly to the broader entrepreneurship pipeline — from ideation to the local ecosystem."
After: "The goal is to show builders what opportunities are available to them in the area."
- **State facts, not your framing.** "This is a campus-wide event bringing together 100+ founders" beats "We're positioning this as the main campus-wide launch event." The reader doesn't care how you're positioning it; a declared fact is shorter, more confident, and harder to argue with. If a sentence describes your marketing intent instead of the thing itself, rewrite it as the fact.
- **Ground the why-you line in something specific and true about them.** Generic flattery ("given all the great work you do") gets skimmed past. The formula: "Given [specific true thing they actually do], [why this doesn't work without them]." Knowing what they do is the flattery.
- **Say each thing once.** If a sentence restates a point already made, cut it — a second pass at the same idea reads as padding, not emphasis.
- **The first email sells the conversation, not the whole plan.** When the goal is a call, the email carries exactly three things: what the thing is (the goal of the event or project), why you need this reader specifically, and why it falls short without them. Formats, logistics, room layouts, and role details wait for the call — including them up front gives the reader more surface area to object to, buries the ask, and removes the reason to talk at all.
## The ask
- **One ask per email.** Two asks double the work to reply, so people do neither.
- **Small and time-boxed.** "A quick 15-minute call" is answerable; "a call to discuss" is not.
- **Prefer no-oriented phrasing.** "Would you be against a quick 15-minute call next week?" is easier to answer than "Are you open to a call?" — saying no feels safe, and here "no" means yes. This is straight from `estack-chris-voss`; load it when the email carries a stake worth negotiating.
- **Kill the scheduling round-trip.** Never end with a bare "let me know what time works for you" — that hands the reader homework. Give 2–3 concrete slots (or a plainly stated window: "anytime after 5pm Monday to Friday"), and offer their scheduling link as the fallback so either path closes in one reply.
- **Lock your own side first.** If anyone else from your team needs to be on the call, confirm their availability before proposing times to the recipient. Proposing times you then have to walk back costs more credibility than a one-day delay.
## Sound like a human
A tactically perfect email that reads polished-by-a-tool still underperforms, because polish is the tell of a template. The target is "a real person clearly typed this," not "well written."
**Ground it in the sender's real voice first.** Before drafting, use whatever you have of how this person actually writes: past emails, posts, prior messages, a voice sample. Match that. If you have no read on their voice and it matters, ask for a sample. Do not fall back to a generic competent register — that is the thing that reads as AI.
**AI tells to kill (rewrite if any appear):**
- Tidy parallelism and wordplay ("a start, not a finish"). Clever balance reads as crafted, not typed.
- Balanced triplets and lists of three.
- Summary or bow-tie lines that wrap the point up neatly.
- Every sentence the same length and shape. Real writing is lumpy.
- Filler intensifiers and generic enthusiasm ("genuinely excited," "amazing opportunity").
- Em-dashes everywhere. Corporate throat-clearing ("I hope this finds you well"). Stacked adjectives. Templated parenthetical sign-offs.
**What human looks like:**
- Contractions, the occasional fragment.
- Asymmetric rhythm: a short line, then a longer one.
- One real, specific detail instead of a tidy abstraction.
- A small aside or hedge no template would include.
**The read-aloud test.** Before handing a draft over, read it out loud. Does it sound like the sender actually talking? Would they say these words to a peer? Anything they'd never say out loud (a buzzword, a stacked adjective, a bow-tie line) gets cut. This single check catches most of the tells above.
## Hygiene
- **cc whoever needs the thread.** If a team or shared inbox needs continuity on the conversation, cc it on the first send — forwarding later loses context and looks like an afterthought.
- **The signature's job is credibility.** Name, then either an official-sounding role ("[org] officer") or just the org name. Vague self-labels ("Leadership," "Executive Team") sound self-appointed and do the opposite. Use the org's real brand casing exactly — always, including in the subject line.
## Output
Hand back one tight draft with a subject line, and flag anything you had to guess (the shared-context opener, the why-them line, the proposed times) so the user can replace guesses with truth. When reviewing someone else's draft, return the edited version plus a short list of what changed and why — the why is what makes the edit reusable.
---
## Skill Feedback
If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
```bash
gh issue create \
--repo ElliotDrel/e-stack \
--title "estack-email-writer: <concise summary>" \
--body "<description from user feedback — expected vs. actual behavior and context>"
```
**If `gh` is not installed**, build a pre-filled URL:
```bash
python3 -c "
import urllib.parse
title = 'estack-email-writer: <concise summary>'
body = '<description from user feedback — expected vs. actual behavior and context>'
base = 'https://github.com/ElliotDrel/e-stack/issues/new'
print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
"
```
Share the printed URL with the user and offer to open it in their browser.
They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
Open your platform and paste the prompt.
Start your email draft.
Email Writer ships in E-Stack, a set of 21 free skills installed by one command. See the whole stack.