@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.
- package/.claude-plugin/plugin.json +12 -0
- package/.mcp.json +9 -0
- package/README.md +355 -0
- package/dist/api.d.ts +21 -0
- package/dist/api.js +73 -0
- package/dist/auth.d.ts +60 -0
- package/dist/auth.js +246 -0
- package/dist/engage-memory.d.ts +63 -0
- package/dist/engage-memory.js +354 -0
- package/dist/index-dev.d.ts +2 -0
- package/dist/index-dev.js +17 -0
- package/dist/index.d.ts +7 -0
- package/dist/index.js +8 -0
- package/dist/server.d.ts +1 -0
- package/dist/server.js +499 -0
- package/dist/skills.d.ts +11 -0
- package/dist/skills.js +97 -0
- package/dist/tools/auth.d.ts +30 -0
- package/dist/tools/auth.js +124 -0
- package/dist/tools/blueprint-commit.d.ts +174 -0
- package/dist/tools/blueprint-commit.js +286 -0
- package/dist/tools/bootstrap.d.ts +64 -0
- package/dist/tools/bootstrap.js +246 -0
- package/dist/tools/campaigns.d.ts +589 -0
- package/dist/tools/campaigns.js +892 -0
- package/dist/tools/cells.d.ts +58 -0
- package/dist/tools/cells.js +48 -0
- package/dist/tools/context.d.ts +88 -0
- package/dist/tools/context.js +271 -0
- package/dist/tools/csv-domains.d.ts +73 -0
- package/dist/tools/csv-domains.js +464 -0
- package/dist/tools/csv-linkedin.d.ts +102 -0
- package/dist/tools/csv-linkedin.js +712 -0
- package/dist/tools/direct-campaigns.d.ts +240 -0
- package/dist/tools/direct-campaigns.js +250 -0
- package/dist/tools/engage-bootstrap.d.ts +94 -0
- package/dist/tools/engage-bootstrap.js +205 -0
- package/dist/tools/engage-discovery.d.ts +78 -0
- package/dist/tools/engage-discovery.js +150 -0
- package/dist/tools/engage-memory.d.ts +181 -0
- package/dist/tools/engage-memory.js +143 -0
- package/dist/tools/engage-state.d.ts +72 -0
- package/dist/tools/engage-state.js +62 -0
- package/dist/tools/enrichment.d.ts +167 -0
- package/dist/tools/enrichment.js +174 -0
- package/dist/tools/flow-preflight.d.ts +68 -0
- package/dist/tools/flow-preflight.js +138 -0
- package/dist/tools/framework.d.ts +44 -0
- package/dist/tools/framework.js +153 -0
- package/dist/tools/interaction-mode.d.ts +27 -0
- package/dist/tools/interaction-mode.js +102 -0
- package/dist/tools/leads.d.ts +2417 -0
- package/dist/tools/leads.js +2307 -0
- package/dist/tools/linkedin.d.ts +210 -0
- package/dist/tools/linkedin.js +229 -0
- package/dist/tools/navigation.d.ts +91 -0
- package/dist/tools/navigation.js +381 -0
- package/dist/tools/one-off.d.ts +229 -0
- package/dist/tools/one-off.js +273 -0
- package/dist/tools/processing.d.ts +70 -0
- package/dist/tools/processing.js +56 -0
- package/dist/tools/prompts.d.ts +211 -0
- package/dist/tools/prompts.js +210 -0
- package/dist/tools/provider-preflight.d.ts +21 -0
- package/dist/tools/provider-preflight.js +59 -0
- package/dist/tools/readiness.d.ts +261 -0
- package/dist/tools/readiness.js +510 -0
- package/dist/tools/rows.d.ts +126 -0
- package/dist/tools/rows.js +105 -0
- package/dist/tools/rubrics.d.ts +497 -0
- package/dist/tools/rubrics.js +681 -0
- package/dist/tools/senders.d.ts +44 -0
- package/dist/tools/senders.js +69 -0
- package/dist/tools/sequencer.d.ts +127 -0
- package/dist/tools/sequencer.js +194 -0
- package/dist/tools/tables.d.ts +35 -0
- package/dist/tools/tables.js +36 -0
- package/dist/tools/verify-row.d.ts +36 -0
- package/dist/tools/verify-row.js +38 -0
- package/dist/tools/workspaces.d.ts +140 -0
- package/dist/tools/workspaces.js +139 -0
- package/dist/utils/workspace-root.d.ts +1 -0
- package/dist/utils/workspace-root.js +39 -0
- package/package.json +46 -0
- package/skills/building-gtm-tables/SKILL.md +216 -0
- package/skills/building-gtm-tables/core/auto-execute.yaml +19 -0
- package/skills/building-gtm-tables/core/blueprint-schema.json +72 -0
- package/skills/building-gtm-tables/references/brief-to-blueprint.md +334 -0
- package/skills/building-gtm-tables/references/column-type-catalog.md +318 -0
- package/skills/building-gtm-tables/references/common-blueprints.fixtures.ts +199 -0
- package/skills/building-gtm-tables/references/common-blueprints.md +44 -0
- package/skills/building-gtm-tables/references/failure-taxonomy.md +197 -0
- package/skills/building-gtm-tables/references/uat-seed-prompts.md +37 -0
- package/skills/building-gtm-tables/references/verify-loop.md +74 -0
- package/skills/campaign-messages/SKILL.md +173 -0
- package/skills/campaign-messages/flow.v1.json +75 -0
- package/skills/craft-message/SKILL.md +401 -0
- package/skills/create-campaign/ARCHITECTURE.md +232 -0
- package/skills/create-campaign/DISCUSS.md +296 -0
- package/skills/create-campaign/FLOW_ASCII.md +240 -0
- package/skills/create-campaign/HOST-PARITY-CHECKLIST.md +49 -0
- package/skills/create-campaign/README.md +142 -0
- package/skills/create-campaign/SKILL.md +286 -0
- package/skills/create-campaign/context/README.md +67 -0
- package/skills/create-campaign/context/_TEMPLATE.md +12 -0
- package/skills/create-campaign/context/context.md +35 -0
- package/skills/create-campaign/context/learnings.md +16 -0
- package/skills/create-campaign/context/registry.json +19 -0
- package/skills/create-campaign/core/flow.v1.json +217 -0
- package/skills/create-campaign/core/policy.md +191 -0
- package/skills/create-campaign/core/providers/apollo.json +35 -0
- package/skills/create-campaign/core/providers/prospeo.json +34 -0
- package/skills/create-campaign/core/providers/registry.json +31 -0
- package/skills/create-campaign/core/providers/sales-nav.json +37 -0
- package/skills/create-campaign/core/providers/signal-discovery.json +42 -0
- package/skills/create-campaign/references/brief-template.md +64 -0
- package/skills/create-campaign/references/campaign-quality.md +84 -0
- package/skills/create-campaign/references/copy-calibration-examples.md +120 -0
- package/skills/create-campaign/references/offer-patterns.md +108 -0
- package/skills/create-campaign/references/provider-selection-strategy.md +212 -0
- package/skills/create-campaign/references/question-examples.md +167 -0
- package/skills/create-campaign/references/token-fill-examples.md +81 -0
- package/skills/create-campaign-brief/ARCHITECTURE.md +72 -0
- package/skills/create-campaign-brief/DISCUSS.md +64 -0
- package/skills/create-campaign-brief/README.md +176 -0
- package/skills/create-campaign-brief/SKILL.md +537 -0
- package/skills/create-campaign-brief/references/brief-synthesis-rules.md +100 -0
- package/skills/create-campaign-brief/references/brief-template.md +220 -0
- package/skills/create-campaign-brief/references/campaign-idea-options.md +30 -0
- package/skills/create-campaign-brief/references/copy-appendix-template.md +62 -0
- package/skills/create-campaign-brief/references/draft-lifecycle.md +23 -0
- package/skills/create-campaign-brief/references/examples/MANIFEST.json +89 -0
- package/skills/create-campaign-brief/references/examples/briefs/clover.md +223 -0
- package/skills/create-campaign-brief/references/examples/briefs/galley.md +222 -0
- package/skills/create-campaign-brief/references/examples/briefs/gelee.md +220 -0
- package/skills/create-campaign-brief/references/examples/briefs/hey-digital.md +234 -0
- package/skills/create-campaign-brief/references/examples/briefs/persona.md +231 -0
- package/skills/create-campaign-brief/references/examples/briefs/revvix.md +220 -0
- package/skills/create-campaign-brief/references/examples/briefs/sellable-dev.md +220 -0
- package/skills/create-campaign-brief/references/examples/briefs/superposition.md +233 -0
- package/skills/create-campaign-brief/references/examples/briefs/superpower.md +219 -0
- package/skills/create-campaign-brief/references/examples/briefs/westpark-villas.md +220 -0
- package/skills/create-campaign-brief/references/icp-lock-question-bank.md +43 -0
- package/skills/create-campaign-brief/references/messaging-inputs.md +58 -0
- package/skills/create-campaign-brief/references/output-acceptance-rubric.md +62 -0
- package/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md +248 -0
- package/skills/create-campaign-brief/references/phase75-canonical-brief-template.md +319 -0
- package/skills/create-campaign-brief/references/phase75-good-brief-and-messaging-examples.md +445 -0
- package/skills/create-campaign-brief/references/quick-research-protocol.md +39 -0
- package/skills/create-campaign-brief/references/reference-sheet-protocol.md +60 -0
- package/skills/create-campaign-brief/references/zero-shot-iteration-rules.md +66 -0
- package/skills/create-campaign-v2/SKILL.md +1619 -0
- package/skills/create-campaign-v2/core/auto-execute.README.md +219 -0
- package/skills/create-campaign-v2/core/auto-execute.yaml +121 -0
- package/skills/create-campaign-v2/core/flow.v2.json +1643 -0
- package/skills/create-campaign-v2/core/policy.md +82 -0
- package/skills/create-campaign-v2/references/ai-tells.md +253 -0
- package/skills/create-campaign-v2/references/approval-gate-framing.md +346 -0
- package/skills/create-campaign-v2/references/draft-lifecycle.md +110 -0
- package/skills/create-campaign-v2/references/escalation-ladder.md +119 -0
- package/skills/create-campaign-v2/references/filter-leads.md +495 -0
- package/skills/create-campaign-v2/references/final-handoff-contract.md +176 -0
- package/skills/create-campaign-v2/references/gold-standard-message-examples.md +394 -0
- package/skills/create-campaign-v2/references/gold-standard-message-patterns.md +314 -0
- package/skills/create-campaign-v2/references/gold-standard-message-validation-example.md +212 -0
- package/skills/create-campaign-v2/references/lead-validation-preview.md +172 -0
- package/skills/create-campaign-v2/references/parallel-critique-protocol.md +368 -0
- package/skills/create-campaign-v2/references/sample-validation-loop.md +289 -0
- package/skills/create-campaign-v2/references/step-13-import-leads.md +151 -0
- package/skills/create-campaign-v2/references/step-15-re-cascade.md +90 -0
- package/skills/create-campaign-v2/references/thomas-revision-filters.md +521 -0
- package/skills/create-campaign-v2/references/thomas-variant-selection.md +202 -0
- package/skills/create-campaign-v2/references/tier-routing-matrix.md +66 -0
- package/skills/create-campaign-v2/references/validation-criteria.md +367 -0
- package/skills/create-campaign-v2/references/watch-link-handoff.md +106 -0
- package/skills/create-campaign-v2-validation/SKILL.md +296 -0
- package/skills/create-post/SKILL.md +1308 -0
- package/skills/create-rubric/SKILL.md +251 -0
- package/skills/engage/SKILL.md +549 -0
- package/skills/engage/core/README.md +23 -0
- package/skills/engage/core/proven-searches.json +11 -0
- package/skills/engage/core/style-guide.template.md +47 -0
- package/skills/engage/core/tracked-people.json +10 -0
- package/skills/enrich-prospects/SKILL.md +97 -0
- package/skills/find-leads/SKILL.md +467 -0
- package/skills/generate-messages/SKILL.md +2361 -0
- package/skills/interview/SKILL.md +132 -0
- package/skills/interview/core/ENGAGE_STYLE_GUIDE.template.md +54 -0
- package/skills/interview/core/ICP.template.md +54 -0
- package/skills/interview/core/VOICE_PROFILE.template.md +101 -0
- package/skills/providers/apollo.md +520 -0
- package/skills/providers/prospeo.md +398 -0
- package/skills/providers/sales-nav.md +372 -0
- package/skills/providers/signal-discovery.md +495 -0
- package/skills/research/SKILL.md +258 -0
- package/skills/research/config.json +9 -0
- package/skills/research/override.md +13 -0
- package/skills/research-prospect/SKILL.md +99 -0
- package/skills/research-sender/SKILL.md +158 -0
- package/skills/workflow-sequences/SKILL.md +85 -0
|
@@ -0,0 +1,220 @@
|
|
|
1
|
+
# sellable.dev 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: 304
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## Design Partner Access for Outbound/GTM Leaders
|
|
10
|
+
|
|
11
|
+
- Sent: 1119
|
|
12
|
+
- Replied: 59
|
|
13
|
+
- Accepted: 377
|
|
14
|
+
- Updated: 2026-03-23T17:48:25.906Z
|
|
15
|
+
|
|
16
|
+
### Campaign Brief
|
|
17
|
+
|
|
18
|
+
# Design Partner Access for Outbound/GTM Leaders
|
|
19
|
+
|
|
20
|
+
For outbound/GTM leaders who are excited about Claude
|
|
21
|
+
|
|
22
|
+
## Campaign Objective
|
|
23
|
+
|
|
24
|
+
Reach outbound and GTM leaders who engaged with Claude-related content and offer them design partner access to the only Claude Code-native GTM platform.
|
|
25
|
+
|
|
26
|
+
## Ideal Customer Profile (ICP)
|
|
27
|
+
|
|
28
|
+
- **Roles:** VP Sales, Head of Growth, Rev Ops, Sales Leaders, GTM Leaders
|
|
29
|
+
- **Signal:** Engaged with Claude/AI content on LinkedIn
|
|
30
|
+
- **Mindset:** Interested in AI-native tooling, not just AI wrappers
|
|
31
|
+
|
|
32
|
+
## Meeting Value (Offer)
|
|
33
|
+
|
|
34
|
+
Two clear options with low friction:
|
|
35
|
+
|
|
36
|
+
a) 15-min call - show how they could book more meetings with their ICP, launch a pilot if they like it
|
|
37
|
+
|
|
38
|
+
b) Send them the video of using Sellable to write and send the exact message to them (meta demo)
|
|
39
|
+
|
|
40
|
+
## Message Template
|
|
41
|
+
|
|
42
|
+
CRITICAL: ALL LOWERCASE - including "hey" and the person's name
|
|
43
|
+
|
|
44
|
+
hey [name],
|
|
45
|
+
|
|
46
|
+
saw you raise your hand for claude + gtm (creepy to reach out based on that, i know) - but this felt too on the nose to ignore.
|
|
47
|
+
|
|
48
|
+
i'm building sellable, the only gtm platform that runs natively on claude code.
|
|
49
|
+
|
|
50
|
+
we're looking for design partners - and [PERSONALIZED REASON - their team size, role, or why they're a perfect fit].
|
|
51
|
+
|
|
52
|
+
two options:
|
|
53
|
+
|
|
54
|
+
a) 15-min call - i'll show you how you could book more meetings with [THEIR ICP - who they want to reach], and if you like it we launch a pilot right there
|
|
55
|
+
|
|
56
|
+
b) i send you the video of me using sellable to write and send this exact message to you (yes, it's that meta)
|
|
57
|
+
|
|
58
|
+
p.s. yes, this message was entirely written and sent via claude code 😊
|
|
59
|
+
|
|
60
|
+
## Hook
|
|
61
|
+
|
|
62
|
+
"saw you raise your hand for claude + gtm (creepy to reach out based on that, i know) - but this felt too on the nose to ignore."
|
|
63
|
+
|
|
64
|
+
Uses parentheses (feels human, AI rarely writes this way). Self-aware about the signal without being apologetic.
|
|
65
|
+
|
|
66
|
+
## Product Line
|
|
67
|
+
|
|
68
|
+
"i'm building sellable, the only gtm platform that runs natively on claude code."
|
|
69
|
+
|
|
70
|
+
Clear, bold positioning. "The only" - not "a".
|
|
71
|
+
|
|
72
|
+
## Personalization Line (REQUIRED)
|
|
73
|
+
|
|
74
|
+
"we're looking for design partners - and [why they're a perfect fit]."
|
|
75
|
+
|
|
76
|
+
Examples:
|
|
77
|
+
|
|
78
|
+
- "someone running 12 enterprise reps felt like a perfect fit"
|
|
79
|
+
- "someone who's built sales orgs from scratch felt like the right person to ask"
|
|
80
|
+
- "someone helping global brands crack japan felt like exactly who we should build for"
|
|
81
|
+
- "someone who hit #1 sales rep then moved into leading a regional team felt like exactly who we should build for"
|
|
82
|
+
|
|
83
|
+
Research their: team size, role, achievements, company scale.
|
|
84
|
+
|
|
85
|
+
## Offer (A/B Format)
|
|
86
|
+
|
|
87
|
+
Always give two clear options:
|
|
88
|
+
|
|
89
|
+
a) 15-min call - must include their specific ICP (who they want to reach)
|
|
90
|
+
b) Meta demo video option
|
|
91
|
+
|
|
92
|
+
Option A must include their specific ICP. Examples:
|
|
93
|
+
|
|
94
|
+
- "book more meetings with b2b marketing leaders"
|
|
95
|
+
- "book more meetings with enterprise marketing teams"
|
|
96
|
+
- "book more meetings with growth-stage b2b companies"
|
|
97
|
+
- "book more meetings with enterprise brands eyeing japan expansion"
|
|
98
|
+
- "book more meetings with mid-market hr leaders"
|
|
99
|
+
|
|
100
|
+
Research their company/role to understand who THEY sell to.
|
|
101
|
+
|
|
102
|
+
## Formatting Rules
|
|
103
|
+
|
|
104
|
+
- ALL LOWERCASE EVERYTHING - "hey travis," not "Hey Travis,"
|
|
105
|
+
- One sentence per line - easy to scan on mobile
|
|
106
|
+
- Parentheses - feels human, AI doesn't write this way
|
|
107
|
+
- A/B options - makes responding easy
|
|
108
|
+
- No sign-offs - no "Best," or "Thanks,"
|
|
109
|
+
- NEVER use em dashes - always use regular dashes (-) instead
|
|
110
|
+
|
|
111
|
+
## P.S. Line (Required)
|
|
112
|
+
|
|
113
|
+
"p.s. yes, this message was entirely written and sent via claude code 😊"
|
|
114
|
+
|
|
115
|
+
## Do NOT Target
|
|
116
|
+
|
|
117
|
+
- Current Sellable users
|
|
118
|
+
- Competitors in the outbound/sales engagement space
|
|
119
|
+
- People who just liked but show no GTM/outbound relevance
|
|
120
|
+
|
|
121
|
+
## Additional Notes
|
|
122
|
+
|
|
123
|
+
- This is Signal Discovery - targeting engagers on specific Claude posts
|
|
124
|
+
- Quality over quantity - these are warm, high-intent leads
|
|
125
|
+
- The self-aware hook + personalized "why you" line is key to standing out
|
|
126
|
+
|
|
127
|
+
### Rubric Markdown
|
|
128
|
+
|
|
129
|
+
(none stored)
|
|
130
|
+
|
|
131
|
+
### Structured Lead Scoring Rubrics
|
|
132
|
+
|
|
133
|
+
#### gtm_sales_leadership_role
|
|
134
|
+
|
|
135
|
+
- Required: true
|
|
136
|
+
- Use for scoring: true
|
|
137
|
+
- Allow partial credit: true
|
|
138
|
+
- Strict matching: false
|
|
139
|
+
- Description: GTM or sales leadership role (VP Sales, Head of Growth, Rev Ops, Sales Leader, GTM Leader)
|
|
140
|
+
- Reason: We are targeting people who own or influence the outbound/GTM motion. These are the decision-makers who would adopt a GTM platform like Sellable. Founders count because at early-stage companies they typically own GTM directly.
|
|
141
|
+
- Criterion: Yes if person holds a GTM or sales leadership title: VP Sales, VP Revenue, VP Growth, Head of Sales, Head of Growth, Head of GTM, Director of Sales, Director of Revenue, Director of Growth, Sales Manager, SDR Manager, BDR Manager, Rev Ops Manager, Head of Revenue Operations, CRO, Chief Revenue Officer, Head of Demand Gen, Sales Leader, GTM Leader, Head of Business Development, Director of Sales Development. Also yes if Founder/CEO/COO at a company that sells B2B (they own the GTM function). No if title is purely marketing, engineering, HR, finance, or other non-GTM function.
|
|
142
|
+
|
|
143
|
+
#### not_competitor
|
|
144
|
+
|
|
145
|
+
- Required: true
|
|
146
|
+
- Use for scoring: true
|
|
147
|
+
- Allow partial credit: true
|
|
148
|
+
- Strict matching: false
|
|
149
|
+
- Description: Not working at a competing outbound/sales engagement platform
|
|
150
|
+
- Reason: Competitors would not be design partners - they would be gathering competitive intelligence. Exclude them entirely.
|
|
151
|
+
- Criterion: No if person works at: Outreach, Salesloft, Apollo, Clay, Instantly, Lemlist, Smartlead, Reply.io, Woodpecker, Mailshake, Mixmax, Groove, Yesware, Lavender, Regie.ai, Amplemarket, 11x, AiSDR, Artisan, Gojiberry, UpLead, or any company that primarily provides outbound automation, sales engagement, or AI SDR services. Yes otherwise.
|
|
152
|
+
|
|
153
|
+
#### b2b_linkedin_targetable
|
|
154
|
+
|
|
155
|
+
- Required: true
|
|
156
|
+
- Use for scoring: true
|
|
157
|
+
- Allow partial credit: true
|
|
158
|
+
- Strict matching: false
|
|
159
|
+
- Description: B2B company whose buyers/prospects are reachable on LinkedIn
|
|
160
|
+
- Reason: Sellable is a LinkedIn outbound platform. Design partners need to be selling to people who are actually reachable and active on LinkedIn. B2B professionals are the sweet spot.
|
|
161
|
+
- Criterion: Yes if the person works at a company that sells to other businesses AND their target buyers are professionals likely active on LinkedIn (B2B SaaS, B2B tech, professional services, consulting, staffing, recruiting, enterprise software, fintech B2B, HR tech, martech, sales tech). No if company is B2C, consumer-facing, or sells to audiences not on LinkedIn (retail consumers, local services, government-only). Be lenient - most B2B companies have LinkedIn-targetable buyers.
|
|
162
|
+
|
|
163
|
+
#### revenue_can_afford_tool
|
|
164
|
+
|
|
165
|
+
- Required: true
|
|
166
|
+
- Use for scoring: true
|
|
167
|
+
- Allow partial credit: true
|
|
168
|
+
- Strict matching: false
|
|
169
|
+
- Description: Company estimated at 500k+ ARR - can afford $1,500-2,500/mo for multiple seats
|
|
170
|
+
- Reason: Our tool costs $1,500-2,500/mo for multiple seats. Design partners need to be at companies that can realistically afford this. We want to be lenient here - if they look like a real business with a team, they likely qualify. The main filter is excluding solo operators and micro-businesses.
|
|
171
|
+
- Criterion: Yes if the company appears to have estimated revenue of $500k+ ARR or shows strong signals of being able to afford $1,500-2,500/month for a GTM tool. Signals include: 20+ employees, has raised funding (seed+), has a sales team of 3+, mentions revenue/growth milestones, or operates in a well-funded vertical. Be lenient - if company size is 10-20+ people and appears to be a real operating business (not a solo consultant or freelancer), lean yes. No if clearly a solo freelancer, 1-2 person side project, pre-revenue solo founder with no funding, or micro-business unlikely to spend on tooling.
|
|
172
|
+
|
|
173
|
+
#### tier1_country
|
|
174
|
+
|
|
175
|
+
- Required: true
|
|
176
|
+
- Use for scoring: true
|
|
177
|
+
- Allow partial credit: true
|
|
178
|
+
- Strict matching: false
|
|
179
|
+
- Description: Located in US, Canada, UK, Australia, or Western Europe
|
|
180
|
+
- Reason: Tier 1 countries have the budget, LinkedIn adoption, and English-language market fit for Sellable. These are the markets where outbound on LinkedIn works best and where companies can afford our pricing.
|
|
181
|
+
- Criterion: Yes if person is located in: United States, Canada, United Kingdom, Australia, New Zealand, Germany, France, Netherlands, Sweden, Denmark, Norway, Finland, Switzerland, Ireland, Belgium, Austria, Spain, Italy, Israel, or Singapore. No if located in countries outside these tier 1 markets. Be lenient if location is unclear - lean yes if they write in English and appear to work at a company headquartered in a tier 1 country.
|
|
182
|
+
|
|
183
|
+
#### seniority_decision_maker
|
|
184
|
+
|
|
185
|
+
- Required: false
|
|
186
|
+
- Use for scoring: true
|
|
187
|
+
- Allow partial credit: true
|
|
188
|
+
- Strict matching: false
|
|
189
|
+
- Description: Has decision-making authority (Manager level or above, or Founder)
|
|
190
|
+
- Reason: Design partners need to be people who can make the decision to adopt and pilot Sellable. Individual contributors can champion but rarely have the authority to commit to a design partnership.
|
|
191
|
+
- Criterion: Yes if title includes: VP, Vice President, Director, Head of, Manager, Lead, Senior Director, Chief, C-suite (CEO, COO, CRO, CMO), Founder, Co-Founder, Owner, Partner, Principal, or equivalent seniority. No if title is individual contributor without 'Senior' or 'Lead' (e.g., SDR, BDR, Account Executive, Sales Rep) unless they are a solo founder or clearly run their own team.
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
## Claude Code Native GTM Platform - Design Partner Access
|
|
196
|
+
|
|
197
|
+
- Sent: 405
|
|
198
|
+
- Replied: 34
|
|
199
|
+
- Accepted: 187
|
|
200
|
+
- Updated: 2026-03-26T21:16:04.508Z
|
|
201
|
+
|
|
202
|
+
### Campaign Brief
|
|
203
|
+
|
|
204
|
+
# Design Partner Access for Outbound/GTM Leaders
|
|
205
|
+
|
|
206
|
+
_For outbound/GTM leaders who are excited about Claude_
|
|
207
|
+
|
|
208
|
+
## Campaign Objective
|
|
209
|
+
|
|
210
|
+
Reach outbound and GTM leaders who engaged with Claude-related content and offer them design partner access to the only Claude Code-native GTM platform.
|
|
211
|
+
|
|
212
|
+
## Ideal Customer Profile (ICP)
|
|
213
|
+
|
|
214
|
+
- **Roles:** VP Sales, Head of Growth, Rev Ops, Sales Leaders, GTM Leaders
|
|
215
|
+
- **Signal:** Engaged with Claude/AI content on LinkedIn
|
|
216
|
+
- **Mindset:** Interested in AI-native tooling, not just AI wrappers
|
|
217
|
+
|
|
218
|
+
## Meeting Value (Offer)
|
|
219
|
+
|
|
220
|
+
Two clear options with low friction:
|
|
@@ -0,0 +1,233 @@
|
|
|
1
|
+
# superposition 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
|
+
## Brex Playbook + Named Proof — YC Job Board Founders
|
|
10
|
+
|
|
11
|
+
- Sent: 1601
|
|
12
|
+
- Replied: 10
|
|
13
|
+
- Accepted: 222
|
|
14
|
+
- Updated: 2026-02-19T22:23:06.991Z
|
|
15
|
+
|
|
16
|
+
### Campaign Brief
|
|
17
|
+
|
|
18
|
+
# Superposition — YC Job Board Founders Hiring Engineers
|
|
19
|
+
|
|
20
|
+
## Sender
|
|
21
|
+
|
|
22
|
+
Edmund Cuthbert — Founder & CEO, Superposition
|
|
23
|
+
Placed the first engineering hire at Brex. Built an agent that helps early startups make hires they didn't think were possible. Outcome-based pricing — you only pay when the role is filled.
|
|
24
|
+
|
|
25
|
+
## ICP
|
|
26
|
+
|
|
27
|
+
Founders/CEOs of YC startups actively hiring engineers. Sourced from Work at a Startup job board. The buyer is the CEO — they own hiring at this stage.
|
|
28
|
+
|
|
29
|
+
## Core Narrative
|
|
30
|
+
|
|
31
|
+
Edmund is a world-class startup recruiter who learned to code and built an agent better at recruiting than he was. The agent doesn't surface applicants — it proactively headhunts, writes personalized outreach that references what actually makes a candidate interesting, and schedules interviews directly into the founder's calendar.
|
|
32
|
+
|
|
33
|
+
## Proof Points (use these — never fabricate)
|
|
34
|
+
|
|
35
|
+
- Placed the first engineering hire at Brex (Edmund's founding story)
|
|
36
|
+
- 13 founding engineer roles filled at early startups, including Newton (YC24), Vitable Health (YC20), Plastic Labs
|
|
37
|
+
- Candidates from Fortune 500 companies, SpaceX, and Apple placed at startups with 4-person teams
|
|
38
|
+
- Plastic Labs case study: 43,802 candidates scanned → 15 that matched traits no resume would show → hired platform engineer
|
|
39
|
+
- Vince Trost (Plastic Labs co-founder): "When other founders tell me they're hiring I tell them it's just a no brainer. You should use Superposition."
|
|
40
|
+
- Vince: "Any time I need to hire now, my default is to get Superposition on it. It runs and just does the work for me."
|
|
41
|
+
|
|
42
|
+
## Case Study Link
|
|
43
|
+
|
|
44
|
+
Include in every message: superposition.ai/case-studies/how-plastic-labs-hired-founding-engineer
|
|
45
|
+
|
|
46
|
+
## What Founders Actually Care About (from Edmund)
|
|
47
|
+
|
|
48
|
+
1. Candidate quality — "holy shit, I didn't think we could hire someone this good"
|
|
49
|
+
2. They won't do sourcing themselves — "We have customers tell us I've already messaged 500 people. Then I say show me. And it's 20."
|
|
50
|
+
3. Outcome-based pricing — no fee unless someone starts
|
|
51
|
+
4. Time — "You're already running a proper funnel to fundraise, proper funnel to sell. If you're going to spend 4 hours a day on LinkedIn, it better be fundraising and selling, not recruiting."
|
|
52
|
+
|
|
53
|
+
## Voice Rules
|
|
54
|
+
|
|
55
|
+
- Sound like Edmund typed it from his phone, not a vendor pitch
|
|
56
|
+
- Curious, precise, charismatic. "Weird is better than sterile."
|
|
57
|
+
- No impersonal personalization (no "I see you went to Bristol University" garbage)
|
|
58
|
+
- Connect every line to the actual problem — hiring
|
|
59
|
+
- Use conversational connectors ("And since...", "The whole thing is...")
|
|
60
|
+
- Soft CTAs ("if useful?", "if that'd be useful?")
|
|
61
|
+
- Human texture words: "actually", "just", "personally", ellipsis, "if useful?"
|
|
62
|
+
|
|
63
|
+
## Personalization (minimal, relevant)
|
|
64
|
+
|
|
65
|
+
- {{firstName}}, {{companyName}} from lead data
|
|
66
|
+
- {{role}} from "Jobs Hiring For" column — rules:
|
|
67
|
+
- Always lowercase (e.g., "full-stack engineer" not "Full-Stack Engineer")
|
|
68
|
+
- If multiple roles listed, pick the one the founder would most want to hire (usually the most senior or foundational engineering role)
|
|
69
|
+
- If no role data, default to "engineer"
|
|
70
|
+
- Reference the job post as the signal — it's honest and relevant
|
|
71
|
+
- DO NOT flatter their mission, comment on their background, or reference anything disconnected from hiring
|
|
72
|
+
|
|
73
|
+
## Anti-Patterns (NEVER do these)
|
|
74
|
+
|
|
75
|
+
- NEVER write a freestyle message — always use the exact template below
|
|
76
|
+
- NEVER make up your own structure, opening, or CTA
|
|
77
|
+
- NEVER write feature-first sentences ("AI-powered recruiting agent for seed-stage startups")
|
|
78
|
+
- NEVER add generic "noticed you're hiring" without the full template differentiator
|
|
79
|
+
- NEVER list stats as a laundry list outside the template structure
|
|
80
|
+
- NEVER use "I noticed" or "I see" openers (template uses "Saw you posted" — use that exact phrasing)
|
|
81
|
+
- NEVER add compliment sandwiches or flatter their mission/company
|
|
82
|
+
- NEVER add impersonal personalization ("I see you went to X school", "I noticed you came through YC S14", "with your background at...")
|
|
83
|
+
- NEVER change the proof points, company names, or stats
|
|
84
|
+
- NEVER rearrange sections or combine lines from the template
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
## ⚠️ CRITICAL: EXACT MESSAGE TEMPLATE ⚠️
|
|
89
|
+
|
|
90
|
+
**THIS IS THE ONLY MESSAGE YOU SHOULD GENERATE.** Copy this template word-for-word. The ONLY things you replace are {{firstName}} and {{role}}. Everything else — every word, every line break, every proof point, every CTA — stays exactly as written below. Do NOT freestyle. Do NOT paraphrase. Do NOT reorganize. Do NOT add your own opener or closer. The two examples below show exactly what correct output looks like — match them precisely.
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
Hey {{firstName}},
|
|
95
|
+
|
|
96
|
+
Saw you posted for {{a role}} — I'm sure every recruiter on LinkedIn is already in your DMs.
|
|
97
|
+
|
|
98
|
+
But..
|
|
99
|
+
|
|
100
|
+
I placed the first engineering hire at Brex.
|
|
101
|
+
|
|
102
|
+
Then built an agent that helps early startups make hires they didn't think were possible.
|
|
103
|
+
|
|
104
|
+
We've placed candidates from Fortune 500 companies, SpaceX, and Apple at startups with 4-person teams.
|
|
105
|
+
|
|
106
|
+
13 founding engineer roles filled at early startups, including:
|
|
107
|
+
|
|
108
|
+
- Newton (YC24)
|
|
109
|
+
- Vitable Health (YC20)
|
|
110
|
+
- Plastic Labs
|
|
111
|
+
|
|
112
|
+
The whole thing is outcome-based, so you only pay when someone actually starts.
|
|
113
|
+
|
|
114
|
+
Two quick options:
|
|
115
|
+
|
|
116
|
+
a) 15-min call — find the uncommonly specific {{role}} who's the exact right fit for your team
|
|
117
|
+
|
|
118
|
+
b) see why Vince at Plastic Labs calls Superposition "a no-brainer" - we scanned 43,802 candidates to find 15 that matched traits no resume would show
|
|
119
|
+
|
|
120
|
+
superposition.ai/case-studies/how-plastic-labs-hired-founding-engineer
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
## ✅ EXAMPLE OUTPUT 1 (role = full-stack engineer)
|
|
125
|
+
|
|
126
|
+
Hey Dorothy,
|
|
127
|
+
|
|
128
|
+
Saw you posted for a full-stack engineer — I'm sure every recruiter on LinkedIn is already in your DMs.
|
|
129
|
+
|
|
130
|
+
But..
|
|
131
|
+
|
|
132
|
+
I placed the first engineering hire at Brex.
|
|
133
|
+
|
|
134
|
+
Then built an agent that helps early startups make hires they didn't think were possible.
|
|
135
|
+
|
|
136
|
+
We've placed candidates from Fortune 500 companies, SpaceX, and Apple at startups with 4-person teams.
|
|
137
|
+
|
|
138
|
+
13 founding engineer roles filled at early startups, including:
|
|
139
|
+
|
|
140
|
+
- Newton (YC24)
|
|
141
|
+
- Vitable Health (YC20)
|
|
142
|
+
- Plastic Labs
|
|
143
|
+
|
|
144
|
+
The whole thing is outcome-based, so you only pay when someone actually starts.
|
|
145
|
+
|
|
146
|
+
Two quick options:
|
|
147
|
+
|
|
148
|
+
a) 15-min call — find the uncommonly specific full-stack engineer who's the exact right fit for your team
|
|
149
|
+
|
|
150
|
+
b) see why Vince at Plastic Labs calls Superposition "a no-brainer" - we scanned 43,802 candidates to find 15 that matched traits no resume would show
|
|
151
|
+
|
|
152
|
+
superposition.ai/case-studies/how-plastic-labs-hired-founding-engineer
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## ✅ EXAMPLE OUTPUT 2 (role = iOS developer)
|
|
157
|
+
|
|
158
|
+
Hey Stefan,
|
|
159
|
+
|
|
160
|
+
Saw you posted for an iOS developer — I'm sure every recruiter on LinkedIn is already in your DMs.
|
|
161
|
+
|
|
162
|
+
But..
|
|
163
|
+
|
|
164
|
+
I placed the first engineering hire at Brex.
|
|
165
|
+
|
|
166
|
+
Then built an agent that helps early startups make hires they didn't think were possible.
|
|
167
|
+
|
|
168
|
+
We've placed candidates from Fortune 500 companies, SpaceX, and Apple at startups with 4-person teams.
|
|
169
|
+
|
|
170
|
+
13 founding engineer roles filled at early startups, including:
|
|
171
|
+
|
|
172
|
+
- Newton (YC24)
|
|
173
|
+
- Vitable Health (YC20)
|
|
174
|
+
- Plastic Labs
|
|
175
|
+
|
|
176
|
+
The whole thing is outcome-based, so you only pay when someone actually starts.
|
|
177
|
+
|
|
178
|
+
Two quick options:
|
|
179
|
+
|
|
180
|
+
a) 15-min call — find the uncommonly specific iOS developer who's the exact right fit for your team
|
|
181
|
+
|
|
182
|
+
b) see why Vince at Plastic Labs calls Superposition "a no-brainer" - we scanned 43,802 candidates to find 15 that matched traits no resume would show
|
|
183
|
+
|
|
184
|
+
superposition.ai/case-studies/how-plastic-labs-hired-founding-engineer
|
|
185
|
+
|
|
186
|
+
---
|
|
187
|
+
|
|
188
|
+
**ROLE VALIDATION RULES for {{role}}:**
|
|
189
|
+
|
|
190
|
+
1. Pull from "Jobs Hiring For" column
|
|
191
|
+
2. Always lowercase (e.g., "senior infrastructure engineer" not "Senior Infrastructure Engineer")
|
|
192
|
+
3. If multiple roles listed, pick the most senior or foundational engineering role
|
|
193
|
+
4. If no role data available, default to "engineer" — {{role}} must always refer to a person, never a job title phrase (e.g., never "engineering role")
|
|
194
|
+
5. Use the same {{role}} value in both the opener AND the CTA option (a)
|
|
195
|
+
6. {{a role}} in the opener = the role with the correct article prepended — use "a" or "an" based on the first letter of the role (e.g., "a full-stack engineer", "an iOS developer", "an engineer")
|
|
196
|
+
|
|
197
|
+
### Rubric Markdown
|
|
198
|
+
|
|
199
|
+
(none stored)
|
|
200
|
+
|
|
201
|
+
### Structured Lead Scoring Rubrics
|
|
202
|
+
|
|
203
|
+
(none stored)
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
## Superposition — Early-Stage Founders Hiring Sales & Growth
|
|
208
|
+
|
|
209
|
+
- Sent: 103
|
|
210
|
+
- Replied: 0
|
|
211
|
+
- Accepted: 12
|
|
212
|
+
- Updated: 2026-03-13T20:59:08.622Z
|
|
213
|
+
|
|
214
|
+
### Campaign Brief
|
|
215
|
+
|
|
216
|
+
# 15-Minute Call to Find Uncommonly Specific Sales Talent for Early-Stage Founders
|
|
217
|
+
|
|
218
|
+
## Campaign Objective
|
|
219
|
+
|
|
220
|
+
Launch campaign to **Founders/CEOs of early-stage startups (YC and non-YC)** who are **actively hiring for sales and growth roles** and offer them **a 15-minute call to find the uncommonly specific sales hire who's the exact right fit for their team, with outcome-based pricing (only pay when someone starts)**.
|
|
221
|
+
|
|
222
|
+
## Ideal Customer Profile (ICP)
|
|
223
|
+
|
|
224
|
+
- **Company type:** Early-stage startups (YC and non-YC) with small teams (typically 4-20 people)
|
|
225
|
+
- **Role & seniority:** Founders/CEOs — they own hiring at this stage
|
|
226
|
+
- **Hiring signal:** Actively posted for sales and growth roles (account executive, SDR, BDR, head of sales, VP of sales, head of growth, growth lead, revenue lead, GTM lead, sales lead)
|
|
227
|
+
- **Geography:** United States (focus on startup hubs: SF, NYC, Austin)
|
|
228
|
+
|
|
229
|
+
## Meeting Value (Offer)
|
|
230
|
+
|
|
231
|
+
In a 15-minute call, we'll discuss how to find the uncommonly specific sales or growth hire who's the exact right fit for your team — candidates from Fortune 500 companies, SpaceX, and Apple placed at startups with 4-person teams. Outcome-based pricing means you only pay when someone actually starts.
|
|
232
|
+
|
|
233
|
+
## Social Proof
|
|
@@ -0,0 +1,219 @@
|
|
|
1
|
+
# Superpower 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
|
+
## Early Detection for Self-Insured Employers
|
|
10
|
+
|
|
11
|
+
- Sent: 210
|
|
12
|
+
- Replied: 3
|
|
13
|
+
- Accepted: 56
|
|
14
|
+
- Updated: 2026-03-12T17:57:54.647Z
|
|
15
|
+
|
|
16
|
+
### Campaign Brief
|
|
17
|
+
|
|
18
|
+
# Early Detection Platform for Benefits Leaders at Self-Insured Companies
|
|
19
|
+
|
|
20
|
+
## Campaign Objective
|
|
21
|
+
|
|
22
|
+
Launch signal-based campaign to **benefits decision-makers** (Manager+) at **self-insured companies with 1,000-5,000 employees** who are actively engaging with employee wellness, benefits strategy, and preventive health content on LinkedIn. Offer them **early detection screening that surfaces health risks before they become claims**.
|
|
23
|
+
|
|
24
|
+
## Ideal Customer Profile (ICP)
|
|
25
|
+
|
|
26
|
+
- **Company type:** Self-insured employers with 1,000-5,000 employees
|
|
27
|
+
- **Role & seniority:** Benefits, Rewards, Wellness, or Well-Being decision-makers (Manager level and above - exclude analysts)
|
|
28
|
+
- **Signal:** Actively engaging with employee wellness, benefits strategy, and preventive health content on LinkedIn from thought leaders at Sequoia Consulting, Mercer, Marsh McLennan, Function Health, and similar
|
|
29
|
+
- **Geography:** United States (implied by self-insured focus)
|
|
30
|
+
- **Exclusions:** General HR, recruiters, agencies/brokers, companies under 1,000 employees, DNC list
|
|
31
|
+
|
|
32
|
+
## Meeting Value (Offer)
|
|
33
|
+
|
|
34
|
+
Signal-based outreach using peer-to-peer tone. Positioning Superpower as early detection tool (1,000+ conditions from a single blood draw) that surfaces health risks before they become claims for self-insured employers. Not a wellness perk - it's preventive health strategy that impacts the bottom line.
|
|
35
|
+
|
|
36
|
+
**VARIANT 1 — Subject: jeff/{{first name}} intro**
|
|
37
|
+
|
|
38
|
+
hey {{first name}}, saw you were active around some {{topic}} stuff recently and figured this might actually be relevant
|
|
39
|
+
|
|
40
|
+
any chance you're exploring early detection or preventive health programs at {{company}}?
|
|
41
|
+
|
|
42
|
+
we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
|
|
43
|
+
|
|
44
|
+
basically your team gets to see what's coming instead of just reacting to it
|
|
45
|
+
|
|
46
|
+
can I send over some more info?
|
|
47
|
+
|
|
48
|
+
**VARIANT 2 — Subject: jeff/{{first name}} intro**
|
|
49
|
+
|
|
50
|
+
hey {{first name}}. saw you were active in some {{topic}} conversations recently and wanted to run something by you
|
|
51
|
+
|
|
52
|
+
most annual physicals test 15 biomarkers max.
|
|
53
|
+
|
|
54
|
+
there's over 100 that actually matter and the gap between those two numbers is where the expensive claims tend to sit
|
|
55
|
+
|
|
56
|
+
teams like Lyft and Notion are already exploring this. one draw, 1,000+ conditions, $199 a person.
|
|
57
|
+
|
|
58
|
+
if your claims costs have been going up and you're not sure where it's coming from... that gap may be a good place to start looking
|
|
59
|
+
|
|
60
|
+
can I send over some more info?
|
|
61
|
+
|
|
62
|
+
## Examples
|
|
63
|
+
|
|
64
|
+
**Example 1 (Variant 1 — self-insured health plans):**
|
|
65
|
+
Subject: susana/prab intro
|
|
66
|
+
|
|
67
|
+
hey susana, saw you were active around self-insured health plan content recently and figured this might actually be relevant
|
|
68
|
+
|
|
69
|
+
any chance you're exploring preventive health programs at Quantum Health?
|
|
70
|
+
|
|
71
|
+
we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
|
|
72
|
+
|
|
73
|
+
basically your team gets to see what's coming instead of just reacting to it
|
|
74
|
+
|
|
75
|
+
can I send over some more info?
|
|
76
|
+
|
|
77
|
+
**Example 2 (Variant 2 — employee wellness programs):**
|
|
78
|
+
Subject: lisa/prab intro
|
|
79
|
+
|
|
80
|
+
hey lisa. saw you were active in some employee wellness programs conversations recently and wanted to run something by you
|
|
81
|
+
|
|
82
|
+
most annual physicals test 15 biomarkers max.
|
|
83
|
+
|
|
84
|
+
there's over 100 that actually matter and the gap is driving the surprise expensive claims every year
|
|
85
|
+
|
|
86
|
+
teams like Lyft and Notion are already exploring this. one test, 1,000+ conditions, $199 a person
|
|
87
|
+
|
|
88
|
+
can I send over some more info?
|
|
89
|
+
|
|
90
|
+
**Example 3 (Variant 1 — employee wellness programs):**
|
|
91
|
+
Subject: princess/prab intro
|
|
92
|
+
|
|
93
|
+
hey princess, saw you were active around employee wellness programs content recently and figured this might actually be relevant
|
|
94
|
+
|
|
95
|
+
any chance you're exploring preventive health programs at Marriott?
|
|
96
|
+
|
|
97
|
+
we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
|
|
98
|
+
|
|
99
|
+
basically your team gets to see what's coming instead of just reacting to it
|
|
100
|
+
|
|
101
|
+
can I send over some more info?
|
|
102
|
+
|
|
103
|
+
## Social Proof
|
|
104
|
+
|
|
105
|
+
Teams like Lyft and Notion are exploring Superpower's early detection platform. Superpower screens for 1,000+ conditions from a single blood draw at $199 per person, providing upstream visibility into employee health risks before they escalate into high-cost claims for self-insured employers.
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
**Campaign Strategy Notes:**
|
|
110
|
+
|
|
111
|
+
- **Signal-based targeting:** Only reach prospects actively engaging with relevant content
|
|
112
|
+
- **ICP filtering:** All prospects filtered against ICP criteria before entering send queue
|
|
113
|
+
- **Positioning:** Early detection tool for claims prevention, not a wellness benefit
|
|
114
|
+
- **Tone:** All lowercase, casual, peer-to-peer - building relationship before asking
|
|
115
|
+
- **Two approved variants:** Testing different hooks (exploratory vs. problem-aware)
|
|
116
|
+
|
|
117
|
+
### Rubric Markdown
|
|
118
|
+
|
|
119
|
+
(none stored)
|
|
120
|
+
|
|
121
|
+
### Structured Lead Scoring Rubrics
|
|
122
|
+
|
|
123
|
+
#### benefits_wellness_role
|
|
124
|
+
|
|
125
|
+
- Required: true
|
|
126
|
+
- Use for scoring: true
|
|
127
|
+
- Allow partial credit: true
|
|
128
|
+
- Strict matching: false
|
|
129
|
+
- Description: Checks if the prospect is in a benefits or wellness leadership role.
|
|
130
|
+
- Reason: We need decision-makers specifically responsible for employee health programs and preventive strategy.
|
|
131
|
+
- Criterion: YES if the title contains keywords like 'Benefits', 'Wellness', 'Total Rewards', 'Well-being', or 'Health Strategy'. NO if the title is strictly clinical (e.g., 'Physician', 'Surgeon') or general HR without a benefits focus.
|
|
132
|
+
|
|
133
|
+
#### seniority_manager_plus
|
|
134
|
+
|
|
135
|
+
- Required: true
|
|
136
|
+
- Use for scoring: true
|
|
137
|
+
- Allow partial credit: false
|
|
138
|
+
- Strict matching: false
|
|
139
|
+
- Description: Ensures the prospect has decision-making authority.
|
|
140
|
+
- Reason: The brief explicitly excludes analysts and targets Manager level and above.
|
|
141
|
+
- Criterion: YES if the title is 'Manager', 'Director', 'VP', 'Head', or 'SVP'. NO if the title includes 'Analyst', 'Coordinator', 'Associate', or 'Specialist'.
|
|
142
|
+
|
|
143
|
+
#### company_size_1k_5k
|
|
144
|
+
|
|
145
|
+
- Required: true
|
|
146
|
+
- Use for scoring: true
|
|
147
|
+
- Allow partial credit: false
|
|
148
|
+
- Strict matching: false
|
|
149
|
+
- Description: Filters for companies within the 1,000-5,000 employee range.
|
|
150
|
+
- Reason: This is the specific sweet spot for self-insured employers mentioned in the brief.
|
|
151
|
+
- Criterion: YES if the company has over 1,000 employees. NO if the company is smaller than 1,000
|
|
152
|
+
|
|
153
|
+
#### not_a_broker_or_agency
|
|
154
|
+
|
|
155
|
+
- Required: true
|
|
156
|
+
- Use for scoring: true
|
|
157
|
+
- Allow partial credit: false
|
|
158
|
+
- Strict matching: false
|
|
159
|
+
- Description: Excludes brokers, consultants, and agencies.
|
|
160
|
+
- Reason: We want to sell directly to the employers, not the intermediaries or agencies.
|
|
161
|
+
- Criterion: YES if the company is a corporate employer. NO if the company is an insurance brokerage, consulting firm (like Mercer, Marsh McLennan, Sequoia), or recruitment agency.
|
|
162
|
+
|
|
163
|
+
Also NO if the title contains 'Consultant Relations', 'Producer', 'Consultant' (when paired with an insurance/brokerage company), or if the company is a healthcare vendor/navigation company (like Quantum Health, Included Health, Accolade, Transcarent).
|
|
164
|
+
|
|
165
|
+
#### exclude_healthcare_vendors_carriers
|
|
166
|
+
|
|
167
|
+
- Required: true
|
|
168
|
+
- Use for scoring: true
|
|
169
|
+
- Allow partial credit: true
|
|
170
|
+
- Strict matching: false
|
|
171
|
+
- Description: Excludes healthcare vendors, carriers, and PBMs that sell to employers.
|
|
172
|
+
- Reason: These companies are competitors or service providers to the target audience, not the target buyers themselves.
|
|
173
|
+
- Criterion: YES if the company is a corporate employer (self-insured). NO if the company is a healthcare technology vendor, health navigation company, health insurance carrier (e.g., UnitedHealthcare, Aetna, Cigna, Blue Cross, Kaiser Permanente), or Pharmacy Benefit Manager (PBM).
|
|
174
|
+
|
|
175
|
+
These are vendors selling to employers, not the target buyers.
|
|
176
|
+
|
|
177
|
+
---
|
|
178
|
+
|
|
179
|
+
## Early Detection for Self-Insured Benefits Leaders
|
|
180
|
+
|
|
181
|
+
- Sent: 273
|
|
182
|
+
- Replied: 1
|
|
183
|
+
- Accepted: 39
|
|
184
|
+
- Updated: 2026-03-16T19:08:53.120Z
|
|
185
|
+
|
|
186
|
+
### Campaign Brief
|
|
187
|
+
|
|
188
|
+
# Free Claims Risk Audit for Self-Insured Benefits Leaders
|
|
189
|
+
|
|
190
|
+
## Campaign Objective
|
|
191
|
+
|
|
192
|
+
Launch campaign to **Benefits Leaders and HR executives** who work at **self-insured companies with 500+ employees** and offer them early detection health screening that identifies expensive claims before they happen.
|
|
193
|
+
|
|
194
|
+
## Ideal Customer Profile (ICP)
|
|
195
|
+
|
|
196
|
+
- **Company type:** Self-insured employers (tech companies, large enterprises)
|
|
197
|
+
- **Role & seniority:** VP/Director of Benefits, VP/Director of HR, Total Rewards Leaders
|
|
198
|
+
- **Company size:** 500+ employees
|
|
199
|
+
- **Geography:** United States
|
|
200
|
+
|
|
201
|
+
## Meeting Value (Offer)
|
|
202
|
+
|
|
203
|
+
In a 15-minute call, we'll review your current preventive health coverage and show you where the gaps are that typically lead to expensive claims—so you can see what's coming instead of just reacting to it.
|
|
204
|
+
|
|
205
|
+
## Social Proof
|
|
206
|
+
|
|
207
|
+
Teams like Lyft and Notion are already using early detection screening. One blood draw screens for 1,000+ conditions (vs. the 15 biomarkers in typical annual physicals) and tends to pay for itself in year one.
|
|
208
|
+
|
|
209
|
+
## Messaging Templates
|
|
210
|
+
|
|
211
|
+
### Variant 1 — Control
|
|
212
|
+
|
|
213
|
+
**Subject: Prab/{{first_name}} intro**
|
|
214
|
+
|
|
215
|
+
Hey {{first_name}}, not sure if you've looked into this but felt it may be relevant to your work.
|
|
216
|
+
|
|
217
|
+
have you ever looked into early detection or preventive health programs for {{company}}?
|
|
218
|
+
|
|
219
|
+
we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
|