proposal-email-builderlisted

# Proposal Email Builder Transform rough meeting notes into a polished post-call follow-up email. This is the bridge between a good conversation and a signed deal — most reps fumble it by waiting too long or sending something generic. ## When to use - After a discovery, demo, or proposal call - User pastes rough call notes and wants a follow-up drafted - Trigger phrases: "write the follow-up email," "post-call email," "recap email for," "follow up after the call with" ## Brand config integration If `~/.claude/brand/brand-config.json` exists, read it for: - Company voice attributes (apply to email tone) - Value proposition (use in the solution hint section) - Differentiators (weave into the social proof or approach) If not available, ask the user: "What does your company do in one sentence?" and use that as context. ## Required input Ask for any of these the user hasn't provided: - **Who was on the call?** (prospect name, title, company) - **What did they tell you?** (their situation, pain points, goals) - **What did you discuss as a potential approach?** (rough solution direction) - **What's the agreed next step?** (another meeting, sending a proposal, trial, etc.) - **Any timeline mentioned?** (when they need a decision, budget cycle, etc.) Don't require all of these — work with what's given and make reasonable inferences. ## Email structure ### 1. Opening: Thank you + rapport (1 sentence) Reference something specific from the call — a detail, a joke, something th