Pipeline

# Lead Generator & Tracker (WordPilot.pro)

Use this playbook to research, qualify, track, and professionally convert leads for WordPilot.pro — an AI-powered writing workspace. This skill operates on a **daily cadence**: each day you check in, WordPilot reports progress, researches new leads, advances existing ones, and produces an updated daily board.

This skill is designed for **sustained, professional lead generation** — not mass blasting. Every lead gets context, every outreach feels human, and every follow-up is tracked.

## Core Philosophy

1. **Research before reaching out.** Never cold-contact someone without understanding their context, work, and why WordPilot might genuinely help them.
2. **Value-first, never salesy.** Position WordPilot as a tool that solves real problems — not a "deal" to jump on.
3. **Slow is smooth.** The conversion pipeline is 5 stages; leads advance when they show real interest, not when a timer expires.
4. **Everything is tracked.** The `/leads/` workspace folder is the single source of truth.
5. **Daily accountability.** Every session produces a concrete update to the daily board.

## When to Apply

- User says "how's lead gen going?", "show me today's leads", "find new leads", "check the pipeline", or similar.
- User opens the workspace and the daily board needs updating.
- User asks to research a specific segment, industry, or persona.
- User wants to draft outreach to a specific lead or stage.
- User wants to review conversion metrics or pipeline health.

## Preconditions

- Gmail should be connected (via Integrations → Composio) for outreach and tracking. If not connected, research and qualification still proceed — but outreach steps will be drafted for review rather than sent.
- Google Sheets or Notion are optional but recommended for external CRM sync. If connected, leads can sync bidirectionally.
- Composio Search and Browser Tool are used for deep lead research — both are pre-connected on WordPilot.

## Conversion Pipeline (6 Stages)

Every lead moves through these stages. Movement between stages is deliberate, not automatic.

### Stage 1 — Discovered
Lead has been identified through research. Basic info captured: name, role, company, why they might need WordPilot. No outreach yet.

### Stage 2 — Researched  
Deep context gathered: recent work, pain points, public content, team size, tech stack, current tools. A "hook" identified — something specific that connects their work to WordPilot's value.

### Stage 3 — Qualified
Lead meets qualification criteria: decision-making authority or influence, active in relevant space (writing, documentation, content, dev tools), company has budget signals, and the fit is genuine — not forced.

### Stage 4 — Contacted
First outreach sent (email, social, or other channel). Message is personalized, references specific research, and opens a conversation — not a pitch.

### Stage 5 — Nurturing
Lead has responded or shown interest. In active conversation. Follow-ups are timely and value-adding. Goal: get them to try WordPilot.pro.

### Stage 6 — Converted
Lead has signed up, joined a waitlist, or committed to trying WordPilot. Hand-off complete. Track for referrals and case studies.

## Workspace Structure

All lead work lives under `/leads/`. Keep this structure clean and always up to date:

```
/leads/
├── daily-board.md          ← Today's todos, progress, and session log
├── pipeline.md             ← Full pipeline view: all leads by stage
├── research-methods.md     ← Research playbooks by persona/industry
├── templates.md            ← Outreach templates, follow-up patterns, DM scripts
├── archive/                ← Converted, dead, or dormant leads
│   └── 2026-05/
└── leads/                  ← Individual lead files (one per lead)
    └── john-doe.md
```

## Daily Cadence (The Loop)

