> ## 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.

# Task Playbooks

> Delegate real, repeatable business work to agents

Doe is built for delegating real 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, and each task ends in a deliverable.

Use playbooks when you want more than an answer. A good playbook describes work a real person would recognize: the goal, the sources, the output, the review standard, and whether it should happen once or on a cadence.

## The Delegation Pattern

| Step    | What to define                                                                            |
| ------- | ----------------------------------------------------------------------------------------- |
| Goal    | The business outcome, not just the question                                               |
| Context | Files, folders, sessions, integrations, websites, or data sources                         |
| Output  | Memo, workbook, table, filled form, draft, chart, file, or team update                    |
| Review  | Citations, calculations, uncertainty, approvals, and what should not happen automatically |
| Cadence | Whether this is a one-time request or a Loop that should run on a cadence                 |

```text theme={null}
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

<CardGroup cols={2}>
  <Card title="Revenue operations" href="/tasks/revenue">
    Pipeline risk, renewal prep, account follow-up, prospecting, CRM hygiene, and sales updates.
  </Card>

  <Card title="Research and strategy" href="/tasks/research">
    Market maps, pricing extraction, competitive intelligence, vendor comparisons, and cited memos.
  </Card>

  <Card title="Finance and operations" href="/tasks/finance">
    Board metrics, investor updates, expense reviews, workbook models, public comps, and recurring reports.
  </Card>

  <Card title="Agents" href="/concepts/agents">
    Learn how Doe coordinates multi-step work, subagents, and reviewable outputs.
  </Card>
</CardGroup>

## 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 repeatable work into a Loop when it should run on a cadence.

## Good First Playbooks

| Team       | First playbook                                                                   |
| ---------- | -------------------------------------------------------------------------------- |
| Sales      | Daily stalled-deal digest with evidence and follow-up drafts                     |
| Finance    | Weekly metrics workbook with charts and variance notes                           |
| Research   | Competitor pricing tracker with source links and change notes                    |
| Operations | Vendor onboarding packet that fills required forms from approved sources         |
| Leadership | Monday executive briefing from CRM, email, support, product, and finance signals |

***

<CardGroup cols={2}>
  <Card title="Prompting" href="/essentials/asking-questions">
    Write prompts that specify goals, sources, outputs, and validation
  </Card>

  <Card title="Loops" href="/essentials/loops">
    Turn repeatable playbooks into scheduled Loops
  </Card>

  <Card title="Sharing" href="/essentials/sharing">
    Package outputs for team review
  </Card>

  <Card title="Integrations" href="/essentials/integrations">
    Connect the systems your agents can use
  </Card>
</CardGroup>