Plural by default. Tuned for the work you actually do.
23 entry points into Dock — same workspace shape, different rows. Each page ships a dashboard mockup of what the workspace looks like, the agent archetypes that fill the stack, and the audit-log proof that the agents you bring keep their own identity.
Use cases are audience-focused journey pages. They explain how a kind of work runs on Dock — which agents fill which roles, what the workspace looks like, what the wire format is. Templates are forkable workspace structures: open one in Dock with a click, fill in your own rows. Each use case here points at the templates that match. Browse templates →
Engineering & Build
5 use casesWorkspaces for shipping software with agents in the loop — sprint boards, spec docs, incident war rooms.
Ship more code. Run agents on the build.
Sprint backlog, spec docs, deploy logs — every artifact your engineering team already writes lives in one workspace. Agents read it before acting, write the small things at high frequency, and hand off cleanly to the next human or agent.
Ship a roadmap your team actually reads.
Now / Next / Later in three tables, a themes doc that explains why, and the agent stack that keeps it current. Stop maintaining a roadmap that drifts from reality.
Run design reviews where every comment ships.
Submitted / Reviewing / Approved as a queue. Critique notes as a doc the design system grows from. Agents pull the latest Figma frame on the row, draft initial critique against your principles, and surface patterns across reviews.
Run incidents in the same place you write the postmortem.
Live war-room doc, incidents table, postmortem library — one workspace. Agents timestamp every status change in the war room, draft the postmortem skeleton from the timeline, and cross-reference past incidents on the same system.
Triage your issue queue without losing your weekend.
Issues, RFCs, release notes — the three workflows OSS maintainers run by hand. Agents read new issues, attempt repro, label, and surface duplicates. The RFC doc replaces a sprawling GitHub thread.
Go-to-market
5 use casesWorkspaces for marketing, sales, and customer-facing teams — calendars, pipelines, account notes.
More words. Fewer drafts in flight.
Editorial calendar, drafts, distribution — three surfaces, one workspace. Your writer agent drafts the long form, the runner schedules and cross-posts, the indexer reports what's resonating so the calendar can adjust.
A pipeline that lives where the work happens.
Lightweight CRM with the relationship context that doesn't fit a column. Deals in a table, account notes per account, lost reasons in a separate table. Agents summarize calls, draft followups, advance stages on closed-won.
Account continuity that survives CSM turnover.
Health, expansion potential, MRR — your account roster. QBR notes per account, a renewal queue that surfaces what's coming up. Agents read usage data, mark accounts at-risk, draft QBR docs from prior notes.
A queue that triages itself.
Inbound tickets, KB articles, response patterns — one workspace. Agents read incoming tickets, attempt repro, surface duplicates against existing KB articles, and draft responses for human review.
Campaigns that ship + the metrics next to them.
Campaigns table, briefs per campaign, performance data on the same row. Agents draft briefs, pull performance numbers, surface what's resonating so the calendar can adjust.
Research & Insights
3 use casesWorkspaces where the artifact is synthesis — interviews, themes, competitive intel.
Interviews in. Themes out. Faster.
Customer interviews, transcripts, verbatim quotes, themes — all in one workspace. Synthesis stops being a redo-every-time activity because every prior interview is still indexed and addressable.
Ad-hoc analytics asks stop drowning in Slack.
Requests, analyses, dashboards in one workspace. The SQL + reasoning + result lives next to the request, so the next similar question gets a 2-min copy-edit instead of a re-derivation.
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.
Operations & People
4 use casesWorkspaces for the work that holds the team together — runbooks, recruiting, compliance, onboarding.
Runbooks that get tested + run.
Vendor management, runbook library, incident-style ops drills. Agents draft new runbooks from incident threads; surface stale ones for refresh; track vendor renewals.
Pipelines that survive role pivots.
Candidates table, interview feedback per candidate, role specs as docs. The indexer summarizes interviewer notes into per-candidate doc, the runner advances stages.
Onboarding and offboarding without the dropped balls.
Per-hire onboarding checklist, offboarding queue, perf-review cycles. Agents mark items done as IT/Slack/Stripe webhooks fire; nudge on overdue.
Contracts, IP, and audit prep in one searchable index.
Active contracts, IP filings, compliance controls — three tables, three docs. Agents flag expiring contracts, draft initial review notes, cross-reference prior matter notes.
Solo & Agency
6 use casesWorkspaces for one human plus a fleet of agents — solo founders, creators, agencies, investors.
Run the team you don't have.
One workspace, one agent stack, your full ops layer. Build, write, run ops, follow up — all on one substrate. Stop switching tabs to be your own PM.
The board you wish you had.
Investor pipeline, fundraise narrative, board prep — all in one workspace. Agents draft updates from KPI rows, summarize founder updates, surface follow-up patterns.
Cross-client visibility without per-client tool sprawl.
Clients in a table, engagement context per client, a renewal queue. Agents update hours-used from time-tracker rows; draft renewal proposals from engagement docs.
Pipelines that compound across funds.
Deal flow journal, investment thesis library, portfolio tracker. Agents read incoming pitches against your theses, surface companies on your pass list whose circumstances may have shifted.
Predictable cadence without scrambling on send day.
Idea bank, issues table, drafts surface. The writer drafts from a theme + idea-bank rows; the runner pings 48h pre-send if no draft.
Per-client narrative + reusable framework library.
Clients in a table, session notes per client, framework library as a doc. Agents draft session prep from prior notes; flag engagements ending in 30 days.