opencode-skills-antigravity 1.0.4 → 1.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (151) hide show
  1. package/bundled-skills/ad-creative/SKILL.md +371 -0
  2. package/bundled-skills/ad-creative/evals/evals.json +90 -0
  3. package/bundled-skills/ad-creative/references/generative-tools.md +637 -0
  4. package/bundled-skills/ad-creative/references/platform-specs.md +213 -0
  5. package/bundled-skills/ai-seo/SKILL.md +407 -0
  6. package/bundled-skills/ai-seo/evals/evals.json +90 -0
  7. package/bundled-skills/ai-seo/references/content-patterns.md +285 -0
  8. package/bundled-skills/ai-seo/references/platform-ranking-factors.md +152 -0
  9. package/bundled-skills/backend-dev-guidelines/SKILL.md +1 -1
  10. package/bundled-skills/cc-skill-security-review/SKILL.md +1 -1
  11. package/bundled-skills/churn-prevention/SKILL.md +433 -0
  12. package/bundled-skills/churn-prevention/evals/evals.json +93 -0
  13. package/bundled-skills/churn-prevention/references/cancel-flow-patterns.md +316 -0
  14. package/bundled-skills/churn-prevention/references/dunning-playbook.md +408 -0
  15. package/bundled-skills/claude-api/LICENSE.txt +202 -0
  16. package/bundled-skills/claude-api/SKILL.md +252 -0
  17. package/bundled-skills/claude-api/csharp/claude-api.md +70 -0
  18. package/bundled-skills/claude-api/curl/examples.md +164 -0
  19. package/bundled-skills/claude-api/go/claude-api.md +146 -0
  20. package/bundled-skills/claude-api/java/claude-api.md +128 -0
  21. package/bundled-skills/claude-api/php/claude-api.md +88 -0
  22. package/bundled-skills/claude-api/python/agent-sdk/README.md +269 -0
  23. package/bundled-skills/claude-api/python/agent-sdk/patterns.md +319 -0
  24. package/bundled-skills/claude-api/python/claude-api/README.md +404 -0
  25. package/bundled-skills/claude-api/python/claude-api/batches.md +182 -0
  26. package/bundled-skills/claude-api/python/claude-api/files-api.md +162 -0
  27. package/bundled-skills/claude-api/python/claude-api/streaming.md +162 -0
  28. package/bundled-skills/claude-api/python/claude-api/tool-use.md +587 -0
  29. package/bundled-skills/claude-api/ruby/claude-api.md +87 -0
  30. package/bundled-skills/claude-api/shared/error-codes.md +205 -0
  31. package/bundled-skills/claude-api/shared/live-sources.md +121 -0
  32. package/bundled-skills/claude-api/shared/models.md +68 -0
  33. package/bundled-skills/claude-api/shared/tool-use-concepts.md +305 -0
  34. package/bundled-skills/claude-api/typescript/agent-sdk/README.md +220 -0
  35. package/bundled-skills/claude-api/typescript/agent-sdk/patterns.md +150 -0
  36. package/bundled-skills/claude-api/typescript/claude-api/README.md +313 -0
  37. package/bundled-skills/claude-api/typescript/claude-api/batches.md +106 -0
  38. package/bundled-skills/claude-api/typescript/claude-api/files-api.md +98 -0
  39. package/bundled-skills/claude-api/typescript/claude-api/streaming.md +178 -0
  40. package/bundled-skills/claude-api/typescript/claude-api/tool-use.md +477 -0
  41. package/bundled-skills/codex-review/SKILL.md +1 -1
  42. package/bundled-skills/cold-email/SKILL.md +167 -0
  43. package/bundled-skills/cold-email/evals/evals.json +94 -0
  44. package/bundled-skills/cold-email/references/benchmarks.md +83 -0
  45. package/bundled-skills/cold-email/references/follow-up-sequences.md +81 -0
  46. package/bundled-skills/cold-email/references/frameworks.md +90 -0
  47. package/bundled-skills/cold-email/references/personalization.md +79 -0
  48. package/bundled-skills/cold-email/references/subject-lines.md +53 -0
  49. package/bundled-skills/content-strategy/SKILL.md +374 -0
  50. package/bundled-skills/content-strategy/evals/evals.json +90 -0
  51. package/bundled-skills/content-strategy/references/headless-cms.md +194 -0
  52. package/bundled-skills/context7-auto-research/SKILL.md +1 -1
  53. package/bundled-skills/dbos-golang/SKILL.md +1 -1
  54. package/bundled-skills/dbos-python/SKILL.md +1 -1
  55. package/bundled-skills/dbos-typescript/SKILL.md +1 -1
  56. package/bundled-skills/debug-buttercup/SKILL.md +1 -1
  57. package/bundled-skills/defuddle/SKILL.md +50 -0
  58. package/bundled-skills/docs/integrations/jetski-cortex.md +3 -3
  59. package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md +1 -1
  60. package/bundled-skills/docs/integrations/jetski-gemini-loader/package.json +1 -0
  61. package/bundled-skills/docs/maintainers/repo-growth-seo.md +3 -3
  62. package/bundled-skills/docs/maintainers/skills-import-2026-03-21.md +81 -0
  63. package/bundled-skills/docs/maintainers/skills-update-guide.md +1 -1
  64. package/bundled-skills/docs/users/bundles.md +1 -1
  65. package/bundled-skills/docs/users/claude-code-skills.md +1 -1
  66. package/bundled-skills/docs/users/gemini-cli-skills.md +1 -1
  67. package/bundled-skills/docs/users/getting-started.md +1 -1
  68. package/bundled-skills/docs/users/kiro-integration.md +1 -1
  69. package/bundled-skills/docs/users/usage.md +4 -4
  70. package/bundled-skills/docs/users/visual-guide.md +4 -4
  71. package/bundled-skills/evaluation/SKILL.md +1 -1
  72. package/bundled-skills/exa-search/SKILL.md +1 -1
  73. package/bundled-skills/firecrawl-scraper/SKILL.md +1 -1
  74. package/bundled-skills/frontend-dev-guidelines/SKILL.md +1 -1
  75. package/bundled-skills/gha-security-review/SKILL.md +2 -1
  76. package/bundled-skills/git-pushing/SKILL.md +1 -1
  77. package/bundled-skills/internal-comms/LICENSE.txt +202 -0
  78. package/bundled-skills/internal-comms/SKILL.md +35 -0
  79. package/bundled-skills/internal-comms/examples/3p-updates.md +47 -0
  80. package/bundled-skills/internal-comms/examples/company-newsletter.md +65 -0
  81. package/bundled-skills/internal-comms/examples/faq-answers.md +30 -0
  82. package/bundled-skills/internal-comms/examples/general-comms.md +16 -0
  83. package/bundled-skills/json-canvas/SKILL.md +253 -0
  84. package/bundled-skills/json-canvas/references/EXAMPLES.md +329 -0
  85. package/bundled-skills/lead-magnets/SKILL.md +319 -0
  86. package/bundled-skills/lead-magnets/references/benchmarks.md +129 -0
  87. package/bundled-skills/lead-magnets/references/format-guide.md +196 -0
  88. package/bundled-skills/memory-systems/SKILL.md +1 -1
  89. package/bundled-skills/obsidian-bases/SKILL.md +506 -0
  90. package/bundled-skills/obsidian-bases/references/FUNCTIONS_REFERENCE.md +173 -0
  91. package/bundled-skills/obsidian-cli/SKILL.md +115 -0
  92. package/bundled-skills/obsidian-markdown/SKILL.md +205 -0
  93. package/bundled-skills/obsidian-markdown/references/CALLOUTS.md +58 -0
  94. package/bundled-skills/obsidian-markdown/references/EMBEDS.md +63 -0
  95. package/bundled-skills/obsidian-markdown/references/PROPERTIES.md +61 -0
  96. package/bundled-skills/product-marketing-context/SKILL.md +250 -0
  97. package/bundled-skills/product-marketing-context/evals/evals.json +85 -0
  98. package/bundled-skills/react-best-practices/SKILL.md +1 -1
  99. package/bundled-skills/revops/SKILL.md +352 -0
  100. package/bundled-skills/revops/evals/evals.json +91 -0
  101. package/bundled-skills/revops/references/automation-playbooks.md +290 -0
  102. package/bundled-skills/revops/references/lifecycle-definitions.md +278 -0
  103. package/bundled-skills/revops/references/routing-rules.md +203 -0
  104. package/bundled-skills/revops/references/scoring-models.md +247 -0
  105. package/bundled-skills/sales-enablement/SKILL.md +358 -0
  106. package/bundled-skills/sales-enablement/evals/evals.json +91 -0
  107. package/bundled-skills/sales-enablement/references/deck-frameworks.md +263 -0
  108. package/bundled-skills/sales-enablement/references/demo-scripts.md +355 -0
  109. package/bundled-skills/sales-enablement/references/objection-library.md +270 -0
  110. package/bundled-skills/sales-enablement/references/one-pager-templates.md +208 -0
  111. package/bundled-skills/seo/SKILL.md +139 -0
  112. package/bundled-skills/seo/references/cwv-thresholds.md +108 -0
  113. package/bundled-skills/seo/references/eeat-framework.md +214 -0
  114. package/bundled-skills/seo/references/quality-gates.md +155 -0
  115. package/bundled-skills/seo/references/schema-types.md +118 -0
  116. package/bundled-skills/seo-competitor-pages/SKILL.md +229 -0
  117. package/bundled-skills/seo-content/SKILL.md +186 -0
  118. package/bundled-skills/seo-dataforseo/SKILL.md +395 -0
  119. package/bundled-skills/seo-geo/SKILL.md +254 -0
  120. package/bundled-skills/seo-hreflang/SKILL.md +209 -0
  121. package/bundled-skills/seo-image-gen/SKILL.md +183 -0
  122. package/bundled-skills/seo-images/SKILL.md +193 -0
  123. package/bundled-skills/seo-page/SKILL.md +103 -0
  124. package/bundled-skills/seo-plan/SKILL.md +136 -0
  125. package/bundled-skills/seo-plan/assets/agency.md +175 -0
  126. package/bundled-skills/seo-plan/assets/ecommerce.md +167 -0
  127. package/bundled-skills/seo-plan/assets/generic.md +144 -0
  128. package/bundled-skills/seo-plan/assets/local-service.md +160 -0
  129. package/bundled-skills/seo-plan/assets/publisher.md +153 -0
  130. package/bundled-skills/seo-plan/assets/saas.md +135 -0
  131. package/bundled-skills/seo-programmatic/SKILL.md +184 -0
  132. package/bundled-skills/seo-schema/SKILL.md +178 -0
  133. package/bundled-skills/seo-sitemap/SKILL.md +129 -0
  134. package/bundled-skills/seo-technical/SKILL.md +175 -0
  135. package/bundled-skills/site-architecture/SKILL.md +366 -0
  136. package/bundled-skills/site-architecture/evals/evals.json +88 -0
  137. package/bundled-skills/site-architecture/references/mermaid-templates.md +216 -0
  138. package/bundled-skills/site-architecture/references/navigation-patterns.md +305 -0
  139. package/bundled-skills/site-architecture/references/site-type-templates.md +293 -0
  140. package/bundled-skills/skill-improver/SKILL.md +1 -1
  141. package/bundled-skills/tavily-web/SKILL.md +1 -1
  142. package/bundled-skills/test-fixing/SKILL.md +1 -1
  143. package/bundled-skills/tool-design/SKILL.md +1 -1
  144. package/bundled-skills/ui-ux-pro-max/SKILL.md +1 -1
  145. package/bundled-skills/verification-before-completion/SKILL.md +1 -1
  146. package/bundled-skills/wiki-changelog/SKILL.md +1 -1
  147. package/bundled-skills/wiki-onboarding/SKILL.md +1 -1
  148. package/bundled-skills/wiki-qa/SKILL.md +1 -1
  149. package/bundled-skills/wiki-researcher/SKILL.md +1 -1
  150. package/bundled-skills/wiki-vitepress/SKILL.md +1 -1
  151. package/package.json +1 -1
