Identify Active Developers from Accounts with High Intent
This playbook helps you identify all relevant developer leads within high-intent accounts.
Developer
Centric Playbook
•
1
min read
Share this playbook
Reo.Dev Intel Features Used
Activity Timeline
Dev Funnel
Tags
Customer Fit Score
Reo.Dev Data Sources Used
Code Interactions
Product Docs
Telemetry Data
Product API
Product Logins
Own GitHub Activities
Competitor GitHub Activities
CRM
Introduction
This playbook helps you identify all relevant developer leads within high-intent accounts, such as those accounts that are in “Mature stages” of evaluating your product, or are deeply and continuously interacting with your “Developer Docs”, or interacting with the “Code Commands”.
By segmenting these developer contacts, you can address stakeholders based on their specific activities and roles, tailoring your messaging for maximum relevance. Leveraging Reo.Dev’s advanced segmentation with multiple filter groups, you’ll cast a wide net to capture both high-engagement developers and those from mature, ICP-fit accounts, ensuring your outreach targets the most promising developer contacts.
Create Segment
We will create an advanced developer segment that captures a broad range of high-intent leads across your target accounts. The segment uses three distinct filter groups:
Advanced Dev Funnel Stage Filter: Targets developers from companies in the ‘Building’ and ‘Deployed’ stages of the Dev Funnel, indicating mature product usage. We also apply a Customer Fit Score of ‘Strong’ or ‘Moderate’ to ensure these accounts align well with your ICP attributes.
Code Interaction Filter: Focuses on developers who have interacted with your code commands, demonstrating strong technical engagement. We filter for accounts where the count of activities exceeds two within the last 180 days, alongside a ‘Strong’ or ‘Moderate’ Customer Fit Score for meaningful and recent engagement.
Documentation Review Filter: Identifies developers who have frequently accessed key product documentation, signaling deeper interest in exploring your product’s features. Similar activity count and recency filters are applied, coupled with the Customer Fit Score criteria to prioritize high-fit accounts.
By using the ‘OR’ operator across the filter groups, the segment captures any developers who meet at least one of these high-intent criteria. This approach maximizes your lead pool by including diverse yet highly engaged developer profiles from ICP-aligned accounts.
Use this enriched segment as a foundation for personalized outreach, allowing you to refine your strategy with subsequent plays for tailored messaging and deeper engagement.
First Filter Group: Under Intel - Dev Funnel - Includes any - ‘Building’ & ‘Deployed’ & Customer Fit Score - Includes any - ‘Strong’ & ‘Moderate’.
Second Filter Group: Under Activity Type - Code Interaction – Includes any - Select All - ‘CLI Installation Initiated & CLI Command Executed’ & Count of Activity is set to Greater than 2 & Date Range is set to ‘Last 180 Days’ & Customer Fit Score - Includes any - ‘Strong’ & ‘Moderate’.
Third Filter Group: Under Activity Type - Docs – Includes any - Select ‘Docs Review’ & Count of Activity is set to Greater than 2 & Date Range is set to ‘Last 180 Days’ & Customer Fit Score - Includes any - ‘Strong’ & ‘Moderate’.
Use the "OR" operator at the filter group level to include developers that meet at least one of the specified filter groups, providing a broader selection of results.
Tip: If your segment seems too narrow or broad, adjust the activity date range or the activity count filters to get your desired pool of accounts.
Plays are step-by-step strategies designed to help you use Reo.Dev's features effectively, guiding you through specific actions to uncover high-intent developers and optimize your outreach.
Play 1: Personalize Developer Outreach Using Activity Timeline Insights in Reo.Dev
This play focuses on individual developer engagement and provides a step-by-step approach for using Reo.Dev’s Activity Timeline to enhance your outreach. You’ll learn how to:
Explore the Developer Profile Card for key details like contact information, activity channels, and engagement history.
Use the Activity Timeline to identify high-value interactions (e.g., forks, pull requests, comments).
Craft personalized messages based on specific actions, increasing the likelihood of a positive response.
Set up alerts for ongoing monitoring of key developer leads.
{{playbook-callout-9}}
Step 1: Navigate to a Developer Profile
Go to your main developer segment created under this play.
Click on any developer lead to open their Profile Card.
Review the key details provided, including:
Designation and Company: Helps understand their role and influence level.
First and Last Activity Date: Provides insight into their engagement recency.
Activity Channels: Lists the sources of their activity (e.g., GitHub, Website).
{{playbook-callout-10}}
Step 2: Analyze the Activity Timeline for Contextual Insights
Scroll down to view the Activity Timeline, showcasing the developer’s interactions over time.
Look for high-intent actions such as:
Forks: Indicates exploration or potential usage of your repository.
Pull Requests: Suggests active contribution or evaluation of your code.
Comments: Provides feedback or indicates interest in specific features.
{{playbook-callout-11}}
Step 3: Craft Your Personalized Outreach Message
Utilize the provided contact details like their LinkedIn profile or email address.
Draft a message that acknowledges their recent interactions. For example:
Example Message 1: Personalized Outreach to a Developer Based on Recent GitHub Activity
"Hi {Developer Name}, I noticed you recently forked our {Repository Name} and submitted a pull request. It’s great to see your interest! I’d love to hear more about your use case and see if there’s any way I can assist you."
Example Message 2: Requesting a Warm Introduction from a Developer Engaged with Product Documentation
Hi {Developer Name}, I saw that you’ve been engaging with our {Version Update} docs. It’s fantastic to see your interest! If it’s not too much trouble, could you help connect me with the right person on your team who might be evaluating our solution further? A warm introduction would be really helpful. Appreciate your support!
Step 4: Set Up Alerts for Ongoing Monitoring
If you feel the profile you are analyzing is not ready yet for outreach but it can be promising soon, you can — click on Follow or Get Alerts for that profile.
Configure alerts based on your preferences:
Email Notifications: Receive updates when new activities are logged.
Slack Notifications: Get real-time alerts within your preferred Slack channel.
{{playbook-callout-13}}
Play Agnostic Execution
This play is applicable across all your developer segments and custom tags. Whether you’re targeting developers engaged with specific features, high-value documentation pages, Github repository activities or CLI commands, the Activity Timeline provides a consistent, actionable approach for personalized outreach.
Play 2: Identify High Intent Developer Leads using “Custom Tags” in Reo.Dev
This play uses Reo.Dev’s custom tags feature to highlight developers with key engagement activities. In this example we have covered three such tag use cases—Own GitHub Interactions, Competitor GitHub Interactions, and Product Login. These tags help you identify developers who are either exploring your repositories, evaluating competitor solutions, or actively engaging with your product. Use these insights to to prioritize high-intent leads, and create targeted, personalized outreach strategies.
Description: Flags developers who have either logged into our Product, interacted with your Github repository or with your competitor repository.
Prerequisite 1: Ensure GitHub repositories are configured correctly in the platform. For detailed setup instructions, refer to this guide.
Prerequisite 2: Ensure the Product Usage API & Product JS is configured with metrics like login activity, trial start, or product usage events. For setup details, refer to the **Product Usage Guide & Product JS Guide.**
{{playbook-tag-4}}
Example Use Cases:
For Own Github: Pitch these developers solutions to try your free tier or the advantages of upgrading to your commercial version.
For Competitor Github: Engage these developers with messaging that highlights the unique benefits of your product compared to competitors. Offer solutions to try your free tier or open-source offering.
For Product Login: Pitch these developers with personalized product support or highlight the advantages of your product features, reinforcing their interest.
Own Github Tag Segment Criteria
Competitor Github Tag Segment Criteria
Product Login Tag Segment Criteria
{{playbook-callout-15}}
Step 2: Apply the Custom Tags to Your Main Developer Segment
Navigate to the main developer segment created in the beginning.
Click on ‘Add Filter’, select ‘Tags’, and choose any of the custom tags created above (e.g., ‘Own GitHub’, ‘Comp GitHub’, ‘Product Login’).
This filter refines your segment, displaying developers who have shown high engagement through specific activities across various touchpoints.
Step 3: Take Action on Your Refined Developer List
Now that your segment is filtered with high-intent developer tags, it’s time to engage:
Click on any developer profile to view their detailed activity timeline and contact information. Use this context to craft highly personalized outreach messages.
Export the segment list for further analysis or direct action by your GTM teams.
Sync the list with your CRM, ensuring seamless follow-up and access to enriched developer profiles for personalized engagement.
{{playbook-callout-33}}
Play Agnostic Execution
The approach of combining multiple tags for developer engagement is designed to be flexible and adaptable across different developer segments. Whether you’re targeting GitHub activities, competitor engagements, or product logins, this play ensures comprehensive coverage and helps you optimize your outreach strategy.
🚀 Next Steps: Log into your Reo.Dev dashboard and implement these tags for your developer segments. By refining your list with meaningful engagement markers, you’ll identify high-intent leads faster and drive better response rates.
Summary
In this playbook, you learned how to identify developer leads within high-intent accounts using an advanced segmentation approach. By leveraging Reo.Dev’s filter groups, you created a wide-reaching developer segment that captures leads based on mature product adoption stages, code command interactions, and documentation engagement. This strategy ensures that your outreach targets high-potential contacts who demonstrate strong interest and fit well with your ICP. With this segment as a base, you can build customized sequences and deliver role-specific messaging, increasing the chances of engaging key stakeholders and driving meaningful conversions.
If you have any questions or need further assistance, please reach out to support@reo.dev or connect with your Customer Success Representative.
Talk to Our Team
Need help to understand this playbook or implementing it? Book a call with our team for guidance. Have a custom playbook requirement or feedback to share? We’d love to hear from you! Simply schedule a meeting, and we’ll help you maximize your results with Reo.Dev
If you have any questions or need help, you can reach out to us in our Slack customer channel, schedule a meeting with our team, or email us at support@reo.dev. We’re here to support you every step of the way and ensure you get the most out of Reo.Dev!
Before creating this segment, ensure you have configured the customer fit score attributes under settings in Reo.Dev. For setup instructions, refer to the guide below.
Under Activity Group - GitHub Repository - Repository Type: Includes any - Select “Owner”.
Under Activity Type - GitHub: Includes any - Select all.
Under Date Range - Select “is” - Select "Last 180 Days."
Use the Matches All operator for combined criteria.
Competitor Github
Under Activity Group - GitHub Repository - Repository Type: Includes any - Select “Competition”.
Under Activity Type - GitHub: Includes any - Select all.
Under Date Range - Select “is” - Select "Last 180 Days."
Use the Matches All operator for combined criteria.
Product Login
Under Activity Type - Product: Includes any - Select "Product Login”.
Under Date Range - Select “is” - Select "Last 180 Days."
Use the Matches All operator for combined criteria.
Note: If your custom tag segment feels too narrow or broad, try modifying the configurations like increasing/decreasing your activity date range period or increasing/decreasing your count of activity # or using the "Matches Any" operator instead of "Matches All" operator to get your desired pool of accounts.
For additional tag-based strategies and advanced segmentation tips, refer to the Reo.Dev Tags Handbook.
Outreach Tip
Leverage the specific activity markers from the tags in your messaging. Acknowledge recent actions like forking your repository or logging into your product to create a more personalized and relevant outreach experience.
Pro Tip
Focus on the last activity date to gauge recent engagement and prioritize those leads for outreach.
Tip
Personalizing your message based on specific developer activities increases the relevance of your outreach, leading to higher engagement rates.
Example Use Case
If the timeline shows a recent fork followed by multiple comments, this developer might be evaluating your project for a specific use case. Consider reaching out with a personalized message referencing their recent activity.
Subscribe to Reo.Dev Playbooks
Be the first to know when new playbooks are added, and receive exclusive pro tips and use cases straight to your inbox.
*By subscribing, you’ll receive updates, expert tips, and our latest playbooks curated for your success. We respect your privacy and won’t spam your inbox.
