What is Dreamstate
Dreamstate runs GTM work in one workspace across the web app, Architect, CLI, MCP, and REST.
Lists in workbooks, outreach sequences, the shared inbox, social publishing, AI visibility, CRM records, and the workflows between them run in one workspace. Every job is reachable from the web app with Architect, the dreamstate CLI, and any MCP client, over one API with the same approvals and one credit balance.
Reading these docs with an agent? Start with /llms.txt for the page map, or /llms-full.txt for the complete text.
The guides, in order
- Your first session: Build a first workbook from workspace context and a sourcing plan.
- Warm network first: Turn post engagement into a worksheet and a sequence.
- Run a 50-lead outbound pilot: Build a worksheet, validate a sequence, and prepare a small outbound pilot.
- Build a founder posting system: Create a social drafting and scheduling system from workspace context.
- Turn replies into meetings: Use Inbox context and CRM records to draft follow-up work.
- Run a visibility sprint: Measure visibility evidence and save useful findings in Context.
- Speed to lead: Build a workflow that connects worksheet, sequence, and trigger work.
- Weekly review: Review runs, sequence activity, worksheets, and credit activity every week.
- Set up cold email infrastructure: Prepare a separate sending domain, two mailboxes, DNS readiness, and warm-up checks before outbound.
- Migrate one Clay table: Import one Clay table, rebuild columns, review ten pilot rows, and compare per-row cost.
- Prioritize identified website visitors: Add identified visitors to CRM context and read a daily ranked contact queue.
- 30-day GTM review: Review monthly spend, campaign results, failed-run causes, and one verdict per live motion.
- Launch a client workspace: Set up client context, review three plays, and quote first paid step.
- Clean up a worksheet: Use worksheet state and provenance to clean up working rows.
- Keep the CRM clean: Maintain saved records and their relationships in the workspace.
- Find out why something failed: Inspect workflow, worksheet, and sequence evidence to diagnose a failed run.
Where each job lives
| Layer | Pack | Where it is |
|---|---|---|
| data | tables: Working lists, worksheets, sources, columns, and rows. | Workbooks /dashboard/workbooks |
| data | crm: Saved canonical people, companies, relationships, and deals. | Records /dashboard/records/person |
| knowledge | knowledge: Workspace context, documents, research, and revisions. | Context /dashboard/context |
| knowledge | visibility: AI visibility, attribution, and competitor evidence. | AI Visibility /dashboard/analytics?view=ai-visibility |
| action | sequence: Outreach sequences, cadence steps, and enrollment. | Sequences /dashboard/automations/sequences |
| action | social: Social drafts, schedules, publishing, and performance. | Calendar /dashboard/calendar |
| action | workflow: Automation graphs, triggers, runs, and diagnostics. | Workflows /dashboard/automations/workflows |
| action | unibox: Messages and replies in existing conversations. | Inbox /dashboard/unibox |
| action | tasks: Assigned work, due dates, delegation, and review. | Tasks /dashboard/tasks |
| control | integrations: Third-party connections, credentials, health, and sync. | Settings, Integrations /dashboard/settings?tab=integrations |
| control | senders: Sender identities, mailbox health, and suppression. | Settings, Outreach /dashboard/settings?tab=outreach |
| control | workspace: Members, billing, credits, tags, comments, and webhooks. | Settings /dashboard/settings |
Two things are deliberately not primitives. The doors you drive from, web app, Architect, CLI, MCP, and REST, all use the same thirteen controls. Outside services, including data providers, mailboxes, LinkedIn, and CRMs, connect under Integrations.