> 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/build-relationships-with-champion-developers-at-your-target-accounts.md). # Build Relationships with Champion Developers at Your Target Accounts * [Introduction](https://docs.reo.dev/playbooks/for-sdrs/build-relationships-with-champion-developers-at-your-target-accounts#introduction) * [Step 1: Select Your Account of Interest](https://docs.reo.dev/playbooks/for-sdrs/build-relationships-with-champion-developers-at-your-target-accounts#step-1-select-your-account-of-interest) * [Step 2: Use Reo Co-Pilot to Identify Your Most Active Developers and Draft Outreach](https://docs.reo.dev/playbooks/for-sdrs/build-relationships-with-champion-developers-at-your-target-accounts#step-2-use-reo-co-pilot-to-identify-your-most-active-developers-and-draft-outreach) * [Step 3: Refine the Message Copy](https://docs.reo.dev/playbooks/for-sdrs/build-relationships-with-champion-developers-at-your-target-accounts#step-3-refine-the-message-copy) * [Step 4: Reach out via Email, Community or LinkedIn](https://docs.reo.dev/playbooks/for-sdrs/build-relationships-with-champion-developers-at-your-target-accounts#step-4-reach-out-via-email-community-or-linkedin) {% 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 Closing enterprise deals in developer-led companies rarely happens through a single buyer conversation. The most effective SDRs run a **two-pronged approach:** they work the top-down motion with buyers while simultaneously building genuine relationships with the developers who are hands-on with your product. Those developers become your internal advocates, and their endorsement often carries more weight with the buying committee than anything you can say.
This playbook covers the bottom-up half of that motion. While a separate playbook covers how to warm up and outreach to buyers [Do account research in seconds & Warm up Buyers](https://docs.reo.dev/playbooks/for-sdrs/do-account-research-in-seconds-and-warm-up-buyers), this one focuses on identifying your most active developers at a target account and crafting personalized, helpful outreach that starts building a champion relationship before the deal is even formally open. The goal is not to pitch. It is to be genuinely useful to the developer based on exactly what they are doing in their evaluation, so that when the buying conversation happens, they are already in your corner. *Let's explore this process in four simple steps.*
#### Step 1: Select Your Account of Interest Navigate to your target account segment or territory list in Reo.Dev and pick an account you want to focus on. Ideal accounts for this playbook are those already showing meaningful developer engagement, such as accounts in the Building or Deployed stage in the Dev Funnel, or accounts with a recent Activity Surge tag, or your custom signals that indicate purchase intent. [**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) Open the account overview to get a read on what is happening there before you move to the next step. #### Step 2: Use Reo Co-Pilot to Identify Your Most Active Developers and Draft Outreach Once you are inside the account overview, open **Reo CoPilot.** CoPilot has visibility into all the developer activity signals Reo.Dev has captured for this account, which means it can surface the most relevant contacts and generate context-specific outreach in seconds. **Prompt 1: Surface the most active developers** Start by asking CoPilot: > "Show me the most active developers at \[Company Name] and what they have been doing recently." CoPilot will surface the developers with the highest engagement, along with a summary of their recent activity across channels like product usage, documentation, GitHub, and CLI commands. Review the list and identify one or two developers who look like strong candidates for outreach based on their recency and depth of engagement. **Prompt 2: Draft a personalized nurture message for your chosen developer** Once you have selected a contact, ask CoPilot to generate an outreach message tailored specifically to their activity: > "Draft a personalized outreach message for \[Developer Name] at \[Company Name]. Make it helpful and technical, focused on supporting them in their evaluation. Reference their recent \[docs activity / CLI commands / GitHub interactions]." CoPilot will use the developer's actual activity timeline to generate a message that references what they have specifically been doing, rather than a generic cold template. The angle here is not to sell but to offer genuine help based on where they are in their evaluation journey. For example, if the developer has been reviewing integration documentation or running install commands, CoPilot can frame the message around making that process easier for them. You can also use the Problem-Solving Outreach prompt from the [Reo Co-Pilot Prompt Library](https://cdn.prod.website-files.com/67e6b65ee328bc6b91324c9a/699b7ac01cf0f9e76c9f787e_Reo%20Copilot%20Prompt%20Library.pdf). If the developer's activity suggests they may be running into challenges: > "Draft an outreach message for \[Developer Name] at \[Company Name] who appears to be working through \[specific use case or docs section]. Offer immediate help and position yourself as a resource." #### **Step 3: Refine the Message Copy** Read through the draft and make any adjustments to match your tone and the specific context you have from your broader account knowledge. The goal is for the message to feel like it came from a person who actually noticed what the developer was doing, not from an automated sequence. #### Step 4: Reach out via Email, Community or LinkedIn Once your message is ready, pull up the developer's contact details directly from their profile card in Reo.Dev. You will find their LinkedIn URL and verified email address there, so you can send the message through whichever channel feels most appropriate for the contact. If the developer is already a member of your **Slack or Discord community,** reaching out via a DM there can add an even more personal touch. It meets them in a space they are already engaged in rather than a cold inbox, and the context of the shared community gives you a natural opening. You can also track your developer community interactions directly in Reo.Dev. Refer to the setup guides to configure this: * [**Slack**](https://docs.reo.dev/integrations/communities/owned-communities/slack) * [**Discord**](https://docs.reo.dev/integrations/communities/owned-communities/discord) Keep it short, specific, and genuinely helpful. {% hint style="info" %} 💡 **Pro tip:** If a developer looks promising but is not quite ready for outreach yet, use the Follow or Get Alerts option on their profile. This way you will be notified when they take new actions, so you can reach out at exactly the right moment with fresh context. {% endhint %} #### Recommended Next Playbooks [Do account research in seconds & Warm up Buyers](https://docs.reo.dev/playbooks/for-sdrs/do-account-research-in-seconds-and-warm-up-buyers) Running the top-down motion at the same time as this bottom-up developer outreach is what makes the multi-threaded approach work. Use this playbook to research the account and warm up the buyer contacts in parallel. [Upload Target Accounts & Get Buyer Contacts](https://docs.reo.dev/playbooks/for-sdrs/upload-target-accounts-and-get-buyer-contacts) If you have not yet identified your buyer contacts at this account, start here to pull the right decision-makers based on your ICP persona configuration. --- # 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/build-relationships-with-champion-developers-at-your-target-accounts.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.