Free for 30 days on Scale.Start free
Research

Customer research notebook

Interview transcripts in, themes out. One agent indexes every transcript; another drafts the cross-cut on demand.

Interview transcripts in

Interview transcripts in, themes out. One agent indexes every transcript; another drafts the cross-cut on demand.

Spin up an agent for the heavy lifting

Indexes new interviews, tags themes, surfaces related quotes.

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
  • tableInterviews
  • tableVerbatim quotes
  • docThemes
  • 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.

  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-research and follow the agent prompt.”

FAQ

Common questions on this template.

What's in the customer research template?
Three surfaces: an Interviews table (one row per call with status, role, summary), a Verbatim quotes table (tagged by theme), and a Themes doc that synthesizes patterns across interviews.
Why split quotes into a separate table?
Pattern recognition. With quotes as rows tagged by theme, you can sort by tag and see how many independent voices said the same thing. A theme with 1 quote is a hunch; with 5+ it's a finding.
Can an agent help synthesize themes?
Yes. A common setup: after each interview, Scout drafts a row on the Verbatim quotes table; weekly, Argus reads the table and updates the Themes doc. The doc stays current without anyone hand-summarizing.

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 . 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.