Find Decision Makers Amongst your Developer Activity

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.

{{playbook-callout-9}}

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

1. 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.
2. 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

Video Link

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.

{{playbook-callout-32}}

Step 1.  Create Custom Tags for Developer Segments

• Segment Type: Developer
• 3 Tags Covered: Own Github | Comp Github | Product Login
• 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.

{{playbook-callout-15}}

Step 2: Apply the Custom Tags to Your Main Developer Segment

1. Navigate to the main developer segment created in the beginning.
2. Click on ‘Add Filter’, select ‘Tags’, and choose any of the custom tags created above (e.g., ‘Own GitHub’, ‘Comp GitHub’, ‘Product Login’).
3. 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:

1. Click on any developer profile to view their detailed activity timeline and contact information. Use this context to craft highly personalized outreach messages.
2. Export the segment list for further analysis or direct action by your GTM teams.
3. 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.