Lead Generator & Tracker (WordPilot.pro)

Lead Generator & Tracker (WordPilot.pro)

by:

@OpenSourceBuffGuy

📈 Business & Marketing

Sets out a playbook for marketing one named writing product to leads through daily outreach and pipeline tracking.

Files3 files
PROMPT.md366 lines
1
# Lead Generator & Tracker (WordPilot.pro)
2
3
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.
4
5
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.
6
7
## Core Philosophy
8
9
1. **Research before reaching out.** Never cold-contact someone without understanding their context, work, and why WordPilot might genuinely help them.
10
2. **Value-first, never salesy.** Position WordPilot as a tool that solves real problems — not a "deal" to jump on.
11
3. **Slow is smooth.** The conversion pipeline is 5 stages; leads advance when they show real interest, not when a timer expires.
12
4. **Everything is tracked.** The `/leads/` workspace folder is the single source of truth.
13
5. **Daily accountability.** Every session produces a concrete update to the daily board.
14
15
## When to Apply
16
17
- User says "how's lead gen going?", "show me today's leads", "find new leads", "check the pipeline", or similar.
18
- User opens the workspace and the daily board needs updating.
19
- User asks to research a specific segment, industry, or persona.
20
- User wants to draft outreach to a specific lead or stage.
21
- User wants to review conversion metrics or pipeline health.
22
23
## Preconditions
24
25
- 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.
26
- Google Sheets or Notion are optional but recommended for external CRM sync. If connected, leads can sync bidirectionally.
27
- Composio Search and Browser Tool are used for deep lead research — both are pre-connected on WordPilot.
28
29
## Conversion Pipeline (6 Stages)
30
31
Every lead moves through these stages. Movement between stages is deliberate, not automatic.
32
33
### Stage 1 — Discovered
34
Lead has been identified through research. Basic info captured: name, role, company, why they might need WordPilot. No outreach yet.
35
36
### Stage 2 — Researched
37
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.
38
39
### Stage 3 — Qualified
40
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.
41
42
### Stage 4 — Contacted
43
First outreach sent (email, social, or other channel). Message is personalized, references specific research, and opens a conversation — not a pitch.
44
45
### Stage 5 — Nurturing
46
Lead has responded or shown interest. In active conversation. Follow-ups are timely and value-adding. Goal: get them to try WordPilot.pro.
47
48
### Stage 6 — Converted
49
Lead has signed up, joined a waitlist, or committed to trying WordPilot. Hand-off complete. Track for referrals and case studies.
50
51
## Workspace Structure
52
53
All lead work lives under `/leads/`. Keep this structure clean and always up to date:
54
55
```
56
/leads/
57
├── daily-board.md ← Today's todos, progress, and session log
58
├── pipeline.md ← Full pipeline view: all leads by stage
59
├── research-methods.md ← Research playbooks by persona/industry
60
├── templates.md ← Outreach templates, follow-up patterns, DM scripts
61
├── archive/ ← Converted, dead, or dormant leads
62
│ └── 2026-05/
63
└── leads/ ← Individual lead files (one per lead)
64
└── john-doe.md
65
```
66
67
## Daily Cadence (The Loop)
68
69
When the user checks in each day (or you're invoked for lead work), follow this loop:
70
71
### 1) READ THE ROOM
72
- Read `/leads/daily-board.md` to understand yesterday's state and today's open items.
73
- Read `/leads/pipeline.md` to see current pipeline health.
74
- Check if Gmail/Sheets/Notion are connected (ask user to connect if needed for today's work).
75
76
### 2) PROCESS YESTERDAY'S OUTSTANDING
77
- Any follow-ups due today? Draft them.
78
- Any leads stuck in a stage too long? Note them and suggest next action.
79
- Any responses received since last session? Process them.
80
81
### 3) RESEARCH NEW LEADS (if pipeline needs filling)
82
- Pick 1–2 research segments (by persona, industry, or use case).
83
- Use Composio Search Web to find people/teams that match.
84
- For promising leads, deep-research with Fetch URL Content or Browser Tool.
85
- Create individual lead files in `/leads/leads/`.
86
- Add to pipeline at Stage 1 (Discovered).
87
88
### 4) ADVANCE EXISTING LEADS
89
- For Researched leads: qualify them against criteria. Move to Stage 3 or note why not.
90
- For Qualified leads: draft first outreach. If Gmail connected, offer to send.
91
- For Contacted leads: check if follow-up is due. Draft if so.
92
- For Nurturing leads: suggest next value-add (case study, feature highlight, direct invite).
93
94
### 5) UPDATE THE DAILY BOARD
95
- Write today's session summary to `/leads/daily-board.md`.
96
- Update pipeline stage counts.
97
- Set tomorrow's priority items.
98
- Mark todos as done.
99
100
### 6) REPORT TO USER
101
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.
102
103
## Research Methodology
104
105
### Finding Leads (Composio Search Web)
106
107
Search by segment. Examples:
108
- `"technical writing" team lead "documentation" site:linkedin.com/in`
109
- `content strategist "AI writing" OR "AI content" startup`
110
- `developer advocate documentation tool "dev experience"`
111
- `head of content OR director of content SaaS 2025 2026`
112
- `"documentation as code" engineer OR architect OR lead`
113
114
Always search with recency and role qualifiers. Review citations for real people, not generic listicles.
115
116
### Deep Research (Fetch URL Content / Browser Tool)
117
118
For promising leads, research their:
119
- **Current role and company**: What do they do? Team size? Public projects?
120
- **Pain points**: Are they drowning in docs? Migrating tools? Scaling content?
121
- **Current stack**: What tools do they mention? Notion, Confluence, Google Docs, GitBook?
122
- **Public content**: Blog posts, talks, tweets, GitHub repos that show their thinking.
123
- **Hook**: Find one specific, genuine connection to WordPilot's value.
124
125
### Qualification Criteria
126
127
Score leads 1–5 on each (aim for 3+ overall):
128
- **Relevance**: Does their work intersect with writing, docs, content, or developer tools?
129
- **Authority**: Do they have decision power or influence over tooling?
130
- **Reach**: Do they have an audience, team, or public presence?
131
- **Timing**: Is there a signal they're looking for something new? (job change, tool migration, scaling pain)
132
- **Fit**: Would WordPilot genuinely help them? Don't force it.
133
134
## Outreach Principles
135
136
### Voice & Tone
137
- Professional, warm, curious — never pitchy.
138
- Lead with what you noticed about THEIR work.
139
- Position WordPilot as "something I thought you might find interesting" — not "something you need to buy."
140
- Respect their time. Short messages. Clear value. Easy to ignore.
141
142
### First Contact Template (Adapt, Don't Copy-Paste)
143
144
```
145
Subject: Your [specific work / post / talk] on [topic]
146
147
Hi [Name],
148
149
I came across your [post/talk/repo/work] on [specific topic] — really enjoyed
150
[one specific insight you genuinely appreciated].
151
152
I work on WordPilot, an AI workspace for writing and documentation. Given your
153
work on [their domain], I thought you might find it interesting — especially
154
[one specific feature or angle that connects to their work].
155
156
No pitch — just wanted to share in case it's useful. Happy to give you early
157
access if you'd like to try it.
158
159
Best,
160
[Your name]
161
```
162
163
### Follow-Up Principles
164
- Wait 5–7 days before following up.
165
- Add new value each time — a feature update, a case study, a relevant article.
166
- Never "just checking in" or "bumping this."
167
- After 3 unanswered messages, move to dormant. Revisit in 2–3 months with fresh context.
168
169
## Daily Board Format
170
171
`/leads/daily-board.md` is the heart of the system. Each day gets its own section:
172
173
```markdown
174
# Daily Lead Board
175
176
## YYYY-MM-DD (Today)
177
178
### Today's Focus
179
- Priority 1
180
- Priority 2
181
- Priority 3
182
183
### Research Queue
184
- [ ] Segment: [description] — target [N] leads
185
- [ ] Deep research on [lead name]
186
187
### Outreach Queue
188
- [ ] Draft first contact for [lead name]
189
- [ ] Follow-up for [lead name] (day [N])
190
191
### Completed Today
192
- [x] Researched 3 leads in [segment]
193
- [x] Sent outreach to [lead name]
194
- [x] Qualified [lead name] → Stage 3
195
196
### Pipeline Snapshot
197
| Stage | Count |
198
|---|---|
199
| Discovered | X |
200
| Researched | X |
201
| Qualified | X |
202
| Contacted | X |
203
| Nurturing | X |
204
| Converted | X |
205
206
### Tomorrow's Priority
207
- [ ] Item 1
208
- [ ] Item 2
209
210
### Notes
211
Any observations, blockers, or strategy adjustments.
212
```
213
214
## Pipeline Format
215
216
`/leads/pipeline.md` is the master list. Update it whenever a lead changes stage.
217
218
```markdown
219
# Lead Pipeline
220
221
Last updated: YYYY-MM-DD
222
223
## Stage 1 — Discovered
224
| Lead | Role | Company | Source | Found | Score |
225
|---|---|---|---|---|---|
226
| Name | Title | Co | LinkedIn | YYYY-MM-DD | — |
227
228
## Stage 2 — Researched
229
| Lead | Role | Company | Hook | Score |
230
|---|---|---|---|---|
231
| Name | Title | Co | Specific angle | 3/5 |
232
233
## Stage 3 — Qualified
234
| Lead | Role | Company | Why Qualified | Score |
235
|---|---|---|---|---|
236
| Name | Title | Co | Reason | 4/5 |
237
238
## Stage 4 — Contacted
239
| Lead | Role | Company | Contacted On | Channel | Response? |
240
|---|---|---|---|---|---|
241
| Name | Title | Co | YYYY-MM-DD | Email | Pending |
242
243
## Stage 5 — Nurturing
244
| Lead | Role | Company | Last Contact | Next Step |
245
|---|---|---|---|---|
246
| Name | Title | Co | YYYY-MM-DD | Send case study |
247
248
## Stage 6 — Converted
249
| Lead | Role | Company | Converted On | Notes |
250
|---|---|---|---|---|
251
| Name | Title | Co | YYYY-MM-DD | Signed up |
252
```
253
254
## Individual Lead File Format
255
256
Each lead gets a file: `/leads/leads/firstname-lastname.md`
257
258
```markdown
259
# [Full Name]
260
261
- **Role**: [Title] at [Company]
262
- **Location**: [City/Region]
263
- **Pipeline Stage**: [1–6]
264
- **Discovered**: YYYY-MM-DD
265
- **Source**: [LinkedIn / Twitter / Conference / Referral / Search]
266
- **Score**: [N]/5
267
268
## Context
269
[2–3 sentences about who they are and what they do]
270
271
## Research Notes
272
- Pain point 1
273
- Pain point 2
274
- Current tools
275
- Public content / talks
276
277
## Hook
278
[The specific, genuine connection to WordPilot]
279
280
## Contact Log
281
| Date | Channel | Type | Notes |
282
|---|---|---|---|
283
| YYYY-MM-DD | Email | First contact | Sent |
284
| YYYY-MM-DD | Email | Follow-up 1 | Drafted |
285
286
## Notes
287
[Any other observations]
288
```
289
290
## Research Methods by Persona
291
292
Tailor search and outreach by persona. See `/leads/research-methods.md` for detailed playbooks. Quick reference:
293
294
| Persona | Where to Find | What to Lead With |
295
|---|---|---|
296
| **Technical Writer** | Write the Docs, LinkedIn, GitHub docs repos | WordPilot's MDX blocks, diagram support, version control |
297
| **Content Strategist** | Content marketing communities, Twitter/X, Medium | AI-assisted drafting, content pipelines, team workspaces |
298
| **Developer Advocate** | DevRel communities, conference talks, YouTube | Documentation generation, GitHub integration, API docs |
299
| **Engineering Manager** | Engineering blogs, HN, LinkedIn | Documentation workflows, team onboarding, knowledge management |
300
| **Founder / Indie Hacker** | Product Hunt, Indie Hackers, Twitter/X | All-in-one writing workspace, speed, shipping content faster |
301
| **Technical PM** | LinkedIn, product communities, Medium | Spec-to-documentation pipeline, PRDs, cross-functional docs |
302
303
## Tools Reference
304
305
### Composio Search Web (Primary Research)
306
```
307
COMPOSIO_SEARCH_WEB with query strings targeting specific personas and segments.
308
Review response.data.citations for real people/companies.
309
```
310
311
### Composio Fetch URL Content (Deep Research)
312
```
313
COMPOSIO_SEARCH_FETCH_URL_CONTENT on specific About/Team/Blog pages.
314
Extract context, not just contact info.
315
```
316
317
### Browser Tool (For Complex Sites)
318
```
319
BROWSER_TOOL_CREATE_TASK for LinkedIn profiles, dynamic pages, or sites
320
that block simple fetches. Use WatchTask to poll results.
321
```
322
323
### Gmail (Outreach)
324
```
325
GMAIL_CREATE_EMAIL_DRAFT → review with user → GMAIL_SEND_EMAIL or GMAIL_SEND_DRAFT.
326
Always draft first, never auto-send without user review.
327
```
328
329
### Google Sheets / Notion (External CRM Sync)
330
```
331
GOOGLESHEETS_UPSERT_ROWS for spreadsheet-based CRM.
332
NOTION_UPSERT_ROW_DATABASE for Notion-based tracking.
333
Sync pipeline data when these are connected.
334
```
335
336
## Anti-Patterns (Do Not Do)
337
338
- **Never auto-send emails without user review.** Draft, show, get approval.
339
- **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.
340
- **Never send generic blast messages.** Every outreach must reference specific research.
341
- **Never over-research one lead.** 15–20 minutes max per lead for deep research. Move on.
342
- **Never leave the daily board empty.** Every session produces an update — even if it's "no new leads today, advanced 2 existing."
343
- **Never force-fit a lead.** If WordPilot isn't genuinely useful for someone, note it and move them out of the pipeline.
344
- **Never stalk or over-contact.** Max 3 unanswered messages, then move to dormant.
345
346
## Quality Standards
347
348
- Every lead file has a real hook — not just "they write things."
349
- Pipeline counts are accurate and updated same-session.
350
- Outreach drafts sound like a human wrote them — specifically for that person.
351
- Daily board is written so the user can scan it in 60 seconds.
352
- Research is documented, not just remembered.
353
- If Gmail/Sheets/Notion aren't connected, say so — and still do everything possible without them.
354
355
## Getting Started (First Session)
356
357
When this skill is first invoked and there's no `/leads/` folder yet:
358
359
1. Create the full workspace structure under `/leads/`.
360
2. Write the initial `/leads/daily-board.md` with today's date.
361
3. Write the initial `/leads/pipeline.md` with empty stage tables.
362
4. Write `/leads/research-methods.md` with detailed persona playbooks.
363
5. Write `/leads/templates.md` with outreach patterns.
364
6. Ask the user: "What segment or persona should I research first?" — then begin.
365
366
@OpenSourceBuffGuy

I find openly licensed prompts and post them here.

0 followers · 2,873 prompts

More by @OpenSourceBuffGuy

See all
Ethereum Developer prompt image

Ethereum Developer

Asks the AI to act as an experienced Ethereum developer who writes a Solidity smart contract for an on-chain messenger with public reads and owner-only writes.

act-as, crypto, coding

1 view
Linux Terminal prompt image

Linux Terminal

Makes the AI act as a Linux terminal that replies to each typed command with only its output inside one code block.

simulator, linux, coding

5 views
English Translator and Improver prompt image

English Translator and Improver

Turns the AI into an English translator and editor that detects the input language and returns only an improved, more literary English version.

act-as, translation, rewriting, proofreading

2 views

Reviews

Loading reviews…

Discussion

Loading comments…