@sellable/mcp 0.1.0

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 (200) hide show
  1. package/.claude-plugin/plugin.json +12 -0
  2. package/.mcp.json +9 -0
  3. package/README.md +355 -0
  4. package/dist/api.d.ts +21 -0
  5. package/dist/api.js +73 -0
  6. package/dist/auth.d.ts +60 -0
  7. package/dist/auth.js +246 -0
  8. package/dist/engage-memory.d.ts +63 -0
  9. package/dist/engage-memory.js +354 -0
  10. package/dist/index-dev.d.ts +2 -0
  11. package/dist/index-dev.js +17 -0
  12. package/dist/index.d.ts +7 -0
  13. package/dist/index.js +8 -0
  14. package/dist/server.d.ts +1 -0
  15. package/dist/server.js +499 -0
  16. package/dist/skills.d.ts +11 -0
  17. package/dist/skills.js +97 -0
  18. package/dist/tools/auth.d.ts +30 -0
  19. package/dist/tools/auth.js +124 -0
  20. package/dist/tools/blueprint-commit.d.ts +174 -0
  21. package/dist/tools/blueprint-commit.js +286 -0
  22. package/dist/tools/bootstrap.d.ts +64 -0
  23. package/dist/tools/bootstrap.js +246 -0
  24. package/dist/tools/campaigns.d.ts +589 -0
  25. package/dist/tools/campaigns.js +892 -0
  26. package/dist/tools/cells.d.ts +58 -0
  27. package/dist/tools/cells.js +48 -0
  28. package/dist/tools/context.d.ts +88 -0
  29. package/dist/tools/context.js +271 -0
  30. package/dist/tools/csv-domains.d.ts +73 -0
  31. package/dist/tools/csv-domains.js +464 -0
  32. package/dist/tools/csv-linkedin.d.ts +102 -0
  33. package/dist/tools/csv-linkedin.js +712 -0
  34. package/dist/tools/direct-campaigns.d.ts +240 -0
  35. package/dist/tools/direct-campaigns.js +250 -0
  36. package/dist/tools/engage-bootstrap.d.ts +94 -0
  37. package/dist/tools/engage-bootstrap.js +205 -0
  38. package/dist/tools/engage-discovery.d.ts +78 -0
  39. package/dist/tools/engage-discovery.js +150 -0
  40. package/dist/tools/engage-memory.d.ts +181 -0
  41. package/dist/tools/engage-memory.js +143 -0
  42. package/dist/tools/engage-state.d.ts +72 -0
  43. package/dist/tools/engage-state.js +62 -0
  44. package/dist/tools/enrichment.d.ts +167 -0
  45. package/dist/tools/enrichment.js +174 -0
  46. package/dist/tools/flow-preflight.d.ts +68 -0
  47. package/dist/tools/flow-preflight.js +138 -0
  48. package/dist/tools/framework.d.ts +44 -0
  49. package/dist/tools/framework.js +153 -0
  50. package/dist/tools/interaction-mode.d.ts +27 -0
  51. package/dist/tools/interaction-mode.js +102 -0
  52. package/dist/tools/leads.d.ts +2417 -0
  53. package/dist/tools/leads.js +2307 -0
  54. package/dist/tools/linkedin.d.ts +210 -0
  55. package/dist/tools/linkedin.js +229 -0
  56. package/dist/tools/navigation.d.ts +91 -0
  57. package/dist/tools/navigation.js +381 -0
  58. package/dist/tools/one-off.d.ts +229 -0
  59. package/dist/tools/one-off.js +273 -0
  60. package/dist/tools/processing.d.ts +70 -0
  61. package/dist/tools/processing.js +56 -0
  62. package/dist/tools/prompts.d.ts +211 -0
  63. package/dist/tools/prompts.js +210 -0
  64. package/dist/tools/provider-preflight.d.ts +21 -0
  65. package/dist/tools/provider-preflight.js +59 -0
  66. package/dist/tools/readiness.d.ts +261 -0
  67. package/dist/tools/readiness.js +510 -0
  68. package/dist/tools/rows.d.ts +126 -0
  69. package/dist/tools/rows.js +105 -0
  70. package/dist/tools/rubrics.d.ts +497 -0
  71. package/dist/tools/rubrics.js +681 -0
  72. package/dist/tools/senders.d.ts +44 -0
  73. package/dist/tools/senders.js +69 -0
  74. package/dist/tools/sequencer.d.ts +127 -0
  75. package/dist/tools/sequencer.js +194 -0
  76. package/dist/tools/tables.d.ts +35 -0
  77. package/dist/tools/tables.js +36 -0
  78. package/dist/tools/verify-row.d.ts +36 -0
  79. package/dist/tools/verify-row.js +38 -0
  80. package/dist/tools/workspaces.d.ts +140 -0
  81. package/dist/tools/workspaces.js +139 -0
  82. package/dist/utils/workspace-root.d.ts +1 -0
  83. package/dist/utils/workspace-root.js +39 -0
  84. package/package.json +46 -0
  85. package/skills/building-gtm-tables/SKILL.md +216 -0
  86. package/skills/building-gtm-tables/core/auto-execute.yaml +19 -0
  87. package/skills/building-gtm-tables/core/blueprint-schema.json +72 -0
  88. package/skills/building-gtm-tables/references/brief-to-blueprint.md +334 -0
  89. package/skills/building-gtm-tables/references/column-type-catalog.md +318 -0
  90. package/skills/building-gtm-tables/references/common-blueprints.fixtures.ts +199 -0
  91. package/skills/building-gtm-tables/references/common-blueprints.md +44 -0
  92. package/skills/building-gtm-tables/references/failure-taxonomy.md +197 -0
  93. package/skills/building-gtm-tables/references/uat-seed-prompts.md +37 -0
  94. package/skills/building-gtm-tables/references/verify-loop.md +74 -0
  95. package/skills/campaign-messages/SKILL.md +173 -0
  96. package/skills/campaign-messages/flow.v1.json +75 -0
  97. package/skills/craft-message/SKILL.md +401 -0
  98. package/skills/create-campaign/ARCHITECTURE.md +232 -0
  99. package/skills/create-campaign/DISCUSS.md +296 -0
  100. package/skills/create-campaign/FLOW_ASCII.md +240 -0
  101. package/skills/create-campaign/HOST-PARITY-CHECKLIST.md +49 -0
  102. package/skills/create-campaign/README.md +142 -0
  103. package/skills/create-campaign/SKILL.md +286 -0
  104. package/skills/create-campaign/context/README.md +67 -0
  105. package/skills/create-campaign/context/_TEMPLATE.md +12 -0
  106. package/skills/create-campaign/context/context.md +35 -0
  107. package/skills/create-campaign/context/learnings.md +16 -0
  108. package/skills/create-campaign/context/registry.json +19 -0
  109. package/skills/create-campaign/core/flow.v1.json +217 -0
  110. package/skills/create-campaign/core/policy.md +191 -0
  111. package/skills/create-campaign/core/providers/apollo.json +35 -0
  112. package/skills/create-campaign/core/providers/prospeo.json +34 -0
  113. package/skills/create-campaign/core/providers/registry.json +31 -0
  114. package/skills/create-campaign/core/providers/sales-nav.json +37 -0
  115. package/skills/create-campaign/core/providers/signal-discovery.json +42 -0
  116. package/skills/create-campaign/references/brief-template.md +64 -0
  117. package/skills/create-campaign/references/campaign-quality.md +84 -0
  118. package/skills/create-campaign/references/copy-calibration-examples.md +120 -0
  119. package/skills/create-campaign/references/offer-patterns.md +108 -0
  120. package/skills/create-campaign/references/provider-selection-strategy.md +212 -0
  121. package/skills/create-campaign/references/question-examples.md +167 -0
  122. package/skills/create-campaign/references/token-fill-examples.md +81 -0
  123. package/skills/create-campaign-brief/ARCHITECTURE.md +72 -0
  124. package/skills/create-campaign-brief/DISCUSS.md +64 -0
  125. package/skills/create-campaign-brief/README.md +176 -0
  126. package/skills/create-campaign-brief/SKILL.md +537 -0
  127. package/skills/create-campaign-brief/references/brief-synthesis-rules.md +100 -0
  128. package/skills/create-campaign-brief/references/brief-template.md +220 -0
  129. package/skills/create-campaign-brief/references/campaign-idea-options.md +30 -0
  130. package/skills/create-campaign-brief/references/copy-appendix-template.md +62 -0
  131. package/skills/create-campaign-brief/references/draft-lifecycle.md +23 -0
  132. package/skills/create-campaign-brief/references/examples/MANIFEST.json +89 -0
  133. package/skills/create-campaign-brief/references/examples/briefs/clover.md +223 -0
  134. package/skills/create-campaign-brief/references/examples/briefs/galley.md +222 -0
  135. package/skills/create-campaign-brief/references/examples/briefs/gelee.md +220 -0
  136. package/skills/create-campaign-brief/references/examples/briefs/hey-digital.md +234 -0
  137. package/skills/create-campaign-brief/references/examples/briefs/persona.md +231 -0
  138. package/skills/create-campaign-brief/references/examples/briefs/revvix.md +220 -0
  139. package/skills/create-campaign-brief/references/examples/briefs/sellable-dev.md +220 -0
  140. package/skills/create-campaign-brief/references/examples/briefs/superposition.md +233 -0
  141. package/skills/create-campaign-brief/references/examples/briefs/superpower.md +219 -0
  142. package/skills/create-campaign-brief/references/examples/briefs/westpark-villas.md +220 -0
  143. package/skills/create-campaign-brief/references/icp-lock-question-bank.md +43 -0
  144. package/skills/create-campaign-brief/references/messaging-inputs.md +58 -0
  145. package/skills/create-campaign-brief/references/output-acceptance-rubric.md +62 -0
  146. package/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md +248 -0
  147. package/skills/create-campaign-brief/references/phase75-canonical-brief-template.md +319 -0
  148. package/skills/create-campaign-brief/references/phase75-good-brief-and-messaging-examples.md +445 -0
  149. package/skills/create-campaign-brief/references/quick-research-protocol.md +39 -0
  150. package/skills/create-campaign-brief/references/reference-sheet-protocol.md +60 -0
  151. package/skills/create-campaign-brief/references/zero-shot-iteration-rules.md +66 -0
  152. package/skills/create-campaign-v2/SKILL.md +1619 -0
  153. package/skills/create-campaign-v2/core/auto-execute.README.md +219 -0
  154. package/skills/create-campaign-v2/core/auto-execute.yaml +121 -0
  155. package/skills/create-campaign-v2/core/flow.v2.json +1643 -0
  156. package/skills/create-campaign-v2/core/policy.md +82 -0
  157. package/skills/create-campaign-v2/references/ai-tells.md +253 -0
  158. package/skills/create-campaign-v2/references/approval-gate-framing.md +346 -0
  159. package/skills/create-campaign-v2/references/draft-lifecycle.md +110 -0
  160. package/skills/create-campaign-v2/references/escalation-ladder.md +119 -0
  161. package/skills/create-campaign-v2/references/filter-leads.md +495 -0
  162. package/skills/create-campaign-v2/references/final-handoff-contract.md +176 -0
  163. package/skills/create-campaign-v2/references/gold-standard-message-examples.md +394 -0
  164. package/skills/create-campaign-v2/references/gold-standard-message-patterns.md +314 -0
  165. package/skills/create-campaign-v2/references/gold-standard-message-validation-example.md +212 -0
  166. package/skills/create-campaign-v2/references/lead-validation-preview.md +172 -0
  167. package/skills/create-campaign-v2/references/parallel-critique-protocol.md +368 -0
  168. package/skills/create-campaign-v2/references/sample-validation-loop.md +289 -0
  169. package/skills/create-campaign-v2/references/step-13-import-leads.md +151 -0
  170. package/skills/create-campaign-v2/references/step-15-re-cascade.md +90 -0
  171. package/skills/create-campaign-v2/references/thomas-revision-filters.md +521 -0
  172. package/skills/create-campaign-v2/references/thomas-variant-selection.md +202 -0
  173. package/skills/create-campaign-v2/references/tier-routing-matrix.md +66 -0
  174. package/skills/create-campaign-v2/references/validation-criteria.md +367 -0
  175. package/skills/create-campaign-v2/references/watch-link-handoff.md +106 -0
  176. package/skills/create-campaign-v2-validation/SKILL.md +296 -0
  177. package/skills/create-post/SKILL.md +1308 -0
  178. package/skills/create-rubric/SKILL.md +251 -0
  179. package/skills/engage/SKILL.md +549 -0
  180. package/skills/engage/core/README.md +23 -0
  181. package/skills/engage/core/proven-searches.json +11 -0
  182. package/skills/engage/core/style-guide.template.md +47 -0
  183. package/skills/engage/core/tracked-people.json +10 -0
  184. package/skills/enrich-prospects/SKILL.md +97 -0
  185. package/skills/find-leads/SKILL.md +467 -0
  186. package/skills/generate-messages/SKILL.md +2361 -0
  187. package/skills/interview/SKILL.md +132 -0
  188. package/skills/interview/core/ENGAGE_STYLE_GUIDE.template.md +54 -0
  189. package/skills/interview/core/ICP.template.md +54 -0
  190. package/skills/interview/core/VOICE_PROFILE.template.md +101 -0
  191. package/skills/providers/apollo.md +520 -0
  192. package/skills/providers/prospeo.md +398 -0
  193. package/skills/providers/sales-nav.md +372 -0
  194. package/skills/providers/signal-discovery.md +495 -0
  195. package/skills/research/SKILL.md +258 -0
  196. package/skills/research/config.json +9 -0
  197. package/skills/research/override.md +13 -0
  198. package/skills/research-prospect/SKILL.md +99 -0
  199. package/skills/research-sender/SKILL.md +158 -0
  200. package/skills/workflow-sequences/SKILL.md +85 -0
