> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentweb.pro/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ---
> About this documentation: Emma is the AI marketing agent built by AgentWeb (the product is also marketed as HireEmma; AgentWeb, Emma, and HireEmma refer to the same product). Emma learns a company's brand, ICP, and positioning, then executes marketing work inside that company's own accounts: research, ad campaigns on Google Ads, Meta, and LinkedIn Ads, LinkedIn and email outbound, organic content, CRM lead enrichment and ICP scoring, and landing pages deployed to the customer's domain. Actions that spend money or post publicly require the user's confirmation.
> For what Emma can read, draft, publish, and spend on per channel, see https://docs.agentweb.pro/capabilities. For an overview of the product, see https://docs.agentweb.pro/what-is-emma. For terminology (skill, work plan, scheduled chat, template), see https://docs.agentweb.pro/concepts.

# Operating rhythm

> The weekly and monthly cadence that keeps pipeline arriving — which scheduled chats to stand up, what the Monday review covers, what must never be scheduled, and how the rhythm splits as the team grows.

Pipeline that arrives in bursts is a pipeline you can't forecast. This page turns the motions into a standing weekly rhythm — what runs automatically, what needs you, and how much time it actually takes.

The honest budget for a founder running Stages 1–2 of the [pipeline system](/playbooks/pipeline-system): **about 15 minutes on most weekdays, one hour on Monday, one hour at month end.** Less than that and the schedules run without anyone reading them. Much more than that and you've built a second job.

## The standing set

These are [scheduled chats](/concepts) — a saved prompt, a cadence, and a destination. Set them up once from **Settings → Scheduled chats**, or ask Emma in [Agent Mode](/user-guide/agent-mode) to create one.

| When               | What runs                                                                  | Your part                                   |   |                              |                                                   |                                  |
| ------------------ | -------------------------------------------------------------------------- | ------------------------------------------- | - | ---------------------------- | ------------------------------------------------- | -------------------------------- |
| **Weekday, early** | Find new leads matching your ICP, enrich, score, draft connection requests | Review the drafts, approve or cut. \~15 min |   | **Weekday, before meetings** | Prospect research on whoever you're meeting today | Read it before the call. \~5 min |
| **Monday**         | Last week's channel metrics plus a lead-source and ICP-score breakdown     | The weekly review below. \~45 min           |   |                              |                                                   |                                  |
| **Friday**         | Content backlog check — what's drafted, what's scheduled, what's stale     | Approve or kill. \~10 min                   |   |                              |                                                   |                                  |
| **Month end**      | Competitor and positioning refresh against Market Strategy                 | Decide what to change. \~30 min             |   |                              |                                                   |                                  |

Start with two. The Monday review and the weekday lead run are the ones that carry the system; the rest are additions once those are habitual.

<Warning>
  **Everything scheduled must end at a draft.** Unattended runs proceed best-effort instead of pausing for approval, so a schedule that can send, post, or spend will eventually do so without you. Write the prompt so its last step is "draft and send me the list," never "send."
</Warning>

## The Monday review

The one hour that makes the other four days worth running. Three questions, in this order.

<Steps>
  <Step title="What produced qualified pipeline?">
    Not leads — qualified ones. Pull the lead-source breakdown with average ICP score per source, per [measurement](/playbooks/measurement).

    You're looking for one thing: a source where volume rose and average score fell. That's the pattern that quietly wastes budget, and it's invisible if you only watch cost per lead.
  </Step>

  <Step title="What did I hear last week?">
    Go through the conversations you actually had. Objections that repeated, language buyers used that you didn't, a segment that keeps saying no.

    Write it into **Brand Hub → Market Strategy**. Emma re-reads it on every run, so this one edit propagates to lead scoring, ad targeting, content angles, and outreach copy at once. Skipping it is the single most common reason a system stops compounding.
  </Step>

  <Step title="What's one thing to change?">
    One. A tightened ICP, a killed campaign, a new content angle, a raised budget on something working.

    Changing four things a week means you never learn which one mattered.
  </Step>
</Steps>

## The monthly maintenance pass

Thirty minutes, month end. Four checks that stop slow decay.

* **Review your schedules.** A schedule pointed at a source that's gone quiet keeps producing empty reports indefinitely, and nobody notices because empty reports look like normal reports. Kill anything you've stopped reading.
* **Check that Market Strategy still matches reality.** If your ICP has shifted and the file hasn't, every downstream output is drifting with it.
* **Convert what worked.** Any conversation you've now had three times should be a [work plan](/user-guide/work-plans) or a [skill](/user-guide/skills). Do it while the thread is fresh — reconstructing it later from memory produces a worse version.
* **Prune the Knowledge Base.** Outdated case studies and superseded positioning docs actively degrade output, because Emma treats them as current.

## The autonomy ladder

Automation earns trust; it doesn't start with it. The failure mode isn't Emma doing something wrong once — it's scheduling a step you never verified, then not reading the output that would have told you.

