Route page
Route · AI lead generation
Build a repeatable list of qualified prospects from one ICP segment.
Goal + expectation
Produce a clean prospect batch your team can contact this week.
Time estimate: 45–75 minutes for one ICP segment and a scored outreach list.
Execution priority
- Run one checklist loop end-to-end before branching scope.
- Capture one proof artifact and one measurable verification signal.
Readiness gate
Start this route only when these signals are true
- ICP slice and conversion target are fixed for this run.
- Data source and enrichment method are selected before sourcing.
- Qualification route owner is ready to accept this batch.
If not ready: If ICP scope keeps changing, pause and align in AI-for-Sales hub before collecting more contacts.
Execution sequence
Run in order: action → output → verification
-
Scope lock: Define one ICP slice with clear trigger event and conversion target.
Output: One-sentence sourcing scope plus exclusion list.
Verify: Scope excludes adjacent ICPs to avoid mixed-quality lists.
If blocked: If trigger is weak, validate with historical wins before sourcing. -
Source and enrich: Pull prospects, normalize fields, and add minimum context.
Output: Clean candidate list with trigger note and role-fit evidence.
Verify: Required fields are complete for at least 70% of candidates.
If blocked: If completion rate is low, improve research quality before scoring. -
Score and handoff: Score records and export top-tier cohort to qualification.
Output: Qualification-ready batch with reason-to-contact per kept lead.
Verify: Duplicate/incomplete records are removed before export.
If blocked: If top-tier count is too low, revise source quality before expanding volume.
Completion trigger: Route is complete when one scored cohort is exported to qualification with clean fields, context notes, and baseline metrics captured.
Steps
- Define one ICP slice (role, company size, trigger event) and lock scope for this run.
- Pull 30–50 prospects from one source and normalize company + contact fields.
- Enrich with minimum context (trigger, relevant pain, and role fit) before scoring.
- Score each prospect by fit, urgency trigger, and contact confidence.
- Hand off only top-tier records to qualification with reason-to-contact notes.
Tool choice
Start with the lead generation systems guide for process shape, then use prospect research workflow to improve data confidence before handoff.
Recommended tools
AI lead generation systems
Use a repeatable structure for sourcing and scoring.
Open lead systemAI prospect research workflow
Gather minimum useful facts before outreach.
Run prospect researchAI prospecting tools compared
Pick stack by budget, speed, and operator maturity.
Compare prospecting toolsChecklist
- Lock one ICP segment and one conversion target for this batch.
- [object Object]
- Remove duplicates and incomplete records before handoff.
- Tag top-tier prospects with one clear reason-to-contact.
- Export qualification-ready records with uniform fields and notes.
Verification
Verify at least 70% of records contain complete fields, a fit score, and a clear qualification reason.
Expected outcome
- One qualification-ready lead list your team can act on without cleanup.
- Reduced wasted outreach on low-context or low-fit records.
- A reusable sourcing baseline for the next batch.
Next-action protocol
Prevent dead ends after route completion
- Hand off top-tier batch to qualification route in the same working session.
- If handoff fails quality check, fix enrichment before sourcing new contacts.
- Reuse disqualifier feedback from qualification to tune next sourcing run.
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.
Route-specific proof notes
- Artifact: A scored lead sheet with fit score, trigger note, and reason-to-contact for every kept record.
- Success checkpoint: At least 20 top-tier records are handoff-ready with no missing required fields.
- Before → after: Disconnected raw contacts with inconsistent context. → Qualification-ready cohort with clear scoring and contact rationale.
- Good vs weak: Top-tier list can move to qualification without manual cleanup. / Large list exists, but scores and reason-to-contact notes are missing.
- Warning: Record count alone is not success if the next route cannot execute immediately.
Monetization depth map
Choose the monetized next action after lead batch quality is clear
- Early validation readiness: Run low-cost sourcing and enrichment to prove one ICP slice first. → Use starter lane
- Team execution readiness: Use balanced prospecting stack to keep weekly lead flow stable. → Use balanced lane
- Revenue-urgency readiness: Use guided implementation when pipeline delays have direct cost. → Use premium lane
If this, do this next
- Fewer than 70% records are handoff-ready: Pause expansion and fix sourcing + enrichment quality. → Improve research quality
- Records are clean but reply quality stays weak: Move directly into outreach lane selection before adding more leads. → Choose outreach lane
- Top-tier cohort is ready for controlled send: Continue the cluster in qualification with fixed pass/fail rules. → Open qualification route
Decision-tied recommendation
Choose your lead-gen execution lane
- Why this option: Lane selection controls sourcing depth, enrichment quality, and expected speed.
- For whom: Teams balancing time-to-first-list versus data quality standards.
- When to choose: Decide before list building so score thresholds and enrichment depth stay consistent.
- What to do next: Complete one full batch, then hand off to qualification without adding new ICP scope.
Route handoff
Choose the next move while this output is fresh
- Primary next step: Qualify leads next — 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.