HOME  /  GUIDES  /  DEVELOPER PLATFORMS

How to find leads on GitHub and other developer platforms

Companies leave a clear trail on developer platforms. Their public repositories show what they build with, their packages show who depends on them, and their activity shows what they're working on this month. If you sell to engineering teams, this is where to look.

6 sites coveredOn Power and higherAll how-to guides
Works on
  1. 1Spot the repository
  2. 2Press Save
  3. 3It lands in your list
  4. 4Follow up
An illustration of the flow, not a screenshot. Tidewater is a fictional company.
WHY THIS CHANNEL

Why developer platforms are worth your time.

Engineering teams rarely announce what they use, but their public work shows it. A repository's dependencies, its commit history and its open issues describe a team's stack and its problems in more detail than a sales call would.

That makes developer platforms unusual: you can qualify a company before you contact it. If their code already depends on the thing you extend or replace, you know the conversation is relevant.

WHAT TO LOOK FOR

The signals worth saving.

01

A company's stack

Public repositories name the frameworks and services a team uses.

02

A popular package

A package with many users means a team with people to support.

03

A new organisation or model

A fresh organisation page on GitHub or Hugging Face is a team that just started shipping.

04

A tool you replace or extend

A repository that depends on it is a team that already has the problem you solve.

SAVE OR SKIP

A quick test before you press Save.

Save it

  • An organisation whose stack matches what you sell into
  • A project that depends on a tool you extend
  • A fast-growing package with a small team behind it

Skip it

  • Personal experiments and coursework
  • Archived repositories
  • Forks with no changes of their own
STEP BY STEP

How to do it.

  1. Open a repository, model, package or organisation page.
  2. Press Save beside its name.
  3. Confirm the owner as the company.
  4. Save the organisation page when you want the company, or a single repository when that project is the reason.
WHAT TO WRITE

Two ways to open.

Your [repository] uses [tool]. We maintain [what you make], which plugs into it and removes [pain]. Happy to show how.
Noticed [package] has a lot of users now. If supporting them is getting heavy, that's what we help with.

Templates, with the parts in brackets for you to fill in. The specific detail is what gets a reply, so don't send them as they are.

A WORKED EXAMPLE

A founder who sells hosted Postgres tooling finds tidewater/queue, a job queue built on Postgres with four contributors and commits this week. She saves the repository, confirms Tidewater as the owner, and writes to the maintainer about a problem she spotted in their open issues.

An invented example. The people and companies in it are fictional.
TIMING

When to follow up.

Activity is the signal. A repository updated this week has a team working on it now. One untouched for a year doesn't.

Whatever the channel, set a follow-up date in On Radar when you save. A lead without a date is a lead you'll rediscover in three months.

WHERE IT WORKS

6 sites in this channel.

SitePlanWhat you save
GitHubPowerSave the owner of a repository, model or package, with its website.
Hugging FacePowerSave the owner of a repository, model or package, with its website.
GitLabPowerSave the owner of a repository, model or package, with its website.
npmPowerSave the owner of a repository, model or package, with its website.
PyPIPowerSave the owner of a repository, model or package, with its website.
Docker HubPowerSave the owner of a repository, model or package, with its website.

Each name links to its own guide, with where the button sits and exactly what a save keeps. The sources page has the full list.

MISTAKES

What to avoid.

Pitching in issues or pull requests. It reads as spam there.
Assuming a personal repository belongs to a company.
Treating stars as budget. They measure interest, and nothing more.
QUESTIONS

The short answers.

Which platforms are covered?

GitHub, Hugging Face, GitLab, npm, PyPI and Docker Hub.

Can I save a whole organisation?

Yes. The button appears on an organisation's own page as well as on a repository, model or package.

Is it acceptable to contact maintainers?

By email, with something useful, usually yes. In issues and pull requests it reads as spam, so keep sales out of them.

Is it safe for my accounts?

Save This Lead never posts, likes, follows or messages, and it never browses on your behalf. It reads a page when you press Save.

What does it cost?

There's a free plan, and paid plans start at $19 a month. The plan each site needs is in the table above and on the pricing page.

One button to save.
One place to find it.

Keep useful posts, leads and their context together. Leave the copy-paste routine behind.

Try Power free for 7 daysDesktop Chrome  ·  No card required  ·  Then Free, with no time limit