@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,222 @@
1
+ # Galley 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: 5
6
+
7
+ ---
8
+
9
+ ## Catersource 2026: AI BEO Launch
10
+
11
+ - Sent: 911
12
+ - Replied: 11
13
+ - Accepted: 187
14
+ - Updated: 2026-02-26T20:37:39.666Z
15
+
16
+ ### Campaign Brief
17
+
18
+ # Catersource 2026: AI BEO Launch
19
+
20
+ ## Campaign Angle
21
+
22
+ Free Catersource attendance pass as the hook, pivots to the BEO demo at booth 1517 as the reason to show up. Straightforward value exchange -- clear offer, low friction, time-bound urgency built in.
23
+
24
+ ## Target
25
+
26
+ Catering company owners, executive chefs, directors of operations, and event managers at mid-market catering companies who still process BEOs manually.
27
+
28
+ ## Pain
29
+
30
+ Teams spend hours rebuilding every event order by hand. BEOs arrive as messy PDFs and get treated as static documents instead of actionable production plans.
31
+
32
+ ## Offer
33
+
34
+ Live demo at Catersource booth 1517 (March 3-5, LA). AI that reads messy BEOs and turns them into production-ready plans in minutes -- recipes, purchasing, prep, nutrition, all mapped automatically. Bring a BEO, we'll run it through right there.
35
+
36
+ ## Hook
37
+
38
+ Free Catersource attendance pass (code: PARTNER2026).
39
+
40
+ ## Proof
41
+
42
+ Not provided -- live demo is the proof mechanism.
43
+
44
+ ## Sender
45
+
46
+ Ian Christopher, Josh Branham, and Jonathan Press (Galley Solutions)
47
+
48
+ ---
49
+
50
+ ## Message Variants
51
+
52
+ ### Variant 1 - Workshopped Final (preferred)
53
+
54
+ **Subject:** catersource booth 1517
55
+
56
+ Hey {{first_name}},
57
+
58
+ not sure if catersource is on your radar next week, but we're at a booth and I've got some free attendance passes if you want one (code: PARTNER2026).
59
+
60
+ Wanted to reach out though as we just built an AI that reads the messiest BEOs and turns them into production-ready plans in minutes. recipes, purchasing, prep, nutrition, all mapped automatically.
61
+
62
+ The part where your team spends hours rebuilding every event order by hand, that's what this replaces.. And a bit more
63
+
64
+ We're doing live demos at the booth. With the free pass you can join the conference and bring a BEO, we'll run it through right there.
65
+
66
+ So if you're around LA march 3-5, would love to have you stop by. first-look slots are filling up though so lmk if you want me to hold one.
67
+
68
+ ### Variant 2 - Adapted from Ian's original brief messaging
69
+
70
+ **Subject:** free catersource pass + something worth seeing
71
+
72
+ Hey {{first_name}},
73
+
74
+ so we managed to get a handful of free attendance passes for catersource next week in LA. happy to send one your way if you're interested (code: PARTNER2026).
75
+
76
+ The reason we're going is we're showing off a new AI tool specifically for caterers.
77
+
78
+ it ingests BEOs, the messy PDF kind, and auto-builds your purchasing, production, and prep plans from them. not a concept. it actually works and we're demoing it live at booth 1517.
79
+
80
+ If you're still rebuilding event orders by hand or treating BEOs like static PDFs, this is probably the booth to hit.
81
+
82
+ March 3-5, LA. let me know if you want a demo slot held.
83
+
84
+ ### Variant 3 - Shorter / more casual
85
+
86
+ **Subject:** booth 1517
87
+
88
+ Hey {{first_name}},
89
+
90
+ not sure if you're making it to catersource next week but I've got a free pass if it helps (PARTNER2026).
91
+
92
+ We're at booth 1517 showing something new... an AI that takes a PDF BEO and turns it into a full production plan. purchasing, prep, nutrition, the whole thing. in minutes, not hours.
93
+
94
+ Bring one of yours. we'll run it live.
95
+
96
+ March 3-5 in LA. lmk if you want me to save you a demo slot.
97
+
98
+ ### Rubric Markdown
99
+
100
+ (none stored)
101
+
102
+ ### Structured Lead Scoring Rubrics
103
+
104
+ #### current_employment
105
+
106
+ - Required: true
107
+ - Use for scoring: true
108
+ - Allow partial credit: false
109
+ - Strict matching: false
110
+ - Description: Verifies the prospect is still at the target company.
111
+ - Reason: Outreach to former employees is ineffective and can damage brand reputation.
112
+ - Criterion: YES if the prospect is currently employed at the company listed in the campaign data. NO if they have left the company or the role is listed as 'Past'.
113
+
114
+ #### catering_hospitality_business
115
+
116
+ - Required: true
117
+ - Use for scoring: true
118
+ - Allow partial credit: true
119
+ - Strict matching: false
120
+ - Description: Ensures the company is an actual operator rather than a vendor.
121
+ - Reason: Galley Assist AI is designed for operators managing complex menus, not for suppliers or vendors.
122
+ - Criterion: YES if the company is a catering company, restaurant with catering, hospitality venue with banquets, or food service operator. NO if the company is a food distributor, equipment vendor, supplier, or staffing/marketing agency.
123
+
124
+ #### west_coast_usa_location
125
+
126
+ - Required: true
127
+ - Use for scoring: true
128
+ - Allow partial credit: false
129
+ - Strict matching: false
130
+ - Description: Ensures both the company and prospect are based on the West Coast, with a primary focus on California and LA proximity.
131
+ - Reason: Attendance at a physical event in LA requires both the organization and the individual to be regionally based to justify the travel/time.
132
+ - Criterion: YES if BOTH the company and the individual are located in California, Oregon, Washington, Arizona, or Nevada. Special priority is given to those in California or within driving distance of Los Angeles. NO if either the company or individual is located outside these states, or if the location is listed only as 'United States' without state-level detail.
133
+
134
+ #### culinary_ops_leadership_role
135
+
136
+ - Required: true
137
+ - Use for scoring: true
138
+ - Allow partial credit: true
139
+ - Strict matching: false
140
+ - Description: Filters for culinary and operations decision-makers while excluding sales/support roles.
141
+ - Reason: The campaign targets those managing BEOs and food operations, not sales or administrative staff.
142
+ - Criterion: YES if the title is in Culinary, Food Service Operations, or Executive Leadership (e.g., Executive Chef, Culinary Director, Director of F&B, VP Operations, COO, CFO, Director of Nutrition). NO if the title is in Sales, Marketing, HR, Recruiting, or is a Coordinator/Assistant/Board Member.
143
+
144
+ culinary sales manager, and cooking or culinary coordinator type roles are permitted
145
+
146
+ ---
147
+
148
+ ## Menu-to-Operations Tool for Multi-Site Foodservice
149
+
150
+ - Sent: 634
151
+ - Replied: 7
152
+ - Accepted: 253
153
+ - Updated: 2026-03-09T20:51:47.135Z
154
+
155
+ ### Campaign Brief
156
+
157
+ # Live Menu Demo for Directors of Dining Services
158
+
159
+ _Try your actual menu converted to full operational plans in 15 minutes_
160
+
161
+ ## Campaign Objective
162
+
163
+ Launch campaign to **Directors and VPs of Dining Services, Culinary Operations, and Food Service Operations** who work at **contract foodservice providers, university dining programs, and corporate campus food operations with 20+ locations** and offer them **a live demo converting one of their actual menus into full operational plans with recipes, purchasing, and stations - no manual rebuild required**.
164
+
165
+ ## Ideal Customer Profile (ICP)
166
+
167
+ **Primary Tier:**
168
+
169
+ - **Titles:** Director of Dining Services, VP of Dining Services, Director of Culinary Operations, VP of Culinary Operations, Director of Food Service Operations, VP of Food Service Operations
170
+ - **Company type:** Contract foodservice providers, university dining programs, corporate campus food operations
171
+ - **Company size:** 20+ locations
172
+ - **Use case:** Managing multi-week rotating menu cycles
173
+ - **Geography:** United States only
174
+
175
+ **Secondary Tier:**
176
+
177
+ - **Titles:** Culinary Director, Executive Chef, Food Service Operations Manager
178
+ - **Same company profile as primary tier**
179
+
180
+ **Anti-ICP (Exclude):**
181
+
182
+ - SMB restaurants without catering or contract dining operations
183
+ - Static menu operations (same items year-round)
184
+ - Front-of-house roles
185
+ - Line cooks or entry-level culinary
186
+ - Companies in Galley's active pipeline (DNC list provided weekly via Slack)
187
+
188
+ ## Meeting Value (Offer)
189
+
190
+ In a 15-minute live session, we'll take one of your actual menus (PDF, catering export, spreadsheet, or text) and convert it into a full operational plan with recipes, purchasing, and stations connected - no manual rebuild required. You'll see exactly how it works with your real data.
191
+
192
+ Alternative: If timing doesn't work, we'll send you a video walkthrough showing the conversion process.
193
+
194
+ **Limited-time incentive:** 10% off for contract foodservice providers through end of March 2026.
195
+
196
+ ## Social Proof
197
+
198
+ Works with GoToFoods and some of the largest franchise groups. Recipes and menus created together, not stitched after the fact. Full preview and approval before anything touches the live system. Regional dining group (12 locations) identified $340K in annual margin leakage. 22-unit fast-casual group reduced menu rollout from 3 weeks to 2 days.
199
+
200
+ ---
201
+
202
+ ## Approved Copy Variants
203
+
204
+ **VARIANT A - "Send Us Your Messiest Menu"**
205
+
206
+ Target: VP / Director of Dining Services, Director of Culinary Operations
207
+
208
+ Angle: Product sells itself. Let them see it work on their own data.
209
+
210
+ Subject: menu planning
211
+
212
+ hey {{first_name}},
213
+
214
+ not sure if this is useful but we've been doing this thing where someone sends us their craziest menu cycle and we build it into an operational plan in about 15 minutes. live, on a call.
215
+
216
+ we built a tool that takes menus from whatever format they're in... PDFs, catering exports, spreadsheets, even text... and turns them into the whole plan. recipes, purchasing, stations. no one rebuilds anything by hand.
217
+
218
+ mostly for {{company_team_type}} running multi-week rotations across a bunch of locations where every cycle change meant hours of manual work that didn't need to exist.
219
+
220
+ if you want to try it with one of your real rotations, happy to set that up. OR I can send a quick video if that's easier.
221
+
222
+ p.s. we're doing 10% off for contract foodservice through end of march.
@@ -0,0 +1,220 @@
1
+ # Gelee 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: 1
6
+
7
+ ---
8
+
9
+ ## LinkedIn Agent for Exited Founders - Q1 2026
10
+
11
+ - Sent: 410
12
+ - Replied: 9
13
+ - Accepted: 96
14
+ - Updated: 2026-03-19T17:31:05.728Z
15
+
16
+ ### Campaign Brief
17
+
18
+ # LinkedIn Agent for Exited Founders - Q1 2026
19
+
20
+ ## Campaign Objective
21
+
22
+ Launch campaign to **exited founders (and active CEOs/CTOs/Founders)** who work at **post-exit ventures or new companies in the US and Canada** and offer them **a fully managed LinkedIn system (AI + human review) that generates pipeline and books calls on autopilot**.
23
+
24
+ ## Ideal Customer Profile (ICP)
25
+
26
+ - **Company type:** Post-exit ventures, new companies founded by serial entrepreneurs, YC / Techstars / Sequoia-backed alumni
27
+ - **Role & seniority:** CEO, CTO, Founder — exited founders strongly preferred ($10M+ exit ideal)
28
+ - **Experience:** 4+ years industry experience
29
+ - **Company size:** Early-stage to growth (founder still central to brand)
30
+ - **Geography:** US (San Francisco, New York, Austin) + Canada
31
+
32
+ ## Meeting Value (Offer)
33
+
34
+ A quick look at how we handle their entire LinkedIn with AI + human review — they barely touch it. In 15 minutes, we can walk through exactly how we generated $50M+ in pipeline for 30 exited founders in the last 30 days, and whether the 4-5 booked calls/month guarantee makes sense for their stage.
35
+
36
+ ## Social Proof
37
+
38
+ - **$50M+ in pipeline** generated across clients in the last 30 days from LinkedIn alone
39
+ - **4-5 booked calls/month guarantee** — or we refund you
40
+ - **~30 exited founders** currently on the platform (YC, Techstars, Sequoia-backed)
41
+ - Positioned as the **"#1 LinkedIn agent for founders"**
42
+
43
+ ---
44
+
45
+ ## Messaging Templates
46
+
47
+ **Sender:** Anjali Dhaliwal
48
+ **Channel:** LinkedIn InMail
49
+ **Signal:** People engaging with founder-led thought leadership and founder-led growth content on LinkedIn
50
+
51
+ ---
52
+
53
+ ### VARIANT 1 — Deep Personalization (company-level + signal)
54
+
55
+ _Personalization: References their previous exit or current venture by name + the signal content they engaged with._
56
+
57
+ ---
58
+
59
+ Hi {{first_name}}, let me know if i'm off, but {{seems_like_you}}.
60
+
61
+ saw you were active in some {{signal_topic}} conversations recently and figured this might be relevant.
62
+
63
+ we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
64
+
65
+ in the last 30 days they pulled in over 50m in pipeline from linkedin alone. Our system also guarantees 4-5 booked calls per month or we refund you.
66
+
67
+ is this worth a look or should i just send a short overview first?
68
+
69
+ ---
70
+
71
+ ### VARIANT 2 — Signal Personalization Only
72
+
73
+ _Personalization: References the type of content they were engaging with. No company-specific detail._
74
+
75
+ ---
76
+
77
+ Hi {{first_name}}, not sure if this is relevant at the moment, but saw you were engaging in some {{signal_topic}} recently and figured this might help.
78
+
79
+ we work with about 30 exited founders right now (yc, techstars, sequoia backed) and handle their entire linkedin with ai + a human review layer. they barely touch it.
80
+
81
+ in the last 30 days they pulled in over 50m in pipeline from linkedin content alone, and our system guarantees 4-5 booked calls per month or we refund you.
82
+
83
+ is this worth a look or should i share some examples?
84
+
85
+ ---
86
+
87
+ ### VARIANT 3 — No Personalization (ICP match only)
88
+
89
+ _Personalization: None. Pure ICP-matched lead from signal discovery list. Lead with proof directly._
90
+
91
+ ---
92
+
93
+ Hi {{first_name}}, not sure if this is relevant atm, but i work with about 30 exited founders (a lot of them from yc, techstars, sequoia companies) and we handle their entire linkedin with ai + a human review layer. they basically don't touch it.
94
+
95
+ in the last 30 days they pulled in over 50m in pipeline from linkedin alone. we also guarantee at least 4-5 booked calls per month from your content or we refund you.
96
+
97
+ is this worth a look or should i send a short overview?
98
+
99
+ ---
100
+
101
+ ### Interpolation Guidelines
102
+
103
+ - **{{first_name}}** — prospect's first name, 1 word, lowercase
104
+ - **{{seems_like_you}}** — a short, specific observation about their current venture or recent exit (e.g., "seems like you started building something new in the pharma space" / "looks like you're back building in fintech after the Stripe exit"). Source from LinkedIn profile. 10–20 words max, lowercase, casual tone.
105
+ - **{{signal_topic}}** — the topic or theme of content they recently engaged with (e.g., "founder-led thought leadership", "founder re-branding", "founder-led growth"). Source from signal/topic column. 2–5 words, lowercase.
106
+
107
+ ---
108
+
109
+ ### Template DOs
110
+
111
+ - Keep all body text lowercase to match the casual, peer-to-peer tone
112
+ - Use the signal topic column to populate {{signal_topic}} — match the exact theme they engaged with
113
+ - For {{seems_like_you}}, reference a specific venture, industry pivot, or recent move visible on their LinkedIn profile
114
+ - Lead with the observation or signal before mentioning Gelee AI
115
+ - End with a low-commitment binary CTA ("worth a look or should I send a short overview?")
116
+ - Keep messages under 100 words per variant
117
+
118
+ ### Template DON'Ts
119
+
120
+ - Don't capitalize the greeting, body, or CTA
121
+ - Don't add sign-offs (Best, Thanks, Regards, etc.)
122
+ - Don't rephrase or reorder the message structure — only fill in placeholders
123
+ - Don't add extra sentences or expand on the proof points
124
+ - Don't use formal language — this should feel like a message from a peer, not a sales rep
125
+
126
+ ---
127
+
128
+ ### Examples
129
+
130
+ **Example 1 — Variant 1 (pharma exit, founder-led growth signal):**
131
+
132
+ Hi sarah, let me know if i'm off, but seems like you started building something new in the pharma space after the Benchling exit.
133
+
134
+ saw you were active in some founder-led growth conversations recently and figured this might be relevant.
135
+
136
+ we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
137
+
138
+ in the last 30 days they pulled in over 50m in pipeline from linkedin alone. Our system also guarantees 4-5 booked calls per month or we refund you.
139
+
140
+ is this worth a look or should i just send a short overview first?
141
+
142
+ ---
143
+
144
+ **Example 2 — Variant 2 (founder re-branding signal):**
145
+
146
+ Hi james, not sure if this is relevant at the moment, but saw you were engaging in some founder re-branding conversations recently and figured this might help.
147
+
148
+ we work with about 30 exited founders right now (yc, techstars, sequoia backed) and handle their entire linkedin with ai + a human review layer. they barely touch it.
149
+
150
+ in the last 30 days they pulled in over 50m in pipeline from linkedin content alone, and our system guarantees 4-5 booked calls per month or we refund you.
151
+
152
+ is this worth a look or should i share some examples?
153
+
154
+ ---
155
+
156
+ **Example 3 — Variant 3 (ICP match only, no signal):**
157
+
158
+ Hi michael, not sure if this is relevant atm, but i work with about 30 exited founders (a lot of them from yc, techstars, sequoia companies) and we handle their entire linkedin with ai + a human review layer. they basically don't touch it.
159
+
160
+ in the last 30 days they pulled in over 50m in pipeline from linkedin alone. we also guarantee at least 4-5 booked calls per month from your content or we refund you.
161
+
162
+ is this worth a look or should i send a short overview?
163
+
164
+ ### Rubric Markdown
165
+
166
+ (none stored)
167
+
168
+ ### Structured Lead Scoring Rubrics
169
+
170
+ #### founder_executive_role
171
+
172
+ - Required: true
173
+ - Use for scoring: true
174
+ - Allow partial credit: true
175
+ - Strict matching: false
176
+ - Description: Checks if the prospect is a Founder, CEO, or CTO.
177
+ - Reason: The campaign specifically targets the highest level of leadership who have the authority to delegate their LinkedIn presence.
178
+ - Criterion: YES if the prospect's current title is CEO, CTO, COO, Founder, or Co-Founder, or other high-level C-level title. YES if they are a serial founder or have previously held a CEO/CTO/Founder title at a company they built. NO if they hold a mid-level management or non-executive role (e.g., Manager, Director of X, Engineer). NO if their headline says pre-seed, pre-funding, aspiring, idea stage, or building in stealth with no prior exit or company-building history behind them. NO if this appears to be their first company with no prior exit or notable venture.
179
+
180
+ #### venture_backed_scaleup
181
+
182
+ - Required: true
183
+ - Use for scoring: true
184
+ - Allow partial credit: true
185
+ - Strict matching: false
186
+ - Description: Evaluates if the company is a venture-backed startup or scale-up.
187
+ - Reason: The offer is tailored to founders in high-growth ecosystems who need to scale pipeline quickly.
188
+ - Criterion: YES if the company is a startup or scale-up with evidence of funding or venture backing (e.g., mentions of YC, Techstars, Sequoia, Series A/B/C) or high-growth tech focus. YES if the founder has previously exited a venture-backed or bootstrapped company at $10M+. NO if it is a large legacy corporation, a small local business, or a solo consultancy with no exit history. NO if the only funding signal is pre-seed, pre-funding, angel round, or bootstrapped with no exit history.
189
+
190
+ #### tier_1_geography
191
+
192
+ - Required: true
193
+ - Use for scoring: true
194
+ - Allow partial credit: false
195
+ - Strict matching: false
196
+ - Description: Ensures the prospect is based in the US or Canada.
197
+ - Reason: The ICP explicitly specifies North American markets, particularly tech hubs like SF, NY, and Austin.
198
+ - Criterion: YES if the prospect is located in the United States or Canada. NO for all other countries.
199
+
200
+ #### ticket_size_qualifier
201
+
202
+ - Required: true
203
+ - Use for scoring: true
204
+ - Allow partial credit: true
205
+ - Strict matching: false
206
+ - Description: Evaluates if the company has the financial capacity for the service based on funding, team size, or revenue signals.
207
+ - Reason: Ensures the prospect's company has the budget for a guaranteed pipeline generation service.
208
+ - Criterion: YES if the prospect is associated with a company that has raised Series A or beyond, has 10+ employees, has been operating for 4+ years, or shows clear signals of a revenue-generating business. YES if they are an exited founder now advising or building their next venture. NO if they are pre-seed, pre-funding, or a first-time founder with no revenue signals. NO if they appear to be a solo solopreneur with no team, a bootstrapped micro-business, or a pre-revenue idea-stage founder. NO if their headline says pre-seed, pre-funding, idea stage, building in stealth, or 0 to 1 with no prior company history.
209
+
210
+ #### exit_seniority_signal
211
+
212
+ - Required: true
213
+ - Use for scoring: true
214
+ - Allow partial credit: false
215
+ - Strict matching: false
216
+ - Description: Checks for evidence of a previous exit, acquisition, or 3+ years of founding experience.
217
+ - Reason: The campaign targets experienced or exited founders who are more likely to value a high-ticket, done-for-you service.
218
+ - Criterion: YES if the prospect shows evidence of a previous exit, acquisition, or 6+ years of experience at a company they founded or led. Signals include: exited, acquired, built and sold, serial founder, former CEO/CTO of a company they founded, or 6+ years tenure at current or previous venture. YES if they are currently building their second or third company after a prior exit. NO if they are a first-time founder at pre-seed or idea stage with no prior exit or company-building history. NO if they recently graduated an accelerator batch (YC W25, W26, S25, F25) with no prior exit.
219
+
220
+ #### tech_digital_industry_filter