100xprism 2.3.1

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 (207) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +196 -0
  3. package/VERSION +1 -0
  4. package/adapters/antigravity.sh +14 -0
  5. package/adapters/claude-code.sh +160 -0
  6. package/adapters/codex.sh +13 -0
  7. package/adapters/copilot.sh +13 -0
  8. package/adapters/cursor.sh +13 -0
  9. package/adapters/gemini.sh +13 -0
  10. package/adapters/lib/__pycache__/modules.cpython-312.pyc +0 -0
  11. package/adapters/lib/modules.py +592 -0
  12. package/adapters/lib/shared.sh +83 -0
  13. package/adapters/lib/sync_plugins.py +113 -0
  14. package/adapters/windsurf.sh +15 -0
  15. package/bin/100xprism.js +29 -0
  16. package/get.sh +24 -0
  17. package/install-project.sh +82 -0
  18. package/install.sh +281 -0
  19. package/lib/adapters/windows.js +429 -0
  20. package/lib/bootstrap.js +33 -0
  21. package/lib/init.js +19 -0
  22. package/lib/install.js +18 -0
  23. package/lib/migrate.js +52 -0
  24. package/lib/platform.js +22 -0
  25. package/lib/update.js +29 -0
  26. package/modules/_lib/reference.md +77 -0
  27. package/modules/a11y-auditor/SKILL.md +151 -0
  28. package/modules/ab-test-setup/SKILL.md +266 -0
  29. package/modules/ab-test-setup/evals/evals.json +105 -0
  30. package/modules/ab-test-setup/references/sample-size-guide.md +263 -0
  31. package/modules/ab-test-setup/references/test-templates.md +277 -0
  32. package/modules/ad-creative/SKILL.md +362 -0
  33. package/modules/ad-creative/evals/evals.json +90 -0
  34. package/modules/ad-creative/references/generative-tools.md +637 -0
  35. package/modules/ad-creative/references/platform-specs.md +213 -0
  36. package/modules/ai-seo/SKILL.md +398 -0
  37. package/modules/ai-seo/evals/evals.json +90 -0
  38. package/modules/ai-seo/references/content-patterns.md +285 -0
  39. package/modules/ai-seo/references/platform-ranking-factors.md +152 -0
  40. package/modules/analytics-tracking/SKILL.md +309 -0
  41. package/modules/analytics-tracking/evals/evals.json +90 -0
  42. package/modules/analytics-tracking/references/event-library.md +260 -0
  43. package/modules/analytics-tracking/references/ga4-implementation.md +300 -0
  44. package/modules/analytics-tracking/references/gtm-implementation.md +390 -0
  45. package/modules/architect/SKILL.md +282 -0
  46. package/modules/branch/SKILL.md +105 -0
  47. package/modules/churn-prevention/SKILL.md +424 -0
  48. package/modules/churn-prevention/evals/evals.json +93 -0
  49. package/modules/churn-prevention/references/cancel-flow-patterns.md +316 -0
  50. package/modules/churn-prevention/references/dunning-playbook.md +408 -0
  51. package/modules/cloud-security/SKILL.md +240 -0
  52. package/modules/cold-email/SKILL.md +178 -0
  53. package/modules/cold-email/evals/evals.json +94 -0
  54. package/modules/cold-email/references/benchmarks.md +83 -0
  55. package/modules/cold-email/references/follow-up-sequences.md +81 -0
  56. package/modules/cold-email/references/frameworks.md +90 -0
  57. package/modules/cold-email/references/personalization.md +79 -0
  58. package/modules/cold-email/references/subject-lines.md +53 -0
  59. package/modules/commit/SKILL.md +195 -0
  60. package/modules/competitor-alternatives/SKILL.md +256 -0
  61. package/modules/competitor-alternatives/evals/evals.json +93 -0
  62. package/modules/competitor-alternatives/references/content-architecture.md +271 -0
  63. package/modules/competitor-alternatives/references/templates.md +223 -0
  64. package/modules/connect/SKILL.md +894 -0
  65. package/modules/content-strategy/SKILL.md +359 -0
  66. package/modules/content-strategy/evals/evals.json +90 -0
  67. package/modules/context-dump/SKILL.md +67 -0
  68. package/modules/copy-editing/SKILL.md +447 -0
  69. package/modules/copy-editing/evals/evals.json +89 -0
  70. package/modules/copy-editing/references/plain-english-alternatives.md +394 -0
  71. package/modules/copywriting/SKILL.md +271 -0
  72. package/modules/copywriting/evals/evals.json +111 -0
  73. package/modules/copywriting/references/cold-email-benchmarks.md +83 -0
  74. package/modules/copywriting/references/cold-email-follow-ups.md +81 -0
  75. package/modules/copywriting/references/cold-email-frameworks.md +90 -0
  76. package/modules/copywriting/references/cold-email-personalization.md +79 -0
  77. package/modules/copywriting/references/cold-email-subject-lines.md +53 -0
  78. package/modules/copywriting/references/copy-frameworks.md +344 -0
  79. package/modules/copywriting/references/email-copy-guidelines.md +113 -0
  80. package/modules/copywriting/references/email-types.md +515 -0
  81. package/modules/copywriting/references/natural-transitions.md +272 -0
  82. package/modules/copywriting/references/sequence-templates.md +168 -0
  83. package/modules/data-query/SKILL.md +58 -0
  84. package/modules/data-viz/SKILL.md +225 -0
  85. package/modules/db/SKILL.md +205 -0
  86. package/modules/db/db-engines/_router.md +24 -0
  87. package/modules/db/db-engines/athena.md +16 -0
  88. package/modules/db/db-engines/cloud-sql.md +16 -0
  89. package/modules/db/db-engines/databricks.md +14 -0
  90. package/modules/db/db-engines/oracle.md +14 -0
  91. package/modules/db/db-engines/postgres.md +15 -0
  92. package/modules/db/db-engines/presto.md +14 -0
  93. package/modules/db/db-engines/snowflake.md +14 -0
  94. package/modules/docs/SKILL.md +100 -0
  95. package/modules/email-sequence/SKILL.md +309 -0
  96. package/modules/email-sequence/evals/evals.json +93 -0
  97. package/modules/email-sequence/references/copy-guidelines.md +113 -0
  98. package/modules/email-sequence/references/email-types.md +515 -0
  99. package/modules/email-sequence/references/sequence-templates.md +168 -0
  100. package/modules/enterprise-design/SKILL.md +75 -0
  101. package/modules/eval/SKILL.md +105 -0
  102. package/modules/figma-translator/SKILL.md +49 -0
  103. package/modules/fix-bugs/SKILL.md +104 -0
  104. package/modules/form-cro/SKILL.md +429 -0
  105. package/modules/form-cro/evals/evals.json +90 -0
  106. package/modules/free-tool-strategy/SKILL.md +178 -0
  107. package/modules/free-tool-strategy/evals/evals.json +90 -0
  108. package/modules/free-tool-strategy/references/tool-types.md +217 -0
  109. package/modules/gate/SKILL.md +232 -0
  110. package/modules/grill-me/SKILL.md +59 -0
  111. package/modules/interaction-engineer/SKILL.md +49 -0
  112. package/modules/issue/SKILL.md +272 -0
  113. package/modules/launch/SKILL.md +345 -0
  114. package/modules/launch-strategy/SKILL.md +353 -0
  115. package/modules/launch-strategy/evals/evals.json +91 -0
  116. package/modules/lint/SKILL.md +126 -0
  117. package/modules/marketing-ideas/SKILL.md +167 -0
  118. package/modules/marketing-ideas/evals/evals.json +90 -0
  119. package/modules/marketing-ideas/references/ideas-by-category.md +366 -0
  120. package/modules/marketing-psychology/SKILL.md +455 -0
  121. package/modules/marketing-psychology/evals/evals.json +88 -0
  122. package/modules/motion-designer/SKILL.md +214 -0
  123. package/modules/onboarding-cro/SKILL.md +220 -0
  124. package/modules/onboarding-cro/evals/evals.json +92 -0
  125. package/modules/onboarding-cro/references/experiments.md +258 -0
  126. package/modules/orchestrate/SKILL.md +77 -0
  127. package/modules/page-cro/SKILL.md +182 -0
  128. package/modules/page-cro/evals/evals.json +111 -0
  129. package/modules/page-cro/references/experiments.md +248 -0
  130. package/modules/page-cro/references/paywall-experiments.md +164 -0
  131. package/modules/paid-ads/SKILL.md +315 -0
  132. package/modules/paid-ads/evals/evals.json +90 -0
  133. package/modules/paid-ads/references/ad-copy-templates.md +207 -0
  134. package/modules/paid-ads/references/audience-targeting.md +243 -0
  135. package/modules/paid-ads/references/platform-setup-checklists.md +277 -0
  136. package/modules/paywall-upgrade-cro/SKILL.md +227 -0
  137. package/modules/paywall-upgrade-cro/evals/evals.json +93 -0
  138. package/modules/paywall-upgrade-cro/references/experiments.md +164 -0
  139. package/modules/popup-cro/SKILL.md +453 -0
  140. package/modules/popup-cro/evals/evals.json +94 -0
  141. package/modules/pr/SKILL.md +203 -0
  142. package/modules/pricing-strategy/SKILL.md +231 -0
  143. package/modules/pricing-strategy/evals/evals.json +90 -0
  144. package/modules/pricing-strategy/references/research-methods.md +152 -0
  145. package/modules/pricing-strategy/references/tier-structure.md +232 -0
  146. package/modules/product-marketing-context/SKILL.md +241 -0
  147. package/modules/product-marketing-context/evals/evals.json +85 -0
  148. package/modules/programmatic-seo/SKILL.md +238 -0
  149. package/modules/programmatic-seo/evals/evals.json +94 -0
  150. package/modules/programmatic-seo/references/playbooks.md +308 -0
  151. package/modules/push/SKILL.md +202 -0
  152. package/modules/referral-program/SKILL.md +255 -0
  153. package/modules/referral-program/evals/evals.json +89 -0
  154. package/modules/referral-program/references/affiliate-programs.md +164 -0
  155. package/modules/referral-program/references/program-examples.md +143 -0
  156. package/modules/release/SKILL.md +293 -0
  157. package/modules/revops/SKILL.md +343 -0
  158. package/modules/revops/evals/evals.json +91 -0
  159. package/modules/revops/references/automation-playbooks.md +290 -0
  160. package/modules/revops/references/lifecycle-definitions.md +278 -0
  161. package/modules/revops/references/routing-rules.md +203 -0
  162. package/modules/revops/references/scoring-models.md +247 -0
  163. package/modules/sales-enablement/SKILL.md +349 -0
  164. package/modules/sales-enablement/evals/evals.json +91 -0
  165. package/modules/sales-enablement/references/deck-frameworks.md +263 -0
  166. package/modules/sales-enablement/references/demo-scripts.md +355 -0
  167. package/modules/sales-enablement/references/objection-library.md +270 -0
  168. package/modules/sales-enablement/references/one-pager-templates.md +208 -0
  169. package/modules/schema-markup/SKILL.md +179 -0
  170. package/modules/schema-markup/evals/evals.json +87 -0
  171. package/modules/schema-markup/references/schema-examples.md +398 -0
  172. package/modules/security/SKILL.md +138 -0
  173. package/modules/seo-audit/SKILL.md +412 -0
  174. package/modules/seo-audit/evals/evals.json +136 -0
  175. package/modules/seo-audit/references/ai-writing-detection.md +200 -0
  176. package/modules/seo-audit/references/content-patterns.md +285 -0
  177. package/modules/seo-audit/references/platform-ranking-factors.md +152 -0
  178. package/modules/signup-flow-cro/SKILL.md +359 -0
  179. package/modules/signup-flow-cro/evals/evals.json +88 -0
  180. package/modules/site-architecture/SKILL.md +357 -0
  181. package/modules/site-architecture/evals/evals.json +88 -0
  182. package/modules/site-architecture/references/mermaid-templates.md +216 -0
  183. package/modules/site-architecture/references/navigation-patterns.md +305 -0
  184. package/modules/site-architecture/references/site-type-templates.md +293 -0
  185. package/modules/social-content/SKILL.md +278 -0
  186. package/modules/social-content/evals/evals.json +92 -0
  187. package/modules/social-content/references/platforms.md +170 -0
  188. package/modules/social-content/references/post-templates.md +177 -0
  189. package/modules/social-content/references/reverse-engineering.md +195 -0
  190. package/modules/spec/SKILL.md +81 -0
  191. package/modules/subagents/SKILL.md +123 -0
  192. package/modules/techdebt/SKILL.md +71 -0
  193. package/modules/terminal-setup/SKILL.md +49 -0
  194. package/modules/test/SKILL.md +493 -0
  195. package/modules/test/references/e2e-patterns.md +294 -0
  196. package/modules/update-claude-md/SKILL.md +52 -0
  197. package/modules/visual-system-architect/SKILL.md +53 -0
  198. package/package.json +44 -0
  199. package/plugins/plugins.json +43 -0
  200. package/shell/aliases.sh +24 -0
  201. package/shell/check-update.sh +212 -0
  202. package/templates/.env.example +199 -0
  203. package/templates/docker-compose.md +46 -0
  204. package/templates/node-frontend.md +56 -0
  205. package/templates/node-fullstack.md +59 -0
  206. package/templates/python-api.md +57 -0
  207. package/update.sh +231 -0
