@opendirectory.dev/skills 0.1.0

package/skills/outreach-sequence-builder/README.md

@@ -0,0 +1,108 @@
+# outreach-sequence-builder
+
+<img width="1280" height="640" alt="outreach-sequence-builder" src="https://github.com/user-attachments/assets/3d73358a-52ca-48e7-b34e-b1ba33246d6e" />
+
+
+Turn a buying signal into a ready-to-send multi-channel outreach sequence. Give the skill a signal and it generates 4-6 personalized touchpoints across email, LinkedIn, and phone, with objection pre-emption built in.
+
+## What It Does
+
+- Identifies the signal type from 7 categories: Post-Fundraise, Hiring Signal, Competitor Displacement, Product Launch, Content Engagement, Event Follow-up, Job Change
+- Loads your ICP from docs/icp.md or asks 4 questions to define target persona and pain points
+- Develops the Insight, Bridge, Opener, and Ask for the specific signal
+- Plans a 4-6 touchpoint channel sequence over 10-14 days
+- Generates all messages with Gemini, enforcing hard limits (100-word emails, 300-character LinkedIn notes, 20-word phone openers)
+- Pre-empts 2-4 objections woven into existing touchpoints
+- Runs a 13-point QA pass before presenting the sequence
+- Saves the sequence to docs/sequences/ and optionally drafts emails in Gmail via Composio
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Sequence generation | aistudio.google.com, Get API key |
+| Composio API key (optional) | Gmail draft creation | app.composio.dev, API Keys |
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Fill in:
+- `GEMINI_API_KEY` (required)
+- `COMPOSIO_API_KEY` (optional, for Gmail draft creation)
+
+Optional: create `docs/icp.md` with your target personas, company profile, pain points, and differentiators. If the file does not exist, the skill asks 4 questions before generating.
+
+## How to Use
+
+Basic sequence from a signal:
+
+```
+"Build an outreach sequence for a prospect who just raised a Series B"
+"They're hiring 8 engineers — write me a sequence"
+"Create outreach based on this signal: they just launched a new product"
+```
+
+With contact context:
+
+```
+"Build an outreach sequence for Sarah Chen, VP Sales at Momentum CRM — they just raised $22M Series B"
+"They switched from Salesforce and posted a frustrated LinkedIn comment. Write a competitor displacement sequence."
+```
+
+With Gmail drafting:
+
+```
+"Build a post-fundraise sequence and draft the emails in Gmail"
+```
+
+## Signal Types
+
+| Signal | Definition | Window |
+|--------|-----------|--------|
+| Post-Fundraise | Company raised a round in the last 30 days | 48 hours from announcement |
+| Hiring Signal | Company posted 5 or more roles in a function you serve | Within the week posts appear |
+| Competitor Displacement | Contact is using a competitor and showing frustration | Within 24 hours |
+| Product Launch | Company launched a new product or major feature | 2-4 weeks after launch |
+| Content Engagement | Contact liked, commented, or shared your content | Start on LinkedIn first |
+| Event Follow-up | You met at a conference or webinar | Within 48 hours of event |
+| Job Change | Contact moved to a new company in the last 60 days | Within 2 weeks of announcement |
+
+## Message Rules
+
+- Only `{{first_name}}` is allowed as a variable. All other details must be filled in from context.
+- Email bodies: 100 words maximum.
+- LinkedIn notes: 300 characters maximum.
+- Phone openers: 20 words maximum.
+- No placeholders like `[Company Name]` or `[INSERT PAIN POINT]`. If the information is not available, the skill asks before writing.
+
+## Output
+
+The sequence is saved to `docs/sequences/{signal-type}.md`. Each touchpoint includes:
+
+- Channel and day number
+- Two subject line variants (email)
+- Message body
+- Word count (email) or character count (LinkedIn)
+- Phone talk track with voicemail script
+
+## Project Structure
+
+```
+outreach-sequence-builder/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── signal-playbook.md
+    ├── sequence-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/outreach-sequence-builder/SKILL.md

@@ -0,0 +1,248 @@
+---
+name: outreach-sequence-builder
+description: Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone. Outputs 4-6 ready-to-send touchpoints over 10-14 days. Optionally drafts email touchpoints via Composio Gmail. Use when asked to write an outreach sequence, build a sales cadence, create a follow-up sequence, personalize outreach for a signal, or generate cold outreach messages. Trigger when a user says "build an outreach sequence for", "write a sales cadence for", "create outreach based on this signal", "they just raised a round write me a sequence", or "generate personalized outreach for".
+compatibility: [claude-code, gemini-cli, github-copilot]
+author: OpenDirectory
+version: 1.0.0
+---
+
+# Outreach Sequence Builder
+
+Take a buying signal. Generate a personalized multi-channel outreach sequence. Output ready-to-send messages across email, LinkedIn, and phone.
+
+---
+
+**Critical rule:** Every message must be filled in completely from the context you load. Only `{{first_name}}` is allowed as a variable. No `[Company Name]` brackets, no `[INSERT PAIN POINT]` placeholders. If you do not have the information to fill something in, ask before writing. Never send a message with an unfilled placeholder.
+
+---
+
+## Step 1: Setup Check
+
+Confirm required env vars:
+
+```bash
+echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
+echo "COMPOSIO_API_KEY: ${COMPOSIO_API_KEY:-not set, Gmail drafting will be skipped}"
+```
+
+**If GEMINI_API_KEY is missing:**
+Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
+
+**If COMPOSIO_API_KEY is missing:**
+Continue. Sequences will be output as formatted text for copy-paste. Gmail draft creation is skipped.
+
+---
+
+## Step 2: Load Context
+
+Check for an existing ICP file and account files:
+
+```bash
+ls docs/icp.md 2>/dev/null && echo "icp found" || echo "icp missing"
+ls docs/accounts/ 2>/dev/null && echo "accounts found" || echo "accounts missing"
+```
+
+**If docs/icp.md exists:** Read it. Extract:
+- Target personas (job titles, seniority, department)
+- Company profile (size, industry, funding stage)
+- Core pain points (use the buyer's exact language)
+- Key differentiators (why your product over alternatives)
+
+**If docs/accounts/{company}.md exists:** Read the relevant file. Extract:
+- Company name, size, recent context
+- Known tech stack or pain points
+- Any existing relationship or prior contact
+
+**If neither exists:** Ask the user these 4 questions. Do not proceed until all 4 are answered:
+1. What does your product do? (one or two sentences)
+2. Who are you targeting? (job title, company size, industry)
+3. What is the main problem you solve? (from the buyer's perspective, not yours)
+4. What is your key differentiator? (why you over the alternative they use today)
+
+---
+
+## Step 3: Identify the Signal
+
+Determine which of the 7 signal types applies. Read `references/signal-playbook.md` for the full Insight, Bridge, Opener, and Ask for each signal type.
+
+**7 signal types:**
+
+| Signal | Definition |
+|--------|-----------|
+| Post-Fundraise | Company raised a funding round in the last 30 days |
+| Hiring Signal | Company posted 5 or more roles in a function you serve |
+| Competitor Displacement | Contact is using a competitor and showing frustration |
+| Product Launch | Company launched a new product or major feature |
+| Content Engagement | Contact liked, commented, or shared your content |
+| Event Follow-up | You met or were in the same session at a conference or webinar |
+| Job Change | Contact moved to a new company in the last 60 days |
+
+**If the user provided a signal in their prompt:** Confirm the type and extract the specific details (round size, role titles, product name, event name, etc.).
+
+**If no signal is clear:** Ask: "What triggered this outreach? (e.g. they raised a round, they're hiring engineers, you met at an event)"
+
+State the detected signal type and the specific detail before proceeding.
+
+---
+
+## Step 4: Develop the Angle
+
+Using the signal type and context loaded in Steps 2-3, define the four angle elements. Read `references/signal-playbook.md` for the formula for this signal type.
+
+Write out explicitly before generating any messages:
+
+```
+Signal: [specific signal + concrete detail]
+Insight: [what this signal reveals about their situation]
+Bridge: [how your product connects to what the signal reveals]
+Opener: [one sentence referencing the specific signal detail]
+Ask: [minimum viable CTA, under 10 words]
+```
+
+The opener must name the specific trigger. Vague openers are rejected.
+
+Good: "Congrats on the $18M Series B — scaling the sales team fast usually creates an onboarding gap."
+Bad: "I saw your company recently raised funding."
+
+---
+
+## Step 5: Plan the Channel Sequence
+
+Design 4-6 touchpoints across email, LinkedIn, and phone. Rules:
+
+- Total duration: 10-14 days
+- Minimum gap: 2 days between any two touches
+- Never use the same channel twice in a row
+- Each follow-up must add new value (new resource, new angle, new proof point). Never "just following up".
+- The final touchpoint is a short breakup message
+
+Default cadence for most signals:
+
+```
+Day 1:  Email (first touch, signal-led opener)
+Day 3:  LinkedIn (connection note or short DM)
+Day 7:  Email (new angle or case study)
+Day 9:  Phone (talk track + voicemail script)
+Day 12: Email (different framing or objection addressed)
+Day 14: Email (short breakup message)
+```
+
+Adjust for signal type:
+- Post-Fundraise: move faster (Day 1, 2, 4, 7, 10). Act within 48 hours of announcement.
+- Event Follow-up: start with LinkedIn, not email (warmer channel first)
+- Content Engagement: start with LinkedIn reply or comment before email
+
+State the planned day and channel for each touchpoint before writing messages.
+
+---
+
+## Step 6: Generate the Sequence
+
+Read `references/sequence-format.md` in full. Read `references/output-template.md` and select the template for this signal type.
+
+Write the Gemini request to a temp file:
+
+```bash
+cat > /tmp/outreach-sequence-request.json << 'ENDJSON'
+{
+  "system_instruction": {
+    "parts": [{
+      "text": "You are a B2B sales copywriter who writes cold outreach that gets replies. Rules: The first sentence of every message is about THEM, not your company. Reference the specific buying signal by name and detail in the opening message. Use contractions naturally. Short sentences. No corporate jargon. No banned words: synergy, leverage, touch base, circle back, ping, loop in, alignment, innovative, cutting-edge, best-in-class, world-class, game-changing, disruptive, bandwidth, deep dive, low-hanging fruit, move the needle. No pleasantries: no 'I hope this email finds you well', no 'Happy Monday', no 'Just wanted to'. Each follow-up adds new value — never 'just following up'. Hard limits: email body under 100 words, LinkedIn note under 300 characters, phone opener under 20 words. Only {{first_name}} is allowed as a variable — fill in all other details from the context provided. The breakup message is short (3-4 sentences), friendly, and leaves the door open."
+    }]
+  },
+  "contents": [{
+    "parts": [{
+      "text": "CONTEXT_AND_INSTRUCTIONS_HERE"
+    }]
+  }],
+  "generationConfig": {
+    "temperature": 0.7,
+    "maxOutputTokens": 4096
+  }
+}
+ENDJSON
+curl -s -X POST \
+  "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=$GEMINI_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d @/tmp/outreach-sequence-request.json \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['candidates'][0]['content']['parts'][0]['text'])"
+```
+
+Replace `CONTEXT_AND_INSTRUCTIONS_HERE` with:
+- The product description, target persona, pain points, and differentiators from Step 2
+- The signal type, specific detail, and the four angle elements from Step 4
+- The channel plan from Step 5
+- Instructions to write each touchpoint with its subject line (email), character count (LinkedIn), and talk track (phone)
+
+For each email touchpoint, require two subject line variants (A/B test).
+
+---
+
+## Step 7: Map Objections
+
+After generating the sequence, identify the 2-4 most likely objections for this signal type. Pre-empt each one naturally within an existing touchpoint. Do not add separate objection-handling messages. Weave the pre-emption into the sequence.
+
+Read the objection playbook in `references/sequence-format.md`. Map which touchpoint handles each objection.
+
+**4 standard objections to pre-empt:**
+
+| Objection | Pre-emption approach |
+|-----------|---------------------|
+| "We already have a solution" | Acknowledge their current tool, position yours as complementary or next step |
+| "Not the right time" | Tie the signal directly to why now is the right time |
+| "Too expensive" | Frame ROI, anchor to a number they care about |
+| "Need to involve more people" | Offer a shareable resource (one-pager, recorded walkthrough) |
+
+State which touchpoint handles each objection before presenting the final sequence.
+
+---
+
+## Step 8: Self-QA
+
+Run every check and fix violations before presenting:
+
+- [ ] Every message starts with a sentence about THEM
+- [ ] The specific signal detail is named in at least the first touchpoint
+- [ ] No unfilled placeholders except `{{first_name}}`
+- [ ] Email bodies are under 100 words (count and state the word count for each)
+- [ ] LinkedIn notes are under 300 characters (count and state for each)
+- [ ] Phone opener is under 20 words
+- [ ] No banned words in any message
+- [ ] No "just following up" in any follow-up
+- [ ] Each follow-up adds a new angle or value
+- [ ] No same channel used twice in a row
+- [ ] At least 2 objections pre-empted across the sequence
+- [ ] Breakup message is 3-4 sentences, friendly, no guilt
+
+Fix any violation before presenting.
+
+---
+
+## Step 9: Output and Save
+
+Present the full sequence in a code block.
+
+**Save to file:**
+```bash
+mkdir -p docs/sequences
+cat > docs/sequences/SIGNAL-TYPE.md << 'EOF'
+SEQUENCE_CONTENT_HERE
+EOF
+echo "Sequence saved to docs/sequences/SIGNAL-TYPE.md"
+```
+
+**If COMPOSIO_API_KEY is set:** Ask: "Draft the email touchpoints in Gmail via Composio?"
+
+On confirmation, for each email touchpoint:
+```bash
+# The agent calls the GMAIL_CREATE_EMAIL_DRAFT Composio action
+# with subject = [subject line], body = [email body], recipient = [contact email if known]
+```
+
+After drafting: "Email drafts created in Gmail. Check your Drafts folder."
+
+**LinkedIn notes:** Present as separate copy-paste blocks with a clear label per touchpoint. LinkedIn does not support programmatic messaging.
+
+**Phone scripts:** Present as a formatted talk track with bullet points, not a rigid script.
+
+

package/skills/outreach-sequence-builder/evals/evals.json

@@ -0,0 +1,36 @@
+{
+  "skill_name": "outreach-sequence-builder",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Build an outreach sequence for Sarah Chen, VP of Sales at Momentum CRM. They just raised a $22M Series B. My product is Ramp, a sales onboarding platform. I help B2B SaaS VP Sales scale ramp time when they grow past 20 reps. Pain point: new reps take too long to hit their first deal. Differentiator: structured playbooks plus live deal coaching, not just content libraries.",
+      "expected_output": "Agent checks GEMINI_API_KEY — set. No docs/icp.md found; uses the context provided in the prompt. Identifies signal type as Post-Fundraise with specific detail '$22M Series B at Momentum CRM.' Writes out all four angle elements: Insight (funding means hiring pressure and ramp bottleneck), Bridge (Ramp shortens time-to-first-deal), Opener (names $22M Series B), Ask (15 minutes to see if we can shorten ramp). Plans 5-touchpoint sequence on Day 1 (Email), Day 2 (LinkedIn), Day 4 (Email), Day 7 (Phone), Day 10 (Email), Day 14 (Email — breakup). Generates all messages with Gemini using the research context. QA pass: all emails under 100 words with word count stated, LinkedIn under 300 characters with count stated, phone opener under 20 words, no banned words, no unfilled placeholders except {{first_name}}, at least 2 objections pre-empted. Saves to docs/sequences/post-fundraise.md. Asks if user wants Gmail drafts created.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write a sales cadence for a prospect who left a frustrated comment about HubSpot's reporting. Their name is Marcus Webb, RevOps Lead at DataStream. My product is Visible, a pipeline analytics platform. Pain point: CRM reporting requires too much manual work. Differentiator: auto-syncs with HubSpot and Salesforce, no manual cleanup needed.",
+      "expected_output": "Agent identifies signal type as Competitor Displacement (HubSpot frustration). Notes that this signal requires a fast first touch (within 24 hours). Opener references the specific frustration (HubSpot reporting requiring manual work). Plans a 5-touchpoint sequence starting with LinkedIn (not email) since the signal came from LinkedIn. Sequence: Day 1 (LinkedIn — reply or comment on the post first, then DM), Day 3 (Email), Day 6 (Phone), Day 9 (Email), Day 12 (Email — breakup). All LinkedIn messages under 300 characters. All emails under 100 words. Touch 3 pre-empts 'we already have a solution' by acknowledging HubSpot and positioning Visible as complementary. No 'just following up' in any message. No banned words. Sequence saved to docs/sequences/competitor-displacement.md.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Build an outreach sequence for a job change signal. Alex Rivera just became Head of Growth at Finova. I know from LinkedIn they led PLG growth at their previous company. My product is June.so, a product analytics platform for PLG teams. Pain point: growth teams at Series A companies can't see activation drop-off without a data engineer. Differentiator: self-serve setup, no data engineer needed.",
+      "expected_output": "Agent identifies signal type as Job Change. Notes the 60-day window and that first touch should happen within 2 weeks of the announcement. Opener references the move to Finova and Alex's PLG background specifically. Angle: Insight is that new Head of Growth has a mandate to prove PLG motion works at Finova. Bridge is that June.so lets them instrument activation without waiting for engineering. Plans standard 6-touchpoint sequence. Touch 1 Email: congrats on the move, references their PLG background and Finova's stage. Touch 2 LinkedIn: connection note under 300 characters. All QA checks pass. Sequence saved to docs/sequences/job-change.md. Composio not configured. Sequences output as formatted text only.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Generate cold outreach messages for a post-fundraise signal but do not include the email drafting step.",
+      "expected_output": "Agent detects GEMINI_API_KEY is missing from environment. Stops at Step 1. Tells the user: 'GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file.' Does not proceed to generate any messages.",
+      "files": [],
+      "setup": "GEMINI_API_KEY not set in environment"
+    },
+    {
+      "id": 5,
+      "prompt": "Create a sequence for Priya Nair, Director of Marketing at GrowthLoop. They posted a case study about their new AI segmentation feature. My product is Copy.ai, an AI writing assistant for marketing teams. We help marketing teams turn campaign briefs into copy 10x faster. Pain point: content production can't keep up with campaign volume. Differentiator: trained on brand voice from past campaigns, not generic prompts.",
+      "expected_output": "Agent identifies signal type as Product Launch (new AI segmentation feature). Opener references the GrowthLoop AI segmentation case study specifically by name. Angle: Insight is that a major feature launch requires marketing content across channels to drive awareness and adoption. Bridge is that Copy.ai removes the bottleneck between the campaign idea and copy going live. Plans standard 5-6 touchpoint sequence. Gemini generates all messages with no unfilled placeholders — all company, product, and contact details are filled in. QA pass confirms: each email under 100 words, word count stated for each, LinkedIn note under 300 characters, character count stated, phone opener under 20 words, no banned words (including 'innovative' and 'game-changing'), at least 2 objections pre-empted, breakup is 3-4 sentences and leaves the door open. Sequence saved to docs/sequences/product-launch.md.",
+      "files": []
+    }
+  ]
+}

package/skills/outreach-sequence-builder/references/output-template.md

@@ -0,0 +1,171 @@
+# Output Template
+
+One template for all signal types. The structure is fixed. Fill in all brackets from context. No brackets should appear in the final output.
+
+---
+
+## Sequence Header
+
+```
+# Outreach Sequence: [Signal Type] — [Company Name]
+
+**Contact:** [First name, last name, title. Write "Not specified" if unknown.]
+**Signal:** [Specific signal detail. Example: "Raised $18M Series B on April 3, 2026"]
+**Product:** [Your product, one sentence]
+**Target persona:** [Job title, company size, industry]
+
+**Angle:**
+- Insight: [What the signal reveals about their situation]
+- Bridge: [How your product connects to that situation]
+- Opener: [One sentence naming the specific signal trigger]
+- Ask: [CTA under 10 words]
+
+**Objection mapping:**
+- Touch X handles: [objection 1]
+- Touch Y handles: [objection 2]
+```
+
+---
+
+## Touchpoint Template
+
+```
+### Day [N] — [Channel: Email / LinkedIn / Phone]
+
+**Subject A:** [subject line variant A, under 8 words]
+**Subject B:** [subject line variant B, under 8 words]
+[subject lines for email only; omit for LinkedIn and Phone]
+
+[Message body]
+
+---
+[Word count: X words] [for email]
+[Character count: X characters] [for LinkedIn]
+```
+
+---
+
+## Worked Example
+
+**Signal type:** Post-Fundraise
+**Company:** Momentum CRM
+**Contact:** Sarah Chen, VP of Sales
+**Signal:** Raised $22M Series B on April 1, 2026
+**Product:** Ramp, sales onboarding and enablement platform
+**Target:** VP Sales, 50-500 employees, B2B SaaS
+
+---
+
+```
+# Outreach Sequence: Post-Fundraise — Momentum CRM
+
+**Contact:** Sarah Chen, VP of Sales
+**Signal:** Raised $22M Series B on April 1, 2026
+**Product:** Ramp, sales onboarding and enablement platform for B2B SaaS teams scaling past 20 reps
+**Target persona:** VP Sales, 50-500 employees, B2B SaaS
+
+**Angle:**
+- Insight: A $22M Series B means Momentum is hiring. New reps need to ramp fast or the round's growth targets slip.
+- Bridge: Ramp cuts new hire time-to-first-deal by shortening the onboarding cycle with structured playbooks and live deal coaching.
+- Opener: "Congrats on the $22M Series B — fast-growing sales teams usually hit a ramp problem before the new hires hit their number."
+- Ask: "Worth 15 minutes to see if we can shorten ramp?"
+
+**Objection mapping:**
+- Touch 3 handles: "We already have a solution" (acknowledges their current LMS, positions Ramp as complementary)
+- Touch 4 handles: "Need to involve more people" (offers shareable one-pager before they ask)
+```
+
+---
+
+### Day 1 — Email
+
+**Subject A:** Series B congrats — one question on ramp
+**Subject B:** $22M and hiring fast — seen this problem before
+
+{{first_name}}, congrats on the $22M Series B.
+
+Momentum is clearly in a hiring phase now. Most VP Sales I talk to at this stage say the same thing: the reps are hired, but 90-day ramp is the bottleneck that kills the year's number.
+
+We help B2B SaaS sales teams cut ramp time by 30% with structured playbooks and live deal coaching.
+
+Worth 15 minutes to see if it fits where you are now?
+
+[Name]
+
+---
+Word count: 72 words
+
+---
+
+### Day 2 — LinkedIn
+
+Hi Sarah, congrats on the Series B. I work with VP Sales teams scaling past 20 reps — ramp time is usually the first thing that breaks. Built something that might be relevant. Mind if I send a quick note?
+
+---
+Character count: 232 characters
+
+---
+
+### Day 4 — Email
+
+**Subject A:** How Lattice cut new rep ramp by 5 weeks
+**Subject B:** One thing that changes at 20+ reps
+
+{{first_name}}, most teams scaling past 20 reps run onboarding off slide decks and Notion docs. Works until it doesn't.
+
+Lattice was in the same spot at Series B. They moved to structured playbooks and live deal coaching. New reps hit their first deal 5 weeks faster in the first quarter after rollout.
+
+Happy to share the breakdown if it's useful.
+
+[Name]
+
+---
+Word count: 68 words
+
+---
+
+### Day 7 — Phone
+
+**Opening line:** Sarah, calling because Momentum just raised a round and ramp time usually becomes the first bottleneck.
+
+**Talk track:**
+- Context: We help VP Sales teams scale onboarding when they go from 10 to 30 reps — structured playbooks and live deal coaching replace the "follow a senior rep" approach that breaks at scale.
+- Value: Lattice cut new hire time-to-first-deal by 5 weeks after switching from Notion-based onboarding.
+- Ask: Is ramp on your radar for the next 90 days, or is headcount the bigger focus right now?
+
+**Voicemail script:**
+"Sarah, it's [Name] from Ramp. I'm calling because Momentum just closed the Series B and fast-growing sales teams usually hit a ramp problem before they hit their targets. We helped Lattice cut time-to-first-deal by 5 weeks — happy to show you how. [Phone number]. No pressure."
+
+---
+
+### Day 10 — Email
+
+**Subject A:** Not sure if this is a fit — honest question
+**Subject B:** Sales team running off Notion docs still?
+
+{{first_name}}, I want to be straight with you.
+
+If Momentum already has a structured onboarding program built out, we are probably not the right fit right now. Most teams at your stage are using a mix of Highspot or Seismic for content and nothing purpose-built for ramp.
+
+If that sounds familiar, I'd love 20 minutes. I can send a one-pager you can share with your ops or RevOps lead before we talk.
+
+[Name]
+
+---
+Word count: 81 words
+
+---
+
+### Day 14 — Email (Breakup)
+
+**Subject A:** Closing the loop
+**Subject B:** Leaving it with you
+
+{{first_name}}, I'll stop reaching out so I'm not cluttering your inbox.
+
+If ramp becomes a priority as you scale the team post-Series B, I'd love to reconnect. The door is open whenever the timing works.
+
+[Name]
+
+---
+Word count: 41 words