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

# Your first 30 days

> A week-by-week ramp for your first month with Emma — context, then one motion, then measurement, then cadence — and what you should have in place by day 30.

[Brand onboarding](/onboarding/brand-onboarding) gets Emma to know your business. This page covers what to do with the four weeks after that — a sequenced ramp that ends with pipeline arriving on a rhythm rather than a portal full of features you haven't touched.

The shape: **context, then one motion, then measurement, then cadence.** Resist adding channels. The most common first-month failure is connecting eight integrations and running none of them properly.

## Pick your track

You don't need to read all 38 pages. Start with the shared foundation, then follow the track that matches where you are.

<Tabs>
  <Tab title="🤝 Founder-led sales">
    **For pre-revenue founders through their first ten customers.** Gets your brand context set, runs outbound and content as a single loop, puts measurement in place, and ends with the weekly cadence that keeps it sustained.

    <Steps>
      <Step title="What is Emma?" icon="circle-info">
        [Read →](/what-is-emma) — What Emma is, who she's for, what she can and can't do.
      </Step>

      <Step title="Concepts" icon="book">
        [Read →](/concepts) — Skill, work plan, scheduled chat, template — the vocabulary you'll use daily.
      </Step>

      <Step title="Brand onboarding" icon="sparkles">
        [Read →](/onboarding/brand-onboarding) — Set up Brand Profile, Market Strategy, founder voice, and Knowledge Base.
      </Step>

      <Step title="First 30 days" icon="calendar-check">
        You're here — the week-by-week ramp below.
      </Step>

      <Step title="Founder-led sales" icon="handshake">
        [Read →](/playbooks/founder-led-sales) — Four stages from LinkedIn audit to meeting prep.
      </Step>

      <Step title="LinkedIn content workflow" icon="pen-nib">
        [Read →](/playbooks/linkedin-content-workflow) — The per-post drafting process that runs alongside outbound.
      </Step>

      <Step title="CRM" icon="users">
        [Read →](/user-guide/crm) — Leads, enrichment, ICP scoring, outreach drafts, engagement tracking.
      </Step>

      <Step title="Operating rhythm" icon="calendar-days">
        [Read →](/playbooks/operating-rhythm) — The weekly cadence, the Monday review, and the autonomy ladder.
      </Step>
    </Steps>
  </Tab>

  <Tab title="💰 Paid ads">
    **For teams whose message is already proven through organic.** Measurement comes before the first campaign because retrofitting attribution doesn't work. Ends at CRM and operating rhythm because paid that doesn't flow into lead scoring and a weekly quality review is paid that optimizes toward cheap leads instead of good ones.

    <Steps>
      <Step title="What is Emma?" icon="circle-info">
        [Read →](/what-is-emma) — What Emma is, who she's for, what she can and can't do.
      </Step>

      <Step title="Concepts" icon="book">
        [Read →](/concepts) — Skill, work plan, scheduled chat, template.
      </Step>

      <Step title="Brand onboarding" icon="sparkles">
        [Read →](/onboarding/brand-onboarding) — Brand Profile, Market Strategy, founder voice, Knowledge Base.
      </Step>

      <Step title="Capabilities" icon="table-list">
        [Read →](/capabilities) — Channel-by-channel: what Emma can read, draft, publish, and spend on.
      </Step>

      <Step title="Measurement" icon="chart-line">
        [Read →](/playbooks/measurement) — Lead-source taxonomy, UTM convention, and the metrics that matter. Do this before the first campaign.
      </Step>

      <Step title="Paid ads on a founder budget" icon="bullseye-arrow">
        [Read →](/playbooks/paid-ads) — The readiness gate, Search vs. Meta, and cost per qualified lead.
      </Step>

      <Step title="Google Ads best practices" icon="bullseye-arrow">
        [Read →](/playbooks/google-ads-best-practices) — Google's guidance distilled for B2B, mapped to Emma's skills.
      </Step>

      <Step title="Analytics and tracking" icon="chart-mixed">
        [Read →](/playbooks/analytics-and-tracking) — Install Pixels, tags, and analytics on your landing pages.
      </Step>

      <Step title="CRM" icon="users">
        [Read →](/user-guide/crm) — Where ad leads land, get scored, and flow into outreach.
      </Step>

      <Step title="Operating rhythm" icon="calendar-days">
        [Read →](/playbooks/operating-rhythm) — The weekly review that catches quality decay before budget does.
      </Step>
    </Steps>
  </Tab>

  <Tab title="🎪 Event-based engagement">
    **For teams with an event, webinar, or meetup coming up.** CRM comes early because events produce a burst of leads that decay fast — the list, the enrichment, and the scoring need to be ready before the event, not after. Loops into founder-led and content because events are highest-intent and fastest to waste — they reward a system that already exists.

    <Steps>
      <Step title="What is Emma?" icon="circle-info">
        [Read →](/what-is-emma) — What Emma is, who she's for, what she can and can't do.
      </Step>

      <Step title="Concepts" icon="book">
        [Read →](/concepts) — Skill, work plan, scheduled chat, template.
      </Step>

      <Step title="Brand onboarding" icon="sparkles">
        [Read →](/onboarding/brand-onboarding) — Brand Profile, Market Strategy, founder voice, Knowledge Base.
      </Step>

      <Step title="CRM" icon="users">
        [Read →](/user-guide/crm) — Set up your lead list, pipeline stages, and enrichment before the event.
      </Step>

      <Step title="Event-led sales" icon="calendar-star">
        [Read →](/playbooks/event-led-sales) — Landing page to lead enrichment to follow-up, inside the 24-hour window.
      </Step>

      <Step title="Founder-led sales" icon="handshake">
        [Read →](/playbooks/founder-led-sales) — Turn event connections into sustained outbound relationships.
      </Step>

      <Step title="LinkedIn content workflow" icon="pen-nib">
        [Read →](/playbooks/linkedin-content-workflow) — Post about the event, recap insights, and stay visible to attendees.
      </Step>

      <Step title="The pipeline system" icon="diagram-project">
        [Read →](/playbooks/pipeline-system) — How events compose with your other motions into one compounding pipeline.
      </Step>

      <Step title="Operating rhythm" icon="calendar-days">
        [Read →](/playbooks/operating-rhythm) — The weekly cadence that keeps event-sourced pipeline from decaying.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Work with Emma — step-by-step guides