When the user checks in each day (or you're invoked for lead work), follow this loop:

### 1) READ THE ROOM
- Read `/leads/daily-board.md` to understand yesterday's state and today's open items.
- Read `/leads/pipeline.md` to see current pipeline health.
- Check if Gmail/Sheets/Notion are connected (ask user to connect if needed for today's work).

### 2) PROCESS YESTERDAY'S OUTSTANDING
- Any follow-ups due today? Draft them.
- Any leads stuck in a stage too long? Note them and suggest next action.
- Any responses received since last session? Process them.

### 3) RESEARCH NEW LEADS (if pipeline needs filling)
- Pick 1–2 research segments (by persona, industry, or use case).
- Use Composio Search Web to find people/teams that match.
- For promising leads, deep-research with Fetch URL Content or Browser Tool.
- Create individual lead files in `/leads/leads/`.
- Add to pipeline at Stage 1 (Discovered).

### 4) ADVANCE EXISTING LEADS
- For Researched leads: qualify them against criteria. Move to Stage 3 or note why not.
- For Qualified leads: draft first outreach. If Gmail connected, offer to send.
- For Contacted leads: check if follow-up is due. Draft if so.
- For Nurturing leads: suggest next value-add (case study, feature highlight, direct invite).

### 5) UPDATE THE DAILY BOARD
- Write today's session summary to `/leads/daily-board.md`.
- Update pipeline stage counts.
- Set tomorrow's priority items.
- Mark todos as done.

### 6) REPORT TO USER
Summarize: what was done today, pipeline health (counts per stage), top 3 priority leads, and what's queued for tomorrow. Keep it concise but complete.

## Research Methodology

### Finding Leads (Composio Search Web)

Search by segment. Examples:
- `"technical writing" team lead "documentation" site:linkedin.com/in`
- `content strategist "AI writing" OR "AI content" startup`
- `developer advocate documentation tool "dev experience"`
- `head of content OR director of content SaaS 2025 2026`
- `"documentation as code" engineer OR architect OR lead`

Always search with recency and role qualifiers. Review citations for real people, not generic listicles.

### Deep Research (Fetch URL Content / Browser Tool)

For promising leads, research their:
- **Current role and company**: What do they do? Team size? Public projects?
- **Pain points**: Are they drowning in docs? Migrating tools? Scaling content?
- **Current stack**: What tools do they mention? Notion, Confluence, Google Docs, GitBook?
- **Public content**: Blog posts, talks, tweets, GitHub repos that show their thinking.
- **Hook**: Find one specific, genuine connection to WordPilot's value.

### Qualification Criteria

Score leads 1–5 on each (aim for 3+ overall):
- **Relevance**: Does their work intersect with writing, docs, content, or developer tools?
- **Authority**: Do they have decision power or influence over tooling?
- **Reach**: Do they have an audience, team, or public presence?
- **Timing**: Is there a signal they're looking for something new? (job change, tool migration, scaling pain)
- **Fit**: Would WordPilot genuinely help them? Don't force it.

## Outreach Principles

### Voice & Tone
- Professional, warm, curious — never pitchy.
- Lead with what you noticed about THEIR work.
- Position WordPilot as "something I thought you might find interesting" — not "something you need to buy."
- Respect their time. Short messages. Clear value. Easy to ignore.

### First Contact Template (Adapt, Don't Copy-Paste)

```
Subject: Your [specific work / post / talk] on [topic]

Hi [Name],

I came across your [post/talk/repo/work] on [specific topic] — really enjoyed 
[one specific insight you genuinely appreciated].

I work on WordPilot, an AI workspace for writing and documentation. Given your 
work on [their domain], I thought you might find it interesting — especially 
[one specific feature or angle that connects to their work].

No pitch — just wanted to share in case it's useful. Happy to give you early 
access if you'd like to try it.

Best,
[Your name]
```

### Follow-Up Principles
- Wait 5–7 days before following up.
- Add new value each time — a feature update, a case study, a relevant article.
- Never "just checking in" or "bumping this."
- After 3 unanswered messages, move to dormant. Revisit in 2–3 months with fresh context.

## Daily Board Format

`/leads/daily-board.md` is the heart of the system. Each day gets its own section:

```markdown
# Daily Lead Board

## YYYY-MM-DD (Today)

### Today's Focus
- Priority 1
- Priority 2
- Priority 3

### Research Queue
- [ ] Segment: [description] — target [N] leads
- [ ] Deep research on [lead name]

### Outreach Queue
- [ ] Draft first contact for [lead name]
- [ ] Follow-up for [lead name] (day [N])

### Completed Today
- [x] Researched 3 leads in [segment]
- [x] Sent outreach to [lead name]
- [x] Qualified [lead name] → Stage 3

### Pipeline Snapshot
| Stage | Count |
|---|---|
| Discovered | X |
| Researched | X |
| Qualified | X |
| Contacted | X |
| Nurturing | X |
| Converted | X |

### Tomorrow's Priority
- [ ] Item 1
- [ ] Item 2

### Notes
Any observations, blockers, or strategy adjustments.
```

## Pipeline Format

`/leads/pipeline.md` is the master list. Update it whenever a lead changes stage.

```markdown
# Lead Pipeline

Last updated: YYYY-MM-DD

## Stage 1 — Discovered
| Lead | Role | Company | Source | Found | Score |
|---|---|---|---|---|---|
| Name | Title | Co | LinkedIn | YYYY-MM-DD | — |

## Stage 2 — Researched
| Lead | Role | Company | Hook | Score |
|---|---|---|---|---|
| Name | Title | Co | Specific angle | 3/5 |

## Stage 3 — Qualified
| Lead | Role | Company | Why Qualified | Score |
|---|---|---|---|---|
| Name | Title | Co | Reason | 4/5 |

## Stage 4 — Contacted
| Lead | Role | Company | Contacted On | Channel | Response? |
|---|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Email | Pending |

## Stage 5 — Nurturing
| Lead | Role | Company | Last Contact | Next Step |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Send case study |

## Stage 6 — Converted
| Lead | Role | Company | Converted On | Notes |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Signed up |
```

## Individual Lead File Format

Each lead gets a file: `/leads/leads/firstname-lastname.md`

```markdown
# [Full Name]

- **Role**: [Title] at [Company]
- **Location**: [City/Region]
- **Pipeline Stage**: [1–6]
- **Discovered**: YYYY-MM-DD
- **Source**: [LinkedIn / Twitter / Conference / Referral / Search]
- **Score**: [N]/5

## Context
[2–3 sentences about who they are and what they do]

## Research Notes
- Pain point 1
- Pain point 2
- Current tools
- Public content / talks

## Hook
[The specific, genuine connection to WordPilot]

## Contact Log
| Date | Channel | Type | Notes |
|---|---|---|---|
| YYYY-MM-DD | Email | First contact | Sent |
| YYYY-MM-DD | Email | Follow-up 1 | Drafted |

## Notes
[Any other observations]
```

## Research Methods by Persona

Tailor search and outreach by persona. See `/leads/research-methods.md` for detailed playbooks. Quick reference:

| Persona | Where to Find | What to Lead With |
|---|---|---|
| **Technical Writer** | Write the Docs, LinkedIn, GitHub docs repos | WordPilot's MDX blocks, diagram support, version control |
| **Content Strategist** | Content marketing communities, Twitter/X, Medium | AI-assisted drafting, content pipelines, team workspaces |
| **Developer Advocate** | DevRel communities, conference talks, YouTube | Documentation generation, GitHub integration, API docs |
| **Engineering Manager** | Engineering blogs, HN, LinkedIn | Documentation workflows, team onboarding, knowledge management |
| **Founder / Indie Hacker** | Product Hunt, Indie Hackers, Twitter/X | All-in-one writing workspace, speed, shipping content faster |
| **Technical PM** | LinkedIn, product communities, Medium | Spec-to-documentation pipeline, PRDs, cross-functional docs |

## Tools Reference

### Composio Search Web (Primary Research)
```
COMPOSIO_SEARCH_WEB with query strings targeting specific personas and segments.
Review response.data.citations for real people/companies.
```

### Composio Fetch URL Content (Deep Research)
```
COMPOSIO_SEARCH_FETCH_URL_CONTENT on specific About/Team/Blog pages.
Extract context, not just contact info.
```

### Browser Tool (For Complex Sites)
```
BROWSER_TOOL_CREATE_TASK for LinkedIn profiles, dynamic pages, or sites 
that block simple fetches. Use WatchTask to poll results.
```

### Gmail (Outreach)
```
GMAIL_CREATE_EMAIL_DRAFT → review with user → GMAIL_SEND_EMAIL or GMAIL_SEND_DRAFT.
Always draft first, never auto-send without user review.
```

### Google Sheets / Notion (External CRM Sync)
```
GOOGLESHEETS_UPSERT_ROWS for spreadsheet-based CRM.
NOTION_UPSERT_ROW_DATABASE for Notion-based tracking.
Sync pipeline data when these are connected.
```

## Anti-Patterns (Do Not Do)

- **Never auto-send emails without user review.** Draft, show, get approval.
- **Never scrape personal emails from unauthorized sources.** Only use publicly available professional contact info or platforms where the person has shared their email for professional purposes.
- **Never send generic blast messages.** Every outreach must reference specific research.
- **Never over-research one lead.** 15–20 minutes max per lead for deep research. Move on.
- **Never leave the daily board empty.** Every session produces an update — even if it's "no new leads today, advanced 2 existing."
- **Never force-fit a lead.** If WordPilot isn't genuinely useful for someone, note it and move them out of the pipeline.
- **Never stalk or over-contact.** Max 3 unanswered messages, then move to dormant.

## Quality Standards

- Every lead file has a real hook — not just "they write things."
- Pipeline counts are accurate and updated same-session.
- Outreach drafts sound like a human wrote them — specifically for that person.
- Daily board is written so the user can scan it in 60 seconds.
- Research is documented, not just remembered.
- If Gmail/Sheets/Notion aren't connected, say so — and still do everything possible without them.

## Getting Started (First Session)

When this skill is first invoked and there's no `/leads/` folder yet:

1. Create the full workspace structure under `/leads/`.
2. Write the initial `/leads/daily-board.md` with today's date.
3. Write the initial `/leads/pipeline.md` with empty stage tables.
4. Write `/leads/research-methods.md` with detailed persona playbooks.
5. Write `/leads/templates.md` with outreach patterns.
6. Ask the user: "What segment or persona should I research first?" — then begin.

FILE:research-methods.md
# Research Methods by Persona

Tailor search, research, and outreach to each persona. Use this as a living playbook — update with what works.

---

## Technical Writer

### Where to Find
- **Write the Docs** community (forum, Slack, conferences)
- LinkedIn: `"technical writer" OR "documentation engineer" team lead OR manager`
- GitHub: contributors to major documentation repos
- Twitter/X: #TechComm #WriteTheDocs #documentation

### What to Research
- Their documentation stack (static site generators, docs-as-code tools)
- Pain points: versioning, review workflows, collaboration bottlenecks
- Public talks or blog posts on documentation practices

### What to Lead With
- WordPilot's MDX advanced blocks for rich documentation
- Markdown-native editing with diagram support (Mermaid / Kroki)
- Version control and GitHub integration for docs-as-code workflows
- "I noticed your talk on [topic] — WordPilot handles [specific pain point]"

### Search Queries
- `"technical writer" "documentation" team lead OR manager 2025 2026 site:linkedin.com/in`
- `"documentation engineer" OR "docs engineer" "developer experience"`
- `"write the docs" speaker OR organizer`

---

## Content Strategist / Head of Content

### Where to Find
- LinkedIn: `"head of content" OR "director of content" OR "VP of content" SaaS`
- Content marketing communities (Superpath, Content Marketing Institute)
- Medium and Substack: content strategy publications
- Twitter/X: #contentstrategy #contentmarketing

### What to Research
- Content volume and team size
- Current content tools (Google Docs, Notion, WordPress)
- Content operations pain points (workflows, approvals, SEO, repurposing)
- Recent campaigns or content initiatives

### What to Lead With
- AI-assisted drafting and editing for content teams
- Workspace collaboration for editorial workflows
- Content pipeline features (draft → review → publish)
- "Your piece on [content challenge] resonated — WordPilot addresses that with [feature]"

### Search Queries
- `"head of content" OR "director of content" SaaS "content strategy" site:linkedin.com/in`
- `"VP of content" OR "content lead" startup OR scaleup`
- `"content operations" manager OR lead`

---

## Developer Advocate / DevRel

### Where to Find
- DevRel communities (DevRel Collective, DevRelX)
- Conference speaker lists (KubeCon, React Conf, Write the Docs)
- YouTube: developer tooling reviews and tutorials
- LinkedIn: `"developer advocate" OR "developer relations"`

### What to Research
- Their content output (blog posts, talks, videos, tutorials)
- Tools they currently recommend or use
- Pain points in creating developer content
- Community engagement style and channels

### What to Lead With
- Documentation generation from code and GitHub repos
- Rich markdown capabilities for tutorials and guides
- Embedded diagrams and equations for technical content
- "Love your tutorial on [topic] — WordPilot's [feature] would streamline that workflow"

### Search Queries
- `"developer advocate" OR "devrel" "documentation" OR "developer experience"`
- `"developer relations" engineer OR lead "content" OR "docs"`
- `devrel speaker "developer tools" OR "developer experience"`

---

## Engineering Manager / Tech Lead

### Where to Find
- LinkedIn: `"engineering manager" OR "engineering lead" documentation OR "knowledge management"`
- Engineering blogs (company blogs, Medium engineering publications)
- Hacker News and Reddit (r/ExperiencedDevs, r/engineering)
- Conference speaker lists (QCon, LeadDev, StrangeLoop)

### What to Research
- Team size and structure
- Documentation practices and pain points
- Onboarding processes and knowledge management challenges
- Technical stack and tooling preferences

### What to Lead With
- Documentation workflows that don't slow down engineering
- Knowledge management and team onboarding features
- GitHub integration for engineering-driven documentation
- "Your team's approach to [engineering practice] is interesting — WordPilot could help with [specific need]"

### Search Queries
- `"engineering manager" OR "engineering lead" "documentation" OR "knowledge management" site:linkedin.com/in`
- `"VP of engineering" OR "director of engineering" "developer productivity"`
- `engineering "internal documentation" OR "technical documentation" manager`

---

## Founder / Indie Hacker

### Where to Find
- Product Hunt: makers and founders
- Indie Hackers community
- Twitter/X: #buildinpublic #indiehacker
- Hacker News: Show HN, launch posts
- LinkedIn: `"founder" OR "co-founder" content OR writing OR documentation`

### What to Research
- Their product and stage
- Content strategy and volume
- Team size (solo? small team?)
- Current writing and publishing workflow
- Public roadmap or challenges

### What to Lead With
- All-in-one writing workspace replacing fragmented tools
- Speed and simplicity for small teams
- AI features that accelerate content creation
- "Following your build journey on [platform] — WordPilot could be a useful writing tool for your stack"

### Search Queries
- `"founder" OR "co-founder" "content" OR "writing" OR "documentation" SaaS site:linkedin.com/in`
- `"indie hacker" OR "solopreneur" "writing" OR "content creation"`
- `site:indiehackers.com "looking for" writing OR content tool`

---

## Technical Product Manager

### Where to Find
- LinkedIn: `"technical product manager" OR "product manager" documentation OR specs`
- Product management communities (Mind the Product, Product School)
- Medium: product management publications
- Conference speaker lists (Industry, ProductCon)

### What to Research
- Product documentation practices
- PRD and spec writing workflows
- Cross-functional communication challenges
- Tools used for product documentation

### What to Lead With
- Spec-to-documentation pipeline
- Rich markdown for PRDs and technical specs
- Collaboration between PM, engineering, and design
- "Your approach to [product practice] is sharp — WordPilot handles [specific workflow need]"

### Search Queries
- `"technical product manager" OR "product manager" "documentation" OR "specs" site:linkedin.com/in`
- `"product manager" "PRD" OR "product requirements" SaaS`
- `"senior product manager" "technical writing" OR "documentation"`

---

## Notes for All Personas

- **Always verify the person is active** — recent posts, talks, or job activity.
- **Prioritize people who publicly share their work** — they're more likely to engage.
- **Look for trigger events**: new role, company pivot, tool migration, scaling challenges.
- **Adapt outreach language** to their persona's vocabulary — don't use "content pipeline" with an engineering manager.

FILE:templates.md
# Outreach Templates & Patterns

Use these as starting points — always customize with specific research for each lead. Never copy-paste.

---

## First Contact Templates

### For Technical Writers
```
Subject: Your [talk/post] on [specific documentation topic]

Hi [Name],

I caught your [talk/post] on [topic] — the point about [specific insight] 
really landed. Documentation teams deal with that exact tension between 
richness and maintainability.

I'm working on WordPilot, an AI writing workspace that handles that well — 
it supports advanced MDX blocks (diagrams, equations, columns) in plain 
markdown, so docs stay readable AND rich. No lock-in, no proprietary format.

No pitch — just thought you might find the approach interesting given your 
work. Happy to share more if you're curious.

Best,
[Your name]
```

### For Content Strategists
```
Subject: Your piece on [content challenge]

Hi [Name],

Really enjoyed your piece on [specific content challenge] — the [specific 
point] matches what a lot of content teams are running into right now.

I work on WordPilot, an AI workspace that helps content teams draft, review, 
and publish faster. The AI doesn't replace writers — it handles the 
repetitive parts so strategists can focus on strategy.

Would be happy to show you how it works if you're interested. No sales 
pressure — just thought it aligned with your thinking.

Best,
[Your name]
```

### For Developer Advocates
```
Subject: Your tutorial on [topic] — sharp work

Hi [Name],

Your tutorial on [topic] was excellent — particularly the [specific part]. 
Creating that kind of content at quality takes real time.

I'm building WordPilot, and one thing we focused on was making technical 
content creation faster: diagrams right in markdown (Mermaid/Kroki), 
GitHub-integrated docs, and AI that actually understands code.

Given how much technical content you produce, I thought you might find it 
useful. Happy to give you early access if you want to try it.

Cheers,
[Your name]
```

### For Engineering Managers
```
Subject: Documentation workflows and developer experience

Hi [Name],

I read about [company/team]'s approach to [engineering practice] — 
impressive how you handle [specific challenge] at scale.

One area I've been thinking about is documentation friction in engineering 
teams. We built WordPilot specifically so docs don't feel like a separate 
chore — markdown-native, GitHub-connected, with AI that helps without 
getting in the way.

No pitch — just curious if documentation workflow is something on your radar. 
Happy to share what we're building if relevant.

Best,
[Your name]
```

### For Founders / Indie Hackers
```
Subject: Writing tool you might find useful

Hi [Name],

Been following your build on [platform] — really impressive progress on 
[product]. The way you handle [specific thing] is smart.

I built WordPilot as an AI writing workspace — it replaces the patchwork of 
Google Docs, Notion, and markdown editors with one tool that actually works 
for real writing. Might be useful for your content, docs, or even product specs.

No pressure — just thought it might save you some tool-switching time. Happy 
to share access if you want to kick the tires.

Cheers,
[Your name]
```

### For Technical Product Managers
```
Subject: Your approach to [product practice]

Hi [Name],

Enjoyed reading about how you handle [specific product workflow] at 
[company] — the [specific insight] is something more teams should adopt.

I work on WordPilot, an AI writing workspace. One thing it handles 
particularly well is the spec-to-documentation pipeline — rich markdown 
with diagrams and equations, collaboration built in, and no proprietary 
format lock-in.

Thought it might be relevant given your focus on [their domain]. Happy to 
show you if you're interested.

Best,
[Your name]
```

---

## Follow-Up Patterns

### Follow-Up 1 (5–7 days after first contact)
```
Subject: Re: Your [original topic]

Hi [Name],

Just following up on my previous note — I know inboxes get busy.

I also wanted to mention [one new specific thing] about WordPilot since I 
last wrote: [feature update, new capability, relevant case study].

No rush — just wanted to keep it on your radar in case it's useful.

Best,
[Your name]
```

### Follow-Up 2 (5–7 days after follow-up 1)
```
Subject: Quick thought on [their domain]

Hi [Name],

I came across [relevant article / trend / insight] and immediately thought of 
your work on [their topic]. [One sentence connecting the insight to them].

WordPilot handles this well — specifically [relevant feature]. I won't keep 
following up after this, but wanted to share the connection.

If it ever becomes relevant, my inbox is open.

Best,
[Your name]
```

### Follow-Up 3 — Final (5–7 days after follow-up 2)
```
Subject: Re: Quick thought on [their domain]

Hi [Name],

Last note from me — I'll leave you be after this.

If you ever want to explore WordPilot, the door's open. We're building 
something genuinely useful for [their persona], and I think you'd find it 
interesting.

No reply needed — just wanted to leave that on the table.

Best,
[Your name]
```

---

## DM / Social Outreach (Twitter, LinkedIn)

### LinkedIn Connection Note
```
Hi [Name] — I came across your [work/talk/post] on [topic] and was really 
impressed by [specific insight]. I work on an AI writing tool that touches 
similar ground. Would love to connect.
```

### Twitter DM (if already connected)
```
Hey [Name] — loved your [post/thread] on [topic]. Working on an AI writing 
workspace that handles [related thing] really well. Thought you might find 
it interesting: [link]. No pitch — just sharing.
```

---

## Response Handling

### If They Reply "Not interested"
```
Thanks for letting me know, [Name]. Totally understand — appreciate you 
taking the time to reply. All the best with [their work/company].
```

### If They Reply "Tell me more"
Send a concise 3–4 sentence overview of WordPilot with one specific feature 
relevant to their work. End with an invitation to try it or schedule a 
quick walkthrough.

### If They Reply "Trying it out"
Celebrate internally (move to Stage 5 — Nurturing). Send a warm welcome 
with a getting-started tip relevant to their use case. Offer to answer 
questions.

---

## Anti-Patterns (Never Do These)

- ❌ "Just following up!" with no new value
- ❌ "We're disrupting the [X] space" jargon
- ❌ Long emails — keep under 150 words
- ❌ HTML-heavy or image-heavy emails
- ❌ Asking for a call in the first message
- ❌ "Limited time offer" or urgency tactics
- ❌ Name-dropping without permission
- ❌ Assuming their pain points without research

# Email Lead Generator & Tracker (WordPilot skill)

Use this playbook when the user asks to research and find qualified leads, draft outreach emails, track a pipeline, or build a lead generation system inside WordPilot.

This skill complements `/skills/email-triage-generator/SKILL.md` (for inbox triage and reply drafting) and `/skills/markdown-writer/SKILL.md` (for polished `.md` deliverables). Use this file for lead generation logic, pipeline design, CRM discipline, and outreach decisions — then use markdown-writer for the final `.md` quality on lead workspace files.

## Persona

You are not a bulk-mailer, a sales machine, or a growth hacker. You operate like a **boutique growth strategist**: methodical, intelligence-led, genuinely curious about the prospect's world, and disciplined about pipeline tracking. Every lead gets researched before it gets an email. Every email reads like a human wrote it for one person. Every action gets logged so the user never wonders what happened yesterday.

## When to apply

- User asks to find leads, build a lead list, research target companies or people.
- User asks to draft cold outreach, follow-ups, or nurture emails for WordPilot.pro.
- User asks to set up a lead pipeline, CRM, or tracking system.
- User asks to run a daily lead generation session.
- Workspace includes `/leads/` starter files.

## Preconditions

1. If the user wants to send or fetch real emails, Gmail must be connected via Integrations (Composio).
2. If Gmail is not connected, tell the user exactly what to connect, then retry.
3. For research-only sessions (finding leads, building lists, drafting emails without sending), no Gmail connection is required — use `internet_search` and the user's uploaded reference materials.
4. Do not invent lead data, company details, or email addresses. Research real companies and people, or clearly label synthesized examples as templates.

## Default pipeline stages

Every lead lives in exactly one stage at a time. The stages form a strict funnel — a lead can only move forward (or be disqualified):

- **Researching** — Identified as a potential fit. Gathering info. Not yet contacted.
- **Outreach Sent** — First email sent. Awaiting response.
- **Engaged** — Prospect replied. Conversation is active.
- **Meeting Booked** — Calendar event confirmed (demo, call, discovery).
- **Conversion** — Prospect converted (trial started, plan purchased, partnership formed).
- **Disqualified** — Not a fit. Moved out of active pipeline.
- **Nurture (Long-Term)** — Good fit but timing is wrong. Check back in 3–6 months.

## Scoring rubric (1–10)

Every lead is scored against the Ideal Customer Profile (ICP) for WordPilot.pro. The ICP is defined in `/leads/ideal-customer-profile.md`.

Default scoring dimensions (each 0–2 points, total 10):

| Dimension | 0 points | 1 point | 2 points |
|---|---|---|---|
| **Role fit** | Not decision-maker or user | Adjacent role / influencer | Direct decision-maker or power user |
| **Company stage** | Pre-revenue or Fortune 500 | Seed / Series A or late-stage enterprise | Series B–D, growing team |
| **Use case clarity** | No obvious need for WordPilot | General writing / content need | Clear AI-writing / doc-automation pain |
| **Tool ecosystem** | No relevant tools | Uses general productivity tools | Already uses AI writing tools, GPT, or Plate-based editors |
| **Reachability** | No public email / no social presence | Email discoverable, low social activity | Public email, active on LinkedIn/Twitter, recent content |

Score meanings:
- **8–10**: Hot lead. Prioritize outreach.
- **6–7**: Warm lead. Worth a tailored email.
- **4–5**: Cool lead. Batch research, low-priority outreach.
- **1–3**: Weak fit. Park in Nurture or Disqualify.

## Phased workflow

The skill operates in five distinct phases. The user may ask for a single phase or a full end-to-end session. Always confirm the scope before starting.

### Phase 1: Research — Find qualified leads

**Input needed**: target industry, role, company stage, geography, or a seed company to riff from.

**Process**:
1. Clarify the ICP lens for this session: what kind of lead would genuinely benefit from WordPilot.pro?
2. Use `internet_search` to find companies and people that match.
3. For each lead found, capture: name, title, company, company size/stage, why they might need WordPilot, public email (if discoverable), LinkedIn or Twitter presence, recent content or activity.
4. Score each lead against the ICP rubric.
5. Write qualified leads to `/leads/pipeline.md` in Researching stage.
6. Do not draft emails yet unless the user also requested Phase 2 in the same session.

**Quality constraints**:
- Minimum 1 verified signal per lead (recent post, job change, funding announcement, product launch, relevant article).
- No more than 3 leads from the same company unless the user explicitly asks for multi-stakeholder outreach.
- Prefer quality over quantity. 5–10 well-researched leads is better than 30 shallow ones.

### Phase 2: Qualify — Score and prioritize

Run this phase when leads already exist in the Researching stage.

**Process**:
1. For each lead in Researching, deepen the research: look for recent activity, pain signals, buying triggers.
2. Assign or refine the ICP score across all 5 dimensions.
3. Re-rank the pipeline: Hot (8–10) first, then Warm (6–7), then Cool (4–5).
4. For leads scoring 1–3, move to Disqualified or Nurture with a one-line reason.
5. Update `/leads/pipeline.md` with scores, ranks, and notes.

### Phase 3: Outreach — Draft personalized emails

Run this phase on Hot and Warm leads in the Researching stage.

**Voice rules — non-negotiable**:
- No "I hope this finds you well."
- No "We're revolutionizing the X industry."
- No "Are you the right person to talk to about...?"
- No fake urgency. No templated pressure.
- **Do**: reference something specific about their work, company, or recent content.
- **Do**: lead with curiosity or insight, not a pitch.
- **Do**: keep it under 120 words.
- **Do**: make the CTA light and easy to ignore ("No rush — just wanted to share this while it was top of mind.")

**Drafting process**:
1. For each qualified lead, draft one outreach email.
2. Each draft includes: subject line, body, and a short note explaining the personalization hook.
3. Write drafts to `/leads/pipeline.md` under the lead's entry.
4. If Gmail is connected and the user confirms send, send through Composio Gmail tools. Always ask before sending — never auto-send.
5. After sending, move the lead from Researching to Outreach Sent.

**Subject line patterns** (choose the one that fits the hook):
- Insight-led: "Your post on [topic] got me thinking"
- Question-led: "Curious how [company] handles [problem]"
- Connection-led: "[Mutual context] — quick question"
- Direct but soft: "WordPilot — in case [specific use case] is on your radar"

### Phase 4: Track — Pipeline management

Run this phase at the start of every lead session, or when the user asks for a status update.

**Process**:
1. Read `/leads/pipeline.md` to get current state.
2. For each active lead, check: days since last touch, stage, next action due.
3. Flag: leads stuck in Outreach Sent > 7 days (needs follow-up), leads in Engaged > 14 days without a meeting (needs re-engagement), leads in Meeting Booked with past dates (needs status check).
4. Present a concise status table in chat.
5. Update `/leads/daily-log.md` with today's review entry.

### Phase 5: Nurture — Follow-up cadence

**Cadence rules**:
- **First follow-up**: 5–7 days after Outreach Sent, if no reply.
- **Second follow-up**: 14 days after first follow-up. After two follow-ups with no response, move to Nurture (Long-Term).
- **Re-engagement**: 90 days after moving to Nurture, send a light-touch check-in if the lead is still relevant.
- **Active conversation**: reply within 1 business day.

**Follow-up voice**: even lighter than outreach. One or two sentences max. "Wanted to bump this in case it got buried." No guilt, no pressure.

## Daily session discipline

When the user starts a lead session:

1. **Review** — Read `/leads/daily-log.md` for yesterday's actions and carry-over items.
2. **Status** — Read `/leads/pipeline.md` and flag anything overdue.
3. **Plan** — Ask the user: research new leads, draft outreach, send queued drafts, follow up on stale leads, or review pipeline?
4. **Execute** — Run the chosen phase(s).
5. **Log** — Write today's actions to `/leads/daily-log.md` before the session ends.

## Markdown output contract

When writing lead artifacts to workspace markdown, prefer:

1. **Pipeline table** in `/leads/pipeline.md` with columns: Lead, Company, Title, Score, Stage, Last Touch, Next Action, Due.
2. **Daily log entries** with: date, actions taken (what + result), research finds, emails sent, replies received, stage changes, carry-over for tomorrow.
3. **Lead cards** in pipeline: each lead gets a focused block with name, company, score, stage, notes, and drafted emails.
4. **ICP definition** in `/leads/ideal-customer-profile.md`: clear, specific, revisable.

## Suggested file usage in lead generation projects

- `/leads/README.md` — Dashboard, glossary, and quick-start guide.
- `/leads/pipeline.md` — Active CRM with all leads, stages, scores, and email drafts.
- `/leads/daily-log.md` — Day-by-day action log and carry-over items.
- `/leads/research-playbook.md` — Where and how to find WordPilot.pro-fit leads.
- `/leads/ideal-customer-profile.md` — ICP definition and scoring rubric.
- `/leads/templates.md` — Email templates by stage (personalization-first, non-salesy).

Update these files incrementally instead of creating scattered one-off files unless the user asks.

## Quality constraints

- Never invent lead data. Research real companies and people, or label examples clearly.
- Never auto-send an email. Always confirm with the user before sending through Gmail.
- Never claim an email was sent, received, or replied to unless the data came from a real tool call.
- Keep outreach drafts personal, short, and non-salesy.
- Log every action. The daily log is the user's memory — treat it as critical infrastructure.
- If the user asks for 50 leads in 10 minutes, push back gently: "I can find 10 well-researched leads in that time, or 50 shallow ones. I'd rather do 10 well. Which do you prefer?"
- When in doubt, research more and pitch less.

FILE:reference/pipeline.md
# Pipeline CRM

This file is your single source of truth for all active leads. Every lead belongs to exactly one stage. Update stage, score, and notes as leads move through the pipeline.

---

## Researching

Leads identified but not yet contacted. Research deeper, score, and decide: qualify for outreach or move to Disqualified / Nurture.

| # | Lead | Company | Title | Score | Found via | Notes | Next action |
|---|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | *Run a research session to find leads* | — |

---

## Outreach Sent

First email sent. Awaiting response. Follow up in 5–7 days if no reply.

| # | Lead | Company | Title | Score | Sent date | Subject | Follow-up due | Notes |
|---|---|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — | — | — |

---

## Engaged

Prospect replied. Conversation is active. Goal: book a meeting.

| # | Lead | Company | Title | Score | Last contact | Conversation status | Next action |
|---|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — | — |

---

## Meeting Booked

Demo, discovery call, or meeting confirmed.

| # | Lead | Company | Title | Score | Meeting date | Meeting type | Prep notes |
|---|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — | — |

---

## Conversion

Trial started, plan purchased, or partnership formed. Log the win and hand off to next steps.

| # | Lead | Company | Title | Conversion date | Outcome | Notes |
|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — |

---

## Disqualified

Not a fit. Archived with reason.

| # | Lead | Company | Title | Original score | Reason disqualified | Date |
|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — |

---

## Nurture (Long-Term)

Good fit but timing is wrong. Revisit in 90 days.

| # | Lead | Company | Title | Score | Reason for nurture | Revisit date | Notes |
|---|---|---|---|---|---|---|---|
| — | *No leads yet* | — | — | — | — | — | — |

FILE:reference/daily-log.md
# Daily Action Log

Record every lead generation action here. This is your memory — treat it as critical infrastructure.

---

## Log format

Each day gets its own section. Use this pattern:

```
### YYYY-MM-DD — [Session focus]

**Actions taken:**
- [Action]: [What happened] — [Result]
- ...

**Research finds:**
- [Lead name], [Company], [Title] — [Why they fit] — Score: X/10

**Emails sent:**
- To: [Name] at [Company] — Subject: "[...]" — [Drafted / Sent via Gmail]

**Replies received:**
- From: [Name] — "[Summary]" — [Next step]

**Stage changes:**
- [Name]: [Old Stage] → [New Stage] — [Reason]

**Carry-over for tomorrow:**
- [Task that needs attention next session]
```

---

## Log entries

### YYYY-MM-DD — Setup

**Actions taken:**
- Created lead generation workspace with pipeline, daily log, research playbook, ICP, and templates.

**Carry-over for tomorrow:**
- Define ICP in `ideal-customer-profile.md`
- Run first research session

FILE:reference/research-playbook.md
# Research Playbook

How to find leads that genuinely benefit from WordPilot.pro. This is not a scrapbooking exercise — every lead must have at least one verified signal before they enter the pipeline.

## What WordPilot.pro offers

A writing workspace with AI assistance, Plate-based markdown editing, and skill-driven workflows. The ideal user is someone who:

- Writes regularly for work (docs, guides, proposals, reports, landing pages, specs)
- Uses or evaluates AI writing tools
- Works in a team that produces documentation or content
- Values structure and workflow over free-form chat interfaces

## Where to look

### 1. Content signals (highest intent)

People writing about, evaluating, or complaining about AI writing tools.

**Search patterns:**
- "[AI writing tool name] alternative" or "[tool] review"
- "best AI writing assistant for [use case: documentation / proposals / marketing]"
- "switching from [tool] to [tool]" — these people are in motion
- "#aitools #writing" on LinkedIn, Twitter, or Substack

**What to look for:** blog posts, Twitter threads, LinkedIn posts, Reddit discussions, Product Hunt comments where someone describes their writing workflow or tool frustration.

### 2. Role-based signals

People in roles where structured writing is a core function.

**Target roles:**
- Content leads, content strategists, technical writers
- Product managers, product marketers
- Founders or heads of growth at early-stage startups
- Documentation engineers, developer advocates
- Marketing directors at Series A–C companies

### 3. Company-stage signals

Companies growing fast enough to need documentation but not so large they have dedicated tools teams.

**Sweet spot:** Series A to Series D, 20–200 employees.
**Also good:** bootstrapped SaaS with 5–50 employees, growing content team.
**Avoid:** pre-revenue startups (no budget), Fortune 500 (too slow, too many stakeholders).

### 4. Tool-ecosystem signals

People already in the AI writing or Plate ecosystem.

**Adjacent tools:**
- Notion AI users looking for more structure
- ChatGPT / Claude power users who mention "writing workflow"
- Plate.js or Slate.js developers and users
- Markdown editors, Obsidian, and structured writing tool communities

### 5. Trigger events (highest conversion potential)

Life events that create immediate need.

- **Funding announcement:** Series A or B raised → scaling content and docs
- **Product launch:** new product or major feature → needs launch docs, landing pages
- **Job change:** new content lead, new head of product → evaluating tools
- **Team growth:** "hiring a content team" or "building out documentation"
- **Rebrand or replatform:** migrating docs, rebuilding site content

## Research process

For each potential lead found:

1. **Verify the signal** — confirm the post, announcement, or activity is real and recent (within 3 months).
2. **Find the person** — LinkedIn is the primary tool. Confirm role and company.
3. **Look for a public email** — website, Twitter bio, LinkedIn about section, GitHub profile.
4. **Find one personalization hook** — a specific thing to reference in outreach: their post, their product, their team's work, a shared context.
5. **Score against ICP** — use the rubric in `ideal-customer-profile.md`.
6. **Add to pipeline** — write to `pipeline.md` in Researching stage.

## Research quality minimums

- Every lead must have at least 1 verified signal (post, announcement, tool mention, role change).
- No more than 3 leads from the same company unless multi-stakeholder outreach is the explicit goal.
- Prefer 5–10 well-researched leads over 30 shallow names.
- If you cannot find a personalization hook, the lead drops to Cool (4–5) regardless of other scores.

FILE:reference/ideal-customer-profile.md
# Ideal Customer Profile

This document defines who WordPilot.pro is for and how to score leads. Revisit and tune this whenever your focus shifts.

## Core ICP

**WordPilot.pro is for professionals who write for work and want an AI-native, structured writing workspace — not just another chat interface.**

The ideal customer:

- Writes regularly as part of their job (docs, guides, proposals, specs, reports, landing pages, blog posts)
- Values structure: headings, tables, callouts, diagrams, versioned files
- Is evaluating or already using AI writing tools
- Works at a company where documentation quality matters
- Prefers a workspace over a prompt box

## Who it's NOT for

- People who only write casually or occasionally
- People happy with ChatGPT/Claude chat and not looking for more
- Enterprise procurement cycles (no patience for 12-month deals)
- Students or academic writers (not the current product focus)
- People who need heavy design/collaboration features (Figma, Notion-style databases)

## 5-Dimension Scoring Rubric

Score each lead 0–2 on every dimension. Maximum total: 10.

### 1. Role fit (0–2)

| Score | Criteria |
|---|---|
| 0 | Not a decision-maker or user. Wrong department entirely. |
| 1 | Adjacent role or influencer. Might champion internally. |
| 2 | Direct decision-maker or power user. Can sign up today. |

**High-signal titles:** Content Lead, Head of Content, Technical Writer, Product Manager, Product Marketer, Founder, Head of Growth, Developer Advocate, Documentation Engineer.

### 2. Company stage (0–2)

| Score | Criteria |
|---|---|
| 0 | Pre-revenue, idea-stage, or Fortune 500 enterprise. |
| 1 | Seed / Series A (small but funded) or late-stage enterprise with autonomous teams. |
| 2 | Series B–D. Growing team, documentation needs scaling, budget exists. |

**Sweet spot:** 20–200 employees, growing, hiring writers or content people.

### 3. Use case clarity (0–2)

| Score | Criteria |
|---|---|
| 0 | No obvious reason they'd need WordPilot. |
| 1 | General writing, content, or documentation need — plausible but unclear. |
| 2 | Clear pain point: scaling docs, AI writing workflow, structured content, multi-format output. |

**High-signal signals:** recent posts about AI writing tools, documentation challenges, content team scaling, markdown workflows.

### 4. Tool ecosystem (0–2)

| Score | Criteria |
|---|---|
| 0 | No relevant tools visible. Analogue workflow. |
| 1 | Uses general productivity tools (Notion, Google Docs, Confluence). |
| 2 | Already uses AI writing tools (ChatGPT, Claude, Jasper, Copy.ai), markdown editors, or Plate-based tools. |

**High-signal tools:** Notion AI, ChatGPT Plus/Pro, Claude, Jasper, Copy.ai, Obsidian, Plate.js, Slate.js, MDX, any "AI writing assistant" in their stack.

### 5. Reachability (0–2)

| Score | Criteria |
|---|---|
| 0 | No public email, no social presence, no way to contact. |
| 1 | Email discoverable. Light social activity. |
| 2 | Public email, active on LinkedIn or Twitter, recent content. Easy personalization hook. |

**High-signal platforms:** active LinkedIn presence, Twitter/X threads about their work, personal website with email, GitHub with public email, conference talks or podcasts.

## Score tiers

| Score | Tier | Label | Action |
|---|---|---|---|
| 8–10 | Hot | Priority outreach | Draft within 24 hours of research |
| 6–7 | Warm | Worth pursuing | Tailored email within the week |
| 4–5 | Cool | Low priority | Batch research; send if bandwidth |
| 1–3 | Weak | Marginal fit | Disqualify or park in Nurture |

## When to revise this ICP

- After 20 outreach emails: review response rates by score tier. Tighten or loosen.
- When the product changes: new features open new use cases and audiences.
- When you discover an unexpected convert: add that signal pattern to the ICP.
- Quarterly: review and refresh regardless.

FILE:reference/templates.md
# Email Templates

Templates are starting points, not finished products. Every email sent must include at least one personalization hook specific to the recipient. Never send a template as-is.

## Template rules

- Replace every `[bracket]` with real, specific details.
- Add at least one line that could only be written for this person.
- Keep it under 120 words.
- Light, curious tone. No pressure.
- Easy-to-ignore CTA. "No rush" is your friend.

---

## Outreach — Insight-led

Use when you found the lead through something they wrote or shared.

**Subject:** Your [post / thread / article] on [topic]

Hi [name],

Your [post / thread] on [specific topic] got me thinking — especially the bit about [specific detail].

I'm building [WordPilot.pro / a writing workspace that does X], and your take on [topic] maps closely to what we're working on.

Would love to hear how you're thinking about [related question]. No rush — just wanted to share while it was top of mind.

[Your name]

---

## Outreach — Question-led

Use when the lead's company or role suggests a specific problem.

**Subject:** Curious how [company] handles [problem]

Hi [name],

Quick question: how is [company] handling [specific problem or workflow] these days?

We've been working on [WordPilot.pro / a tool that helps with X], and I keep hearing from [similar roles / companies] that [pain point] is a real challenge.

Would love to hear if that maps to your world at all. Zero pitch — genuinely curious.

[Your name]

---

## Outreach — Connection-led

Use when you share mutual context: industry, background, tool, community.

**Subject:** [Mutual context] — quick question

Hi [name],

Saw we both [share mutual context: same industry / same tool / same community / same event]. Your work on [specific thing] caught my eye.

I'm working on [WordPilot.pro / brief one-line description], and I've been talking to [similar people / roles] about how they handle [problem].

Worth a 2-minute read? Happy to share more if it's interesting — no pressure either way.

[Your name]

---

## Follow-up #1 — Light bump (5–7 days after outreach)

**Subject:** Re: [original subject]

Hi [name],

Wanted to bump this in case it got buried. Would still love your take on [original hook / question].

No worries if the timing's off.

[Your name]

---

## Follow-up #2 — Last attempt (14 days after first follow-up)

**Subject:** Re: [original subject]

Hi [name],

One last ping — I'll leave you alone after this. If [topic / problem] is on your radar at any point, I'd be happy to share what we're building.

Either way, really respect the work you're doing at [company].

[Your name]

---

## Re-engagement — Nurture check-in (90 days)

**Subject:** [Name], still thinking about [original hook]

Hi [name],

We chatted briefly [a few months ago / earlier this year] about [original topic]. Not sure where things landed on your end, but I wanted to say hi and see if anything has changed.

No agenda — just checking in.

[Your name]

---

## Meeting confirmation — Day before

**Subject:** Still on for tomorrow? [Meeting topic]

Hi [name],

Looking forward to our call tomorrow. I've blocked out [time] and I'm ready to dive into [topic].

Here's the link if you need it: [meeting link]

Speak soon,

[Your name]

---

## Post-meeting follow-up — Same day

**Subject:** Great conversation — next steps

Hi [name],

Really enjoyed our conversation earlier. Quick summary of what we covered:

- [Key point 1]
- [Key point 2]
- [Next step]

[Specific next action from your side] by [date]. Let me know if anything else comes to mind.

[Your name]