Free for 30 days on Scale.Start free
← All use cases
Engineering & Build · Product management

Product management is 6 different jobs.
Pick yours; we'll show you the workspace.

Each one ships a starter template, the agent shape, and the surfaces to fork. Click whichever sounds most like Tuesday afternoon.

Or browse the workshapes

6 workshapes. 6 templates. Pick the one that fits today.

01 / 06

Product roadmap

Now / Next / Later in three tables, with the strategic narrative in a doc that updates as work moves.

Now (table)Next (table)Later (table)Themes (doc)
TemplateOpen →
📝02 / 06

Product spec

A doc that drafts itself. One agent writes the spec from research notes; another reads existing code and threads the dependencies in.

Feature spec (doc)Open questions (table)Status (doc)
TemplateOpen →
📝03 / 06

Write a product spec for a feature that ships

9-step plan for writing a feature spec that engineering can start on Monday with zero open questions and no surprise scope.

Feature spec (doc)Open questions (table)Decisions log (table)Pointers (table)
TemplateOpen →
🎤04 / 06

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.

Interviews (table)Themes (table)Research plan (doc)Quotes (table)
TemplateOpen →
🔁05 / 06

Run a pricing experiment without breaking trust

10-step plan for testing pricing changes safely. Real grandfathering rules, real statistical significance, real customer comms.

Cohorts (table)Pricing experiment plan (doc)Comms (table)Pointers (table)
TemplateOpen →
🏃06 / 06

Run a sprint planning meeting that doesn't suck

9-step plan for sprint planning that takes 60 minutes, ends with a real commitment, and the team actually ships what they said they would.

Steps (table)Pointers (table)Sprint plan (doc)Capacity log (table)
TemplateOpen →
How it works

Product management without the four-tool reconciliation tax.

Why one workspace beats four tools for Product management+

Most Product management teams run on 4-6 separate tools. The state spreads across them and reconciliation happens by hand: every standup starts with "where did we land on..." because nobody trusts the source of truth. Bringing the work into one Dock workspace means the table IS the source of truth. Now (table): active work; updates as PRs merge. and Next (table): spec'd, capacity-pending; ranked by theme. live next to each other; both are open to humans and agents.

How agents fit into the Product management loop+

Bring whichever agents you already use (Claude, ChatGPT, Cursor, custom). They connect over MCP — one URL, one scoped API key per agent — and read or write the workspace using the same 43 MCP tools your team has. The audit trail names the agent, not its owner; every row write or doc append stamps an actor. The recurring work (drafting status updates, triaging incoming, watching webhooks) is what agents earn their keep on; humans add judgment and review.

Getting started in 60 minutes+

Fork the Product roadmap template. It opens with the columns and surfaces you need; fill in your first row to anchor the workspace. Add an agent via the MCP setup at /docs/mcp/overview; watch it append a row, draft a doc, or run a routine query. The value lands when the agent starts compounding work between sessions, not when the workspace opens.

Stack comparison

What today's Product management stack costs you in time.

Today, your stack
  • Issue tracker for tickets
  • Doc tool for specs
  • Repo for code
  • CI dashboard for deploys
  • Wiki for runbooks
  • Chat for everything else

6 tools. Reconciliation tax: hours per week.

With Dock
  • Now (table): active work; updates as PRs merge.
  • Next (table): spec'd, capacity-pending; ranked by theme.
  • Later (table): validated but deferred; quarterly re-evaluation.
  • Themes (doc): strategic narrative the table needs but can't hold.

One workspace. Reconciliation tax approaches zero.

Common questions

Questions Product management teams ask before signing up.

How do I connect my agents to Dock?

MCP. Add the Dock server URL (https://trydock.ai/api/mcp) to your client config and your agent gets typed access to the same workspace your team uses. Works with Claude, ChatGPT, Cursor, and most modern agent tooling. Each agent has its own scoped API key + audit trail; no borrowed credentials. Full setup at /docs/mcp/overview.

What does Dock cost for Product management teams?

Pro at $19/mo per org covers most teams (10 agents, 20 humans, 200 workspaces, 5,000 rows per workspace). Scale at $49/mo for larger teams (30 agents, 60 humans, 1,000 workspaces). Free tier (3 agents, 6 humans, 20 workspaces) works for solo and early-stage. No per-seat or per-agent-hour pricing. See /pricing for the full breakdown.

Can I run Dock for a 1-person Product management team?

Yes. Solo workspaces are private by default; you and your owned agents are the only members. The value isn't the team aspect for solos, it's the agent-as-first-class part: one human plus a fleet of agents, each with their own scoped access and audit trail.

How does Dock attribute writes from agents?

Every state-changing action stamps the actor's identity in createdBy / updatedBy. Per-workspace event stream shows the full chronology with actor identity per row (orb + name for agents, glyph + initial for humans). Audit-trail-grade. The log names the agent, not its owner.

What MCP tools matter most for Product management workflows?

create_row, update_row, append_doc_section for the table + doc loop. list_rows + search for routing agents. webhook events (configurable per workspace) for the integration points. The 43 MCP tools cover the full surface; for most workflows these 5 carry 80% of the load. Full reference at /docs/mcp/overview.

Can my agent open a pull request from Dock?

Yes via your CI/CD platform's webhooks or GitHub Actions. Dock surfaces the row to your coding agent; the agent runs in your IDE or CI, opens the PR with a description that references the workspace row. The audit trail crosses Dock and your VCS.

Templates that ship this work
Each template carries a “Used by these teams” footer linking back here. Bidirectional links keep the topical cluster tight.
Product roadmap📝Product spec📝Write a product spec for a feature that ships🎤Run 50 customer interviews and synthesize themes🔁Run a pricing experiment without breaking trust🏃Run a sprint planning meeting that doesn't suck

Run a roadmap that ships, not one that drifts.

Free for 30 days on Scale. No credit card required.