Once your context is set and you've picked your track, these guides walk you through running each motion end to end with Emma — every work plan, every checkpoint, in order.

<Columns cols={3}>
  <Card title="Founder-led sales" icon="handshake" href="/playbooks/founder-led-sales">
    Four stages from LinkedIn audit to meeting prep. The default starting motion for pre-revenue founders.
  </Card>

  <Card title="Event-led sales" icon="calendar-star" href="/playbooks/event-led-sales">
    Landing page to enrichment to follow-up, inside the 24-hour window before trust decays.
  </Card>

  <Card title="Your first Meta campaign" icon="rectangle-ad" href="/playbooks/first-meta-campaign">
    Connect, verify brand, build creatives, landing page, pre-launch gate, and measurement — step by step.
  </Card>
</Columns>

## Week 1 — Context

Everything Emma produces reads from what you set up this week. Time spent here is not overhead; it's the multiplier on the next eleven months.

<Steps>
  <Step title="Finish brand onboarding properly">
    Both parts — the portal wizard and the deep-dive in [Agent Mode](/user-guide/agent-mode). The deep-dive is the part that makes output sound like you.

    Paste two or three real posts you've written when Emma asks. Described tone produces generic voice; pasted examples produce yours.
  </Step>

  <Step title="Load the Knowledge Base yourself">
    Emma points you at it but doesn't fill it. Case studies, customer interviews, your best posts, positioning docs. An empty Knowledge Base is the single most reliable cause of generic output.
  </Step>

  <Step title="Read the ICP personas properly">
    Emma generates them; you validate them. Keep only the ones you have actually sold to or interviewed. A plausible-sounding persona you invented will quietly misdirect lead scoring, ad targeting, and content angles for months.
  </Step>

  <Step title="Get into the Slack group">
    Email [support@agentweb.pro](mailto:support@agentweb.pro) and ask to be added to the shared Slack group. Emma lives there alongside the AgentWeb founder team, so it's both your support channel and the fastest way to get an answer from a human who knows the product.

    Do this in week 1 rather than when you hit your first problem. The questions worth asking early — is my ICP definition too broad, is this output normal — are the ones you won't think to ask once you're heads-down.
  </Step>

  <Step title="Connect only what you need this month">
    LinkedIn if you're doing outbound. Gmail or Outlook if you're sending email. That's it for now — the rest from **Settings → Connected Accounts** when a motion needs them.
  </Step>
</Steps>

**End of week 1:** Brand Guidelines, Market Strategy, and a populated Knowledge Base. Ask Emma to draft something and check whether it sounds like you. If it doesn't, fix it here rather than working around it later.

## Week 2 — One motion

Pick the motion that matches where you are, and run only that one.

| If you                                                   | Run                                                                                           |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Have fewer than ten customers                            | [Founder-led sales](/playbooks/founder-led-sales) — see the step-by-step guide above          |
| Have an event or webinar coming up                       | [Event-led sales](/playbooks/event-led-sales) — see the step-by-step guide above              |
| Have a proven message and want to scale with paid        | [Your first Meta campaign](/playbooks/first-meta-campaign) — see the step-by-step guide above |
| Have a message that already works and want organic reach | [Content engine](/playbooks/content-engine)                                                   |

