outreach

name	outreach
description	Draft investor outreach — cold email, intro ask, forwardable blurb, or follow-up — grounded in the investor's thesis, the current narrative, and prior thread history. Use when the founder needs to send anything to an investor.

Outreach Composer

Arguments: investor name/id, optionally a kind (cold, intro-ask, forwardable, follow-up). Default: infer from status — Not started → cold or forwardable; has a relationship path through someone → intro-ask; Met/Replied → follow-up.

Ground every draft in

1. investors/<slug>.md — Why fit, Talking points, Relationship path, Objections already on record.
2. the narrative doc in company/ (e.g. company/COMPANY.md) — the positioning source of truth. Never invent new positioning in an email; if the narrative doesn't fit this investor, flag it instead.
3. company/profile.md — current proof points (use the freshest, most concrete ones).
4. Gmail (read-only): prior thread with this investor or the intro node — never draft cold copy for someone mid-conversation.

Craft rules

• Cold: 120 words max. One thesis-fit sentence in THEIR language, one proof point with a number, one specific ask. No "hope you're well."
• Intro-ask: addressed to the intro node (from Relationship path), makes the ask forwardable-easy: why this investor specifically, plus a self-contained blurb below the fold.
• Forwardable blurb: 80 words, third person, no links walls — one claim, one proof, one ask. Written so the forwarder looks smart sending it.
• Follow-up: reference the specific conversation, answer the sharpest open objection, deliver (or date-stamp) any promised proof, restate the next step.
• Match the founder's voice — pull register and phrasing cues from company/voice.md; never sound like a template.
• Every draft ends with a concrete next step that's easy to say yes to.

Output

• Propose round outreach draft --investor <n> --kind <kind> --subject "..." --body "..." — proposal only. Never send email; the founder sends manually.
• All writes go through the round CLI queue — never pass --yes, never touch round.db directly; the founder approves in the app.
• For intro-asks/forwardables, also show the founder both pieces (the ask + the blurb) in chat.
• If the right move is NOT to send (no warm path and weak thesis fit, or a missing proof asset would make this email the only impression), say so and propose a round tasks add --text "..." --investor <n> for the prerequisite (e.g. the missing proof asset) instead.