Examples are angles, not copy-paste
Swap in the client’s metric, stack, and deadline. Keep the rhythm: problem → proof → plan → question. Never ship an example unchanged — clients spot templates instantly.
Twelve angles to rotate
- “You mentioned X — we did Y with similar constraints.”
- “Three risks I see in this brief and how I’d de-risk them.”
- “If you only fix one thing first, fix X — here’s why.”
- “Quick audit note from your site/repo/screenshot.”
- “Milestone map for a two-week v1.”
- “Team-of-one vs agency — why solo fits this post.”
Store winners, not walls of text
When a letter earns a reply, tag why in a notes doc (niche, opener type, proof used). Reuse the pattern, not the paragraph.
Six more angles to rotate
- Risk-first: “The biggest delivery risk here is X; I would de-risk it by Y.”
- Metric-first: “Similar project moved [metric] from A to B in [time].”
- Process-first: “Week 1 discovery, Week 2 build, Week 3 QA — here is what each includes.”
- Tool-first: “You listed Zapier + HubSpot; I have shipped six integrations between them.”
- Question-first: “Before quoting milestones, I need clarity on [single ambiguity].”
- Portfolio-first: “Thumbnail case study attached in portfolio item #2 matches your industry.”
Store winning openers in a swipe file
Tag by niche and opener type (risk-first, metric-first, question-first). When a new job arrives, pick a tag, customize nouns, and run the replace-name test. Your swipe file grows with your career — it is not static AI output.