> 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/for-sdrs/upload-target-accounts-and-get-buyer-contacts.md). # Upload Target Accounts & Get Buyer Contacts * [Introduction](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts#introduction) * [Step 1: Configure Your Buyer Personas](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts#step-1-configure-your-buyer-personas) * [Step 2: Upload Your Target Account List](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts#step-2-upload-your-target-account-list) * [Step 3: Get Buyer Contacts](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts#step-3-get-buyer-contacts) {% 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 . {% endhint %} ### Introduction Knowing which accounts are active is only half the battle. The other half is getting in front of the right person at that account before the window closes. This playbook walks you through how to upload your target account list into Reo.Dev and then find the right buyer contacts, either in bulk across your full list or individually for specific accounts you want to prioritize. *Let's set this up in three simple steps.*
#### Step 1: Configure Your Buyer Personas Before pulling any buyer contacts, you need to tell Reo.Dev what a buyer looks like for your product. Buyer Personas let you define the exact seniority levels, job functions, and titles you want Reo.Dev to surface when searching for decision-makers, so you are not wading through irrelevant profiles. > Navigate to **Settings → Configurations → Persona Configuration** to set up your persona.
You can start from one of Reo.Dev's pre-built persona templates (US Technology Buyers, DevOps Buyers, AI/ML Buyers, Cybersecurity Buyers) or create a new one from scratch using filters for location, seniority level, job function, and designation. **Example Buyer Personas** | Persona Name | Seniority | Job Titles | Location | | -------------------- | ----------------- | ---------------------------------------------------------------------------- | ------------- | | AI/ML Buyers | VP, Director, CXO | Head of AI, Chief Data Scientist, VP Engineering (AI), Machine Learning Lead | USA, Europe | | Cybersecurity Buyers | Director, VP, CXO | CISO, Director of Threat Intelligence, VP Security | North America | | Cloud/DevOps Buyers | Director, VP | Director of Cloud Engineering, Head of DevOps, VP Platform Engineering | APAC, USA | Once saved, your persona will appear under My Personas and will be available to use in the next steps. {% hint style="success" %} **Learn more:** [**Buyer Persona Configuration in Reo.Dev**](https://docs.reo.dev/buyers/buyer-persona-configuration-in-reo.dev) {% endhint %} #### Step 2: Upload Your Target Account List **How to upload your list:** 1. Go to Tools and click on Lists from the sidebar. 2. Click Import and select Accounts as the list type. 3. Give your list a clear name, for example **`"John’s Target Accounts - Feb 26"`**, and click Next. 4. Upload your CSV file. Make sure your file includes a Company Domain Name column, as this is the primary key Reo.Dev uses to match and enrich your accounts. 5. Map the Company Domain Name column and any other columns you want to bring in, then click Done. > For a detailed walkthrough of the CSV upload process, refer to the [Custom Lists guide](https://docs.reo.dev/accounts/custom-lists). Your list will be processed and enriched with developer activity. You will receive an email once the import is complete. #### Step 3: Get Buyer Contacts Once your list is uploaded and your persona is ready, you have two ways to find buyer contacts depending on whether you want to work the full list in bulk or go deep on specific accounts.
**Option A1: Bulk – Create a Buyer Audience** Use this when you want to find buyers across your entire target account list in one go. Navigate to the sidebar **→ Audience → Buyer → Create Audience**. **1)** Select your uploaded target account list as the source. **2)** Select the buyer persona you configured in **Step 1** from the dropdown. If needed, you can also apply additional filters here to refine results further.
**3)** If you only want to reach buyers who can be contacted via email, check the **"Only include buyers with email"** box before proceeding. **4)** Click **Continue to Save**, give your audience a name, and set the maximum number of buyers per company. You can cap this at up to **5-10 profiles per account.** This is a useful control if you want to keep outreach focused rather than pulling every possible contact from large enterprise accounts. **5)** Click **Save Audience**. [Reo.Dev](http://Reo.Dev) will fetch the buyers and your audience will be ready within a couple of minutes to upto 24 hours depending on the audience size. Once generated, you can view all buyer profiles with their designation, company, location, LinkedIn handle, and email ID. From here you can download a CSV, sync buyers to your CRM, send data via Webhooks or enroll them directly into an email campaign. > [**🔗 Full Guide on how to Create a Buyer Audience**](https://docs.reo.dev/audiences/buyer-audience) **Option A2: Bulk – Create a Buyer Segment** > [**Buyer Segments Guide**](https://docs.reo.dev/buyers/how-to-find-segment-and-engage-decision-makers-in-reo.devs-buyer-section) Use this when you want to surface buyers from your target accounts who have already demonstrated some form of activity across your connected data sources — and work with them as a live, dynamic segment you can run email campaigns against directly inside Reo.Dev. The key **difference** between a **Buyer Audience** and a **Buyer Segment** comes down to what gets surfaced. A **Buyer Audience** pulls contacts purely based on persona match. It looks at all companies in your list and finds profiles that fit your defined seniority, job function, and title criteria, regardless of whether those individuals have interacted with your product, docs, GitHub, community, or any other connected source. A **Buyer Segment** works differently. It only surfaces buyers from accounts where some form of developer or contact activity has already been recorded by Reo.Dev. That activity could be a doc page visit, a GitHub interaction, a CLI command, a website visit, a community signal, or activity on a competitor or complementary repository. If Reo.Dev has captured any signal from that account, it will surface the matching buyer profiles from there. This means a Buyer Segment gives you a smaller, higher-signal list. Every buyer in it comes from an account that is already showing some level of engagement. **How to create it:** Go to Segments and click Create Segment. Set the Segment Type to **Buyers.** {% hint style="info" %} **Segment Criteria:** * **Segment:** Basic * **Segment Type:** Buyers * **Filter:** Lists (Accounts) → Includes Any → select your uploaded target account list (e.g. `john's target accounts - feb 26.csv`) {% endhint %} Save the segment. Reo.Dev will populate it with buyer profiles from your list where contact activity has been detected. > **🔗** [**Full guide on creating buyer segments and running buyer campaigns**](https://docs.reo.dev/buyers/how-to-find-segment-and-engage-decision-makers-in-reo.devs-buyer-section) **Option B: Individual – Get Buyer Contacts for a Specific Account** Use this when you have received a Slack alert on a high-priority account and want to find the right person to reach out to immediately. 1. Navigate to the **Accounts** view and switch to **Lists** using the dropdown at the top. Select the target account list you uploaded in **Step 2.** 2. Click on any account you want to prioritize. Inside the account page, go to the **More Prospects** tab. 3. Select your buyer persona you created in **Step 1** from the dropdown to filter results against your ICP criteria. 4. Review the profiles surfaced. Select the ones that look relevant and click **Reveal** to fetch their contact details. 5. The revealed buyers will appear in **revealed tab** of that account with their full profile information.
{% hint style="info" %} **Note on Credits:** Both the Buyer Audience and the individual Find More Buyers options consume credits. Revealing a LinkedIn profile costs 1 credit; revealing both LinkedIn and a verified email costs 2 credits. Credits are pooled across your whole team. To understand how credit consumption works in detail, refer to the [Reo.Dev](http://Reo.Dev) [Credit-Based Pricing FAQs](https://docs.reo.dev/faqs-troubleshooting/reo.dev-credit-based-pricing-faqs). 📞 To add more credits to your account, contact your **Account Manager.** {% endhint %} #### Next Action Steps **A) For your Bulk Buyer List** Once your buyer audience/segment is ready, there are a few directions you can take it depending on your GTM motion. The most direct path is enrolling the audience in a bulk email campaign. [Reo.Dev](http://Reo.Dev) connects directly with Apollo, Outreach, and Salesloft so you can push buyers into an existing sequence without downloading anything.
**Guides:** * [**Full guide on creating buyer segments and running buyer campaigns**](https://docs.reo.dev/buyers/how-to-find-segment-and-engage-decision-makers-in-reo.devs-buyer-section) * [**Learn how to run bulk email campaigns to your Buyer Audience**](https://docs.reo.dev/campaigns/run-bulk-email-campaigns) **Guides to connect your Email tool with Reo.Dev:** * [**Apollo**](https://docs.reo.dev/integrations/email/apollo.io) * [**Outreach**](https://docs.reo.dev/integrations/email/how-to-integrate-and-use-outreach.io-with-reo.dev) * [**Salesloft**](https://docs.reo.dev/integrations/email/how-to-integrate-and-use-salesloft-with-reo.dev) If LinkedIn prospecting is part of your workflow, download the CSV of buyer LinkedIn handles from your audience and add them as first degree connections, either manually or through an automation tool like [Phantombuster](https://phantombuster.com/). You can also send buyer audience data to any external tool automatically using [Reo.Dev](http://Reo.Dev)'s Webhooks integration. > **🔗** [**Learn more about Webhooks**](https://docs.reo.dev/integrations/webhooks) **Recommended playbook to help you next here:** [**Add Buyer Contacts as LinkedIn Connections on Autopilot for your Sales Reps**](https://app.notion.com/p/Add-Buyer-Contacts-as-LinkedIn-Connections-on-Autopilot-for-your-Sales-Reps-30c33e0c3ba280c68bb3cae9cd6963eb?pvs=21) If you have a field marketing motion running alongside sales, this buyer list is also a clean source for event invitations, conference outreach, or closed room dinner invites where you want warm, intent-qualified faces in the room rather than cold attendees. **B) For Individual Account Buyers** **Use** [**Reo-Copilot**](https://docs.reo.dev/playbooks/for-sdrs/do-account-research-in-seconds-and-warm-up-buyers) 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. --- # 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/for-sdrs/upload-target-accounts-and-get-buyer-contacts.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.