> 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/getting-started/for-admins/step-1-create-your-target-account-list.md). # Step 1: Create your target account list Everything you need to build your target account list in Reo, step by step. Everything in Reo starts with your target account list. Signals, scoring, alerts, outreach: all of it builds on the accounts you bring in here. This guide walks you through multiple ways to build your target account list, so you can pick whichever works best for your teams. ### Overview There are 3 ways to build a target account list in Reo: {% stepper %} {% step %} ### [**Import from CRM**](#method-1-import-from-your-crm-1) Pull a list or segment straight from HubSpot, Salesforce or Attio, and keep it synced automatically. Your Reo list stays as current as your CRM, always. {% endstep %} {% step %} ### [Upload a file](#method-2-upload-a-file-csv-excel-1) Drop in a CSV or Excel file of accounts and have a list ready in minutes. Ideal for one-off imports or accounts that live outside your CRM. {% endstep %} {% step %} ### [Build a segment ](#method-3-build-a-segment-1) Filter Reo's own account universe by region, firmographics, and tech stack (and, if your CRM is connected, by CRM Owner) to find best fit accounts without needing a file at all {% endstep %} {% endstepper %} Whichever method you choose, Reo enriches every account with signals like org size, buyers, and de-anonymized developer activity. {% hint style="success" %} **Our recommendation is to use Import from CRM wherever possible, because:** * Your CRM is already your single source of truth. * importing from it, and keeping the import synced, means the accounts you work with in Reo always match what's in your CRM. * It also saves you the trouble of re-exporting and re-uploading a CSV every time your CRM segment changes. {% endhint %} *** ### Method 1: Import from your CRM **Who it's for:** Anyone who builds lists or segments natively in HubSpot, Salesforce, or Attio. {% hint style="info" %} **Supported today:** Account lists from HubSpot, Salesforce or Attio. Looking to bring in specific deals or leads instead? Build a list of those in your CRM first, then bring that list into Reo as an account list. {% endhint %} #### **Prerequisites** * Your CRM should be connected to Reo. * **Using Attio?** * **You'll need to re-authorize the integration once to enable support for Lists.** This is a one-time step, and it won't affect your existing CRM connection or workflow. * From the **left navigation menu >** go to **Lists >** then click **Import from CRM**. If you're connected to Attio, a prompt to re-authorize the integration appears.

* Click **Authorise in Attio** to complete the authorization process in Atto. * Once you're done, you're brought back to your Attio integration screen in Reo, showing a success status. #### Steps 1. From the **left navigation menu >** go to **Lists >** then click **Import from CRM**.

2. A 3-step wizard opens: **Select source >** **Map columns > Add details**.

> ***Information on each step is provided in its own tab below. Work through them in order using the tabs to move from one to the next.*** {% tabs %} {% tab title="Select source" icon="1" %} 1. **Search for and select the CRM list you want to import** from the dropdown. Each result shows the list name and its record count.