@@ -0,0 +1,111 @@
1
+ {
2
+ "skill_name": "copywriting",
3
+ "evals": [
4
+ {
5
+ "id": 1,
6
+ "prompt": "Write homepage copy for a SaaS tool that automates employee onboarding. Target audience is HR directors at mid-size companies (200-2000 employees). Main differentiator is that it integrates with all major HRIS systems and cuts onboarding time from 2 weeks to 2 days.",
7
+ "expected_output": "Should check for product-marketing-context.md first. Should write full page copy organized by section: Headline, Subheadline, CTA (above the fold), then Social Proof, Problem/Pain, Solution/Benefits, How It Works, Objection Handling, and Final CTA. Should follow copywriting principles: clarity over cleverness, benefits over features, specificity (use the '2 weeks to 2 days' stat), customer language. Headline should communicate core value proposition. CTAs should be action-oriented ('Start Free Trial' not 'Submit'). Should provide 2-3 headline alternatives with rationale. Should include annotations explaining key copy choices. Should include meta content (SEO page title and meta description).",
8
+ "assertions": [
9
+ "Checks for product-marketing-context.md",
10
+ "Writes full page copy organized by section",
11
+ "Includes Headline, Subheadline, and CTA above the fold",
12
+ "Includes Social Proof, Problem/Pain, Solution/Benefits, How It Works sections",
13
+ "Uses the '2 weeks to 2 days' specificity in copy",
14
+ "CTAs are action-oriented, not generic",
15
+ "Provides 2-3 headline alternatives with rationale",
16
+ "Includes annotations explaining copy choices",
17
+ "Includes meta content (SEO title and meta description)"
18
+ ],
19
+ "files": []
20
+ },
21
+ {
22
+ "id": 2,
23
+ "prompt": "Rewrite this headline: 'An Innovative AI-Powered Platform for Streamlined Business Operations' — it's for a B2B SaaS tool that helps small businesses manage invoicing and payments.",
24
+ "expected_output": "Should identify problems: jargon ('innovative,' 'AI-powered,' 'streamlined,' 'business operations'), too vague, company language not customer language. Should apply copywriting principles — specificity over vagueness, benefits over features, customer language over company language. Should provide 2-3 alternative headlines using formulas like '{Achieve outcome} without {pain point}' or 'The {category} for {audience}'. Each alternative should include rationale. Should also suggest a subheadline that adds specificity.",
25
+ "assertions": [
26
+ "Identifies jargon in original headline",
27
+ "Identifies vagueness as a problem",
28
+ "Identifies company language vs customer language issue",
29
+ "Provides 2-3 alternative headlines",
30
+ "Alternatives use headline formulas from the skill",
31
+ "Each alternative includes rationale",
32
+ "Suggests a subheadline"
33
+ ],
34
+ "files": []
35
+ },
36
+ {
37
+ "id": 3,
38
+ "prompt": "i need copy for my pricing page. we have three plans: starter ($29/mo), pro ($79/mo), business ($199/mo). it's a social media scheduling tool for marketers",
39
+ "expected_output": "Should trigger on the casual phrasing. Should ask or infer audience context. Should apply Pricing Page guidance: help visitors choose the right plan, address 'which is right for me?' anxiety, make recommended plan obvious. Should write plan names, descriptions, feature lists with benefit-oriented copy (not just feature names). Should include a page headline that addresses the pricing decision. CTAs should be specific per plan. Should handle objection handling (FAQ copy). Should provide alternatives for key elements.",
40
+ "assertions": [
41
+ "Triggers on casual phrasing",
42
+ "Applies Pricing Page guidance",
43
+ "Addresses 'which plan is right for me' anxiety",
44
+ "Makes recommended plan obvious",
45
+ "Writes benefit-oriented feature copy, not just feature names",
46
+ "Includes page headline",
47
+ "CTAs are specific per plan",
48
+ "Includes FAQ or objection handling copy",
49
+ "Provides alternatives for key elements"
50
+ ],
51
+ "files": []
52
+ },
53
+ {
54
+ "id": 4,
55
+ "prompt": "Write copy for our About page. We're a 3-person startup that built a developer tool for database migrations. Founded because we kept losing data during migrations at our last jobs. Tone should be professional but human.",
56
+ "expected_output": "Should apply About Page guidance: tell the story of why you exist, connect mission to customer benefit, still include a CTA. Should adapt voice and tone to 'professional but human' as specified. Should tell the founder origin story authentically. Should connect the personal pain to the customer's pain. Should include a CTA even on the About page. Copy should follow style rules: active voice, confident, specific. Should NOT be overly corporate or generic.",
57
+ "assertions": [
58
+ "Applies About Page guidance",
59
+ "Tells the story of why the company exists",
60
+ "Connects mission to customer benefit",
61
+ "Includes a CTA",
62
+ "Adapts tone to professional but human",
63
+ "Uses the founder origin story",
64
+ "Connects personal pain to customer pain",
65
+ "Uses active voice",
66
+ "Avoids corporate jargon"
67
+ ],
68
+ "files": []
69
+ },
70
+ {
71
+ "id": 5,
72
+ "prompt": "Can you improve this CTA? We currently have 'Learn More' on our feature page for our analytics dashboard product.",
73
+ "expected_output": "Should immediately identify 'Learn More' as a weak CTA per the guidelines. Should apply the CTA formula: [Action Verb] + [What They Get] + [Qualifier]. Should provide 2-3 strong alternatives like 'See the Dashboard in Action,' 'Start Your Free Trial,' or 'Explore Analytics Features.' Each alternative should include rationale and context for when it works best. Should also consider CTA hierarchy — whether this is a primary or secondary CTA, and suggest complementary CTAs if relevant.",
74
+ "assertions": [
75
+ "Identifies 'Learn More' as a weak CTA",
76
+ "Applies the CTA formula from the skill",
77
+ "Provides 2-3 strong alternatives",
78
+ "Each alternative includes rationale",
79
+ "Considers CTA hierarchy (primary vs secondary)",
80
+ "Suggests complementary CTAs"
81
+ ],
82
+ "files": []
83
+ },
84
+ {
85
+ "id": 6,
86
+ "prompt": "Write me a 5-email welcome sequence for new trial users of our project management tool.",
87
+ "expected_output": "Should recognize this is an email copywriting task, not page copywriting. Should defer to or cross-reference the email-sequence skill, which specifically handles email sequences, drip campaigns, and lifecycle emails. May provide brief general guidance but should make clear that email-sequence is the right skill for this task.",
88
+ "assertions": [
89
+ "Recognizes this as email sequence work",
90
+ "References or defers to email-sequence skill",
91
+ "Does not attempt to write a full email sequence using page copywriting patterns"
92
+ ],
93
+ "files": []
94
+ },
95
+ {
96
+ "id": 7,
97
+ "prompt": "Review this copy and tell me what's wrong: 'We are extremely excited to announce our revolutionary, cutting-edge platform that will totally transform how businesses optimize their workflows! Sign up now!!'",
98
+ "expected_output": "Should apply the Quick Quality Check. Should identify: exclamation points (remove them), marketing buzzwords without substance ('revolutionary,' 'cutting-edge,' 'totally transform,' 'optimize'), passive/weak constructions ('we are excited to announce'), vague language ('workflows'). Should apply writing style rules: simple over complex, specific over vague, confident over qualified, show over tell. Should rewrite the copy following these principles. Should provide 2-3 alternatives.",
99
+ "assertions": [
100
+ "Identifies exclamation point overuse",
101
+ "Identifies marketing buzzwords without substance",
102
+ "Identifies vague language",
103
+ "Applies writing style rules",
104
+ "Rewrites the copy following principles",
105
+ "Provides alternatives",
106
+ "Result is specific, clear, and jargon-free"
107
+ ],
108
+ "files": []
109
+ }
110
+ ]
111
+ }
@@ -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.