Research

Competitive intel

Beat the reactive 'we should do that too' cycle. Updates per competitor, weekly implications doc.

Open in Dock

Competitors

Updates

Implications

Status

TitleStatusOwner

Beat the reactive 'we should do that too' cycleactiveAgent

Competitors (table)queuedYou

Updates (doc)draftedAgent

Implications (doc)draftedYou

…

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

Beat the reactive 'we should do that too' cycle

Beat the reactive 'we should do that too' cycle. Updates per competitor, weekly implications doc.

Spin up an agent for the heavy lifting

Reads competitor blogs, changelogs, twitter nightly. Posts updates.

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

tableCompetitors
docUpdates
docImplications
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>/competitive-intel and follow the agent prompt.”

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

FAQ

Common questions on this template.

What does the competitive intel template include?

A Competitors table (one row per competitor with stage, latest move, last reviewed), an Updates doc (chronological log of competitive moves: launches, pricing changes, hires), and an Implications doc that synthesizes 'so what does this mean for us'.

How frequently should I update competitive intel?

Most teams: monthly review of the Competitors table, real-time appends to the Updates doc as moves are spotted. Quarterly synthesis pass on the Implications doc. Daily intel-watching is usually overkill outside of a hot category.

Can a research agent track competitors automatically?

Yes. Scout (a research agent) can monitor competitor blogs, changelog feeds, and X accounts daily, and append to the Updates doc when something material happens. Weekly, Argus synthesizes the new entries into the Implications doc.

Related templates

More from Research

ResearchMixed

Run 50 customer interviews and synthesize themes

12-step plan from cold list to synthesized themes doc. Real scripts, real recruiting tactics, real synthesis without the hand-waving.

ResearchMixed

Customer research notebook

Interview transcripts in, themes out. One agent indexes every transcript; another drafts the cross-cut on demand.

ResearchMixed

Investment thesis library — quarterly sourcing cycle

Quarterly sourcing cycle. Your watcher agent monitors the pass list for circumstance changes (new funding, team moves, market shifts) and surfaces re-evaluation candidates. Theses stay current.

Browse all Research templates →

Used by these teams · 1

Teams that run this template, with their full setup.

Competitive intelligenceUse case

Beat the reactive 'we should do that' cycle.

Competitor updates auto-collected nightly. A weekly implications doc. Strategy emerges instead of being chased. The indexer reads competitor blogs/changelogs/X; the writer drafts the 'should we?' essay weekly.

Open the use case