Free for 30 days on Scale.Start free
Run4 stepsOngoing, ~30 min/week + 1 hr at month end

Hiring pipeline, monthly cycle

A monthly-cycling hiring pipeline where no candidate falls through the cracks for 5+ days, every interview has a scorecard, every closed role has a why, and every month ends with honest funnel conversion data the team can act on.

Open in DockSee every step →

A monthly-cycling hiring pipeline where no candidate falls through the cracks for 5+ days

A monthly-cycling hiring pipeline where no candidate falls through the cracks for 5+ days, every interview has a scorecard, every closed role has a why, and every month ends with honest funnel conversion data the team can act on.

Spin up an agent for the heavy lifting

Your tracker agent (yours) flags candidates stuck in a stage 5+ days, surfaces them in the Friday memo so they don't rot. Pings the candidate owner via MCP send_message.

4 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
4Steps
3Agent prompts
3Tools mapped
Surfaces
  • tableRoles
  • tableCandidates
  • docFriday memo
  • tableScorecards
  • docMonth 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>/hiring-pipeline and follow the agent prompt.”

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

Common questions on this template.

When do I graduate to a real ATS like Greenhouse or Ashby?
Around 50 employees, or when you have 8+ concurrent roles, or when you need DEI dashboards / OFCCP reporting / structured-interview kits. Below that, this workspace is faster + cheaper + more flexible. The data shape (Roles + Candidates + Scorecards) maps cleanly to Greenhouse fields if you migrate later.
How do I keep candidate PII safe?
Limit what's in the row: name, role, LinkedIn URL, source channel, current stage. Don't paste resumes, salary history, or personal contact info. Use the `pii_minimized` row flag to track which rows are using initials only (some founders prefer this). For email comms, use your inbox; the workspace tracks state, not communications.
Can the agent send rejection emails?
No, by design. Rejections are high-judgment communication; the agent flags 'ready for rejection decision' but the human writes and sends the email. Auto-rejection is how candidates get the form-letter experience that hurts your employer brand for years.
How do I handle two stages at once (e.g. interview loop + reference checks in parallel)?
Add a `parallel_stage` column. The primary stage is the funnel position (e.g. Interview loop), the parallel_stage tracks side-quests (Reference checks pending). The Friday memo treats parallel_stage as informational; it doesn't trigger the 5-day stuck-flag.
What if I have 8+ open roles?
You're at the edge of this template's intended scale. Two options: (1) fork per team or per function (engineering pipeline, GTM pipeline) so each Friday memo is focused, or (2) graduate to a real ATS. Once you're juggling 30+ candidates across 10+ roles, the value of structured ATS workflows starts to outweigh the flexibility of a workspace.
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.