Identify Developers Opening Issues & Comments on your Competitor GitHub Repositories

This play helps you tailor developer outreach by using detailed activity timeline insights. It focuses on leads from your ICP accounts who are actively engaging with your competitor’s GitHub repositories. By analyzing actions like opening issues and commenting, you can uncover pain points and challenges they are experiencing with competing solutions. Use these insights to craft highly targeted messaging that positions your product as the superior choice. By addressing their specific needs and aligning with their current evaluation stage, you can effectively convert competitive interest into opportunities, driving meaningful conversations and adoption of your product.

{{playbook-callout-9}}

Step 1: Navigate to a Developer Profile

1. Go to your main developer segment created for this play, focusing on leads opening issues on competitor GitHub repositories.
2. Click on any developer lead to open their Profile Card.
3. Review the key details provided, including:
   • Designation and Company: Understand their role and decision-making influence.
   • First and Last Activity Date: Gauge their engagement recency.
   • Activity Channels: Check where their activities are logged (e.g., GitHub).

{{playbook-callout-10}}

Step 2: Analyze the Activity Timeline for Contextual Insights

• Scroll down to view the Activity Timeline, which highlights the developer’s recent interactions.
• Pay close attention to high-intent activities such as:
  • Opened Issues: Indicates they are actively troubleshooting or exploring gaps in competitor solutions.
  • Comments: Offers direct feedback that can reveal pain points or interests.
  • Other Activities: Pull requests or forks can signal deeper evaluation.

{{playbook-callout-23}}

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:

Example Message 1: Offering a Free Trial or Open-Source Version Based on an Issue/Comment

Subject: Saw your recent activity on {Competitor Repo Name}—try this!

Hi {Name},

I noticed your recent {issue/comment} on {Competitor Repo Name} discussing {specific challenge or feature gap}. At {Your Company Name}, we’ve been solving similar challenges with {Your Product Name}, and I think it might help streamline your process.

The best part? We offer an open-source version/free trial of our product, so you can explore its capabilities at your own pace.

Here’s the link to get started: [Insert Link to Open-Source Repository or Trial Signup]. If you have any questions while trying it out, I’d be happy to assist or even set up a quick call to walk you through the basics.

Looking forward to hearing your thoughts,

Best,

{Your Name}

Example Message 2: Addressing a Developer's Issues or Comments on a Competitor Repository

Hi {Name},

I noticed your recent {issue/comment} on {Competitor Repo Name} regarding {specific context of the issue or comment}, and I wanted to reach out. It sounds like you're tackling a challenge that’s all too familiar in this space.

At {Your Company Name}, we’ve developed {Your Product Name}, which specifically addresses {related feature or functionality} to solve these problems seamlessly.

If you’re exploring alternatives, I’d be happy to set up a quick call or offer a demo to show how we can make things easier for your team.

Looking forward to supporting your goals,

Best,

{Your Name}

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.