Identify Leads in ICP Accounts Active on Your GitHub Repository

Play 1: Personalize Developer Outreach Using Activity Timeline Insights in Reo.Dev

Video Link

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.

Step 1: Navigate to a Developer Profile

1. Go to your main developer segment created under this play.
2. Click on any developer lead to open their Profile Card.
3. 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

1. Scroll down to view the Activity Timeline, showcasing the developer’s interactions over time.
2. 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

1. Utilize the provided contact details like their LinkedIn profile or email address.
2. Draft a message that acknowledges their recent interactions. For example:

"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."

{{playbook-callout-12}}

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.

{{playbook-callout-9}}

Configure alerts based on your preferences:

1. Email Notifications: Receive updates when new activities are logged.
2. 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 Reo.Dev ‘Custom Tags’

Video Link

This play demonstrates the power of custom tags for developer segments. With tags, you can track specific activities like forks, stars, pull requests, or comments on your GitHub repositories. By adding these markers, you refine your existing segments and build a targeted list of developers, helping you identify high-intent leads and personalize your outreach.

{{playbook-callout-14}}

Step 1. Create a Custom Tag - Forked on Own GitHub Repositories

• Segment Type: Developer
• Tag Name: Forked Own Repo
• Description: Flags developers who have forked your GitHub repositories, indicating strong interest & evaluation
• Prerequisites: Ensure Own GitHub repositories are configured correctly in the platform. For detailed setup instructions, refer to this guide.

{{playbook-tag-3}}

• Example Use Case: This tag can be used to identify developers who are actively exploring your GitHub repository by forking it. Such actions often indicate early-stage evaluations or experimentation with your project. Leverage this tag to prioritize outreach to developers who may become potential champions or advocates.
• Bonus Tips & Recommendations: This same tag structure can be used to create similar tags to track and combine other high-intent Github activities on your own or competitor repositories such as Stars, Comments, Pull Requests, and Watches. Using these tags collectively allows you to further prioritize your developer profiles and gather more engagement markers to personalize your outreach messaging.

{{playbook-callout-15}}

Step 2: Apply the Custom Tag to Your Main Segment

1. Switch to your main developer segment created in the first video under this play.
2. Click on ‘Add Filter’, select ‘Tags’, and choose the custom tag ‘Forked Our Repo’ that you just created.
3. This filter refines your segment to show only developers who have demonstrated strong interest by forking your repository.

Step 3: Take Action on Your Refined Developer List

Now that you’ve applied your custom tag and refined your developer segment, it’s time to engage your leads:

1. Click on any developer profile to view their detailed activity timeline and contact information. Use this context to craft personalized outreach messages.
2. Export the segment list if you prefer to work externally with this data.
3. Sync the list to your CRM for seamless integration, enabling your GTM teams to have access to the most up-to-date and relevant leads.

{{playbook-callout-16}}

Play Agnostic Execution

This play is designed to be flexible and applicable across all developer segments and tags. Whether you’re tracking GitHub activity, CLI usage, or documentation visits, custom tags provide a consistent way to enhance your targeting and optimize your outreach strategy.

🚀 Next Steps: Dive into your Reo.Dev dashboard and start creating custom tags for your developer segments. By refining your target list with meaningful engagement markers, you’ll be well on your way to driving higher response rates and closing more deals.