200 personalised cold emails sent over 5 days
200 personalised cold emails sent over 5 days, 15-25% reply rate, 5-15 first calls booked, your domain reputation intact, and a Prospects table you'll keep working for the next 90 days.
Run10 steps5 working days
Run a 5-day cold email outreach sprint
200 personalised cold emails sent over 5 days, 15-25% reply rate, 5-15 first calls booked, your domain reputation intact, and a Prospects table you'll keep working for the next 90 days.
Steps
Prospects
Outreach sprint plan
Sent log
+1 moreTitleStatusOwner
Define the ICP and the offer in 1 pageshippedYou
Build a 200-row prospect list with verified emailsactiveAgent
Set up a secondary sending domain (don't burn your main domain)queuedYou
Research each prospect: 3-bullet brief + 1 personalisation hookdraftedAgent
…
Public preview of the cloned workspace. Same chrome you'll see after Open in Dock.
Spin up an agent for the heavy lifting
Researches each prospect: company news, recent posts, role context, mutual connections. Outputs a 3-bullet brief per prospect.
10 steps, 6 official links, 6 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
6Agent prompts
6Official links
6Tools mapped
Surfaces
- tableSteps
- tableProspects
- docOutreach sprint plan
- tableSent log
- docStatus
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.
- 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.
- 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.
- 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>/run-a-cold-email-outreach-sprint and follow the agent prompt.”
FAQ
Common questions on this template.
Why 200 emails over 5 days, not 5000 over 5 days?
Because the bottleneck on early-stage outbound is reply rate, not list size. 200 deeply-researched emails to a tight ICP get 15-25% reply rates and 5-15 booked calls. 5000 sprayed emails get 1-2% reply rates and burn your domain reputation in the process. The math: 200 * 20% = 40 replies, while 5000 * 2% = 100 replies but with worse deliverability for the next sprint and 90% of replies being 'not interested'. Quality wins on both metrics that matter.
Should I use my main domain or a secondary domain for cold email?
Always a secondary. Cold email volume on your primary domain destroys deliverability for customer + transactional email. Buy yourcompany.co or yourcompanyhq.com, set up SPF/DKIM/DMARC, warm for 14 days, and use that. Replies forward to your real inbox via mail forwarding so you don't miss anything.
What reply rate should I expect?
For 200 deeply-personalised emails to a tight ICP with trigger events: 15-25% reply rate, 5-10% positive-reply rate, 5-15 booked calls. For broader ICPs without triggers: 5-10% reply rate. For spray-and-pray: 1-3% reply rate, but the marginal positive-reply rate is so low and the deliverability cost so high that the absolute volume of booked calls is often lower.
Can I fully automate the cold email pipeline?
Partially. Agents are great at: research, draft generation, reply categorisation, follow-up drafting, analysis. Agents are bad at: judging draft quality, replying to nuanced objections, choosing which prospects to cut. The pattern that works is: agent drafts at scale, human reviews every draft (30 sec each), human sends. Full automation tanks reply rates because every email reads identical and the prospect smells the agent.
What does the cold email outreach stack cost?
Free path: a secondary domain ($12/year) + your own SMTP + agent for drafts. ~$20/year. Paid path: secondary domain + Apollo ($59/mo) + Instantly or Smartlead ($37-39/mo) + Hunter or NeverBounce ($49/mo) + agent API tokens (~$10-30/mo) = around $150-200/mo. Most founders running their first sprint can do it on the free path; scale to paid tooling once the sprint is repeatable.
How often can I run a sprint to the same prospect list?
Once every 90-180 days minimum. Sending the same prospect 4 emails in 30 days gets the prospect's domain to mark you as spam. Each sprint also burns your fresh-prospect inventory in that ICP — by sprint 3 you should be either expanding the ICP or running a different motion (events, content, partnerships).
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.
Used by these teams · 1
Teams that run this template, with their full setup.
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.
About this template
Curated by the Dock team at Vector Apps Inc. 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.