| name | consulting-outbound-email |
| description | The process every personalized outbound email runs through before it is staged — gather full context on the person, decide who it is really for and what the objective is (set by temperature), simulate the reader, and pass the pre-send gate. Use when drafting or reviewing any 1:1 nudge, follow-up, broadcast, or stakeholder note. Voice and craft live in consulting-copy-writer; the context gather lives in consulting-lead-context. |
Consulting Outbound Email
The shared gate for outbound email. consulting-email-atomizer, consulting-followup-sequencer,
consulting-stakeholder-update, and the newsletter compile (consulting-friday-review) all run their
drafts through this before staging.
This skill owns the process: who the email is for, what its objective is, the reader-POV check, and
the pre-send gate. It does not own the writing rules.
- Voice and craft →
consulting-copy-writer. Zero em-dashes, short and direct, plain words a human
would say out loud, evidence over vague authority, confident-not-needy outreach posture. Every rule
there applies to every email; this skill does not restate them.
- Context gather →
consulting-lead-context. The full dossier on the person before you write.
1. Read all context first
Never draft from a snippet or a single source. Before writing to a named person, gather everything
knowable by running consulting-lead-context: the post or thread they actually engaged (read the FULL
thing, not their one-line comment), Gmail history for them and their colleagues, Granola notes, the
deal file (pipeline/<stage>/<deal>/AGENTS.md or clients/<client>/), the live Attio record, and the
consulting-lead-temperature record on the dashboard (recompute it if it is missing or stale).
Resolve it yourself. Escalating "confirm X before I send" to the human is the last resort, only after
those sources are exhausted. If the answer sits in a post, a profile, a thread, or a company's homepage,
go get it.
2. Decide who it is for, and the objective
- Who: the exec sponsor (keep it light, route the work to the team) vs. the hands-on POC (go deep on
their actual pain). Target the message and the ask to that person, not the company in general. Get
every name, title, and role right.
- Objective (set by temperature, not just tone): let the
consulting-lead-temperature score set
what this one touch is for.
- Hot (8-10): advance or close. A direct ask, book the next step.
- Cooling (5-7): regain attention and curiosity. Lead with something genuinely interesting, ask
for little or nothing. Do not try to close — that is what reads as a pushy vendor.
- Cold (2-4): pure value, no ask.
The ask scales with temperature; rising vs. falling shifts the tone even at the same score.
3. Reader-POV loop (any important email)
Spawn a subagent to read the draft as the actual recipient — a busy human with limited attention: line
by line in their voice, where they skim, what feels salesy / needy / presumptuous, and reply odds
(1-10). Revise and loop until it lands. Keep those simulated reactions ephemeral; never file them into
the CRM or a deal folder.
Pre-send checklist
Source: Sid's drafting notes (2026-06-19). Applies on top of every format in library/email-templates/.
