The problem
Why this system exists
High-intent security conversations happen across public communities, hiring activity, leadership changes, and company posts, but the signals are fragmented and difficult to prioritize.
Intent Intelligence
Cybersecurity Intent Pipeline
Combines Reddit conversations and LinkedIn activity to surface cybersecurity buying signals, qualify accounts, enrich contacts, and notify teams about high-intent leads.
The outcome
What it produces
A configurable seven-stage workflow that captures public intent, scores it, applies FITS qualification, enriches accounts, and surfaces the strongest opportunities.
System overview
How the playbook moves from input to outcome.
Each stage has one job. The sequence stays visible while the active state moves through the system.
01
Collect
Scan Reddit and LinkedIn sources for relevant activity.
02
Filter
Remove noise before spending AI-scoring resources.
03
Score
Classify signals and suggest an outreach direction.
04
Qualify
Apply firmographic, intent, technographic, and structural fit.
05
Enrich
Attach companies, people, supporting evidence, and contact paths.
06
Notify
Surface the strongest qualified leads for human action.
Reddit conversations
LinkedIn jobs
New security leaders
Company posts
Unified signal layer
Collect · deduplicate · score
FITS qualification
Firmographic82
Intent94
Technographic76
Structural88
Inputs
What the system needs
- Reddit conversations
- LinkedIn jobs and posts
- Leadership and company changes
- Client-specific intent playbook
Outputs
What comes out
- Deduplicated intent-signal database
- HOT, WARM, and COLD classifications
- FITS-qualified accounts
- Enriched contacts and evidence
- Suggested outreach directions
Inside the repository
The important pieces, without the file-system noise.
The explainer shows the operating structure. The repository remains the source of truth for complete setup and implementation details.
Cybersecurity-B2B-Lead-Gen-Flywheel/
- 01scripts/: collection, scoring, enrichment, and alerts
- 02scripts/lib/: shared scoring and signal helpers
- 03.claude/skills/: slash-command stage wrappers
- 04clients/: ICP and scoring configuration
- 05supabase/migrations/: unified signal data model
- 06data/: gitignored local output
Guardrails
What the system deliberately protects.
- Generated lead data stays in gitignored local storage or Supabase.
- Client playbooks control weights, competitors, and ICP criteria.
- Confidence and time decay affect signal priority.
- The system surfaces opportunities for review rather than auto-contacting them.
Quick start
From repository to first useful run.
- 01Add the required Apify token and any optional provider keys.
- 02Configure topics and client scoring criteria.
- 03Run the Reddit and LinkedIn collection stages.
- 04Review scored signals and qualified accounts.
- 05Enrich and act on the highest-intent leads.
Adapt the system
Want a version built around your market, tools, and sales process?
Keep exploring
Related playbooks
Claude Code SkillsOpen source
GTM Flywheel
Fifteen structured Claude Code skills that turn ICP research, signal scoring, outbound copy, campaign analytics, and sales intelligence into one compounding GTM system.
ICP Research
Signal Scoring
Cold Email
A versioned set of operating skills with scoring models, decision trees, templates, and quality checks that Claude Code can apply consistently to your own data.
Sales EnablementOpen source
Microsite Pipeline
Turns one sales lead into a researched, personalized eight-page sales microsite and PDF using sourced company data.
Lead
Enrich
Synthesize
A repeatable local pipeline that researches a company, generates TAM, ICP, and sales-signal insights, then renders an on-brand HTML page and PDF without fabricating missing data.