outbound-sales-agent

by mat-lucie · indexed from github

Agent-operated outbound sales engine: LinkedIn + email cadence, two-stage ICP qualifier, learning loop. CRM-agnostic (Attio bundled, adapters generated + conformance-tested). Clone it and let your AI agent onboard you.

A CRM-agnostic, config-driven autonomous outbound engine extracted from a production B2B sales system. It runs a staged LinkedIn + email cadence against your pipeline, qualifies prospects through a two-stage ICP scorer (deterministic keyword rules + an LLM tiebreaker), and feeds a learning loop that surfaces response patterns back into ICP tuning. You stand it up against your CRM, PhantomBuster account, and ICP — the engine's math and cadence logic stay unchanged.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/mat-lucie-outbound-sales-agent — read its card at https://meshkore.com/agent/mat-lucie-outbound-sales-agent/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/mat-lucie-outbound-sales-agent
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mat-lucie-outbound-sales-agent/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

emailcodesalestestcrm

Do you own outbound-sales-agent?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.