Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing ~5 min/Sun to update weekly_metrics.json

Weekly management dashboard

A Monday-morning dashboard workspace where pipeline and revenue come from HubSpot automatically, cash and headcount come from a small JSON file you update Sunday night, and Claude writes the commentary fresh every week.

Open in DockSee every step →

A Monday-morning dashboard workspace where pipeline and revenue come from HubSpot automatically

A Monday-morning dashboard workspace where pipeline and revenue come from HubSpot automatically, cash and headcount come from a small JSON file you update Sunday night, and Claude writes the commentary fresh every week.

Spin up an agent for the heavy lifting

Pulls HubSpot pipeline + closed won every Monday at 7 AM, reads weekly_metrics.json, drafts executive commentary, appends a row to Weekly metrics and a section to Weekly commentary. Never modifies past rows or sections.

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
4Tools mapped
Surfaces
  • tableWeekly metrics
  • docSetup guide
  • docWeekly commentary
  • 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>/weekly-management-dashboard and follow the agent prompt.”

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

Common questions on this template.

What if I don't use HubSpot?
Setup guide includes the SOQL swap for Salesforce (Opportunities with StageName != Closed Lost for pipeline, StageName = Closed Won + CloseDate >= this_week for closed won) and the GET /api/v1/deals swap for Pipedrive (status=open for pipeline, status=won&start_date=YYYY-MM-DD for closed won). Set the relevant env vars and adjust get_pipeline_metrics() accordingly.
Why a JSON file instead of a Dock table for manual metrics?
weekly_metrics.json is the smallest possible input surface. Sunday night, you open one file, change a few numbers, save. Doing the same thing through a Dock table means switching context to the browser, finding the right cell, etc. The dashboard surface is the output; the JSON file is the input. Keep them separate.
Can the agent update weekly_metrics.json on my behalf?
No. The agent reads weekly_metrics.json but never writes it. Cash balance and headcount are facts the operator owns. Letting the agent populate them creates an attribution problem when the Monday number looks wrong. Set the Sunday reminder instead.
What if Monday morning's commentary surfaces something I don't want shared?
Edit the section. Weekly commentary is a doc surface; you can rewrite or delete sections directly. The agent doesn't re-generate past sections, so your edits stick. For weeks where you want a totally different tone (board update vs. team standup), edit the prompt in generate_commentary() once.
Does this work alongside an existing BI tool?
Yes. The Monday dashboard is a snapshot, not a replacement for Looker, Metabase, or Snowflake. Pipeline and revenue numbers should match your BI tool. If they don't, the most common reason is the HubSpot deal stage filter (closedwon spelling, custom stages); check Settings, CRM, Deal Stages.
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.