Find Accounts with Multiple Developers Evaluating Your Competitor GitHub Repositories

Play: Track Developers and Buyers Engaging with Competitor Repositories

This play helps you identify developers and buyers from accounts that are actively engaging with your competitors’ repositories. By analyzing developer activities like forks, stars, opened issues, and pull requests, you can uncover engagement patterns to craft personalized outreach. With this data, you can identify decision-makers and leverage Apollo integration to initiate timely sequences that position your product as the superior alternative.

Video Link‍

{{playbook-callout-1}}

1. Navigate to the Prospects Tab:
   • Click on the account of interest → Go to the Prospects tab.
   • Choose between the Buyers or Developers sub-tabs based on your target audience.
   • For more detailed steps on using this feature, refer to our Find Buyer Contact Guide.
2. Utilize the "Find More Buyers" Feature:
3. Click on Find More Buyers to discover additional prospects. This feature leverages AI to identify decision-makers based on:
   • Developer Activity Location: Suggests prospects from locations where active developers interact with your assets.
   • Seniority Level: Automatically includes profiles at the “Director” level or higher for effective targeting.
   • Adjust filters like Location, Seniority, and Job Function for precision. Refer to the detailed Find Buyer Contact Guide for full filtering options.‍
4. Create and Save Personas:
   • Quickly access predefined buyer attributes by creating a persona.
   • Click Select or Create Persona → Add desired attributes → Save Persona.
   • The next time you use the tool, you can instantly select your saved persona for streamlined searching.
5. Import from CRM:
   • If your CRM is integrated, click Import from CRM. This feature synchronizes existing prospects from your CRM, helping avoid duplicate outreach efforts.
   • For more details, see the Find Buyer Contact Guide.
6. Add to Outreach List:
   • Select relevant buyer profiles and click Add Buyers. These contacts will appear in the list, enriched with their source information.
7. Apollo.io Integration (Recommended):
   • To streamline outreach, directly add selected profiles to your Apollo.io sales sequence:
     • Click Add to Apollo Sequence → Choose the relevant sequence.
     • Confirm the sender and click Send to Sequence.
   • For detailed Apollo.io configuration with Reo.Dev, check the Apollo.io Setup Guide.
8. Craft Your Personalized Outreach Message
   • Utilize the provided contact details like their LinkedIn profile or email address.
   • Draft a message that acknowledges their engagement with competitive repositories and positions your product as the superior alternative. For example:

Hi {Developer Name},
I noticed your recent activity on {Competitor Repository Name}, including your {specific activity like a comment or issue}. I wanted to introduce you to {Your Product Name}, which directly addresses {specific challenge or feature gap} and could help you {Business outcome your product solves for}. Let me know if you'd like to explore how we can support your team!
Looking forward to connecting,
{Your Name}

{{playbook-callout-3}}

{{playbook-callout-2}}

Play Agnostic Execution

The above Play is consistent across different segments, playbook collections and plays. Whether you’re targeting top accounts, recent product sign-ups, or competitors’ users, the goal remains the same: Activate your outreach list effectively. By following this structure, you can ensure a robust, multi-channel outreach strategy that maximizes the use of high-intent signals gathered by Reo.Dev and win more deals.

Messaging Examples & Best Practices

{{playbook-callout-18}}

Additionally, each example below is tailored to two distinct personas: Buyers and Developers/Champions.

• Buyers typically hold senior positions (e.g., Directors or above) and possess decision-making authority. They are identified using our AI’s classification based on job titles, seniority levels, and other criteria, such as location and job function. It can also account for your configuration of persons in our platform’s settings.
• Developers or Champions, on the other hand, are the technical stakeholders who actively engage with your GitHub repositories or product documentation, driving adoption and internal advocacy.

The distinction is crucial to ensure the messaging aligns with the recipient’s role and responsibilities, enhancing its relevance and effectiveness. Personalizing your approach based on persona not only increases engagement but also aligns your messaging with the recipient's potential interest in either the technical or strategic benefits of your product.

{{playbook-callout-19}}

Multiple Repositories Engagement Angle – Accounts Evaluating Several Competitive Repos

This approach targets accounts with multiple developers engaging across various competitive repositories within the last 180 days. By analyzing activities such as forks, stars, issues, pull requests, and watches, you can identify accounts actively exploring solutions in your category. This type of engagement suggests a higher level of intent, making these accounts prime candidates for outreach where you can position your product as the superior alternative.

1a. Email (Buyer Persona)

Subject: {Name}, exploring multiple solutions in {Solution Category}?

Hi {Name},

I noticed that your team has been exploring several competitive repositories in {Solution Category}, suggesting you might be evaluating options for your next steps. At {Your Company Name}, we believe {Your Product Name} offers distinct advantages, including {specific feature/benefit}, to streamline workflows and boost productivity.

Would you be open to a quick conversation to discuss how {Your Product Name} can help optimize your processes and add more value beyond other available options?

Best regards,

{Your Name}

1b. LinkedIn Message (Buyer Persona)

Hi {Name},

I came across your team’s recent activities across multiple competitive repositories in {Solution Category}, which indicates a strong interest in identifying the right solution. At {Your Company Name}, we offer a robust alternative in {Solution Category}, with innovative features like {unique feature/advantage} that can set your team apart.

Would love to connect and share how {Your Product Name} could meet your needs and add unique value!

Looking forward to connecting,

{Your Name}

1c. Email (Developer Persona)

Subject: Evaluating alternatives? Try {Your Product Name}

Hi {Name},

I noticed your recent engagements across multiple competitive repositories in {Solution Category}. If you're exploring similar tools, {Your Product Name} could offer exactly what you’re looking for, with features like {specific technical feature/benefit} that enhance workflows and improve integration.

Feel free to reach out if you'd like to explore our open-source version or try our commercial offering. We’d love to support your team’s journey!

Best,

{Your Name}

Hi {Name},

I saw that you and your team have been exploring several competitive repositories in {Solution Category}. If you’re open to considering new tools, {Your Product Name} provides advanced features that simplify workflows and deliver faster results.

Let me know if you’d like more information or would be interested in a free trial. I’d be happy to assist!

Best,

{Your Name}