Speed To Lead Agent
FreeNot checkedMCP server for qualifying and responding to inbound leads in seconds using a multi-agent AI pipeline.
About
MCP server for qualifying and responding to inbound leads in seconds using a multi-agent AI pipeline.
README
⚡ speed-to-lead-agent
Qualify and respond to every inbound lead in seconds — with an AI agent you self-host.
A multi-agent pipeline (LangGraph) that takes a raw inbound lead, scores its fit, drafts a personalized reply, and routes it to your CRM/Slack. Bring your own keys; runs locally with none.
Why this exists
Speed is the highest-leverage variable in inbound sales. In the canonical study ("The Short Life of Online Sales Leads," Harvard Business Review, 2011 — Oldroyd, McElheran & Elkington), firms that attempted to contact a lead within an hour were ~7× more likely to have a meaningful conversation with a decision-maker than those who waited just an hour longer — and ~60× more than those who waited 24+ hours. Yet most teams reply in hours or days because a human has to read, qualify, and write every first response.
This agent collapses that delay to seconds: it qualifies the lead, drafts a tailored reply, and hands your team a ready-to-send message (or auto-sends the high-confidence ones) — so no good lead goes cold while someone is in a meeting.
Self-hosted and open-source. A free, ownable alternative to per-seat "instant lead response" SaaS — your lead data never leaves your infrastructure.
What it does
flowchart LR
W([Webhook<br/>form · Cal · Typeform]) -->|202, instant| Q[[Redis queue]]
Q --> R(research<br/>enrich company)
R --> QL(qualify<br/>fine-tuned classifier)
QL -->|spam/non-buyer| D[discard + log]
QL -->|real lead| DR(draft<br/>personalized reply)
DR --> RT(route<br/>CRM · Slack · send)
RT --> M[(funnel metrics<br/>attribution · latency)]
- Instant intake — the webhook returns
202immediately and a worker runs the slow part, so capture never blocks on an LLM call. - Explainable qualification — every lead gets a tier (
hot/warm/cold/spam), an ICP-fit score, a buyer-intent label, and human-readablereasons. A confidence gate decides auto-send vs. human review. - Personalized drafts — intent-aware first-touch replies, provider-agnostic (Gemini/Groq/OpenAI/…
via
litellm) with a keyless template fallback. - Real GTM integrations — Twenty / HubSpot CRM, Slack alerts, email — behind your own keys.
- Funnel analytics — source attribution, qualification rate, and speed-to-lead p50/p95, exposed as JSON and Prometheus.
- MCP server — the same capabilities exposed to Claude/Cursor as tools.
Quickstart (zero keys, 2 minutes)
git clone https://github.com/OmateLabs/speed-to-lead-agent
cd speed-to-lead-agent
make install # uv sync
make demo # runs sample leads through the full pipeline — no signups
You'll see each sample lead qualified, scored, and routed, plus a funnel summary. Then run the API:
make serve # http://127.0.0.1:8000 (docs at /docs)
curl -s localhost:8000/leads/sync -H 'content-type: application/json' -d '{
"email": "[email protected]",
"name": "Maria Chen",
"message": "Need pricing for a 40-person team — can we book a demo?",
"source": "google_ads"
}' | python -m json.tool
Configuration (bring your own keys)
Copy .env.example to .env. Every key is optional — a missing one disables that feature, it
never breaks the app. With none set, you're in DEMO_MODE (local stub model + console adapters).
| Variable | Enables | Required? | Get it |
|---|---|---|---|
LLM_API_KEY + LLM_MODEL |
LLM-written replies (else templated) | optional | Gemini / Groq (free) |
TWENTY_API_URL + TWENTY_API_KEY |
Push leads to Twenty CRM | optional | Twenty → Settings → API |
HUBSPOT_API_KEY |
Push leads to HubSpot | optional | HubSpot private app |
SLACK_WEBHOOK_URL |
New-lead Slack alerts | optional | Slack webhooks |
WEBHOOK_SIGNING_SECRET |
Verify inbound webhook signatures | recommended | self-generated |
GREENHOUSE_API_KEY |
ATS / recruiting-pipeline mode | optional | Greenhouse Harvest |
The classifier
Qualification runs behind a single Qualifier interface with two implementations:
RuleQualifier— a transparent, deterministic baseline (the keyless default). Strong, auditable, zero dependencies.- LoRA-fine-tuned intent classifier — DistilBERT fine-tuned with PEFT/LoRA (PyTorch), 744K
trainable params (1.1% of the model), served as its own inference path.
make trainproduces the adapter (~30s on a laptop); when present it loads automatically, otherwise the rule baseline is used.
Result — on a hand-written, held-out realistic set (messages unseen in training):
| Strategy | Accuracy | Macro-F1 | $/1k leads |
|---|---|---|---|
| Rule baseline (keyword) | 0.500 | 0.500 | $0 |
| LoRA classifier | 0.938 | 0.933 | ~$0 (local) |
Nearly 2× the intent accuracy of keyword rules on phrasing it never saw — for ~$0, locally, in milliseconds. That's the case for fine-tuning over a per-lead LLM call. Full methodology in docs/benchmarks.md and MODEL_CARD.md.
Tech
Python 3.12 · FastAPI · LangGraph multi-agent · pydantic · litellm · Hugging Face + PEFT/LoRA
· FAISS · Redis · MCP · Docker / Helm · GitHub Actions · Langfuse + Prometheus/Grafana.
Project layout
src/speed_to_lead/
├── api/ FastAPI app, webhook security
├── agents/ LangGraph pipeline (research → qualify → draft → route)
├── services/ qualify · enrich · draft (swappable behind protocols)
├── integrations/ CRM (Twenty/HubSpot) · Slack · email
├── analytics/ attribution + speed-to-lead funnel metrics
├── ml/ LoRA fine-tune + eval (the classifier)
├── worker/ async queue (in-memory → Redis)
└── mcp_server/ Model Context Protocol server
Deploy
- Single host:
docker compose up— api + worker + Redis + Postgres. - Kubernetes:
helm install stl infra/helm/(orkubectl apply -f infra/k8s/) — liveness/readiness probes, resource limits, non-root, optional HPA, and bring-your-own-key via a referencedSecret. - Serverless: it's a standard ASGI app — deploys to Hugging Face Spaces / Cloud Run / Render unchanged.
Roadmap
- Multi-agent pipeline + keyless demo + funnel analytics
- LoRA-fine-tuned classifier + eval scorecard
- MCP server · FAISS ICP similarity · ATS (Greenhouse) connector
- Langfuse tracing + Prometheus/Grafana dashboards (config-as-code)
- Deploy (HF Spaces / Cloud Run) + demo GIF
License
MIT © 2026 Omate Labs
Install Speed To Lead Agent in Claude Desktop, Claude Code & Cursor
unyly install speed-to-lead-agentInstalls into Claude Desktop, Claude Code, Cursor & VS Code — handles npx, uvx and build-from-source repos for you.
First time? Get the CLI: curl -fsSL https://unyly.org/install | sh
Or configure manually
Run in your terminal:
claude mcp add speed-to-lead-agent -- uvx --from git+https://github.com/OmateLabs/speed-to-lead-agent speed-to-lead-agentFAQ
Is Speed To Lead Agent MCP free?
Yes, Speed To Lead Agent MCP is free — one-click install via Unyly at no cost.
Does Speed To Lead Agent need an API key?
No, Speed To Lead Agent runs without API keys or environment variables.
Is Speed To Lead Agent hosted or self-hosted?
Self-hosted: the server runs locally on your machine via the install command above.
How do I install Speed To Lead Agent in Claude Desktop, Claude Code or Cursor?
Open Speed To Lead Agent on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.
Related MCPs
Fetch
Web content fetching and conversion for efficient LLM usage.
AWS KB Retrieval
Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
by modelcontextprotocolSpring AI MCP Server
Provides auto-configuration for setting up an MCP server in Spring Boot applications.
llm-analysis-assistant
A very streamlined mcp client that supports calling and monitoring stdio/sse/streamableHttp, and can also view request responses through the /logs page. It also
by xuzexin-hzCompare Speed To Lead Agent with
Not sure what to pick?
Find your stack in 60 seconds
Author?
Embed badge for your README
Browse similar
All ai MCPs
