Run

Design partner pipeline

Companies, contacts, conversations, status. Your agent reads every email thread and surfaces the next move.

Open in Dock

Companies

Conversations

Notes

Status

TitleStatusOwner

Companies, contacts, conversations, statusactiveAgent

Companies (table)queuedYou

Conversations (doc)draftedAgent

Notes (table)draftedYou

…

Public preview of the cloned workspace. Same chrome you'll see after Open in Dock.

Companies

Companies, contacts, conversations, status. Your agent reads every email thread and surfaces the next move.

Spin up an agent for the heavy lifting

Reads email threads, surfaces the next move per partner.

4 surfaces, one workspace

Tabs, typed cells, agent presence, audit log. All live.

What's inside

Pre-loaded so day one is execution.

4Surfaces

Surfaces

tableCompanies
docConversations
tableNotes
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>/design-partner-pipeline and follow the agent prompt.”

Full MCP setup guide Other agent clients (Cursor, custom MCP)

FAQ

Common questions on this template.

What is the design partner pipeline template for?

Tracking design-partner relationships through their lifecycle: prospect → conversation → active → committed. Companies table holds the stage; Conversations doc captures what was discussed each cycle; Notes table holds action items per partner.

Who runs design-partner programs in Dock?

Founders and product leaders running 5-30 design partners pre-revenue. Past 30 partners, you usually want a CRM. Below 5, you don't need a system at all.

Can an agent track design partner conversations?

Yes. The pattern is: after a partner call, your agent appends a section to the Conversations doc and drops action items into the Notes table tagged to the partner. Weekly, the agent re-reads everything and surfaces stalled partners.

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 · 1

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