@@ -0,0 +1,94 @@
1
+ {
2
+ "skill_name": "cold-email",
3
+ "evals": [
4
+ {
5
+ "id": 1,
6
+ "prompt": "Write a cold email to VP of Marketing at mid-size B2B SaaS companies. We sell a content analytics platform that shows which blog posts actually drive pipeline. Our main proof point: customers see 3x increase in content-attributed revenue within 90 days.",
7
+ "expected_output": "Should check for product-marketing-context.md first. Should write like a peer, not a vendor. Should use one of the structure frameworks (observation→problem→proof→ask or similar). Subject line should be 2-4 words, lowercase, internal-looking. Every sentence should earn its place. Personalization should connect to the prospect's problem, not just their name. Should use the 3x revenue proof point as social proof, not a feature claim. CTA should be low-friction (not 'book a demo'). Should provide 2-3 variations. Should include a quality check against the guidelines.",
8
+ "assertions": [
9
+ "Checks for product-marketing-context.md",
10
+ "Writes like a peer, not a vendor",
11
+ "Uses a structure framework from the skill",
12
+ "Subject line is short, lowercase, internal-looking",
13
+ "Every sentence earns its place (concise)",
14
+ "Personalization connects to prospect's problem",
15
+ "Uses proof point as social proof",
16
+ "CTA is low-friction",
17
+ "Provides 2-3 variations"
18
+ ],
19
+ "files": []
20
+ },
21
+ {
22
+ "id": 2,
23
+ "prompt": "Help me write a cold email to CTOs at enterprise companies. I sell cybersecurity training. My current email has a 2% open rate and 0% reply rate.",
24
+ "expected_output": "Should diagnose the current email's likely problems based on 2% open rate (subject line issue) and 0% reply rate (body/relevance issue). Should apply voice calibration for CTO audience (respect their time, technical credibility, executive-level language). Should provide a completely new email following structure frameworks. Subject line should be 2-4 words, look internal. Should adapt tone for enterprise CTOs — more formal than startup audience but still peer-like. Should provide the email plus analysis of why each element works.",
25
+ "assertions": [
26
+ "Diagnoses problems from the performance data",
27
+ "Identifies subject line as likely open rate issue",
28
+ "Applies voice calibration for CTO audience",
29
+ "Subject line is short, lowercase, internal-looking",
30
+ "Adapts tone for enterprise audience",
31
+ "Uses structure framework from the skill",
32
+ "Explains why each element works"
33
+ ],
34
+ "files": []
35
+ },
36
+ {
37
+ "id": 3,
38
+ "prompt": "write me a follow-up sequence. prospect didn't reply to my first email about our HR software. how many should I send and how far apart?",
39
+ "expected_output": "Should trigger on casual phrasing. Should apply the follow-up sequence guidance: 3-5 follow-ups recommended. Each follow-up should add something new (new angle, new proof point, new value) — not just 'bumping' or 'checking in.' Should provide timing recommendations between emails. Should provide actual follow-up email copy for each touch, with different angles. Should include a breakup email at the end. Should note that each follow-up should be shorter than the previous.",
40
+ "assertions": [
41
+ "Triggers on casual phrasing",
42
+ "Recommends 3-5 follow-up emails",
43
+ "Each follow-up adds something new",
44
+ "Does not use 'just bumping' or 'checking in' language",
45
+ "Provides timing between emails",
46
+ "Provides actual copy for each follow-up",
47
+ "Includes a breakup email",
48
+ "Follow-ups get progressively shorter"
49
+ ],
50
+ "files": []
51
+ },
52
+ {
53
+ "id": 4,
54
+ "prompt": "Review this cold email and tell me what's wrong: 'Dear Sir/Madam, I hope this email finds you well. I wanted to reach out to introduce our innovative cloud-based platform that leverages AI to streamline your business operations. We have helped over 500 companies transform their workflows. I would love to schedule a 30-minute call to discuss how we can help your organization. Best regards, John'",
55
+ "expected_output": "Should apply the quality check framework. Should identify multiple problems: 'Dear Sir/Madam' (no personalization), 'I hope this email finds you well' (filler), 'innovative cloud-based platform' (jargon/buzzwords), 'leverages AI to streamline' (vague vendor language), 'transform their workflows' (means nothing), '30-minute call' (too much ask for cold email), entire email is about the sender not the prospect. Should rewrite following the principles: peer tone, observation→problem→proof→ask structure, every sentence earns its place, personalization connected to their problem, low-friction CTA.",
56
+ "assertions": [
57
+ "Identifies lack of personalization",
58
+ "Identifies filler phrases",
59
+ "Identifies jargon and buzzwords",
60
+ "Identifies vendor language vs peer language",
61
+ "Identifies CTA as too high-friction",
62
+ "Notes email is sender-focused not prospect-focused",
63
+ "Provides a rewritten version",
64
+ "Rewrite follows cold email principles"
65
+ ],
66
+ "files": []
67
+ },
68
+ {
69
+ "id": 5,
70
+ "prompt": "What are the best subject lines for cold emails? I want to maximize open rates.",
71
+ "expected_output": "Should apply the subject line guidelines: short (2-4 words), lowercase or sentence case, internal-looking (should look like it came from a colleague, not a vendor). Should provide examples following these principles. Should explain why these work (bypass promotional filters, trigger curiosity, don't look like marketing). Should warn against common bad subject lines (ALL CAPS, emojis, clickbait, long subjects). Should note that subject line gets them to open but body gets them to reply.",
72
+ "assertions": [
73
+ "Applies subject line guidelines (2-4 words, lowercase, internal-looking)",
74
+ "Provides specific examples",
75
+ "Explains why the format works",
76
+ "Warns against common bad subject line patterns",
77
+ "Notes distinction between open rate and reply rate"
78
+ ],
79
+ "files": []
80
+ },
81
+ {
82
+ "id": 6,
83
+ "prompt": "Can you help me set up an automated email drip campaign for leads who download our whitepaper?",
84
+ "expected_output": "Should recognize this is a lifecycle/nurture email sequence, not cold outreach. Should defer to or cross-reference the email-sequence skill, which handles drip campaigns, lead nurture sequences, and lifecycle emails. Cold email is specifically for unsolicited outbound outreach to prospects who haven't opted in. Should make this distinction clear.",
85
+ "assertions": [
86
+ "Recognizes this as lifecycle/nurture email, not cold outreach",
87
+ "References or defers to email-sequence skill",
88
+ "Explains the distinction between cold email and lifecycle email",
89
+ "Does not attempt to design a nurture sequence using cold email patterns"
90
+ ],
91
+ "files": []
92
+ }
93
+ ]
94
+ }
@@ -0,0 +1,83 @@
1
+ # Benchmarks, Data & Expert Methods
2
+
3
+ ## Core Performance Metrics (2024–2025)
4
+
5
+ | Metric | Average | Good | Excellent | Source |
6
+ | -------------------------- | ------- | ------ | --------- | ------------------------ |
7
+ | Open rate | 27.7% | 40–45% | 50%+ | Belkins, Snov.io |
8
+ | Reply rate | 4–5.8% | 5–10% | 10–15% | Belkins, Reachoutly |
9
+ | Reply rate (best-in-class) | — | — | 15–25%+ | Digital Bloom, Instantly |
10
+ | Positive reply % | ~48% | 55–60% | 62–65% | Digital Bloom |
11
+ | Meeting booking rate | 0.5–1% | 1–2% | 2.3%+ | Reachoutly |
12
+ | Bounce rate | 7.5% | <4% | <2% | Belkins |
13
+
14
+ ## Realistic Funnel Model
15
+
16
+ 500 emails → 100 opens (20%) → 25 replies (5%) → 8 positive replies (30%) → 4 meetings (50%) → 1 client (25% close). ~**0.2% end-to-end conversion** for average performers.
17
+
18
+ ## Performance Levers (ranked by impact)
19
+
20
+ 1. **Hook type** — Timeline hooks outperform problem hooks by 3.4x in meetings
21
+ 2. **Personalization depth** — Up to 250% more replies
22
+ 3. **Brevity** — 25–75 words optimal, 83% more replies under 75 words
23
+ 4. **Targeting precision** — ≤50 contacts per campaign = 2.76x higher reply rates
24
+ 5. **Follow-up strategy** — First follow-up adds 49% more replies
25
+ 6. **Reading level** — 3rd–5th grade = 67% more replies
26
+ 7. **Send timing** — Thursday peaks at 6.87% reply rate
27
+
28
+ ## Declining Effectiveness Trend
29
+
30
+ Reply rates dropped from 7–8% (2020–2022) to 4–5.8% (2024–2025), ~15% YoY decline. Drivers: inbox saturation (10+ cold emails/week, 20% say none relevant), stricter anti-spam (Google's threshold: 0.1% complaints), AI email flood (more volume, less quality signal). Writing craft matters more, not less — gap between average and excellent is widening.
31
+
32
+ ## Response Rates by Seniority
33
+
34
+ - **Entry-level:** Highest engagement at 8% reply, 50% open
35
+ - **C-level:** 23% more likely to respond than non-C-suite when they engage (6.4% vs 5.2%)
36
+ - **CTOs/VP Tech:** 7.68% reply
37
+ - **CEOs/Founders:** 7.63% reply
38
+ - **Heads of Sales:** 6.60% (most targeted role, highest saturation)
39
+
40
+ ## Industry Variation
41
+
42
+ **Highest responding:** Nonprofits (16.5%+), legal (10%), EdTech (7.8%), chemical (7.3%), manufacturing (6.1%).
43
+ **Lowest responding:** SaaS (3.5%), financial services (3.4%), IT services (3.5%).
44
+
45
+ ## Top 15 Mistakes (ranked by impact)
46
+
47
+ 1. **Too long** — 70% of emails above 10th-grade level. Under 75 words = 83% more replies
48
+ 2. **Too self-focused** — "We are a leading..." signals sales pitch. Count I/We sentences
49
+ 3. **No clear value prop** — 71% of decision-makers ignore irrelevant emails
50
+ 4. **Generic templates** — {{FirstName}} isn't personalization. Recipients detect instantly
51
+ 5. **Feature dumping** — "Great reps lead with problems" (Lavender). One proof point beats ten features
52
+ 6. **False personalization** — "Loved your post!" without specifics is transparent
53
+ 7. **Asking too much too soon** — 30-min call in first email = "proposing on first date"
54
+ 8. **Pushy language** — "Act Now" stacking increases spam flagging by 67%
55
+ 9. **No CTA** — Without a clear next step, momentum dies
56
+ 10. **"Just checking in" follow-ups** — "I never heard back" = 12% drop in bookings
57
+ 11. **Wrong tone for audience** — Founder ≠ RevOps lead ≠ sales leader
58
+ 12. **Jargon/buzzwords** — "Leverage synergistic platform" → "We help you book more meetings"
59
+ 13. **Unsubstantiated claims** — "300% more leads" without proof triggers skepticism
60
+ 14. **Too many contacts per company** — 1–2 people = 7.8% reply; 10+ = 3.8%
61
+ 15. **Fake urgency** — Fake "Re:" / "Fwd:" / countdown timers destroy trust
62
+
63
+ ## Cultural Calibration
64
+
65
+ | Factor | US | UK | Germany/DACH | Scandinavia |
66
+ | ------------ | --------------- | ------------------------ | -------------------- | ----------------------- |
67
+ | Tone | Direct, casual | Polite, professional | Precise, data-driven | Fact-based, egalitarian |
68
+ | Length | Shorter, blunt | Longer, insight-led | Detail-oriented | Concise but substantive |
69
+ | Social proof | Outcome numbers | Research-led credibility | Technical precision | Shared values |
70
+
71
+ North America: 4.1% response. Europe: 3.1%. Asia-Pacific: 2.8%. Shorter, more direct sequences work better in US. UK needs more insight/personality. GDPR affects European tone.
72
+
73
+ ## Expert Quick Reference
74
+
75
+ | Expert | Core Method | Best For |
76
+ | -------------- | --------------------------------------------------------------- | ----------------------------------------------- |
77
+ | Alex Berman | 3C's: Compliment → Case Study → CTA | High-ticket B2B services, agencies |
78
+ | Josh Braun | "Poke the Bear" — neutral questions exposing invisible problems | Empathy-driven consultative selling |
79
+ | Kyle Coleman | Systematic research + AI personalization at scale | Bridging mass outreach and deep personalization |
80
+ | Becc Holland | Psychographic personalization, Premise Buckets | Combining personalization with relevance |
81
+ | Will Allred | Data-driven coaching, Mouse Trap, Vanilla Ice Cream | Any context; universal frameworks |
82
+ | Justin Michael | 1–3 sentence hyper-brevity, quote their own words | High-velocity SDR teams at scale |
83
+ | Sam Nelson | Agoge Sequence — Triple on Day 1 (email + LinkedIn + call) | Multi-channel, tiered personalization |
@@ -0,0 +1,81 @@
1
+ # Follow-Up Sequences
2
+
3
+ 55% of replies come from follow-ups, not the initial email. Yet 48% of salespeople never follow up even once.
4
+
5
+ ## How Many: 3–5 Total Emails
6
+
7
+ - Highest single-email reply rate: **8.4%** (Belkins).
8
+ - 4–7 email campaigns achieve **27% reply rates** vs 9% for 1–3 emails (Woodpecker, 20M emails).
9
+ - By 4th follow-up, response rates drop **55%** and spam complaints **triple**.
10
+ - Resolution: longer sequences catch different timing windows. Cap at 4 follow-ups (5 total emails). Each must add genuinely new value.
11
+
12
+ ## Optimal Cadence
13
+
14
+ Increase the gap between each touch:
15
+
16
+ | Touch | Day | Notes |
17
+ | ------------- | ----- | ---------------------------------------------- |
18
+ | Initial email | 0 | Maximum personalization investment |
19
+ | Follow-up 1 | 3 | Waiting 3 days increases response by up to 31% |
20
+ | Follow-up 2 | 7–8 | Different angle |
21
+ | Follow-up 3 | 14 | New value piece |
22
+ | Follow-up 4 | 21–28 | Breakup email |
23
+
24
+ **Best days:** Tuesday–Thursday (Thursday peaks at 6.87% reply rate).
25
+ **Best times:** 9–11 AM or 1–3 PM in prospect's local time.
26
+ **Avoid:** Monday mornings (inbox overload), Friday afternoons (checked out).
27
+
28
+ ## Angle Rotation
29
+
30
+ Each follow-up must stand alone while building toward the goal. Never just "bump this up."
31
+
32
+ | Email | Angle | Purpose |
33
+ | ----------- | ---------------------------------------------------------- | -------------------------- |
34
+ | Initial | Personalized hook + core value prop + soft CTA | Introduce problem/solution |
35
+ | Follow-up 1 | Different angle, new value piece (stat, insight, resource) | Show additional benefit |
36
+ | Follow-up 2 | Social proof / case study from similar company | Build credibility |
37
+ | Follow-up 3 | New insight, industry trend, or relevant resource | Demonstrate expertise |
38
+ | Follow-up 4 | Breakup — acknowledge silence, leave door open | Trigger loss aversion |
39
+
40
+ Add only **one new value proposition per email** (SalesBread). This naturally forces different angles.
41
+
42
+ ## The Breakup Email
43
+
44
+ Leverages loss aversion — removing pressure while creating scarcity through withdrawal. Close.com reports **10–15% response rates** from breakup emails with cold prospects.
45
+
46
+ **Structure:**
47
+
48
+ 1. Acknowledge you've reached out multiple times
49
+ 2. Validate their potential lack of interest
50
+ 3. State this is your final email for now
51
+ 4. Leave the door open
52
+
53
+ **Example:**
54
+
55
+ > I haven't heard back, so I'll assume now isn't the right time. Before I close the loop: [1-sentence insight or resource]. If that changes things, feel free to reply. Otherwise, no hard feelings — good luck with [their goal].
56
+
57
+ **1-2-3 Format** (reduces friction to near zero):
58
+
59
+ > Since I haven't heard back, I'll keep it simple. Reply with a number:
60
+ >
61
+ > 1 — Interested, let's talk
62
+ > 2 — Not now, check back in 3 months
63
+ > 3 — Not interested, please stop
64
+
65
+ **Critical rule:** If you send a breakup email, honor it. Do not contact the prospect again.
66
+
67
+ ## Phrases That Kill Response Rates
68
+
69
+ - "I never heard back" → **12% drop** in meeting booking rate (Gong)
70
+ - "Just checking in" → Zero value, signals laziness
71
+ - "Bumping this to the top of your inbox" → Presumptuous
72
+ - "Did you see my last email?" → Guilt-tripping
73
+ - "Following up on my previous message" → Generic, adds nothing
74
+
75
+ ## CTA Adjustment by Seniority
76
+
77
+ **Executives/founders:** Ultra-low-effort, curiosity-driven. "Curious?" or "Worth 2 min?"
78
+
79
+ **Mid-level managers:** More specific value. "Want me to walk through how [Company] saved 15 hours/week?"
80
+
81
+ Higher in the org chart = less friction you can ask for.
@@ -0,0 +1,90 @@
1
+ # Cold Email Copywriting Frameworks
2
+
3
+ Frameworks beat templates — they teach thinking patterns, not copy-paste shortcuts.
4
+
5
+ ## PAS — Problem, Agitate, Solution (default)
6
+
7
+ **Structure:** Identify pain → Amplify consequences → Present solution + soft CTA.
8
+ **Best for:** Problem-aware but not solution-aware prospects. The workhorse framework.
9
+
10
+ > Most VP Sales at companies your size spend 5+ hours/week on manual CRM reporting. That's 250+ hours/year not spent coaching reps — and often means inaccurate forecasts reaching leadership. We built a tool that auto-generates CRM reports in real time. Teams like Datadog reduced reporting time by 80%. Would it make sense to see how?
11
+
12
+ ## BAB — Before, After, Bridge
13
+
14
+ **Structure:** Current painful situation → Ideal future → Your product as the bridge.
15
+ **Best for:** Transformation-driven offers with clear before/after. Emotional decision-makers.
16
+
17
+ > Right now, your team is likely spending hours manually sourcing leads — feast or famine each quarter. Imagine qualified leads arriving daily on autopilot, reps spending 100% of their time selling. That's what our platform does. Companies like HubSpot saw a 40% pipeline increase within 90 days. Can I show you how?
18
+
19
+ ## QVC — Question, Value, CTA
20
+
21
+ **Structure:** Targeted pain question → Brief value → Direct next step.
22
+ **Best for:** C-suite prospects who prefer brevity. Qualify interest immediately.
23
+
24
+ > Are your SDRs spending more time researching than selling? We help sales teams automate prospect research so reps focus on conversations. Clients see 3x more meetings per rep per week. Worth a 10-minute demo?
25
+
26
+ ## AIDA — Attention, Interest, Desire, Action
27
+
28
+ **Structure:** Hook/stat → Address specific challenge → Social proof/outcome → Clear CTA.
29
+ **Best for:** Data-driven prospects, high-ticket pitches with strong stats.
30
+
31
+ > Companies in pharma lose 30% of leads due to manual outreach. Given {{Company}}'s growth this quarter, pipeline velocity is likely top of mind. Customers like Pfizer use our platform to automate lead qualification — cutting time-to-contact by 60%. Worth a 15-minute call?
32
+
33
+ ## PPP — Praise, Picture, Push
34
+
35
+ **Structure:** Genuine compliment → How things could be better → Gentle push to action.
36
+ **Best for:** Senior prospects who respond to relationship-building. Requires genuine trigger.
37
+
38
+ > Your keynote on scaling SDR teams was spot-on — especially on ramp time as the hidden cost. What if you could cut that in half? Our in-inbox coach helps new reps write effective emails from day one with real-time scoring. Open to a quick chat about how this could support your growth?
39
+
40
+ ## Star-Story-Solution
41
+
42
+ **Structure:** Introduce character (customer) → Tell challenge narrative → Reveal results.
43
+ **Best for:** Strong customer success stories. Humanizes the pitch.
44
+
45
+ > Last year, Sarah — VP Sales at a Series B startup — had 5 SDRs competing against a rival with 20. Her team was getting crushed on volume. They adopted our AI prospecting tool and sent hyper-personalized emails at 3x pace without losing quality. Within 90 days, they booked more meetings than their competitor's entire team. Happy to share how this could work for {{Company}}.
46
+
47
+ ## SCQ — Situation, Complication, Question
48
+
49
+ **Structure:** Current reality → Complicating challenge → Question that speaks to need → Optional answer.
50
+ **Best for:** Consultative selling. Mirrors how professionals present to leadership.
51
+
52
+ > Your team doubled this year. That usually means onboarding is eating into selling time. How are you handling ramp for new hires?
53
+
54
+ ## ACCA — Awareness, Comprehension, Conviction, Action
55
+
56
+ **Structure:** Contrarian hook → Explain benefit simply → Provide proof → Strong CTA.
57
+ **Best for:** Analytical buyers who need evidence (engineers, CFOs, ops leaders).
58
+
59
+ > Most sales teams measure rep activity. The top 5% measure rep efficiency instead. When Acme switched, they booked 40% more meetings with fewer emails. Worth seeing how?
60
+
61
+ ## 3C's (Alex Berman)
62
+
63
+ **Structure:** Compliment → Case Study → CTA.
64
+ **Best for:** Agency/services cold outreach. Case study does the heavy lifting.
65
+
66
+ > Big fan of [Company]. We just built an app for [Competitor] that does XYZ. I have a few more ideas. Interested?
67
+
68
+ ## Mouse Trap (Lavender/Will Allred)
69
+
70
+ **Structure:** Observation + Binary value-prop question. 1–2 sentences total.
71
+ **Best for:** Maximum brevity. Impulsive reply based on curiosity.
72
+
73
+ > Looks like you're hiring reps. Would it be helpful to get a more granular look at how they're ramping on email?
74
+
75
+ ## Justin Michael Method
76
+
77
+ **Structure:** Trigger/Pain → Solution hint → Binary CTA. 1–3 sentences, no intro.
78
+ **Best for:** High-velocity SDR teams. Mobile-optimized. Deliberately polarizing.
79
+
80
+ Spend max 1 minute on personalization. Use industry/persona-level signals. For top-tier prospects, quote their own words from interviews — they almost always respond.
81
+
82
+ ## Vanilla Ice Cream (Lavender)
83
+
84
+ **Structure:** Observation → Problem/Insight → Credibility → Solution → Call-to-Conversation.
85
+ **Best for:** Universal "base" framework that works everywhere. Five parts.
86
+
87
+ ## PASTOR (Ray Edwards)
88
+
89
+ **Structure:** Problem → Amplify → Story → Testimony → Offer → Response.
90
+ **Best for:** Longer-form or multi-email sequences. Consulting, education, complex B2B services. Each element can be developed across separate touches.
@@ -0,0 +1,79 @@
1
+ # Personalization at Scale
2
+
3
+ Personalization drives **50–250% more replies** (Lavender). The key insight: **if your personalization has nothing to do with the problem you solve, it's just an attention hack** (Clay).
4
+
5
+ ## Four Levels of Personalization
6
+
7
+ ### Level 1 — Basic (merge tags)
8
+
9
+ First name, company name, job title. Table stakes, no longer differentiating. ~5% lift.
10
+
11
+ ### Level 2 — Industry/segment
12
+
13
+ Industry-specific pain points, trends, regulatory challenges. Scalable via micro-segmentation.
14
+
15
+ > Most {{industry}} teams struggle with {{lead gen problem}}, which often leads to wasted effort.
16
+
17
+ ### Level 3 — Role-level
18
+
19
+ Challenges specific to their role and seniority.
20
+
21
+ > As Head of Sales, keeping pipeline steady is probably your biggest headache. Your RevOps team is small, so you're likely wearing multiple hats during scaling.
22
+
23
+ ### Level 4 — Individual (gold standard)
24
+
25
+ Specific, timely observations about that person connected to the problem you solve.
26
+
27
+ > Noticed you're hiring 3 SDRs — sounds like you're scaling outbound fast. Most teams hit follow-up fatigue during onboarding.
28
+
29
+ ## Research Signal Stack
30
+
31
+ | Signal | Where to find it | How to use it |
32
+ | ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
33
+ | Recent funding | Crunchbase, LinkedIn, press | "Congrats on Series B — scaling teams fast usually creates X challenge" |
34
+ | Job postings | LinkedIn Jobs, careers page | "Noticed you're hiring 3 SDRs — sounds like you're scaling outbound" |
35
+ | Tech stack | BuiltWith, Wappalyzer, HG Insights | "I see you're using HubSpot — most teams at your stage hit a ceiling with X" |
36
+ | LinkedIn activity | Posts, comments, job changes | "Really enjoyed your post about X" |
37
+ | Company news | Google News, press releases | "Congrats on acquiring X — integrating teams usually creates Y challenge" |
38
+ | Podcast/talks | Google, YouTube, podcasts | "Caught your talk at SaaStr on X — really insightful" |
39
+ | Website changes | Manual review | "Your new pricing page caught my eye — curious how it's converting" |
40
+
41
+ ## The 3-Minute Personalization System
42
+
43
+ From "30 Minutes to President's Club":
44
+
45
+ **Step 1:** Build a research stack of top 10 buying signals — 5 company triggers, 5 person triggers. Stack-rank by relevance.
46
+
47
+ **Step 2:** Build a 3x3 template: (1) personalization attached to a problem, (2) problem you solve, (3) one-sentence solution + low-friction CTA.
48
+
49
+ **Step 3:** Create 5 "trigger templates" — pre-written personalization paragraphs for each trigger, with a smooth segue into the problem.
50
+
51
+ The personalization must logically connect to the problem. This creates 5 reusable triggers with the rest of the email constant. A top SDR writes a personalized email in **under 3 minutes**.
52
+
53
+ ## The Four -Graphic Principles (Becc Holland)
54
+
55
+ - **Demographic** — Age, profession, background
56
+ - **Technographic** — Tech stack, tools used
57
+ - **Firmographic** — Company size, funding, industry, growth stage
58
+ - **Psychographic** — Values, passions, beliefs (highest-impact dimension)
59
+
60
+ Tapping into what prospects are passionate about drives significantly higher response rates.
61
+
62
+ ## Observation-Based Openers (highest performing)
63
+
64
+ **Trigger-event:** "Congrats on the recent funding round — scaling the team from here is exciting, and I imagine [challenge] is top of mind."
65
+
66
+ **Observation:** "Your recent post about [topic] resonated — especially the part about [detail]. Got me thinking about how that applies to [challenge]."
67
+
68
+ **Industry insight:** "Most [role titles] I talk to spend [X hours/week] on [problem] — curious if that matches your experience at [Company]."
69
+
70
+ ## What Feels Fake (avoid)
71
+
72
+ - AI-generated emails with similar phrasing ("I hope this email finds you well")
73
+ - Generic attention hacks disconnected from problem ("Cool that you went to UCLA!" → pitch)
74
+ - Over-personalizing to creepiness
75
+ - "I saw your LinkedIn profile and wanted to reach out" — signals mass automation
76
+
77
+ ## The "So What?" Test
78
+
79
+ After writing any opening line, read from prospect's perspective: "So what? Why would I care?" If the answer is nothing, rewrite.
@@ -0,0 +1,53 @@
1
+ # Subject Line Optimization
2
+
3
+ The subject line determines whether the email gets read. The data is counterintuitive: **short, boring, internal-looking subject lines win decisively.**
4
+
5
+ ## Length: 2–4 words
6
+
7
+ - 2-word subject lines get **60% more opens** than 5-word (Lavender).
8
+ - Going from 2 to 4 words reduces replies by **17.5%**.
9
+ - 2–4 words yield **46% open rates** vs 34% for 10 words (Belkins, 5.5M emails).
10
+ - Mobile truncates at 30–35 characters — brevity is practical necessity.
11
+
12
+ ## Internal Camouflage Principle
13
+
14
+ Subject lines that look like they came from a colleague, not a vendor, double open rates (Gong). Buyers mentally categorize before opening — if it looks like sales, it's filtered.
15
+
16
+ **High-performing examples:** "reply rates" · "trial delays" · "hiring ops" · "employee turnover" · "Q2 forecast" · "new patients" · "personalization issue" · "second page"
17
+
18
+ ## Capitalization: lowercase wins
19
+
20
+ All-lowercase has highest open rates (Gong, 85M+ emails). Lowercase looks more personal/internal. For cold outreach specifically, lowercase beats title case.
21
+
22
+ ## Personalization: context over name
23
+
24
+ Personalized subject lines boost opens **26–50%**, but type matters:
25
+
26
+ - **First name in subject line → 12% fewer replies.** Signals automation.
27
+ - **Contextual personalization works:** pain points, competitors, trigger events, industry challenges.
28
+ - Use {{painPoint}}, {{competitor}}, {{commonGround}} — not {{firstName}}.
29
+
30
+ ## Questions: only when highly specific
31
+
32
+ Data conflicts: Belkins says questions perform well (46% open rate). Lavender says questions lower opens by **56%**. Resolution: **specific pain questions work** ("Need help with {{challenge}}?"), **generic questions fail** ("Quick question?" / "Have 15 minutes?"). Default to statements.
33
+
34
+ ## What to Avoid
35
+
36
+ | Anti-pattern | Impact |
37
+ | ---------------------------------------------- | --------------------------- |
38
+ | Salesy language ("increase," "boost," "ROI") | -17.9% opens |
39
+ | Urgency words ("ASAP," "urgent") | Below 36% opens |
40
+ | Excessive punctuation ("!!!" or "??") | -36% opens |
41
+ | Numbers and percentages | -46% opens |
42
+ | Emojis | Hurt B2B professionalism |
43
+ | Pitching product in subject | -57% replies |
44
+ | Empty/no subject line | +30% opens but -12% replies |
45
+ | Spam triggers ("free," "guarantee," "act now") | Deliverability risk |
46
+
47
+ ## C-Suite Subject Lines
48
+
49
+ Executives receive 300–400 emails daily, decide in seconds. They respond **23% more often** than non-C-suite when emails pass their filter (6.4% reply rate).
50
+
51
+ What works: ultra-concise, human, understated. "{{companyInitiative}}" · "thank you" · "an update" · "a question" · reference to a specific project or trigger event.
52
+
53
+ Anything "salesy" is immediately rejected.