Lead Scorer

Agent workflows

How a run works: the phases it goes through, where you are asked to approve, how to replay it, and how the daily drip works.

Concepts · Last updated

A workflow run is the unit of work in Lead Scorer. One run takes a brief and produces a campaign ready to launch, pausing at the points where a human decision is worth more than a machine one.

The phases of a run

  1. 1

    Brief and interview

    The agent reads your product and ICP, then asks for what is missing rather than guessing.

  2. 2

    Discovery

    Lead Scorer discovers companies on the web and checks their activity against the target criteria. Source links support company identification and qualification.

  3. 3

    Lead approval

    You keep or drop the accounts. Rejections carry a written reason. This gate exists before any credit is spent.

  4. 4

    Company enrichment

    Lead Scorer enriches the approved companies with business context.

  5. 5

    Company scoring

    Each company is scored against your product and ICP. Accounts that do not qualify are removed before decision-maker discovery or contact enrichment.

  6. 6

    Decision-maker discovery, enrichment and scoring

    Only for qualified companies, Lead Scorer finds current decision-makers, enriches their profiles and scores their fit against your product. Only qualified leads move on to drafting.

  7. 7

    Drafting and transport-safe cleanup

    Messages are written from real facts and versioned outreach rules, then placeholders and email HTML are sanitized before they reach your review queue.

  8. 8

    Ready to launch

    You approve the drafts, set the cap and the window, and launch.

Replaying a run

Every run is replayable step by step. You can see which companies came back from discovery, which leads were rejected and why, what enrichment produced, what each score was based on, and which quality checks governed a message before your review. If you cannot explain why a lead is in your pipeline, the tool has failed.

The daily drip

A run does not have to be a one-off batch. Set it to drip and fresh companies are found, enriched and scored every day. Decision-makers are then found, enriched and scored only at qualified companies, and qualified leads arrive as drafts in your queue like work from a teammate, still behind your approval, still inside your daily cap.

Reading workflows from your own agent

Use your client's native web search to find hiring companies and verify vacancies on their source pages. Read list_hiring_taxonomy and search_hiring_companies before saving verified evidence with upsert_company_hiring_signal into a discovered CRM company list. MCP cannot start or advance backend hiring workflows. Read app workflow progress with get_workflow_run. Hiring is a potential need, never proof of consulting demand.

list_workflows · get_workflow_run · list_workflow_runs