flow

Project Hunter — tool-call lifecycle

One project_hunter call end to end: score the public candidate feed against the domain rubric, cross-reference ClaritySoft for dedup, return a ranked report. Never creates a lead.

Flow

Overview

Capture-only: candidates are scored (domain rubric), cross-referenced against the CRM for dedup, ranked and returned. A human decides what enters the pipeline — the workflow never writes.

The flow

How it works

  1. Max (agent) on claude.ai → MCP tool call
  2. Project Hunter → direct request/response — no events
  3. ProjectHunterService → public project candidates / accounts — dedup cross-ref only, never creates a lead
  4. Lead-Source Read → vendor API
  5. CRM Read → vendor API
  6. Lead Source (Web) → results fold in
  7. ClaritySoft CRM → results fold in
  8. ProjectHunterReport assembled → ranked, scored candidates + markdown digest returned in the tool result