Goal + expectation

Move only high-likelihood prospects into outreach and remove weak-fit records early.

Time estimate: 30–60 minutes to score one lead batch and finalize outreach-ready records.

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

  • Lead-generation batch is complete with required firmographic/context fields.
  • Pass score and disqualifier logic are defined before scoring begins.
  • One operator owns final disposition decisions for this cohort.

If not ready: If scoring logic is not fixed, return to /hubs/ai-for-sales/lead-generation/ and lock required fields + thresholds first.

Execution sequence

Run in order: action → output → verification

  1. Rule lock: Finalize pass/fail rubric and explicit disqualifiers.
    Output: Scoring rubric with numeric threshold and fail flags.
    Verify: Rubric is approved before first record is scored.
    If blocked: If team disagrees on threshold, run a 10-record calibration pass first.
  2. Cohort scoring: Score every lead using identical rubric and assign disposition.
    Output: Fully scored cohort with ready-now, nurture, and disqualify buckets.
    Verify: 100% of records contain score, disposition, and reason note.
    If blocked: If required data is missing, send records back to research before scoring.
  3. Outreach handoff: Attach one messaging angle to each ready-now lead and export cohort.
    Output: Outreach-ready file with reason-to-contact for each kept lead.
    Verify: Export includes no missing required fields.
    If blocked: If messaging angle is weak, enrich intent signal before export.

Completion trigger: Route is complete when outreach-ready records pass audit and non-qualified records are routed to nurture/archive with reason codes.

Steps

  1. Define pass/fail rules for fit, need, authority, and timing.
  2. Score each lead against the same rubric instead of ad-hoc notes.
  3. Segment into ready now, nurture later, or disqualify.
  4. Attach one outreach angle to each ready-now lead.
  5. Export only ready-now records into the outreach queue.

Tool choice

Use the qualification workflow as the decision anchor and only re-open prospect research when required data is missing.

Recommended tools

Data quality

AI prospect research workflow

Fill missing firmographic and intent signals before scoring.

Fill missing data

Checklist

  • Set one explicit pass score and one explicit disqualifier.
  • Score 100% of leads with the same rubric fields.
  • Add one next action label for each qualified lead.
  • Push non-qualified leads into a nurture or archive list.
  • Record disqualification reasons to improve future sourcing.

Verification

Verify qualified leads contain complete scoring fields, one messaging angle, and a mapped outreach next action.

Expected outcome

  • Cleaner handoff from sourcing to outreach.
  • Higher reply quality from better-fit lead selection.
  • A visible qualification standard your team can repeat.

Next-action protocol

Prevent dead ends after route completion

  • Open outreach route immediately with the approved cohort and message-angle notes.
  • Send non-qualified records to nurture/archive with explicit reason code.
  • Revisit lead-generation criteria if disqualifier rates exceed planned threshold.

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 pass/fail-scored cohort with one approved outreach angle per qualified lead.
  • Success checkpoint: 100% of outreach-ready records include score fields, disposition, and next action label.
  • Before → after: Mixed-fit prospect list with uncertain readiness. → Outreach queue contains only qualified records that meet pass criteria.
  • Good vs weak: Operators can explain why each kept lead passed in one sentence. / Leads are marked qualified, but disqualifier logic and next actions are absent.
  • Warning: More “qualified” leads is not progress if pass/fail logic cannot be audited.

Decision-tied recommendation

Choose your qualification control lane

  • Why this option: Qualification rigor directly affects outreach quality and follow-up efficiency.
  • For whom: Teams that need consistent lead decisions across multiple operators.
  • When to choose: Lock this before outreach copywriting so messaging uses the same pass/fail logic.
  • What to do next: Approve one outreach-ready cohort and push it into the outreach route.

Route handoff

Choose the next move while this output is fresh

  • Primary next step: Launch outreach 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.

Always move forward

Choose your next action

Start now