@@ -0,0 +1,234 @@
1
+ # Hey Digital Campaign Brief + Rubric Archive
2
+
3
+ Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
4
+
5
+ Campaigns captured: 4
6
+
7
+ ---
8
+
9
+ ## Predictable Paid Growth for B2B SaaS Leaders
10
+
11
+ - Sent: 1253
12
+ - Replied: 16
13
+ - Accepted: 285
14
+ - Updated: 2026-02-17T02:09:56.241Z
15
+
16
+ ### Campaign Brief
17
+
18
+ # Campaign: Predictable Paid Growth for B2B SaaS Leaders
19
+
20
+ ## Offer
21
+
22
+ 15-min call to walk through how we turned paid into a reliable growth channel for a similar B2B SaaS company — and what would apply to theirs.
23
+
24
+ ## Target Buyer
25
+
26
+ Primary: Head of Marketing / VP Marketing at B2B SaaS companies (20-150 employees, Series A-B or bootstrapped + growing). 1-10 person marketing team with no senior, dedicated performance marketing owner.
27
+
28
+ What they care about: Pipeline quality, revenue impact, looking competent to the CEO and sales, removing pressure and chaos.
29
+
30
+ ## Emotional Context (USE THIS TO WRITE BETTER HOOKS)
31
+
32
+ The person you're writing to is likely experiencing one or more of these:
33
+
34
+ - Pressure from leadership to grow faster — paid is being discussed as a lever
35
+ - Frustration with stalled performance or unclear results
36
+ - Fear of wasting budget or looking reckless
37
+ - Wants paid to stop being questioned every month
38
+ - Wants a clear line from ads to pipeline to revenue
39
+ - Wants to stop firefighting and guessing
40
+
41
+ What success looks like to them: Paid is no longer questioned. Clear line from ads to pipeline to revenue. Fewer internal debates, more confidence.
42
+
43
+ ## Scenario-Based Angles (MATCH TO PROSPECT'S SITUATION)
44
+
45
+ Do NOT default to one angle for every prospect. Figure out which scenario they're in and adapt.
46
+
47
+ | Scenario | Signals to Look For | Angle |
48
+ | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
49
+ | Not running paid (growth slowing, leadership pushing to try it) | No ad library presence, organic-only content, recent funding, hiring for marketing roles | "Your competitors are spending on paid. Here's how companies like yours launched it without wasting budget — and got leadership to trust it." |
50
+ | Using another agency (vanity metrics, poor results, agency doesn't understand SaaS) | Currently running ads but generic creative, mentions of agency on LinkedIn, job posts for marketing roles despite having an agency | "We hear this a lot — the agency sends traffic reports but nobody can tie it to pipeline. Here's what changed for [peer company]." |
51
+ | DIY paid (campaigns launched and left, no time to iterate, unclear attribution) | Small team running ads in-house, no dedicated paid person, sporadic ad activity | "Running ads without a dedicated person means campaigns get launched and left. Here's how [peer company] fixed that and made paid their most predictable channel." |
52
+
53
+ ## Messaging Rules
54
+
55
+ ### 5th Grade Language — No Jargon
56
+
57
+ Write at a 5th grade reading level. If a word wouldn't make sense to a 12-year-old, replace it.
58
+
59
+ **Banned terms and replacements:**
60
+
61
+ - "attribution" → "figuring out which campaigns actually work" or "tracking what's working"
62
+ - "PLG" / "product-led growth" → "self-serve funnel" or "self-serve signup"
63
+ - "CPA" → "ad costs"
64
+ - "self-direct" → "explore on their own"
65
+ - "ICP" → "target audience" or "ideal customer"
66
+ - "CAC" → "cost to get a customer"
67
+ - "growth engine" → avoid in outreach (sounds salesy). Use "reliable channel" or "predictable channel" instead.
68
+ - "vanity metrics" → don't use the term. Instead show the contrast: "traffic but no pipeline" or "clicks but no revenue"
69
+
70
+ Keep sentences short. One idea per sentence.
71
+ Use everyday words: "sorted out" not "untangled", "hard part" not "tricky part", "figure out" not "determine".
72
+
73
+ ### Message Pattern (CRITICAL)
74
+
75
+ 1. Hook about THEM (company news, post, trigger, or scenario signal — must be fresh and specific)
76
+ 2. Bridge to peer case studies — frame around how paid became predictable and trusted, not just raw numbers
77
+ 3. Why it's relevant to them specifically (connect the dots to their scenario)
78
+ 4. a/b CTA (see below)
79
+
80
+ ### Differentiators — Drop 1-2 Naturally Per Message
81
+
82
+ Pick the most relevant to the prospect. These should feel organic, not listed.
83
+
84
+ - "We only work with B2B SaaS companies — it's not a vertical, it's the whole company"
85
+ - "Your account is led by a senior strategist who's worked with 200+ SaaS companies, not a junior account manager"
86
+ - "Creative is in-house — strategy, copy, and design under one roof, so nothing gets lost in translation"
87
+ - "We've done this with 200+ SaaS companies, so the playbook is tested"
88
+
89
+ ### CTA Style — a/b Choice (CRITICAL)
90
+
91
+ End every message with two options formatted as a/b.
92
+
93
+ - Option a = a short call to walk through what worked for the peer companies and how it applies to them.
94
+ - Option b = send them the B2B Ads Arsenal — Hey Digital's free resource vault with ad templates, playbooks, creative angles, and case studies from 200+ SaaS companies.
95
+
96
+ Lowercase "two options:" — casual, not formal.
97
+ Keep each option to one line.
98
+ No "no pressure" or sign-offs after the options.
99
+
100
+ **Format:**
101
+
102
+ two options:
103
+
104
+ a) 15-min call — I walk through what worked for [peer company] and how it'd apply to [their company]
105
+
106
+ b) I send you our B2B Ads Arsenal — ad templates, playbooks, and case studies from 200+ SaaS companies so you can dig in yourself
107
+
108
+ ## Social Proof — Frame Around Efficiency + Confidence, Not Vanity
109
+
110
+ - Every message must include 2 credibility logos with results.
111
+ - Pick logos that are PEERS of the prospect's company.
112
+ - NEVER default to the same 2 logos for every message. Match them.
113
+ - Frame results through the lens of paid becoming predictable and trusted — not just raw percentage increases.
114
+ - Instead of "623% trial sign-up increase" → "SocialBee turned paid into their most reliable growth channel"
115
+ - Instead of just a number → connect it to what the prospect cares about: pipeline, revenue, leadership confidence
116
+ - Lead with the transformation story, support with the metric
117
+
118
+ ### Logo Matching Guide
119
+
120
+ Pick the row that best matches the prospect. Use case study logos (marked with \*) for proof. Name-drop 1-2 additional clients from "Also Worked With" to show depth.
121
+
122
+ | Prospect Type | Case Study Logos | Also Worked With |
123
+ | ----------------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
124
+ | Dev tools / API | *PostHog (18.5% cloud conversion) + *Stream (243% sign-up growth) | Webshare, Portainer, MetalBear, ScrapingBee, Cord, Spectro Cloud, Kilo Code |
125
+ | AI SaaS | *StealthGPT (287% paid subscriptions) + *Writesonic (350% revenue growth) | Rogo, Proton, Posh AI, meticulous, Entelligence AI, Toma, Rosie |
126
+ | Analytics / data | *Fathom (39.1% qualified trial increase) + *PostHog (18.5% cloud conversion) | ThoughtSpot, Keboola, Swarmia, \*Hotjar (94% decrease in YouTube ad costs) |
127
+ | Marketing / sales tools | *SocialBee (623% trial sign-ups) + *Wiza (88% sign-up increase) | Adjust, Instantly, Modash, AWeber, Voyado, Saleo, Wynter, TrueClicks |
128
+ | Productivity / PM | *Toggl (52% less ad spend, 159% closed-won deal increase) + *Pitch (56% sign-up increase) | Doist (Todoist), Gather |
129
+ | Security / compliance | DigiCert + Drata + Aikido Security | (name-drop only - no published metrics) |
130
+ | HR / people | WorkBuzz + WorkMotion + Sova | (name-drop only) |
131
+ | SMB / vertical SaaS | *DripJobs (483% trial increase) + *Pabau (27% demo booking increase) | Loftware, Coassemble, Deskpro, Helply, Fieldwire |
132
+ | Comms / messaging | \*Mailgun by Sinch (10% cost per sign-up decrease) | Respond.io, DialMyCalls, Sendify |
133
+ | General B2B SaaS | *Hotjar (94% YouTube ad cost decrease) + *Lokalise (250% trial conversion growth) | Voucherify, Keragon, Red Points, Classiq, Revv |
134
+ | Default fallback | *Hotjar + *Toggl (52% less ad spend) | Pick 1-2 from the prospect's closest category above |
135
+
136
+ ### Full Case Study Library
137
+
138
+ - Toggl (project management SaaS) — 52% reduction in ad spend, 41% drop in cost per org created, 159% increase in closed-won deal value, 100% close rate on qualified pipeline
139
+ - StealthGPT (AI SaaS) — 287% increase in paid subscriptions
140
+ - Hotjar (analytics/UX SaaS) — 94% decrease in YouTube ad costs
141
+ - Pitch (presentation SaaS) — 56% increase in sign-ups
142
+ - Writesonic (AI writing SaaS) — 350% growth in revenue
143
+ - DripJobs (field service SaaS) — 483% increase in trials
144
+ - Pabau (healthcare SaaS) — 27% increase in demo bookings
145
+ - Fathom (analytics SaaS) — 39.1% increase in qualified trial sign-ups
146
+ - PostHog (product analytics, dev tool) — 18.5% increase in cloud conversion
147
+ - Lokalise (localization SaaS) — 250% growth in trial conversions
148
+ - Stream (messaging/feeds API, dev tool) — 243% growth in sign-ups
149
+ - Wiza (sales prospecting SaaS) — 88% increase in sign-ups
150
+ - Cord (developer tools) — 56% increase in sign-ups on paid social
151
+ - Mailgun by Sinch (email API) — 10% decrease in cost per sign-up
152
+ - Pixelz (image editing SaaS) — 110% increase in MQLs on LinkedIn
153
+ - SocialBee (social media SaaS) — 623% increase in trial sign-ups
154
+ - CXL (marketing education) — 131% increase in purchases
155
+ - Document360 (knowledge base SaaS) — 59% decrease in cost per lead
156
+
157
+ ## Tone
158
+
159
+ - Peer-level, conversational, tentative (hedge words: "probably", "might", "usually")
160
+ - No evaluative language, no fake enthusiasm
161
+ - Human texture: use contractions, ellipsis, parenthetical asides
162
+ - Write like you're a peer who's seen this problem 200 times, not a salesperson
163
+
164
+ ## Examples — STYLE INSPIRATION ONLY
165
+
166
+ WARNING: These examples show the QUALITY and VOICE to aim for. Do NOT copy their structure, angle, logos, or CTA as a template. Every message must be built from scratch based on the prospect's actual scenario, company, and situation.
167
+
168
+ ### Example 1: Scenario — Not running paid yet (leadership pushing to try it)
169
+
170
+ Hey Sarah,
171
+
172
+ Saw Acme just closed their Series B... usually that's when the board starts asking about paid channels.
173
+
174
+ We helped PostHog through that exact moment — they had a huge free user base but needed to figure out if paid could actually drive cloud conversions without burning budget. Ended up increasing cloud conversions 18.5%.
175
+
176
+ The thing that made it work was having a clear system from day one... not just launching ads and hoping.
177
+
178
+ two options:
179
+
180
+ a) 15-min call — I walk through how PostHog set it up and what would apply to Acme
181
+
182
+ b) I send you our B2B Ads Arsenal — ad templates, playbooks, and case studies from 200+ SaaS companies so you can dig in yourself
183
+
184
+ ### Example 2: Scenario — Using another agency (not getting results)
185
+
186
+ Hey Mike,
187
+
188
+ Noticed Beacon's been running paid for a while but the creative looks pretty generic for a dev tools company... usually means the agency doesn't really get SaaS buying cycles.
189
+
190
+ We only work with B2B SaaS — it's the whole company, not a vertical. When Stream came to us from a similar situation, they grew sign-ups 243% because we rebuilt the strategy around how devs actually evaluate tools.
191
+
192
+ two options:
193
+
194
+ a) 15-min call — I walk through what changed for Stream and how it'd apply to Beacon
195
+
196
+ b) I send you our B2B Ads Arsenal — ad templates, playbooks, and case studies from 200+ SaaS companies so you can dig in yourself
197
+
198
+ ### Rubric Markdown
199
+
200
+ (none stored)
201
+
202
+ ### Structured Lead Scoring Rubrics
203
+
204
+ #### senior_marketing_leader
205
+
206
+ - Required: true
207
+ - Use for scoring: true
208
+ - Allow partial credit: false
209
+ - Strict matching: false
210
+ - Description: Ensures the prospect has marketing leadership authority.
211
+ - Reason: The offer is for a 15-minute strategy call, which requires someone with budget and strategic oversight.
212
+ - Criterion: The prospect's title indicates they own or influence the paid marketing budget. Target titles: Head of Marketing, VP Marketing, CMO, Director of Marketing, Director of Demand Gen, Director of Growth, Head of Growth, Marketing Manager (at companies under 50 people). Exclude: Product Marketing, Content Marketing, Field Marketing, Customer Marketing, Marketing Ops, Partnerships, Sales.
213
+
214
+ #### tier_1_geography
215
+
216
+ - Required: true
217
+ - Use for scoring: true
218
+ - Allow partial credit: false
219
+ - Strict matching: false
220
+ - Description: Ensures the prospect is in a Tier 1 market.
221
+ - Reason: The sample contains leads from Pakistan, India, and Nigeria; these regions often have different ad cost structures and buying cycles than the campaign's core case studies.
222
+ - Criterion: YES if the prospect is located in a Tier 1 region: USA, Canada, UK, Ireland, Australia, New Zealand, or Western Europe. NO if located in regions like India, Pakistan, Nigeria, or South America.
223
+
224
+ #### not_fractional_role
225
+
226
+ - Required: true
227
+ - Use for scoring: true
228
+ - Allow partial credit: true
229
+ - Strict matching: false
230
+ - Description: Filters out temporary or part-time marketing leaders.
231
+ - Reason: Fractional leaders often lack the long-term budget authority or internal team stability required for this type of agency partnership.
232
+ - Criterion: YES if the prospect is a full-time employee. NO if the title includes 'Fractional', 'Interim', 'Consultant', or 'Advisor'.
233
+
234
+ #### b2b_saas_company
@@ -0,0 +1,231 @@
1
+ # Persona Campaign Brief + Rubric Archive
2
+
3
+ Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
4
+
5
+ Campaigns captured: 3
6
+
7
+ ---
8
+
9
+ ## V2 - Content Roadmap for B2B SaaS/Tech Founders
10
+
11
+ - Sent: 418
12
+ - Replied: 11
13
+ - Accepted: 89
14
+ - Updated: 2026-03-09T19:02:26.067Z
15
+
16
+ ### Campaign Brief
17
+
18
+ # Content Roadmap for B2B SaaS/Tech Founders
19
+
20
+ ## Campaign Objective
21
+
22
+ Launch campaign to **founders, CEOs, and senior leaders** who work at **B2B SaaS and tech companies** and offer them **a 15-minute content roadmap call showing how LinkedIn ghostwriting can generate ICP-aligned pipeline**.
23
+
24
+ ## Ideal Customer Profile (ICP)
25
+
26
+ - **Company type:** B2B SaaS, tech startups, growth-stage companies
27
+ - **Role & seniority:** Founders, CEOs, CTOs, CMOs, VPs, Directors — senior leadership
28
+ - **Company size:** 10-500 employees
29
+ - **Geography:** Global (English-speaking focus)
30
+
31
+ ## Meeting Value (Offer)
32
+
33
+ In a 15-minute call, I'll show you a content roadmap for your company on LinkedIn — what I'd post, how I'd position you, and how to ensure the people engaging are your actual buyers, not random connections.
34
+
35
+ Alternative CTA: Share a page showing how this works in practice with real founder results.
36
+
37
+ ## Social Proof
38
+
39
+ **Primary Proof:**
40
+
41
+ - 11 clients generated over 350 million impressions in the past 12 months
42
+ - 85%+ of engagement is ICP-aligned (actual buyers, not random people)
43
+ - One founder hit 30 million impressions in a year
44
+ - Another went from 0 to 60k followers in 12 months — both 85%+ ICP aligned
45
+
46
+ ## Messaging Guidelines
47
+
48
+ - **Lead with:** Signal reference (saw them engaging with relevant posts on LinkedIn)
49
+ - **Bridge to:** How LinkedIn ghostwriting can take content completely off their plate while ensuring ICP-aligned engagement
50
+ - **Avoid:** Generic phrases like "best-in-class", "industry-leading", "cutting-edge"
51
+ - **Voice:** Casual, lowercase, conversational. No hard sells.
52
+
53
+ ### CRITICAL: Industry Personalization Rules
54
+
55
+ Personalize by **role/seniority**. Keep industry references **broad and general**. Never reference the prospect's specific vertical or niche.
56
+
57
+ #### Bad vs Better Examples (from real messages in this campaign):
58
+
59
+ **Lead: Peadar Coyle — Founder, AudioStack (Generative AI Audio)**
60
+
61
+ - BAD: "founders in the **generative ai space** i ghostwrite for generated over 350 million impressions"
62
+ - BETTER: "founders in **tech** i ghostwrite for generated over 350 million impressions"
63
+
64
+ **Lead: Will Savage — Field CTO, Omni (BI & Data)**
65
+
66
+ - BAD: "ctos and leaders in the **bi and data space** i ghostwrite for generated over 350 million impressions"
67
+ - BETTER: "**CTOs and technical leaders** i ghostwrite for generated over 350 million impressions"
68
+
69
+ **Lead: Jennifer Phan — Co-founder & CEO, Passionfroot (Creator Economy)**
70
+
71
+ - BAD: "founders in the **creator economy space** i ghostwrite for generated over 350 million impressions"
72
+ - BETTER: "founders in **tech** i ghostwrite for generated over 350 million impressions"
73
+
74
+ **Lead: Himanshu Agarwal — Founder's Office, Tilt (Fintech)**
75
+
76
+ - BAD: "founders in the **fintech space** i ghostwrite for generated over 350 million impressions"
77
+ - BETTER: "founders in **tech** i ghostwrite for generated over 350 million impressions"
78
+
79
+ **Lead: Karen Church — VP Research & Data Science, Intercom**
80
+
81
+ - BAD: "VPs in the **data science and analytics space** i ghostwrite for"
82
+ - BETTER: "**VPs and senior leaders** in B2B SaaS i ghostwrite for"
83
+
84
+ #### Allowed industry terms (use ONLY these):
85
+
86
+ - "tech"
87
+ - "B2B SaaS"
88
+ - "SaaS"
89
+ - "specialized niches"
90
+
91
+ #### Allowed role/seniority personalization (DO use these):
92
+
93
+ - "founders in tech"
94
+ - "CTOs and technical founders"
95
+ - "CMOs in B2B SaaS"
96
+ - "VPs and senior leaders"
97
+ - "leaders in the SaaS space"
98
+
99
+ #### NEVER use specific verticals like:
100
+
101
+ - generative AI, creator economy, fintech, healthtech, edtech, martech, adtech, cybersecurity, BI and data, HR tech, proptech, legaltech, etc.
102
+
103
+ ## Message Variants
104
+
105
+ **Variant A (Signal + Personalized + Two Options):**
106
+
107
+ - Open with signal reference (post engagement)
108
+ - Personalize by role/seniority (keep industry BROAD per rules above)
109
+ - Include social proof (350M impressions, 85%+ ICP aligned)
110
+ - Close with two options: a) 15 min call for content roadmap, b) share results page
111
+
112
+ **Variant B (Signal + Generic + Page Offer):**
113
+
114
+ - Open with signal reference
115
+ - Use generic positioning: "premium ghostwriter and content strategist for B2B SaaS and Tech founders"
116
+ - Include social proof
117
+ - Close with offer to share a page showing how it works in practice
118
+
119
+ ---
120
+
121
+ ## Message Templates
122
+
123
+ ### Variant A — Signal-Led + Two Options CTA
124
+
125
+ **Subject:** linkedin for {{company}}
126
+
127
+ hey {{first_name}},
128
+
129
+ not sure if this is relevant but i saw you engaging with some posts about {{example mentioning the post we know they engaged with; founder-led thought leadership}} on linkedin and thought i'd send you a note.
130
+
131
+ for context, {{general mention of seniority title, example; founders in other specialized niches, founders, cmos, csuite etc}} i ghostwrite for generated over 350 million impressions in the past 12 months.
132
+
133
+ but what actually matters is that 85%+ of the engagement is ICP aligned. if there isn't ICP alignment, none of the virality or engagement matters.
134
+
135
+ two options:
136
+
137
+ a) in a 15 min call, i can show you a content roadmap and what i'd do for {{company}} and you tell me if it's interesting
138
+ b) i can share a page showing how one founder hit 30 million impressions in a year and another went from 0 to 60k followers in 12 months... both 85%+ ICP aligned
139
+
140
+ ### Variant B — Pattern Interrupt + Low-Friction CTA
141
+
142
+ **Subject:** linkedin for {{company}}
143
+
144
+ hey {{first_name}},
145
+
146
+ i keep seeing your name pop up in founder-led thought leadership conversations on linkedin so I figured i'd reach out.
147
+
148
+ i'm a premium ghostwriter and content strategist for B2B SaaS and Tech founders on LinkedIn. In the last 12 months, 11 clients generated over 350 million impressions.
149
+
150
+ the whole model is i take Linkedin completely off your plate and ensure the people engaging with your content end up being your actual buyers, not random people.
151
+
152
+ happy to send over a page showing what this looks like in practice if you're curious.
153
+
154
+ Ps. one founder hit 30 million impressions in a year and another went from 0 to 60k followers in 12 months. just figured this might be useful so let me know.
155
+
156
+ ---
157
+
158
+ ## Do NOT Target
159
+
160
+ - Other ghostwriters or content agencies
161
+ - People already working with Julian
162
+ - Non-English speakers
163
+
164
+ ## Additional Notes
165
+
166
+ - Julian is a premium LinkedIn ghostwriter and content strategist
167
+ - The core model: take LinkedIn completely off the founder's plate and ensure ICP-aligned engagement
168
+ - All social proof is real and verified — do not embellish or modify the numbers
169
+
170
+ ### Rubric Markdown
171
+
172
+ (none stored)
173
+
174
+ ### Structured Lead Scoring Rubrics
175
+
176
+ #### executive_level_title
177
+
178
+ - Required: true
179
+ - Use for scoring: true
180
+ - Allow partial credit: true
181
+ - Strict matching: false
182
+ - Description: Prospect holds CEO, Founder, Co-Founder, or C-level executive title
183
+ - Reason: Campaign targets decision-makers at the founder/C-suite level who control content strategy budgets
184
+ - Criterion: YES if the prospect's current title is CEO, Founder, Co-Founder, or a C-level executive (CMO, CTO, COO, CFO, CPO, etc.). NO if they are an employee (e.g., Manager, Director, VP) or in a non-executive role.
185
+
186
+ #### b2b_saas_tech_company
187
+
188
+ - Required: true
189
+ - Use for scoring: true
190
+ - Allow partial credit: true
191
+ - Strict matching: false
192
+ - Description: Company operates in B2B SaaS, AI, Data, or RevOps technology
193
+ - Reason: Campaign specifically targets B2B SaaS and Tech companies where founder-led content drives ICP-aligned engagement
194
+ - Criterion: YES if the company is B2B SaaS, AI, Data, or RevOps technology. This includes startups and established firms. NO for B2C, traditional retail, or non-tech professional services.
195
+
196
+ #### tier_1_geography
197
+
198
+ - Required: true
199
+ - Use for scoring: true
200
+ - Allow partial credit: false
201
+ - Strict matching: true
202
+ - Description: Prospect located in US, Canada, or UK only
203
+ - Reason: Campaign focuses on Tier 1 English-speaking markets where LinkedIn engagement drives pipeline
204
+ - Criterion: YES if the prospect and/or company's current location is in the United States, Canada, or United Kingdom, Ireland, or Australia. NO if located in Indonesia, Italy, India, or any other country outside these three target countries.
205
+
206
+ #### not_marketing_competitor
207
+
208
+ - Required: true
209
+ - Use for scoring: true
210
+ - Allow partial credit: false
211
+ - Strict matching: true
212
+ - Description: Prospect is not a marketing services competitor (ghostwriting, LinkedIn coaching, agency)
213
+ - Reason: Excludes direct competitors while keeping SaaS/Tech founders who are active on LinkedIn
214
+ - Criterion: NO only if the prospect's PRIMARY business is marketing services (LinkedIn coaching, ghostwriting, agency). YES if they are a SaaS/Tech founder who is active on LinkedIn or sharing insights (like Craig Hubbard), as these are ideal targets, not competitors.
215
+
216
+ #### not_tommy_clark
217
+
218
+ - Required: true
219
+ - Use for scoring: true
220
+ - Allow partial credit: false
221
+ - Strict matching: true
222
+ - Description: Prospect is not Tommy Clark or associated with Tommy Clark companies
223
+ - Reason: Excludes specific individual/company from campaign targeting
224
+ - Criterion: NO if the prospect's name is Tommy Clark or works at a company owned/founded by Tommy Clark. YES for all other prospects.
225
+
226
+ ---
227
+
228
+ ## Signal Discovery — Content Strategy Post Engagers
229
+
230
+ - Sent: 103
231
+ - Replied: 6
@@ -0,0 +1,220 @@
1
+ # Revvix Campaign Brief + Rubric Archive
2
+
3
+ Source: [75-ALL-CLIENT-CAMPAIGN-CORPUS.json](/Users/christianreyes/dev/dittto-fresh/web/.planning/phases/75-canonical-campaign-brief-and-copy-calibration/75-ALL-CLIENT-CAMPAIGN-CORPUS.json)
4
+
5
+ Campaigns captured: 8
6
+
7
+ ---
8
+
9
+ ## RSAC 2026 Speaker Outreach - Michelle/Daniel V2
10
+
11
+ - Sent: 73
12
+ - Replied: 3
13
+ - Accepted: 18
14
+ - Updated: 2026-03-12T18:19:22.888Z
15
+
16
+ ### Campaign Brief
17
+
18
+ # RSAC 2026 Speaker Outreach for Security Leaders
19
+
20
+ ## Campaign Objective
21
+
22
+ Launch campaign to **security leaders and practitioners attending RSAC 2026** who work at **companies dealing with CVE prioritization and vulnerability noise** and offer them **a live demo or coffee chat at the Spektion booth (ESE #7) showing runtime-based exploitability analysis**.
23
+
24
+ ## Ideal Customer Profile (ICP)
25
+
26
+ - **Company type:** Companies attending RSAC 2026 with security, AppSec, vulnerability management, or SOC teams
27
+ - **Role & seniority:** Security leaders and practitioners, AppSec / vulnerability management / SOC decision-makers
28
+ - **Company size:** Any size dealing with CVE prioritization challenges
29
+ - **Geography:** Attending RSAC 2026
30
+
31
+ ## Meeting Value (Offer)
32
+
33
+ Live demo or coffee chat at the Spektion booth (ESE #7) during RSAC. We'll show runtime-based exploitability analysis vs traditional scanning. Low-pressure: "happy to grab a coffee or just say hi."
34
+
35
+ ## Social Proof
36
+
37
+ Winner: Software Supply Chain Security. Enterprise customers across all industries are choosing Spektion to transform their vulnerability management programs and take control of their software risk.
38
+
39
+ ## Messaging Templates
40
+
41
+ **Subject: RSAC next week**
42
+
43
+ Hey {{first_name}},
44
+
45
+ So I noticed you'll be at RSAC and wanted to reach out before the week gets crazy.
46
+
47
+ Most {{team_type}} we chat with are sending thousands of "critical" CVEs to IT, and it's getting harder to prioritize the ones that matter most.
48
+
49
+ We show what's actually exploitable on your endpoints based on runtime activity, including AI tools that scanners might miss.
50
+
51
+ We'll be at the Spektion booth ESE #7 all week, happy to grab a coffee or just say hi.
52
+
53
+ Let me know if this sounds interesting.
54
+
55
+ ### Interpolation Guidelines
56
+
57
+ - {{first_name}} — prospect's first name, 1 word
58
+ - {{team_type}} — from prospect's role/title, 2-4 words (e.g., "security teams", "AppSec teams", "vulnerability management teams", "SOC teams")
59
+
60
+ ### Template DOs
61
+
62
+ - Use the prospect's actual team type based on their LinkedIn title for {{team_type}}
63
+ - Keep all text lowercase and casual to match the peer-to-peer tone
64
+ - Reference the specific booth location (ESE #7) exactly as written
65
+ - Keep the event urgency ("next week", "before the week gets crazy")
66
+
67
+ ### Template DON'Ts
68
+
69
+ - Don't capitalize the greeting or body text
70
+ - Don't add sign-offs (Best, Thanks, etc.) or signatures
71
+ - Don't add extra sentences or rephrase — only fill in placeholders
72
+ - Don't make it salesy — keep the low-pressure, event-based warmth
73
+
74
+ ### Examples
75
+
76
+ **Example 1 (Security Director):**
77
+
78
+ Subject: RSAC next week
79
+
80
+ Hey Sarah,
81
+
82
+ So I noticed you'll be at RSAC and wanted to reach out before the week gets crazy.
83
+
84
+ Most security teams we chat with are sending thousands of "critical" CVEs to IT, and it's getting harder to prioritize the ones that matter most.
85
+
86
+ We show what's actually exploitable on your endpoints based on runtime activity, including AI tools that scanners might miss.
87
+
88
+ We'll be at the Spektion booth ESE #7 all week, happy to grab a coffee or just say hi.
89
+
90
+ Let me know if this sounds interesting.
91
+
92
+ **Example 2 (VP of AppSec):**
93
+
94
+ Subject: RSAC next week
95
+
96
+ Hey Marcus,
97
+
98
+ So I noticed you'll be at RSAC and wanted to reach out before the week gets crazy.
99
+
100
+ Most AppSec teams we chat with are sending thousands of "critical" CVEs to IT, and it's getting harder to prioritize the ones that matter most.
101
+
102
+ We show what's actually exploitable on your endpoints based on runtime activity, including AI tools that scanners might miss.
103
+
104
+ We'll be at the Spektion booth ESE #7 all week, happy to grab a coffee or just say hi.
105
+
106
+ Let me know if this sounds interesting.
107
+
108
+ **Example 3 (SOC Manager):**
109
+
110
+ Subject: RSAC next week
111
+
112
+ Hey Jennifer,
113
+
114
+ So I noticed you'll be at RSAC and wanted to reach out before the week gets crazy.
115
+
116
+ Most SOC teams we chat with are sending thousands of "critical" CVEs to IT, and it's getting harder to prioritize the ones that matter most.
117
+
118
+ We show what's actually exploitable on your endpoints based on runtime activity, including AI tools that scanners might miss.
119
+
120
+ We'll be at the Spektion booth ESE #7 all week, happy to grab a coffee or just say hi.
121
+
122
+ Let me know if this sounds interesting.
123
+
124
+ ### Rubric Markdown
125
+
126
+ (none stored)
127
+
128
+ ### Structured Lead Scoring Rubrics
129
+
130
+ (none stored)
131
+
132
+ ---
133
+
134
+ ## RSAC 2026 Speaker Outreach - Michelle Variant (Updated)
135
+
136
+ - Sent: 137
137
+ - Replied: 2
138
+ - Accepted: 36
139
+ - Updated: 2026-03-06T21:28:51.007Z
140
+
141
+ ### Campaign Brief
142
+
143
+ # RSAC 2026 Speaker Outreach - Michelle Variant
144
+
145
+ ## Campaign Overview
146
+
147
+ - **Sender:** Michelle
148
+ - **Event:** RSAC 2026
149
+ - **Company:** Spektion
150
+ - **Booth:** ESE #7
151
+
152
+ ## Messaging Template
153
+
154
+ **Subject:** RSAC next week
155
+
156
+ Hey {{first_name}},
157
+
158
+ So I noticed you'll be at RSAC and wanted to reach out before the week gets crazy.
159
+
160
+ Most {{team_type}} we chat with are sending thousands of "critical" CVEs to IT, and it's getting harder to prioritize the ones that matter most.
161
+
162
+ We show what's actually exploitable on your endpoints based on runtime activity, including AI tools that scanners might miss.
163
+
164
+ We'll be at the Spektion booth ESE #7 all week, happy to grab a coffee or just say hi.
165
+
166
+ Let me know if this sounds interesting.
167
+
168
+ ## Variable Examples
169
+
170
+ | Variable | Examples |
171
+ | --------------- | ----------------------------------------------------------------------- |
172
+ | `{{team_type}}` | security teams, AppSec teams, vulnerability management teams, SOC teams |
173
+
174
+ ## Target Audience
175
+
176
+ - Security leaders and practitioners attending RSAC 2026
177
+ - Teams dealing with CVE prioritization and vulnerability noise
178
+ - AppSec / vulnerability management / SOC decision-makers
179
+
180
+ ## Pain Points
181
+
182
+ - Drowning in thousands of "critical" CVEs with no way to prioritize
183
+ - Sending too many alerts to IT that don't actually matter
184
+ - Scanners missing AI tools and runtime-specific risks
185
+ - Lack of visibility into what's actually exploitable on endpoints
186
+
187
+ ## Offer
188
+
189
+ - Live demo or coffee chat at the Spektion booth (ESE #7) during RSAC
190
+ - Show runtime-based exploitability analysis vs traditional scanning
191
+ - Low-pressure: "happy to grab a coffee or just say hi"
192
+
193
+ ## Tone
194
+
195
+ - Casual, peer-to-peer
196
+ - No hard sell — event-based warmth
197
+ - Short and scannable
198
+
199
+ ### Rubric Markdown
200
+
201
+ (none stored)
202
+
203
+ ### Structured Lead Scoring Rubrics
204
+
205
+ #### not_direct_competitor
206
+
207
+ - Required: false
208
+ - Use for scoring: true
209
+ - Allow partial credit: false
210
+ - Strict matching: true
211
+ - Description: Prospect does not work at top 5 direct competitors
212
+ - Reason: Direct competitors won't buy Spektion; other security vendors are potential partners and have relevant security teams
213
+ - Criterion: YES if company is NOT one of these five direct competitors: Tenable, Rapid7, CrowdStrike, Qualys, Wiz. NO if company is one of these five. All other security vendors (CyberArk, SentinelOne, Palo Alto, Zscaler, etc.) should score YES - they're potential partners or connectors.
214
+
215
+ #### security_related_title
216
+
217
+ - Required: false
218
+ - Use for scoring: true
219
+ - Allow partial credit: true
220
+ - Strict matching: false