Route page
Route · Generative lead generation
Build one ICP-aligned lead list with AI-assisted research prompts and clean handoff fields.
Goal + expectation
Generate one usable lead batch with context, score, and owner-ready handoff.
Time estimate: 45–60 minutes for one 30–50 lead batch.
Execution priority
- Run one checklist loop end-to-end before branching scope.
- Capture one proof artifact and one measurable verification signal.
Steps
- Lock one ICP slice and one trigger (hire, funding, role expansion, stack change).
- Generate research prompts and gather 30–50 candidate accounts.
- Add minimum context fields and confidence score per record.
- Keep only leads that pass fit + trigger threshold.
- Export accepted leads into qualification queue with notes.
Tool choice
Start with lead generation systems. Use compare only if tooling uncertainty blocks execution today.
Recommended tools
AI lead generation systems
Use this as the execution playbook for sourcing and scoring rules.
Open playbookAI prospect research workflow
Use this when lead context fields are missing or weak.
Add contextBest AI tools for lead generation
Open compare if your tooling choice is still blocked.
Open compareChecklist
- Every kept record has company, contact, role, trigger, and reason-to-contact.
- Duplicate domains and stale contacts are removed.
- Pass/fail threshold is written before filtering.
- Export includes owner and timestamp.
Verification
Verify at least 70% of kept leads include valid trigger + reason-to-contact + confidence score.
Expected outcome
- One qualification-ready lead packet with clear reasoning.
- Lower rejection rate during qualification.
- Reusable prompt + filter structure for weekly runs.
Evidence instrumentation
Evidence packet and verification
Define the output packet, verify the checkpoint, and record one measurable signal before moving forward.
Checkpoint cadence: Capture baseline before execution, then verify at day-1 and day-7 checkpoints.
Handoff rule: Do not switch tools/routes until one verified packet is saved.
Decision support
Choose your next action
- Why this option: Each option maps to how quickly you need results and how much guidance you want during execution.
- For whom: Teams deciding between direct execution and compare-first self-serve paths.
- When to choose: Pick before step 1 so checklist decisions stay consistent across the route.
- What to do next: Select one path, complete this checklist once, then move to the next route.
Route handoff
Choose the next move while this output is fresh
- Primary next step: Route · Lead qualification — continue the cluster loop with the packet from this route.
- Secondary fallback: Use this if blockers appear and you need to re-check bottleneck priority.