Free for 30 days on Scale.Start free
Run4 stepsOngoing, ~30 min/week + 1 hr at month end

Customer discovery pipeline, monthly cycle

A monthly-cycling discovery pipeline where every conversation has a structured row, every theme is grounded in 3+ conversations, every hypothesis has a status backed by evidence, and every month produces honest signal on what's changed in customer speak.

Open in DockSee every step →

A monthly-cycling discovery pipeline where every conversation has a structured row

A monthly-cycling discovery pipeline where every conversation has a structured row, every theme is grounded in 3+ conversations, every hypothesis has a status backed by evidence, and every month produces honest signal on what's changed in customer speak.

Spin up an agent for the heavy lifting

Your synthesizer (yours) reads new Conversations rows, tags them against existing Themes, drafts new candidate themes when patterns emerge.

4 steps, 0 official links, 3 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.

6Surfaces
4Steps
3Agent prompts
3Tools mapped
Surfaces
  • tableConversations
  • tableThemes
  • tableHypotheses
  • docFriday memo
  • docMonth retro
  • 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>/customer-discovery-pipeline and follow the agent prompt.”

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

Common questions on this template.

How is this different from `run-50-customer-interviews`?
That template is a one-off sprint: ship 50 interviews in 3 weeks, build the synthesis at the end. This template is the operating cycle after the sprint, when you're at 3-8 conversations per week ongoing. The sprint produces the seed Themes + Hypotheses; this cycle keeps them current. Most teams need both: the sprint at the beginning, the cycle after.
How many conversations a week is the right number?
3-8 is the sustainable cadence for a founder doing discovery alongside building. Below 3 the signal is too thin; above 8 you stop having time to synthesize what you heard. If you need more volume, hire a researcher; the agent can help with synthesis but it can't conduct conversations.
How do I handle conversations that aren't recorded?
Paste the 3 best quotes you remember + sentiment into the row right after the call. Memory degrades fast: 30 min after the call you remember 80%, 4 hours later 40%. Build the discipline of logging within the same calendar hour as the call.
Can the agent run the conversations for me?
No. Agents are bad at conversation: they don't pause, they don't read tone, they don't lean into surprise. The agent's job is to prep (3 questions before the call) and synthesize (themes after the call). The conversation itself is a high-bandwidth human task.
What if customers use vocabulary I don't understand?
Quote them verbatim, even when the language sounds weird. Customer vocabulary is the input to your positioning; if you translate it into your team's words, the signal dies on the way in. The agent surfaces frequency shifts in customer language each month so you can spot when their words drift.
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 →

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.