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

Most Founders 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. Investors (table): fund, partner, status, last touch. and Updates (doc): quarterly investor updates; agents draft from KPIs. live next to each other; both are open to humans and agents.

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.

Fork the Investor relations tracker 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.

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.

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.

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.

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.

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.

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.