Automation KB Problem → Fix → Action

Goal + expectation

Produce one clean cohort that qualification can use immediately.

Time estimate: 45–60 minutes for one scored cohort with owner-confirmed handoff.

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

  • One ICP slice and conversion target are fixed.
  • One data source and enrichment method are chosen.
  • Qualification owner is ready to accept this batch.

If not ready: If ICP scope keeps changing, return to /hubs/ai-for-sales/ and lock scope first.

Cluster continuity

AI-for-Sales operator path · Stage 1 of 5

  • Current stage: Stage 1 — Build the first execution packet.
  • Do this before starting: Start here unless a qualified cohort already exists.
  • Output you should produce: One scored cohort with reason-to-contact notes.
  • What this unlocks next: Open qualification route and apply pass/fail logic.

Execution sequence

Run in order: action → output → verification

  1. Lock scope: Define one ICP slice, one trigger, and one exclusion list.
    Output: One-sentence sourcing scope.
    Verify: Scope excludes adjacent ICPs.
    If blocked: If trigger is weak, calibrate with recent wins first.
  2. Source and score: Pull, normalize, enrich, and score one batch.
    Output: Scored cohort with reason-to-contact notes.
    Verify: Required fields are complete for at least 70% of records.
    If blocked: If quality is low, improve source/enrichment before adding volume.
  3. Handoff now: Export top-tier records to qualification in the same session.
    Output: Qualification-ready file with owner note.
    Verify: No duplicate or incomplete records in export.
    If blocked: If handoff is rejected, fix data quality before new sourcing.

Completion trigger: Route is complete when one scored cohort is accepted by qualification with baseline counts attached.

Steps

  1. Lock one ICP slice and one conversion target.
  2. Pull 30–50 prospects from one source.
  3. Enrich with minimum context before scoring.
  4. Score by fit, trigger urgency, and contact confidence.
  5. Export only top-tier records to qualification.

Tool choice

Start with lead generation systems, then use prospect research to fix confidence gaps.

Recommended tools

System

AI lead generation systems

Use a repeatable sourcing and scoring structure.

Open lead system
Research

AI prospect research workflow

Add minimum useful context before handoff.

Run prospect research

Checklist

  • Keep one ICP and one target for this batch.
  • [object Object]
  • Remove duplicates and incomplete records.
  • Add one reason-to-contact per kept lead.
  • Export owner-ready file to qualification.

Output handoff

Required packet before qualification

  • Top-tier cohort export with fit score and reason-to-contact.
  • Baseline counts (sourced, usable, kept) with timestamp.
  • Qualification owner acceptance note.

Verification

Verify at least 70% of records have complete fields, fit score, and reason-to-contact.

Expected outcome

  • Qualification-ready lead list with minimal cleanup.
  • Less wasted outreach on low-fit records.
  • Reusable sourcing baseline for the next batch.

Next-action protocol

Prevent dead ends after route completion

  • Hand off to qualification in the same working session.
  • Do not open outreach routes before qualification accepts the packet.
  • If handoff fails, fix enrichment before collecting more leads.

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: Scored cohort sheet with fit score and reason-to-contact on every kept lead.
  • Success checkpoint: At least 20 top-tier records are handoff-ready with no missing required fields.
  • Before → after: Raw contacts with mixed quality and no scoring standard. → Qualification-ready cohort with explicit scoring and ownership.
  • Good vs weak: Qualification can execute immediately without cleanup. / Big list exists but scores or rationale are missing.
  • Warning: Volume alone is not progress if the next route cannot run.

Monetization depth map

Choose investment depth after handoff quality is proven

Decision support

Choose your lead-gen lane

  • Why this option: Lane choice controls speed, data quality, and handoff reliability.
  • For whom: Teams balancing fast list creation with qualification standards.
  • When to choose: Choose before sourcing so thresholds stay consistent.
  • What to do next: Finish one batch and hand off before adding new ICP scope.
Starter lead lane Balanced lead lane Assisted intake lane

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.
Next route: Qualify leads next Return to hub triage Re-run this route

Always move forward

Choose your next action

Open route Run tool Open hub
Open route