Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing ~10 min/week review

Weekly pipeline health report

A Monday-morning workspace where every open deal has one row scored Green / Yellow / Red, a markdown coverage report drafted for the sales meeting, and an agent that never edits CRM fields on its own.

A Monday-morning workspace where every open deal has one row scored Green / Yellow / Red

A Monday-morning workspace where every open deal has one row scored Green / Yellow / Red, a markdown coverage report drafted for the sales meeting, and an agent that never edits CRM fields on its own.

Spin up an agent for the heavy lifting

Reads CRM every Monday at 6 AM, scores each open deal for stage health and slippage, writes one Pipeline row per deal, drafts a coverage report into Reports, posts a Status entry. Never edits deal amount, stage, or close date in the CRM.

5 steps, 0 official links, 2 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.

4Surfaces
5Steps
2Agent prompts
5Tools mapped
Surfaces
  • tablePipeline
  • docSetup guide
  • docReports
  • 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>/weekly-pipeline-health-report and follow the agent prompt.”

FAQ

Common questions on this template.

Does the agent edit deals in my CRM?
No. The agent only reads from the CRM. Amount, Stage, Close Date, Owner are all rep-controlled fields that the agent never writes. The agent writes to Dock surfaces only: Pipeline rows, Reports sections, Status paragraphs.
How does it handle multi-pipeline orgs?
One workspace per pipeline. Fork this template per pipeline (New Business, Renewal, Expansion). The PIPELINE_ID env var locks each workspace to one pipeline so the stage rules align.
What if our reps don't log activities consistently?
Last Activity Days will trip every deal into Yellow or Red. The Health rules tune via env vars (ACTIVITY_YELLOW_DAYS, ACTIVITY_RED_DAYS), but the deeper fix is rep behavior. The Status entries will flag this so the operator sees the systemic issue.
Can I customize the Health scoring?
Yes. Open run_pipeline_report.py and adjust STAGE_TYPICAL_DAYS (dict of stage to expected days), ACTIVITY_YELLOW_DAYS / ACTIVITY_RED_DAYS, SLIP_RED_THRESHOLD. The Extending section in Setup guide shows how to add custom rules (e.g. Red on late-stage with no demo logged).
Does this work with Salesforce?
Yes with code edits. The default script targets HubSpot v3 CRM API. The Extending section in Setup guide shows the simple-salesforce swap: same compute logic, swap the fetch_open_deals() body to a SOQL query against Opportunity where IsClosed = false. Pipedrive is similar with python-pipedrive.

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.