t420-kol-scout — KOL Discovery + Personalized DM
Purpose
Find crypto/DePIN Key Opinion Leaders (KOLs) on X/Twitter, score their relevance, personalize outreach from templates, send DMs, and track results.
Dependencies
brave-search— Web search for KOL discoverygrok-search— X/Twitter search for KOL profiles and recent activitychirp— X/Twitter read, DM sendingexa— Neural search for deeper KOL researchleadklick— Log leads to Supabase
Rate Limits
Max 20 DMs per day (hard cap: 30)
Min 30 minutes between DMs (to avoid X rate limiting)
1 follow-up per KOL (after 48 hours, if no response)
Max 10 DMs per session (morning + afternoon sessions)
Workflow
Phase 1: Discovery
Search for KOLs matching these criteria:
Follower range: 5,000 - 50,000 (micro-KOLs, more responsive)
Topics: DePIN, Solana, robotaxi, autonomous vehicles, RWA, crypto infrastructure
Activity: Posted within last 7 days
Engagement: Avg 10+ likes per post (indicates real audience)
Language: English (primary), expand to other languages if capacity allows
Search queries:
Phase 2: Scoring
Score each KOL 1-10 based on:
Relevance
30%
How closely their content aligns with T420 thesis
Audience size
20%
5K-10K (6pts), 10K-25K (8pts), 25K-50K (10pts)
Engagement rate
25%
Likes+replies / followers ratio
Recent activity
15%
Days since last post about DePIN/Solana/RWA
Tone fit
10%
Builder mentality vs. hype/shill style
Threshold: Only DM KOLs scoring 6+ out of 10.
Phase 3: Personalization
For each qualifying KOL, research and note:
Their most recent relevant post (to reference in DM)
Projects they've previously promoted
Their typical content style (technical, hype, analytical)
Any existing connection to Solana/DePIN ecosystem
Phase 4: DM Composition
Select and personalize from these templates:
Template A — Direct (for DePIN/Solana natives):
Template B — Value-First (for skeptical/analytical KOLs):
Template C — Exclusive (for higher-follower KOLs):
Personalization rules:
Always reference something specific from their recent content
Match their communication style (formal vs. casual)
Never send identical messages to multiple KOLs
Template is a starting point — adapt, don't copy-paste
Phase 5: Send + Log
Send DM via chirp
Log to kol-tracker.json:
KOL handle, name, follower count
Score (1-10)
Template used (A/B/C)
Personalization notes
Timestamp sent
Status: "dm_sent"
Log to leadklick (Supabase) for persistence
Phase 6: Follow-Up
After 48 hours with no response: Send one follow-up:
After 72 hours total with no response: Mark as "no_response" and move on
If interested: Move to deal negotiation (send KOL Content Kit details)
If declined: Thank them gracefully, mark as "declined"
Deal Negotiation (After Interest)
When a KOL expresses interest, send partnership details:
Negotiation bounds (do NOT exceed without Zane approval):
Standard: 500K tokens for 1 thread + 48hr pin
Max: 750K tokens for 10+ tweet thread + 72hr pin + 1 follow-up engagement tweet
Cash component: Not available (escalate to Zane if demanded)
Output Format (kol-tracker.json entry)
A/B Testing
Track response rates by template. After 30 DMs (10 per template), analyze which template performs best and shift 70% of future DMs to the winning template.
Abort Conditions
If DM send fails 3x consecutively → pause for 6 hours (possible rate limit)
If account gets restricted → STOP immediately, alert Zane in daily brief
If response rate drops below 3% after 50+ DMs → pause, redesign templates, consult Zane
Last updated
Was this helpful?