{% hint style="info" %} Note: CRM imports are limited to 10,000 accounts per list, to keep the import fast and reliable. If your list has more than 10,000 accounts, import it as a CSV file instead ([see Method 2](https://app.gitbook.com/o/j0dmg4x3Hdhfj3EDr66v/sites/site_LYknN/s/x46P5sAHxDG7PqOdVLxI/~/edit/~/changes/701/getting-started/for-admins/step-1-build-your-target-account-list#method-2-upload-a-file-csv-excel)). {% endhint %} 2. If you can't find your list, it's usually for one of two reasons: 1. **Only account lists can be imported and enriched today.** Contact and lead lists aren't supported. 2. You recently created or updated the list in your CRM, and it hasn't synced to Reo yet. Click **Refresh CRM lists** to pull the latest version right away. {% endtab %} {% tab title="Map columns" icon="2" %} 1. **Select the column that contains the company domain or website.** 1. Get this right: it's the foundational step Reo uses to match your CRM accounts to the correct accounts in Reo. 2. So, an incorrect mapping here can cause accounts to import against the wrong records. 2. All your CRM columns are listed below that. 3. **Toggle on the individual ones you want to bring into Reo**, or tick **Import all** to bring everything over in one go. 1. **A search box** helps you find specific columns if your CRM has a lot of them. 2. Reo **automatically detects each column's type** (string, integer, date, and so on)

{% endtab %} {% tab title="Add details" icon="3" %} 1. **List type** is set to **Account**. 2. **Provide a list name and description** (this will help your team members understand the list’s purpose when you share it).

3. Before you save, **Reo shows you an import summary:** 1. The number of accounts that will be imported 2. How many of those need enrichment 3. The estimated credits that enrichment will cost 4. Your available credit balance 5. Which signals enrichment will add: tech stack, engineering team size and growth, job postings, prospect buyers, and AI insights

4. **If your CRM list includes accounts that don't need enrichment** *(because they're already in Reo and already enriched)* Reo shows **the option to import them without enriching**, at no credit cost. 1. This keeps the number of accounts in your Reo list matched to the number of accounts in your CRM list, even for the ones you're not spending credits to enrich.

5. The **Keep Reo list in sync with CRM list** toggle is on by default. Leave it on if you want this list to update automatically whenever your CRM list changes, **which is what we recommend for most use cases.**

{% hint style="warning" %} Important - Decide on the sync between your CRM and Reo \ \ Turn it off only if you specifically want a one-time snapshot import with no ongoing connection to your CRM. You can do this later as well, from the **Lists** view. {% endhint %} 6. Click **Save changes**. {% endtab %} {% endtabs %} **Prefer to watch instead?** This quick walkthrough covers the entire process below, from selecting your CRM list to keeping it in sync. {% embed url="" %} ### After you import Open the list and you'll see Reo's standard account fields alongside the CRM columns you chose to import, all on the same account records. On the main **Lists** page, each list shows a **Source** column that tells you how it was created: * **Created in Reo:** built manually inside Reo, for example with Build a segment * **Imported file:** brought in via CSV or Excel upload * **A CRM's logo (for example, Hubspot), with a sync icon:** imported from that CRM * **Agent created:** built by a Reo agent * **MCP created:** built through Reo's MCP integration * **API created:** built through the Reo API

### Manage syncing lists between your CRM and Reo

If a new account is added to your CRM list

* The new account will be added and enriched in Reo automatically, using credits as needed. Sync checks for changes every 24 hours. * The sync icon next to a CRM-sourced list means Reo is keeping it in sync with your CRM automatically.

If an account is removed from your CRM list

* The account will be removed from Reo list as well. * Credits already spent enriching that account aren't refunded.

Click the sync icon at any time to see the list's sync status and the date it last synced. You're in control of it: use the **Disable sync** button if you'd rather this list stop updating automatically and become a one-time snapshot instead.

*** {% hint style="info" icon="circle-question" %} **Have more questions about importing from CRM?** Check out [some of the frequently asked questions](https://docs.reo.dev/faqs-and-troubleshooting/things-to-know-before-and-after-you-import-accounts-from-crm) for answers on credits, syncing behavior, and common troubleshooting scenarios. {% endhint %} ### Method 2: Upload a file (CSV/Excel) Use this when your accounts aren't in a connected CRM, you need a one-off import, or your CRM list is larger than the 10,000 account limit for CRM imports. #### Steps 1. From the **left navigation menu >** go to **Lists >** then click **Import file**.

2. Choose the list type, **Accounts or Developers >** **upload your file >** click **Next**. * For accounts, you can import and enrich in the same flow. * For developers, it's import only; enrichment isn't available for developer lists. * *Supported file types: CSV, XLSX, and XLS.*

3. Select the **column containing the company domain or website**, then click **Next**. 4. You'll see the **full list of columns available to import from your file**. 5. **Toggle on the individual columns you want to bring into Reo**, or tick **Import all** to bring everything over in one go. * **A search box** helps you find specific columns if your file has a lot of them. * For every column you import, **choose its type**: string, integer, or date.

6. Click **Next**. 7. **Give your list a name and an optional description.** A good description helps your team understand what the list is for, especially useful if you plan to share it.

8. Before you save, Reo shows you an import summary: 1. The number of accounts that will be imported 2. How many of those need enrichment 3. The estimated credits that enrichment will cost 4. Your available credit balance 5. Which signals enrichment will add: tech stack, engineering team size and growth, job postings, prospect buyers, and AI insights

9. **If your CSV file includes accounts that don't need enrichment** *(because they're already in Reo and already enriched)* Reo shows **the option to import them without enriching**, at no credit cost. 10. Click **Save changes**. You'll get an email once the import finishes, and your list will appear under **My Lists**. {% hint style="info" %} **Good to know:** A file upload is a one-time snapshot.\ \ It won't stay in sync with your source file or your CRM, so if your account list changes afterward, you'll need to export and upload again. If you'd rather your list stayed current on its own, use Import from CRM instead ([see Method 1](https://app.gitbook.com/o/j0dmg4x3Hdhfj3EDr66v/sites/site_LYknN/s/x46P5sAHxDG7PqOdVLxI/~/edit/~/changes/701/getting-started/for-admins/step-1-build-your-target-account-list#method-1-import-from-your-crm)). {% endhint %} ### After you import Open the list and you'll see Reo's standard account fields alongside the CRM columns you chose to import, all on the same account records. On the main **Lists** page, each list shows a **Source** column that tells you how it was created: * **Created in Reo:** built manually inside Reo, for example with Build a segment * **Imported file:** brought in via CSV or Excel upload * **A CRM's logo (for example, Hubspot), with a sync icon:** imported from that CRM * **Agent created:** built by a Reo agent * **MCP created:** built through Reo's MCP integration * **API created:** built through the Reo API

*** ### Method 3: Build a segment Use this **when you want to filter accounts Reo already tracks**, without importing anything new. {% hint style="info" icon="circle-info" %} Segments are customizable cohorts of high-intent accounts, developers, or buyers, built from specific filters and attributes. They help you act on the ones that matter most, so you can prioritize outreach and focus your team on the opportunities most likely to convert. {% endhint %} #### Steps 1. From the **left navigation menu >** go to **Segments >** click **Create new**.

2. Choose whether to build a **Basic** or **Advanced** segment, depending on how many filter criteria you need to combine. {% hint style="info" %} For a full walkthrough of the difference, see the [Basic & Advanced Segments Guide](https://docs.reo.dev/segments/basic-and-advanced-segments). {% endhint %}

3. Choose what the segment is for: **Accounts**, **Developers**, or **Buyers**.

4. **Name the segment.** 5. **Add a tag name and description.** Tags let you quickly filter and prioritize these accounts later, based on the same criteria you're defining now. {% hint style="info" %} See [Customizing Tags](https://docs.reo.dev/accounts/customizing-tags) for more on how tags work across Reo. {% endhint %}

6. **Add your filters.** Choose from Reo's full range of filters, including region, firmographics, tech stack, developer activity. If your CRM is connected, filter by **CRM Owner** to see only the accounts you personally own.

{% hint style="info" %} For the complete list of available filters, see [Filters 101](https://docs.reo.dev/segments/filters-101). {% endhint %}

7. If you're combining more than one filter, choose how they should relate: 1. **Match All (the AND operator)** 2. **Match Any (the OR operator)**

8. As you add filters, Reo shows you **a live count of how many accounts currently match your criteria**, so you can see the size of your segment before you save it.

9. If you'd like this segment to be what you see by default, check **Set this as Default Segment**. This makes it the view you land on whenever you open the Accounts, Developers, or Buyers dashboard.

10. Click **Save and Exit**. *** ### Credits and enrichment status Enrichment is what powers the signals Reo adds to your accounts, and it draws from your credit balance. As an admin, here's what you'll see if you run low:

On your first import or enrichment

If you don't have enough credits, your list shows the status **Enrichment incomplete**. Buy more credits to finish enriching the list.

On a later sync

If there aren't enough credits to enrich newly added accounts, the list shows the status **Sync paused**. Buy more credits to resume.

### What’s next Once your accounts are in Reo, see ‘Explore your account data’ to learn how to review the firmographics, activity, and buyer insights Reo has gathered for each one. --- # 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/getting-started/for-admins/step-1-create-your-target-account-list.md?ask=&goal= ``` `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.