> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/playbooks/agents/build-a-live-outbound-list-with-reo-agents-and-sync-it-to-your-crm.md).

# Build a live outbound list with Reo Agents and sync it to your CRM

Use any Reo Agent to find accounts showing a technical buying signal, narrow them to your ICP, and sync them to your CRM as a live outbound list that keeps updating.

You can set this up in three steps:

1. **Discover:** Find accounts showing your signal using a Reo Agent
2. **Qualify:** Layer on your GTM filters and save the result as a segment
3. **Action:** Sync the segment to your CRM so your team always has the latest accounts to work

Here's a quick walkthrough video of the full workflow: 

{% embed url="<https://reo-dev.portal.trainn.co/share/j7kW1Tg7ijEKnvcNyVi9wQ>" %}

### Before you start: pick your signal

This workflow works with any agent in the Reo agent library. Pick the signal that best matches why a company would need your product.

| Agent               | What it finds                                                               | Example prompt                              |
| ------------------- | --------------------------------------------------------------------------- | ------------------------------------------- |
| Tech Migration      | Companies replacing or migrating parts of their tech stack                  | *Who is migrating from Jenkins to Airflow?* |
| Tech Adoption       | Companies growing their adoption of a specific technology                   | *Scaling Kubernetes and Helm adoption*      |
| Tech Maturity       | Companies where specific technologies are core to their stack               | *Who runs Airflow or Astronomer at scale?*  |
| Tech Role Hiring    | Companies hiring for specific technologies or skills                        | *Hiring platform engineers skilled in K8s*  |
| Tech Team Expansion | Companies expanding specific tech functions                                 | *Aggressively scaling DevOps Platform team* |
| Eng Org Size & Mix  | Companies by engineering team size and mix                                  | *50+ platform engineers in large orgs*      |
| Open Signal         | News, filings, blogs and more that make a company worth reaching out to now | *SOC 2 Type II certified in last 90 days*   |

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F5rxyzEnL1egLMS2LDUdF%2F1.png?alt=media&amp;token=63a78975-00e1-4d8d-a685-59c58e8b8ab9" alt=""><figcaption></figcaption></figure>

You can also skip the library and describe any signal in plain English.

### Step 1: Discover accounts showing your signal

1. Go to **Agents** in Reo and open the **Reo agent library**.
2. Select the agent that matches your signal and click **Chat and Build**. You can also skip the library and describe your signal directly in the chatbox under **Discover new accounts**.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FEFbe6WPaBuFzwZda9ECZ%2F2.png?alt=media&amp;token=48cb3c56-6ab6-4263-b029-776ed5b649ea" alt=""><figcaption></figcaption></figure>

3. Describe what you want to find, for example *"Who is migrating from Jenkins to Airflow?"*. Reo returns every matching company, including ones not yet tracked in Reo.
4. Click **Save as list**. Reo auto-fills the list name, description, agent name, and agent tag. Edit them if you want something more recognizable, since you'll use this list in the next step.
5. Choose **All Companies, Always** and set the auto re-run to **Every month** (recommended). This keeps adding new companies that match your criteria, so the list stays fresh.
6. Click **Save as list.**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FjI6Yp4aPcVms09SzDNdo%2F3.png?alt=media&amp;token=077be0f2-528c-45b5-b0fc-c48f94b9d455" alt=""><figcaption></figcaption></figure>

**Note:** Saving a list consumes credits: 3 credits for every new company not already in Reo, and 1 credit for every company already in Reo. The dialog shows the estimated credits before you save.

{% hint style="info" icon="lightbulb" %}
**Tip: Wait for the list to finish building.** Go to **Lists** and check the **Status** column for your new list. Once it shows **Completed**, you'll also get an email saying your agent run has completed and a new list with the agent's findings has been created. This usually takes about 15 minutes, but can take up to 24 hours. Start adding filters and saving a segment only after the status changes to Completed.
{% endhint %}

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FlFwhdiM5fjNKraogCXSP%2F4.png?alt=media&amp;token=3fc5cddf-ebc1-4371-b1a8-129b894c73c5" alt=""><figcaption></figcaption></figure>

### Step 2: Qualify the list with your GTM filters and Save a New Segment

Narrow the list to accounts that match your ICP and show the right intent, then save it as a segment.

1. Open your saved list. Click the **Add Filter** button at the top left of the list and layer on the filters that matter to your team
2. Click **Add Filter** and layer on the filters that matter to your team, like:
   * **Firmographics:** Employee Range, Industry, Region/Country, ICP Fit
   * **CRM:** Accounts you own or that sit in your territory
   * **Engagement Signals:** Accounts already showing developer activity
3. Click **Save as new segment**.
4. Give the segment a clear name, add a tag if you use them, and click **Save and view segment**.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FCmvnSjvnl9Inu236Ua0X%2F5.png?alt=media&amp;token=1c3acbee-8d28-4808-b686-b8537eb691ff" alt=""><figcaption></figcaption></figure>

Your segment is now a live GTM list. As the agent re-runs and finds new matching companies, the ones that match your filters show up here automatically.

### Step 3: Sync the segment to your CRM

1. Go to your saved Segment. In your segment, select the accounts you want to sync. To sync everything, click **Select all accounts in this segment**.
2. Click **Send to CRM** (for example, **Send to HubSpot**).

Your team now has a priority list in the CRM they already work from. Because the segment updates as the agent re-runs, you can keep syncing new accounts week to week without rebuilding the list.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F3a6nvJ0t2s9sqt3GgOUL%2F6.png?alt=media&amp;token=5c968e60-3174-4c5f-8e48-1fbcc457d72e" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reo.dev/playbooks/agents/build-a-live-outbound-list-with-reo-agents-and-sync-it-to-your-crm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.