Track All Accounts Evaluating a Specific Competitor GitHub Repository

Play: Track Developers and Buyers Engaging with a Specific Competitor Repository

This play helps you identify both developers and buyers from accounts actively engaging with a specific competitor's GitHub repository. By analyzing developer activities such as forks, stars, pull requests, and opened issues, you can uncover intent signals to tailor personalized outreach. With these insights, you can pinpoint decision-makers and utilize Apollo integration to launch targeted sequences, effectively positioning 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}}

GitHub Activity Angle – Recent Engagement on a Competitor Repo

This approach targets accounts recently active on a specific competitive GitHub repository, performing activities like forking, starring, or raising issues. This engagement can signal that these accounts are evaluating solutions in your category, offering a timely opportunity to introduce your product as an alternative.

1a. Email (Buyer Persona)

Subject: {Name}, exploring better options in {Solution Category}?

Hi {Name},

I noticed your team’s recent activity on {Competitive Repo Name}, indicating potential exploration in {Solution Category}. At {Your Company Name}, we’ve developed {Your Product Name}, which offers unique features like {specific feature/benefit} to streamline processes and deliver measurable results.

Would you be open to a quick call to explore how we can align with your goals and offer superior value compared to {Competitive Repo Name}?

Looking forward to discussing how {Your Product Name} can support your team’s success.

Best regards,

{Your Name}

1b. LinkedIn Message (Buyer Persona)

Hi {Name},

I noticed your team’s recent engagement with {Competitive Repo Name}, which aligns closely with the solutions we offer at {Your Company Name}. If you’re evaluating alternatives in {Solution Category}, I’d love to introduce you to {Your Product Name}, designed to drive efficiency and ROI.

Let’s connect to discuss how {Your Product Name} can deliver value to your team and help you achieve your strategic objectives.

Best regards,

{Your Name}

1c. Email (Developer Persona)

Subject: Exploring alternatives to {Competitive Repo}?

Hi {Name},

I saw you’ve been engaging with {Competitive Repo Name}, which is great for {specific use case}. If you’re exploring options, {Your Product Name} offers advanced features like {specific feature/technical benefit} to enhance workflows and address your specific needs.

Would you like to check out our free trial or set up a quick chat? We’re always happy to support developers like you in exploring the best tools for your goals.

Looking forward to your reply!

Best regards,

{Your Name}

1d. LinkedIn Message (Developer Persona)

Hi {Name},

I noticed your recent activity on {Competitive Repo Name}. At {Your Company Name}, we’ve built {Your Product Name} with advanced features like {specific feature/technical benefit} to make your development process faster and more efficient.

Would you be interested in learning how it compares to {Competitive Repo Name}? I’d be happy to share more details or help you get started with a free trial.

Best regards,

{Your Name}