Free for 30 days on Scale.Start free
Run10 steps3-5 days build, ongoing weekly use

Build a sales-followup agent that never forgets

An agent watching your pipeline daily, drafting followups at the right cadence point, surfacing stalling deals in a morning Next Actions digest, never sending without your approval, deals that slip through your fingers go from common to rare.

Open in DockSee every step →

An agent watching your pipeline daily

An agent watching your pipeline daily, drafting followups at the right cadence point, surfacing stalling deals in a morning Next Actions digest, never sending without your approval, deals that slip through your fingers go from common to rare.

Spin up an agent for the heavy lifting

Drafts the followup email or LinkedIn message at the right cadence point.

10 steps, 13 official links, 5 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
10Steps
5Agent prompts
13Official links
6Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docSales agent plan
  • tablePipeline
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/build-a-sales-followup-agent and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Why not just use my CRM's built-in followup automation?
CRM automation is rule-based and templated: 'send template X if no reply in N days.' An agent reads the actual thread context, picks the right template AND fills it with details from the conversation, drafts something that sounds like you, and surfaces stalling deals based on patterns the rules can't see (a vague 'looking forward to it' that didn't go anywhere). You can keep the CRM alongside the agent, the agent reads + writes through its API.
Won't auto-drafted emails feel generic and hurt my reply rate?
Generic templates do, contextual drafts don't. The pattern in this template reads the last 5-10 emails in the thread + meeting notes + the deal-specific Pipeline row, then drafts an email that references those details. Reply rates on contextual drafts are typically equal or better than fully-handwritten followups, with 80-90% less time per draft. The constraint is keeping the templates short (under 100 words) and the placeholders specific.
Can I let the agent send automatically?
No, and the template doesn't support that. The risk-reward isn't worth it: one auto-sent draft to a key prospect with the wrong context loses the deal. The pattern is draft-but-don't-send: the agent drafts, you click Send. Total time per draft after agent: 30-60 seconds (read, light edit, send). Total time without agent: 5-10 min (think, write, edit, send). The agent saves the slow part; the click is fast.
How does this interact with my CRM?
Two patterns. (a) The Dock Pipeline surface is the source of truth; the agent reads + writes the Pipeline rows; if you want CRM data, you mirror nightly. (b) Your CRM is the source of truth; the agent reads via the CRM API and updates rows there. Pattern (b) is better if your team already lives in the CRM; pattern (a) is better if the CRM is creaky and you want a parallel source of truth that's faster + more agent-friendly.
What does this cost in API tokens?
For a 50-deal pipeline with daily scans + 5-10 drafts/day on Claude Sonnet: $20-50/month. With Opus drafts on the high-stakes deals (Negotiation stage): $40-100/month. CRM + cron + hosting: $0-30/month on free tiers. Total: $30-150/month on top of your existing CRM + email subscriptions. ROI is the cost of one missed follow-up that closes-lost a $5K+ deal; you do the math.
Can my AI agents help build the agent?
Yes. The template ships agent prompts for the slow parts: drafting cadence rules from your historical close patterns, drafting message templates per stage, generating the daily Next Actions digest, the weekly win/loss review, and the iteration plan. The Pipeline + Brief surfaces are the canonical record, every deal's state, every template version, every weekly review.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →
Used by these teams · 2

Teams that run this template, with their full setup.

SalesUse case

A pipeline that lives where the work happens.

Deals in a table, notes per account, lost reasons separate. Agents summarize calls, draft followups, advance stages on closed-won. The relationship context that doesn't fit a column.

Open the use case
Agency operatorsUse case

Cross-client visibility without per-client tool sprawl.

Clients in a table, engagement context per client, a renewal queue. Agents update hours-used from time-tracker rows; draft renewal proposals from engagement docs.

Open the use case

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.