Run

Agency client portfolio

Cross-client visibility without per-client tool sprawl. Hours-used vs allocated drives margin and renewal conversations.

Open in Dock

Clients

Engagement docs

Renewal queue

Status

TitleStatusOwner

Cross-client visibility without per-client tool sprawlactiveAgent

Clients (table)queuedYou

Engagement docs (doc)draftedAgent

Renewal queue (table)draftedYou

…

Public preview of the cloned workspace. Same chrome you'll see after Open in Dock.

Cross-client visibility without per-client tool sprawl

Cross-client visibility without per-client tool sprawl. Hours-used vs allocated drives margin and renewal conversations.

Spin up an agent for the heavy lifting

Updates hours-used from time-tracker rows. Flags overruns.

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

tableClients
docEngagement docs
tableRenewal queue
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.

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.
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.
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>/agency-portfolio and follow the agent prompt.”

Full MCP setup guide Other agent clients (Cursor, custom MCP)

FAQ

Common questions on this template.

What does the agency portfolio template ship with?

A Clients table (one row per active engagement with stage, ARR, owner), Engagement docs (one per client, holding the SOW + meeting notes + deliverables), and a Renewal queue table tracking upcoming contract renewals.

Who is this template for?

Boutique agencies, design studios, and consulting practices with 5-50 clients. Solo consultants get less from the multi-surface shape; large agencies usually want a vertical agency-management tool.

Can my agents help run client engagements?

Yes. A common pattern: Argus drafts deliverable summaries weekly per client, Flint pings on stale renewal-queue rows 60 days out, Scout researches incoming prospects and seeds the Clients table.

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 →

Used by these teams · 1

Teams that run this template, with their full setup.

Agency operatorsUse case

Cross-client visibility without per-client tool sprawl.

Clients in a table, engagement context per client, a renewal queue. Agents update hours-used from time-tracker rows; draft renewal proposals from engagement docs.

Open the use case