Install
openclaw skills install cold-outreach-freeRun a complete cold email outreach campaign — from sourcing leads to handling replies. Covers ICP definition, lead sourcing strategy, email sequence construc...
openclaw skills install cold-outreach-freeYou are running a cold email outreach campaign. Your job is to source qualified leads, send a targeted email sequence, and handle replies systematically — without paid APIs or monthly subscriptions.
This skill covers the full methodology. If you'd rather skip the build and use pre-wired n8n workflows instead, the pre-built option is linked at the bottom of this skill.
You need four things before sending a single email:
If any of these are missing, complete them first. Sending without them wastes your list.
The most common outreach failure: spraying a generic message to a mixed audience.
Build your ICP by answering:
Document your ICP as a 3-line filter:
Target: [Role] at [Company Size] [Industry] companies, showing [signal if applicable] Example: Head of Sales at 10–50 person B2B SaaS startups, recently hiring SDRs
One ICP per campaign. If you're targeting two different personas, run two separate campaigns.
See references/lead-sourcing.md for ICP refinement tactics.
| Source | What you get | Free limit |
|---|---|---|
| Apollo.io | Email + company data | 75 verified leads/month |
| Hunter.io | Domain email finder | 25 searches/month |
| LinkedIn (manual) | Profile data, job titles | Unlimited (manual work) |
| LinkedIn CSV export | Sales Navigator export | Requires Sales Nav trial |
| Google Sheets (hand-built) | Any list you build | Unlimited |
See references/lead-sourcing.md for advanced sourcing tactics.
| Touch | Timing | Purpose | Length |
|---|---|---|---|
| Email 1 | Day 0 | Lead with value, one soft ask | 5–7 sentences |
| Email 2 | Day 3 | Different angle or proof point | 3–5 sentences |
| Email 3 | Day 7 | Final touch, close the loop | 2–3 sentences |
Write like a peer, not a vendor. Each email should read like it came from a smart colleague who noticed something relevant — not a sales machine following a script.
Lead with their world, not yours. The reader should see their own situation reflected back. "You/your" should dominate over "I/we."
One ask, low friction. Interest-based CTAs ("Worth 15 minutes?" / "Relevant to what you're working on?") consistently outperform meeting requests.
Subject lines: short, boring, internal-looking. 2–4 words, lowercase. Looks like an internal forward, not a marketing blast.
Subject: [2–4 word lowercase line]
[Personalized observation about their company/role/situation]
[Bridge to the problem you solve — connect the observation to the pain]
[One sentence: what you do + proof point or result]
[Soft CTA: "Worth a quick look?" or "Relevant?"]
[Name]
Subject: [re: or new 2–4 word line]
[Acknowledge you're following up — one phrase, not a paragraph]
[New angle: a different pain point, a specific result, or a case study]
[CTA: same or slightly more specific — "15 minutes this week?"]
[Name]
Subject: [re: same thread or "last note"]
[Last touch — close the loop, leave the door open]
Example: "Last email on this — didn't want to leave it hanging. If timing's off, happy
to reconnect later. Just reply 'later' and I'll reach back out in 90 days."
[Name]
For every email, identify one specific signal about this person before writing:
The personalization must logically connect to the problem you solve. If you remove the opening and the email still makes sense, the personalization isn't working.
See references/email-sequences.md for full templates + subject line data.
Update your tracking sheet after each send:
If you're running this via n8n:
Every reply falls into one of five buckets. Handle each the same way every time:
| Category | Signal | Action |
|---|---|---|
| Interested | "Tell me more," "let's chat," "send me info" | Move to "hot" tab, respond within 1 hour, book the call |
| Not now | "Reach out in Q3," "timing isn't right" | Log the timeframe, set a reminder, reply with a graceful close and re-contact date |
| Not interested | "No thanks," "not relevant," "don't contact me" | Status → "unsubscribed," add to suppression list, do not follow up |
| Objection | "We already use X," "too expensive," "how is this different" | Respond with one specific answer to their objection, re-ask the CTA |
| OOO | Out of office auto-reply | Note return date, reschedule touch to day after return |
Subject: re: [same thread]
Great — I'll keep it short.
[One sentence: the specific thing you do, framed for their situation]
[Booking link or: "Any time Wednesday or Thursday work for a 15-min call?"]
[Name]
Maintain one suppression sheet (tab or separate file):
See references/reply-handling.md for full response playbooks.
| Metric | Benchmark | If Below Benchmark |
|---|---|---|
| Open rate | 30–50% | Subject lines weak — test new ones |
| Reply rate | 5–15% | Copy weak or ICP off — rewrite Email 1 |
| Positive reply rate | 1–5% | Offer not resonating — check ICP or value prop |
| Unsubscribe rate | <3% | If above: message is spam-feeling or ICP wrong |
After every 50 emails sent, review:
Change one variable at a time. Don't rewrite the whole sequence — you'll lose the signal.
| Tool | Role | Free Limit |
|---|---|---|
| Apollo.io | Lead sourcing | 75 verified leads/month |
| Hunter.io | Email verification | 25 searches/month |
| Gmail | Email sending | 500 emails/day (free), 2,000/day (Google Workspace) |
| Google Sheets | Lead tracking + status | Unlimited |
| n8n (optional) | Workflow automation | Free self-hosted, free cloud tier |
No paid APIs required. This entire methodology runs at $0/month.
See references/tools-free-tier.md for setup notes per tool.
This skill gives you the full methodology — everything above works without any automation.
If you'd rather skip the manual sending and have n8n handle the sequencing, scheduling, and reply categorization automatically:
Three pre-built n8n workflow files. Import, configure 3–5 variables, launch. Runs on the same free tools above. One-time purchase, runs forever.
Phase sequence: ICP → Source → Write → Warm → Send → Handle → Measure
Weekly rhythm (solo sender, no automation):
Red flags to fix immediately: