Agent SwarmLead Prospecting
Plug your prospecting stack into the swarm — daily discovery, drafting, and scheduling — with a human-in-the-loop gate before anything sends. Tracks "already contacted" so re-runs don't double-touch.
Plug your prospecting tools into the swarm and let agents handle discovery, drafting, and scheduling — with a human gate before anything goes out.
What it does
Every morning the swarm discovers companies with growth signals, finds the right contact (marketing, growth, ops), drafts personalized outreach per prospect, drops everything into a review folder, emails a summary, and waits for explicit human approval before sending. Tracks who's been contacted so re-runs don't double-touch.
Agents
- Lead — orchestrates the daily run.
- Researcher (or any general-purpose worker) — discovery and email drafting.
- Human-in-the-loop reviewer — you. The HITL gate blocks the workflow on a Slack reaction.
Tools & Skills
Built-in (ships with agent-swarm)
request-human-input— the HITL gate. Workflow pauses until a human reacts in Slack. See the HITL Gates pattern.slack-post/slack-reply— surface the review and accept the gate response.- agent-fs — drafts live here, one folder per day's batch. You can edit before approving.
- Swarm KV store — namespaced per-workflow state for the "contacted prospects" set, so re-fires don't re-prospect the same person.
Custom (swarm-managed)
agentmail-sending— sends the email once approved (enforces signing + signature rules). Routes replies back into the swarm via the per-account inbox.
Third-party providers
- Growth-signal source — pick any analytics or telemetry tool that can surface companies showing intent. We use Plausible, Google Search Console, and our own website telemetry.
- Contact-finder — we use Enginy; any CRM or contact-enrichment provider with an HTTP API works.
- AgentMail — outbound email with per-account inboxes that route replies back into the swarm.
These are integrations, not skills — wire them in via a script node.
Workflows / Schedules
daily-lead-prospecting— runs every morning:- Discover companies with growth signals.
- Find marketing/growth/ops contacts via your contact-finder.
- Skip anyone already in the "contacted" KV set.
- Draft a personalized outreach per prospect, store in agent-fs.
- Email a digest (subject + preview + agent-fs link to each draft) for human review.
- HITL gate — workflow blocks here.
- On approval: send via AgentMail, log into KV. On rejection: archive and continue.
Patterns used
- HITL Gates — a human approves before any outbound email sends.
Tips for new swarm users
- The HITL gate is non-negotiable for cold outbound. Agents are great at drafting; humans should sign off on tone, target, and timing.
- Keep the "contacted prospects" set in swarm KV with a TTL (90–180 days) so a prospect can be re-engaged on a sensible cadence.
- AgentMail's per-account inbox is the unlock for two-way conversations — replies route back into the swarm and can trigger follow-up flows.
- Don't over-personalize. Two facts that prove you researched the prospect beat a paragraph of synthetic empathy.
- Be honest about the swarm's role. We surface "drafted by an agent, sent by a human" — deception breaks trust the moment they ask.
Feature Development
Take feature requests from Slack or a Linear ticket and turn them into pull requests, end to end — with research, planning, implementation, review, and merge handled by specialized agents that hand context off via agent-fs.
Content Generation
Topic mining, blog posts, social posts, memes, comparison and how-to pages, and release notes — at the cadence you want, with LLM-as-judge quality gates and human craft on top before anything ships.