So move one rung at a time, and only on evidence.

### Level 1 — Interactive, every item reviewed

You're in the conversation. Emma drafts, you read every item, you approve each one. Nothing is scheduled.

The point of this level isn't caution for its own sake — it's calibration. You cannot judge whether Emma's output is good until you've seen enough of it to know what good looks like for your ICP and your voice.

**Stay here until:** you've reviewed roughly 50 items of a given kind (leads, drafts, messages) and you can predict what she'll produce before she produces it.

### Level 2 — Scheduled drafting, interactive approval

Emma runs on a cadence and produces a batch. The schedule's final step is *"draft and send me the list"* — never *"send"*. You approve and dispatch in a separate, interactive session.

This is where most founders should live indefinitely. It removes the work of remembering and preparing, and keeps a human on every outbound action.

**Before promoting, run both evals:**

* **Human eval — your edit rate.** Across the last three batches, what fraction did you approve unchanged? Below about 80% and the output isn't stable enough to sample rather than read. Track it; don't estimate it from memory.
* **Agent eval — make Emma grade herself.** Add a final step to the plan: *"Before presenting, score each item 1–5 against these criteria: ICP fit, personalization specificity, factual grounding. Flag anything below 4 and say why."* Then check her scores against your own judgment on a sample. If her self-scores don't correlate with yours, she isn't ready to be trusted as a filter, and the fix is sharper criteria rather than more autonomy.

**Stay here at least:** three or four weeks of stable batches.

### Level 3 — Scheduled drafting, sampled review

Same as Level 2, except you spot-check rather than read everything — review Emma's flagged items plus a random sample of the rest.

Approval is still interactive. What changed is how much you read, not whether a human dispatches.

**Requires:** a sustained edit rate above 80%, agent self-scores that track your judgment, and at least a few hundred reviewed items.

### Level 4 — Narrow autonomy, low blast radius only

A small set of actions run without you: internal research, enrichment, scoring, report generation, drafting into a queue.

Everything at this level shares three properties — **reversible, private, and cheap**. If an action fails any one of those, it doesn't belong here regardless of how well Emma has performed.

### What never reaches Level 4

| Never autonomous                  | Why                                             |
| --------------------------------- | ----------------------------------------------- |
| Sending outreach                  | Irreversible, and it's your reputation attached |
| Publishing posts or comments      | Public and permanent                            |
| Any ad spend or budget change     | Irreversible and metered                        |
| Deleting leads, lists, or records | Irreversible                                    |

These stay interactive permanently. Not because Emma performs badly on them, but because the cost of the rare failure is unbounded while the saving is a few minutes.

<Warning>
  **The ladder is enforced by how you write the prompt, not by a setting.** Unattended runs proceed best-effort rather than pausing for approval — there is no confirmation gate waiting for you at 9am. A scheduled prompt that *can* send *will* send. Level 2 and 3 exist because the plan ends at a draft, so write it that way and re-read it after every edit.
</Warning>

### When to drop back down

Demote immediately, without treating it as a setback:

* Your edit rate falls below 80% for two consecutive batches.
* Anything went out that you'd have stopped.
* **Your ICP, positioning, or brand voice changed.** This is the one people miss. Emma re-reads Market Strategy on every run, so a positioning change alters her output while your trust calibration still reflects the old version. Return to Level 2 and re-baseline.
* A source went quiet and the schedule kept producing empty output nobody noticed.

## Where each motion should sit

| Activity                                 | Sensible level                             |
| ---------------------------------------- | ------------------------------------------ |
| Lead discovery, enrichment, ICP scoring  | 4 — internal, reversible, cheap            |
| Meeting prep and research reports        | 4 — output is for you only                 |
| Weekly metrics and lead-source summaries | 4 — read-only                              |
| Drafting outreach messages               | 2 or 3 — drafting scheduled, sending never |
| Drafting posts and content               | 2 or 3 — same split                        |
| Sending outreach, publishing, ad changes | 1 — permanently interactive                |

## Scaling the rhythm

As the team grows, the cadence stays and the ownership splits:

* **Solo founder:** you run all of it. Keep the standing set to two or three.
* **Founder + first marketer:** marketer owns the Monday review and content backlog; founder keeps outreach approval and the conversation-to-strategy loop. That second one shouldn't be delegated — it depends on being in the sales conversations.
* **Small team:** move to a shared workspace so schedules, brand context, and lead lists are visible to everyone rather than trapped in one person's account. See [Organization sharing](/onboarding/organization-sharing).

## Next steps

* [The pipeline system](/playbooks/pipeline-system) — what this rhythm is operating.
* [Measurement](/playbooks/measurement) — the review prompt and the metrics behind it.
* [Work plans](/user-guide/work-plans) — turning a repeated conversation into a reusable sequence.
* [Agent Mode](/user-guide/agent-mode) — creating and managing scheduled chats.