Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.doe.so/llms.txt

Use this file to discover all available pages before exploring further.

Think of Doe as a cloud workforce for knowledge work. You give agents the goal, the context they can use, the output you need, and the approval rules. Doe does the searching, reading, analysis, drafting, file work, spreadsheet work, and handoff. Use playbooks when you want more than an answer. A good playbook creates a repeatable way to get work done.

​
The Cloud Workforce Pattern

StepWhat to define
GoalThe business outcome, not just the question
ContextFiles, folders, sessions, integrations, websites, or data sources
OutputMemo, workbook, table, filled form, draft, chart, file, or team update
ReviewCitations, calculations, uncertainty, approvals, and what should not happen automatically
CadenceWhether this is a one-time request or a Loop that should run on a schedule
Goal: identify enterprise renewal risk for the next 30 days.
Sources: @HubSpot, @Gmail, @Slack, and the Customer Contracts folder.
Output: a prioritized table, cited evidence, and draft owner follow-ups.
Review: do not send messages until I approve.
Cadence: every Monday at 9am PT.

​
Where To Deploy Agents

Revenue operations

Pipeline risk, renewal prep, account follow-up, prospecting, CRM hygiene, and sales updates.

Research and strategy

Market maps, pricing extraction, competitive intelligence, vendor comparisons, and cited memos.

Finance and operations

Board metrics, investor updates, expense reviews, workbook models, public comps, and recurring reports.

Agents

Learn how Doe coordinates multi-step work, subagents, and reviewable outputs.

​
What Makes a Strong Playbook

Strong playbooks combine several Doe capabilities:
  • Search across files, conversations, and connected apps.
  • Inspect source documents and cite the evidence.
  • Create or edit durable files such as PDFs, DOCX files, CSVs, and spreadsheets.
  • Draft emails, messages, and calendar events for approval.
  • Use spreadsheets and code sandboxes for analysis, validation, charts, and exports.
  • Share the result with the right people.
  • Convert the workflow into a Loop when it should run repeatedly.

​
Good First Playbooks

TeamFirst playbook
SalesDaily stalled-deal digest with evidence and follow-up drafts
FinanceWeekly metrics workbook with charts and variance notes
ResearchCompetitor pricing tracker with source links and change notes
OperationsVendor onboarding packet that fills required forms from approved sources
LeadershipMonday executive briefing from CRM, email, support, product, and finance signals

Prompting

Write prompts that specify goals, sources, outputs, and validation

Loops

Turn repeatable playbooks into standing agents

Sharing

Package outputs for team review

Integrations

Connect the systems your agents can use