The 7 GitHub Buying Signals Every Sales Team Should Track

Developers delete more cold emails than any other professional segment. They have finely tuned BS detectors, they hate being sold to, and they can usually tell in the first sentence whether you actually understand their work. The templates below are built on one principle: earn the right to reach out by demonstrating you've done actual research, then make the ask small.

All five are based on real outreach campaigns run by B2B devtool companies using GitLeads-sourced leads. Reply rates cited are from campaigns with 100+ sends per template.

Template 1: The Competitor Star (Signal-Based)

Use when: you detect that a developer starred a competing or adjacent open-source project. Best for: selling alternatives or complementary tools.

Subject: Quick question about [CompetitorTool]

Hi [First Name],

I noticed you starred [CompetitorRepo] recently — I'm guessing you're either
evaluating [CompetitorTool] or already using it for [use case].

We built [YourProduct] specifically for teams who outgrow [CompetitorTool] on
[specific dimension: e.g., "multi-environment support" / "cost at scale"].
The difference is [one-sentence differentiation].

Worth a 20-minute look? I can show you a live demo on your actual setup.

[Name]
[Title] at [Company]

P.S. Full disclosure — I found your GitHub profile through public activity.
To opt out of future messages: reply "unsubscribe."

---
Reply rate benchmark: 28–34%
Best for: Competitive displacement campaigns

Why This Works

You lead with proof that you know what they're working on. "I noticed you starred" is not creepy when you're reaching out as a professional about their professional GitHub activity — it's the same as saying "I saw your post on HackerNews." The ask is small (20 minutes, conditional on relevance), and you give them an easy out in the PS.

Template 2: The Problem Matcher (Issue-Based)

Use when: you detect a developer opening an issue in a repo that relates to a problem your product solves. Best for: highly specific ICP targeting.

Subject: Re: the [issue title] you opened on [repo]

Hi [First Name],

Saw you opened "[Issue Title]" on [RepoName] — that exact problem is something
we solve at [YourCompany].

[1-2 sentences explaining how you solve the specific problem they raised,
using their exact terminology from the issue.]

Curious if it's still blocking you or you found a workaround. Happy to share
how we approached it if useful.

[Name]

---
Reply rate benchmark: 38–45%
Note: Only use if your solution genuinely addresses the issue they opened.
Do not fabricate relevance.

Why This Works

This template has the highest reply rate because it reads like a response to a public question. You're essentially saying "I saw you ask a question, here's an answer." Developers respond well to this because they asked the question publicly in the first place — they want help. The ask is implicit and minimal: you're offering info, not a demo.

Template 3: The Stack Recognizer (Tech-Based)

Use when: you detect a developer's active repos use a specific tech stack that your product integrates with. Best for: SDK or integration partnerships.

Subject: [YourTool] + [Their Stack] integration

Hi [First Name],

Looked at your repos — you're building with [TechStack]. We just shipped a
native [YourTool] integration for [TechStack] that [does X in Y way].

Most [TechStack] teams we work with were previously [doing the thing manually /
using a workaround]. The integration handles [specific pain point] automatically.

Docs are at [link]. Worth 15 minutes to see if it fits your setup?

[Name]
[Title] | [Company]

---
Reply rate benchmark: 22–29%
Best for: SDK/integration products with clear stack-specific value

Template 4: The New Repo Trigger (Timing-Based)

Use when: a developer creates a new public repo using your target tech stack. Best for: developer tools that help developers at the start of a new project.

Subject: Saw you just started [repo-name]

Hi [First Name],

Noticed you created [repo-name] yesterday — looks like you're starting
a new [project type] project.

Early on is the best time to wire in [your product category], before the
config debt builds up. We have a [free tier / free trial] specifically for
solo founders and small teams.

Takes 5 minutes to set up. Want me to send over the quickstart?

[Name]

---
Reply rate benchmark: 24–31%
Timing is critical: send within 48 hours of repo creation.

Template 5: The Referral Mention (Social Proof)

Use when: the developer works at a company or uses a tool that has overlap with your existing customers. Best for: late-stage or mid-funnel outreach.

Subject: [MutualCustomer] uses [YourProduct] — curious if it's relevant for you

Hi [First Name],

Quick note — [MutualCustomer / Developer in same ecosystem] uses [YourProduct]
for [use case]. Thought it might be useful for your work on [their repo / company].

The main thing they said it solved: [specific outcome in developer terms].

No pressure — just wanted to put it on your radar since there's tech stack overlap.

[Name]
[Company]

---
Reply rate benchmark: 19–26%
Best for: warm outreach where mutual context exists

Follow-Up Sequence: The Two-Touch Rule

For developer audiences, limit yourself to two follow-ups maximum. Developers who don't reply to three messages aren't going to reply to a fourth, and sending more damages your reputation. The optimal cadence:

• Day 0: Initial email (templates above)
• Day 5: One follow-up, reference the original, add new information or a relevant resource
• Day 12: Final follow-up — break-up email ("I'll stop bugging you after this one...")
• Day 13+: Mark as cold, remove from sequence

Follow-up 1 (Day 5):
Subject: Re: [original subject]

Bumping this in case it got buried.

One thing worth adding: [new piece of value — case study link, relevant blog post,
or updated info about your product].

Still happy to show you a quick demo if timing is better now.

[Name]

---

Follow-up 2 (Day 12):
Subject: Last one from me

Not going to keep emailing if it's not relevant — I'll take silence as a no.

But if you ever want to revisit [problem you solve], [product landing page]
is the quickest way to explore.

Good luck with [their project/company].

[Name]

What Not to Do

• Don't open with "I came across your profile" — it's a red flag that you're mass-emailing
• Don't pitch in the first sentence — state a problem or observation first
• Don't ask for a 30-minute call in the first email — 15 minutes max, make it optional
• Don't use "just checking in" in follow-ups — it adds no value
• Don't fake personalization — a wrong detail (wrong repo name, wrong language) destroys credibility instantly
• Don't skip the opt-out footer — legally required under GDPR/CAN-SPAM, and it's the right thing to do

Getting Leads to Email

These templates only work if you have the right lead data: GitHub username, confirmed email, and the specific signal (star, fork, issue, new repo) that triggered the outreach. GitLeads automates this — define your ICP, select which GitHub signals to monitor, and get a queue of enriched leads with the signal context pre-filled for template personalization. The free tier gives you 50 leads per month to validate the approach before scaling.