Free for 30 days on Scale.Start free
Run11 steps60-90 days from kickoff to 'self-running'

Onboard your first 10 customers

10 customers using the product weekly, hitting their first success metric within 30-60 days, willing to give a reference call, and giving you 80% of the bug reports / feature requests that shape the next 6 months of roadmap.

10 customers using the product weekly

10 customers using the product weekly, hitting their first success metric within 30-60 days, willing to give a reference call, and giving you 80% of the bug reports / feature requests that shape the next 6 months of roadmap.

Spin up an agent for the heavy lifting

Drafts kickoff agendas, weekly check-ins, milestone celebrations, and the case-study brief from real usage data.

11 steps, 5 official links, 4 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
11Steps
4Agent prompts
5Official links
5Tools mapped
Surfaces
  • tableCustomers
  • docOnboarding plan
  • tableIssues
  • tablePointers
  • 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>/onboard-your-first-10-customers and follow the agent prompt.”

FAQ

Common questions on this template.

Why white-glove and not self-serve at this stage?
Self-serve onboarding works when you have 10000 customers and a 5% activation rate — the 500 who succeed pay for the 9500 who don't. With 10 customers and a 50%+ activation expectation, the math inverts: every customer matters too much to risk on docs and onboarding flows you haven't validated. White-glove until customer 50+ is the right default.
How long does white-glove onboarding take per customer?
Realistic budget: 5-10 hours/week per customer for the first 30 days, tapering to 1-2 hours/week by day 60. With 10 active customers in onboarding at once, expect 1-2 founders or CSMs full-time on this work. That's why 'first 10 customers' is a deliberate ceiling.
Should I onboard 10 customers in parallel or 2-3 at a time?
2-3 in parallel until you've documented the template, then scale up. Onboarding 10 in parallel before you know what you're doing means each customer gets a worse experience and you can't learn fast enough between them.
Can my AI agents actually help with customer success?
Yes for the off-stage work: drafting kickoff agendas, drafting check-in recaps, monitoring usage data and flagging churn risks 2-3 weeks early, drafting case study first drafts. Not for the customer-facing call itself. Use agents to keep you informed and ready, not to replace the human relationship.
What's the most common reason early customers churn?
Three reasons in order: (1) they never hit the first success metric because onboarding stalled (the most common, and most preventable), (2) the champion left or changed role internally and the new owner doesn't see value, (3) the product doesn't actually solve the problem they thought it did (real fit issue, hardest to fix). Watch for (1) by week 3 — that's when you can still save it.

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.