Free for 30 days on Scale.Start free
Run5 steps1 hour first-time setup, ongoing ~5 min/day review

Vendor contract renewal tracker

A rolling daily workspace where every vendor contract has one row, the agent surfaces upcoming renewals at 90 / 60 / 30 days out with a tailored recommendation, and you never get caught flat-footed by an auto-renew that fired without notice.

Open in DockSee every step →

A rolling daily workspace where every vendor contract has one row

A rolling daily workspace where every vendor contract has one row, the agent surfaces upcoming renewals at 90 / 60 / 30 days out with a tailored recommendation, and you never get caught flat-footed by an auto-renew that fired without notice.

Spin up an agent for the heavy lifting

Reads Contracts daily, flags every renewal hitting a 90 / 60 / 30 day window, drafts a 3-5 sentence renewal recommendation per contract, appends to Renewal alerts and Status. Never modifies Contracts.status or Contracts.allocated without owner sign-off.

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
  • tableContracts
  • docSetup guide
  • docRenewal alerts
  • 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>/vendor-contract-renewal-tracker and follow the agent prompt.”

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

Common questions on this template.

How does this know which contracts are coming up?
A daily Python script reads the Contracts table from this Dock workspace, computes days until each row's Renewal Date, and fires an alert the first time a contract enters the 90 / 60 / 30 day window. Each alert is tracked on the row itself so the same window doesn't fire twice.
Does the agent renew or cancel contracts on my behalf?
No. The agent surfaces upcoming renewals and drafts a recommendation for each. You decide and message the vendor. The agent doesn't touch Contracts.status, Annual Value, or Auto-Renew — those are operator-only fields.
What if I don't have Slack?
Skip the SLACK_WEBHOOK_URL env var. The agent still appends every alert to the Renewal alerts doc surface and the Status doc surface inside Dock. You'll see them when you open the workspace.
Can I change the alert windows?
Yes. Set ALERT_WINDOWS in .env to a comma-separated list of day counts. The default is 90,60,30. If you only want one alert, set it to 60. If you want earlier visibility for high-value contracts, set 120,90,60,30. The script and the agent both read this value.
Does this work with Salesforce / HubSpot for contract data?
Not in v1 — Contracts is the canonical source. The script reads from the Dock table. A future extension can pull contract metadata from a connected CRM or CLM (Ironclad, ContractWorks, Spotdraft) on a daily sync and write to Contracts.
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.