> 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-your-account-list-using-reo-agents.md).

# Build your account list using Reo Agents

* [<mark style="color:$info;">Introduction</mark>](https://docs.reo.dev/playbooks/agents/enrich-existing-account-segments-lists-with-key-signals-using-reo-agents#introduction)
* [<mark style="color:$info;">Step 1: Find net new accounts using Reo Agents</mark>](#step-1-find-net-new-accounts-using-reo-agents)
* [<mark style="color:$info;">Step 2: Create an account segment</mark>](#step-2-create-an-account-segment)
* [<mark style="color:$info;">Step 3: Prospect new opportunities</mark>](#step-3-prospect-new-opportunities)

{% hint style="info" %}
📌 **Need help at any point?** If you need support implementing this playbook end to end, contact your **Account Manager** or write to us at <support@reo.dev>.
{% endhint %}

#### Introduction

For devtool companies, the best-fit accounts are often hidden in signals like — the technologies they use, scale of tech adoption, hiring patterns, the engineering org team size and mix and more! These are key data points that signal budget and need for your tool.

That’s where Reo Chat Agents come in.

You can describe the signal you care about — for example, “Companies expanding their DevSecOps team” or “Companies having an ongoing cloud migration project”— and Reo will help you find matching accounts.

{% hint style="info" %}
💡Refer to this [signals library](https://www.reo.dev/reo-agents) to see the different kinds of agents you can build and the signals you can track.
{% endhint %}

You can save those matching accounts as a list in Reo and further create a segment to track developer activity across them — including activity on your website, docs, GitHub, packages, and other key touchpoints. So you can spot high-fit accounts that are already showing intent - ensuring no opportunities slip through the crack.

You can set this up with this simple 3-step workflow

1. Find new accounts using Reo Chat Agents
2. Create an account segment
3. Prospect new opportunities

<figure><img src="/files/2pKYyGesNUUBNUlgP3Xb" alt="" width="375"><figcaption></figcaption></figure>

#### Step 1: Find net new accounts using Reo Agents

1. Navigate to the **Agents** section in Reo.

<figure><img src="/files/5uDUvSA4m76UjGsLyzh3" alt=""><figcaption></figcaption></figure>

2. Click on **Discover new accounts in the chatbox.** If you're using one of the built-in signals, choose it first, then click **Chat and Build**, then select **Discover new accounts.**

In the chatbox, simply describe the signal you want to track.

For example:

> <mark style="color:$info;">**“Find companies expanding their DevSecOps team”**</mark>

3. Reo fetches a list of all companies matching the signal you described - including those that aren’t tracked on Reo yet. Click on ‘Save accounts as a list’ to add all these accounts to Reo.

<figure><img src="/files/QGeR0g6voxY8DkRkwnAI" alt=""><figcaption></figcaption></figure>

4. Reo auto-generates the list name and description + the agent name and description. You can edit those now if you want something more recognizable - you'll be using this tag in the next step to build a segment, so a clear, consistent naming convention helps.
5. Choose the **All companies, always** option to add all the companies fetched by the agent. Set the re-run frequency to every month (recommended) so you can keep your pipeline fresh. Save your list.

<figure><img src="/files/4LKlrjThZ7EdrkDi4HJQ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
💡 Note: This consumers credits. 3 credits for every new company that does not already exist in Reo. 1 credit for every company already found in Reo.
{% endhint %}

#### Step 2: Create an account segment

Once you’ve set up an agent, the next step is to create a segment so you can monitor these accounts easily and track the ones already showing activity.

To create a segment, Go the segments > Click on create segment

* **Segment:** Basic
* **Segment Type:** Account
* **Segment Filters:**

  * Account > Intel > ICP Fit Score > Choose Strong/Moderate: (optional but recommended) Layering in at least one firmographic filter alongside your territory scope helps narrow the list to ICP-fit accounts that and gives you a more focused outreach list
  * CRM Owner/Location: Add these filters to surface accounts that you own or are in your territory.
  * You can use either of these filters:&#x20;
    * Account > Intel > Agent Account Tags (choose the agent tag from step 1.4) OR, Account > Source > Lists > (Choose the list name from step 1.4)

  <figure><img src="/files/OztEbTxJWvxR5qk6dj4v" alt=""><figcaption></figcaption></figure>

&#x20;            \- OR, Account > Source > Lists > (Choose the list name from step 1.4)

<figure><img src="/files/n6kVTrrsgr0MmDW5wZGS" alt="" width="563"><figcaption></figcaption></figure>

#### Step 3: Prospect new opportunities

Your segment is now a live, continuously updated list of accounts in your territory/assigned to you - that are showing active developer engagement. These are your net new opportunities.

1. Work through the accounts in this segment to prioritize outreach. Sort by date of most recent activity, Activity score, etc. to identify which accounts have the most momentum.
2. Use **Reo-Copilot** to get a summary of the Developer Activity, whether the Account is ready for Sales outreach, understand their Top use case, generate a personalised message to be used for Email / Linkedin outreach, etc. This context is what separates a generic cold outreach from a message that actually lands.
3. From there, find the right buyer contacts to reach out to in those accounts and add them to your email or LinkedIn outreach sequences or do 1:1 outreach.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reo.dev/playbooks/agents/build-your-account-list-using-reo-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.