Qualifies an inbound lead against the team's real ICP, explains the score, pauses on ambiguous routing, and returns a signed handoff to the CRM or automation that sent it.
Designed for
Founder-led sales and lean revenue teams that need consistent lead qualification without adding another sales platform
Operating goal
Turn each inbound lead event into an evidence-backed priority, owner, and next action in one run.
4 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 1 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 1 harnesses before production use.
Normalizes the event into a compact lead profile.
Fast classification model
Scores fit using the connected qualification rules.
Balanced reasoning model
Packages an approved decision for the originating system.
Structured output model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for LeadFlow: Inbound Lead Qualification Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
Parse the trigger payload into facts, unknowns, and qualification inputs.
Compare the lead with the selected Notion rubric and explain every material score.
Review ambiguous, low-confidence, or high-value routing before the result leaves Codelit.
Return the approved score, rationale, owner, and next action in the run result.
Open it in Codelit, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowScreens a candidate against a role rubric, records evidence for every criterion, pauses before a shortlist decision, and returns a structured recruiter handoff.
Turns one approved Notion source into channel-specific drafts, checks claims and voice, pauses before publication, and returns a ready-to-schedule content package.
A Slack-native engineering agent that receives operational requests, gathers context from tickets and repos, routes work to specialist agents, and drafts auditable responses before anything risky happens.