Free for 30 days on Scale.Start free
Run5 stepsOngoing, ~1 hr/month + 1 hr at quarter end

Investor update cadence, quarterly cycle

A quarterly-cycling investor update workspace where the monthly draft takes 30 min instead of 4 hours, asks are tracked across updates, KPIs roll forward without manual aggregation, and quarter-end produces honest data on which investors actually engage.

Open in DockSee every step →

A quarterly-cycling investor update workspace where the monthly draft takes 30 min instead of 4 hours

A quarterly-cycling investor update workspace where the monthly draft takes 30 min instead of 4 hours, asks are tracked across updates, KPIs roll forward without manual aggregation, and quarter-end produces honest data on which investors actually engage.

Spin up an agent for the heavy lifting

Your update drafter (yours) reads this month's KPIs row + your bullet notes + last update + Asks log status, drafts the monthly update doc following the canonical structure.

5 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
5Steps
3Agent prompts
3Tools mapped
Surfaces
  • tableKPIs
  • tableInvestors
  • docLatest update
  • tableAsks log
  • docQuarter 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>/investor-update-cadence and follow the agent prompt.”

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

Common questions on this template.

Should I include all the bad news?
Yes, with judgment. Investors who get only good news for 12 months and then a 'we're shutting down' email feel betrayed. Investors who hear about the hard quarters along with the good ones trust you and lean in when things get hard. The Lowlights section forces this discipline; don't skip it.
What if my KPIs aren't growing?
Show them anyway. Stagnation is data. Investors will infer that you're hiding worse data if KPIs stop appearing. The honest framing is: 'MRR flat at $12k for the third month, here's what we're trying'. That's a stronger update than 'big things coming next month' for the third month in a row.
Can my agent send the update?
No, by design. The send is the highest-stakes step in the cycle: voice, recipient list, BCC vs To, attachments. Agents don't send; founders send. The agent's job is to make the draft 80% done so your 20% is the high-judgment part.
Should asks go in every update or just sometimes?
Every update. Asks are the value exchange: investors get insight, you get help. Vague asks ('intros to good people') get ignored. Specific named asks ('intros to head-of-payments at fintech series-B companies in NYC') get delivered. The Asks log forces you to track which asks deliver, so over time you learn what to ask for.
How do I track replies if investors reply to my email?
Two patterns: (1) Forward each reply to a workspace-monitored email address (Dock can read that surface), or (2) paste reply notes directly into Latest update's 'incoming replies' section. The agent reads either and updates Investors.last_replied + relevant Asks log rows. Replies in your inbox stay in your inbox; the workspace tracks the metadata.
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.