For most people at this stage it's founder-led sales, run alongside a light content cadence. Not paid — see [when you're ready for paid](/playbooks/paid-ads).

By the end of the week you want a CRM lead list with enriched, ICP-scored leads and your first batch of outreach approved and sent. Real conversations are the goal, not volume.

**End of week 2:** first conversations booked, and a clear sense of which claim gets a reply.

## Week 3 — Measurement

Now, before habits set and while there's little data to retrofit.

<Steps>
  <Step title="Set up the lead-source taxonomy">
    Three custom fields on your lead lists, one closed set of source values. Full setup in [measurement](/playbooks/measurement).
  </Step>

  <Step title="Adopt the UTM convention">
    One pattern, lowercase, applied to every link you paste anywhere. Ask Emma to build tagged URLs rather than assembling them by hand.
  </Step>

  <Step title="Build a landing page if you're driving traffic anywhere">
    Emma generates it, deploys it, creates a lead list for it, and injects UTM attribution automatically. Install your Pixel and analytics at the same time — see [analytics and tracking](/playbooks/analytics-and-tracking).
  </Step>
</Steps>

**End of week 3:** you can answer "where did this lead come from?" from the CRM.

## Week 4 — Cadence

Turn what you did manually into something that runs whether or not you remember it.

<Steps>
  <Step title="Convert what worked into a work plan">
    Any conversation you've now had three times. Say *"make this as a workplan"* while the thread is still open — reconstructing it later from memory produces a worse version.
  </Step>

  <Step title="Stand up two scheduled chats">
    The weekday lead run and the Monday review. Two, not five. See [operating rhythm](/playbooks/operating-rhythm).

    Check that both end at a draft. Scheduled runs don't pause for approval — you're starting at rung 2 of the [autonomy ladder](/playbooks/operating-rhythm#the-autonomy-ladder), not the top of it.
  </Step>

  <Step title="Run your first Monday review">
    Which source produced qualified leads, what you heard in conversations, and one thing to change. Write what you heard into Market Strategy — that's the step that makes the system compound.
  </Step>
</Steps>

**End of week 4:** leads arriving on a schedule, a weekly review you'll actually run, and one reusable work plan.

## Support and staying connected

Two channels, and they do different jobs.

**Slack — day to day.** Email [support@agentweb.pro](mailto:support@agentweb.pro) to be added to the shared group. Emma is in the channel alongside the AgentWeb founder team, so you can ask a question in the same place whether the answer comes from the agent or a person.

**Live check-in — every few weeks.** Join a webinar or office hours session, or book time with the founder team directly. Worth doing at least once in your first month, and periodically after.

The live sessions are the higher-value of the two, and the one people skip. Written support answers the question you knew to ask. A conversation surfaces the thing you didn't — an ICP that's drifted, a motion you're running in the wrong order, a workaround you built for a problem that has a real fix. Bring what isn't working, not just what is; the roadmap moves on that feedback.

## Where you should be at day 30

| Have                                                 | Not yet                               |
| ---------------------------------------------------- | ------------------------------------- |
| Brand context Emma reads on every run                | Paid campaigns                        |
| One motion running and producing conversations       | More than one primary content surface |
| Lead source and UTM tracking in place                | Every integration connected           |
| Two scheduled chats you read                         | A large library of work plans         |
| One work plan converted from real use                | Attribution you fully trust           |
| A seat in the Slack group and one live check-in done | —                                     |

If you're behind on this, the usual culprit is week 1 — thin brand context makes everything downstream feel like it isn't working, and the instinct is to add channels rather than go back and fix the foundation.

## Month 2 and beyond

* Add a second motion, once the first is producing without daily attention.
* Consider paid, using the readiness gate in [paid ads](/playbooks/paid-ads).
* Add the monthly maintenance pass from [operating rhythm](/playbooks/operating-rhythm).
* Move to a shared workspace if anyone else joins — see [organization sharing](/onboarding/organization-sharing).

## Next steps

* [The pipeline system](/playbooks/pipeline-system) — how the motions compose once you're past month one.
* [Founder-led sales](/playbooks/founder-led-sales), [Event-led sales](/playbooks/event-led-sales), [Your first Meta campaign](/playbooks/first-meta-campaign) — step-by-step guides in the **Work with Emma** section.
* [Concepts](/concepts) — skill, work plan, scheduled chat, template.
* [Capabilities](/capabilities) — what Emma can do per channel before you connect anything.