> 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-aes/warm-up-buyers-in-your-target-deals.md).
# Warm up Buyers in your Target Deals
* [Introduction](https://docs.reo.dev/playbooks/for-aes/warm-up-buyers-in-your-target-deals#introduction)
* [Step 1: Use Reo-Copilot Prompts](https://docs.reo.dev/playbooks/for-aes/warm-up-buyers-in-your-target-deals#step-1-use-reo-copilot-prompts)
* [Step 2: Refine the Message Copy](https://docs.reo.dev/playbooks/for-aes/warm-up-buyers-in-your-target-deals#step-2-refine-the-message-copy)
* [Step 3: Send Message via Email or LinkedIn](https://docs.reo.dev/playbooks/for-aes/warm-up-buyers-in-your-target-deals#step-3-send-message-via-email-or-linkedin)
* [Next Steps](https://docs.reo.dev/playbooks/for-aes/warm-up-buyers-in-your-target-deals#next-steps)
### Introduction
Finding the right accounts to go after is only the first part of the job. The harder part is knowing who exactly to reach out to at that account and what to say when you do. Most AE’s either spend too long digging through LinkedIn and company pages trying to piece together enough context to write a decent message, or they skip the research entirely and send something generic that goes nowhere.
Neither works well when you are trying to move fast on accounts that are actively evaluating right now and are a part of an active deal.
Reo CoPilot solves both problems at once. It surfaces the key decision-makers worth reaching out to within an account and uses that account's actual developer activity to generate a personalized outreach message, so you are not starting from scratch every time.
*Let's explore this process in three simple steps.*
#### Step 1: Use Reo-Copilot Prompts
Navigate to any account page of interest in Reo.Dev and open **Reo CoPilot** from the account view. Run the following three prompts in sequence.
**Prompt 1:**
> **✦ Summarize last 30 days activity**
Use this to get a quick read on what the account has been doing. Look for signals like a spike in docs visits, CLI commands being run, product activity, enterprise features being explored, or multiple developers showing up for the first time. If the summary looks interesting, move to Prompt 2.
***
**Prompt 2:**
> **✦ Is this account showing purchase intent?**
CoPilot will analyze the activity patterns and tell you whether the signals suggest early exploration, active evaluation, or something closer to a buying decision. If the answer looks promising, this is your green light to start drafting outreach.
If you want to monitor purchase intent signals across your full target account list and get alerted when new accounts start showing evaluation activity, refer to this playbook:
[**Track Purchase Intent in Your Target Accounts and Get Real-Time Slack Alerts**](https://docs.reo.dev/playbooks/for-sdrs/track-purchase-intent-in-your-target-accounts-and-get-real-time-slack-alerts)
***
**Prompt 3:**
> **✦ Who are the key decision-makers among the developers active on this account?**
This surfaces the people within the account who are both technically engaged and likely to have influence or authority over a purchase decision. These are your warmest contacts because they are already interacting with your product.
At this point you have two options for who to reach out to. You can use the decision-makers CoPilot identifies from developer activity, or you can go after buyer contacts pulled based on your ICP persona.
If you have not set up your buyer contacts yet, refer to this playbook: [Upload Target Accounts & Get Buyer Contacts](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts)
**Prompt 4:**
> **✦ Generate a personalized outreach message for {Buyer Name}**
Replace `{Buyer Name}` with the specific contact you want to reach out to. CoPilot will use the account's recent activity to write a message that references what their team has actually been doing, so your outreach does not read like a cold template.
🔗 **Bonus Resource:** [**Reo Co-Pilot Prompt Library**](https://cdn.prod.website-files.com/67e6b65ee328bc6b91324c9a/699b7ac01cf0f9e76c9f787e_Reo%20Copilot%20Prompt%20Library.pdf)
#### Step 2: Refine the Message Copy
CoPilot gives you a strong starting point, but take a minute to review the draft and adjust the tone or angle to match your messaging style and any specific context you have about that account or contact. Small tweaks go a long way in making the message feel like it came from you rather than a tool.
#### Step 3: Send Message via Email or LinkedIn
Once you are happy with the message, send it directly via email or LinkedIn. With the activity context behind you, you are reaching out at exactly the right moment with exactly the right hook.
#### Next Steps
Once you are ready to move beyond one-off outreach and enroll buyers into structured sequences at scale, the next playbook will walk you through exactly that.
**Recommended playbook to help you next:**
[Add Prospects to your Email Sequences](https://docs.reo.dev/playbooks/for-aes/add-prospects-to-your-email-sequences)
---
# 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-aes/warm-up-buyers-in-your-target-deals.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.