# How to turn open-source users into pipeline

By Joe Cantu, founder of Insights ABM · Published 2026-11-19 · Updated 2026-11-19
Source: https://insightsabm.com/blog/open-source-users-to-pipeline/

> **Short answer:** Open-source usage is the strongest buying signal a developer tool company has, but most teams can't see who is using their project. To turn it into pipeline: capture downloads and docs views by company with a tool like Scarf, sync them to HubSpot or Salesforce, score each company on fit and depth of usage, find the platform and engineering leaders at the best-fit accounts, and run warm, helpful outreach within 24 hours of a usage spike. Measure demos and pipeline from open-source accounts.

For a commercial open-source or developer tool company, usage is the best buying signal you'll ever get. A company downloading your package every day already has the problem you solve. Yet most teams can't see who those companies are, so sales ends up cold-calling lists while warm accounts go unnoticed.

Here's the playbook we've used with developer tool clients, including [Axoniq](/blog/account-based-marketing-success-stories-real-life-examples-to-inspire-your-strategy/), to turn open-source adoption into pipeline.

## Step 1: Capture usage by company

You can't act on what you can't see. Scarf [tracks open-source downloads, documentation views, and other artifact interactions](https://about.scarf.sh/scarf-for-sales-leaders/) and matches them to companies. You can [route downloads through your own domain, embed analytics in packages, or add pixels to docs](https://about.scarf.sh/platform), and Scarf [doesn't store personal data](https://go.opensource.org/scarf).

Capture at least:

- Package and container downloads
- Documentation and quick-start page views
- Visits to enterprise, pricing, and security pages on your site

## Step 2: Put it in the CRM

Usage that lives in a separate dashboard gets ignored. Scarf [syncs open-source insights to Salesforce and HubSpot](https://about.scarf.sh/post/how-we-use-scarf-for-open-source-marketing/). Match each event to the company record so activity adds up at the account level.

## Step 3: Score fit and depth

Not every user is a buyer. A student, a hobbyist, and a Fortune 500 platform team look the same in download counts. Score on two things:

| Fit | Depth of usage |
| --- | --- |
| Industry, size, region | Downloads rising over 3+ weeks |
| Tech stack that matches your product | Several environments or teams |
| Regulated or at-scale use case | Docs on production, security, or scaling |
| Not already a customer | Visits to pricing or enterprise pages |

Accounts high on both go to sales. High fit with light usage goes to nurture and ads. Low fit stays community.

## Step 4: Find the buying committee

The developer downloading your package rarely signs the contract. Use Apollo or a similar tool to find the people who do: VP of Engineering, Head of Platform, SRE or infrastructure leads, and, for security-heavy products, the CISO's team.

## Step 5: Reach out warmly within 24 hours

Speed matters, and so does tone. Good outreach is helpful, specific, and never says "we saw you downloading our software."

- **Lead with a problem they're likely to hit next:** production hardening, scale, compliance, or support.
- **Offer something useful:** an architecture review, a production checklist, or office hours with an engineer.
- **Write for the role:** reliability and cost for platform leads, risk and speed for engineering leaders.

## Step 6: Support it with ads and content

Sync high-fit open-source accounts to LinkedIn as a company audience and run proof-led ads aimed at engineering leaders. Publish the content those buyers search for: comparisons, migration guides, and production best practices. Reddit and technical YouTube also work well for developer audiences.

## Step 7: Measure pipeline, not stars

GitHub stars and download counts show popularity, not revenue. Report weekly on:

- Open-source accounts that reached sales
- Meetings and demos booked from them
- Pipeline and win rate versus other sources

## What does this look like in practice?

For Axoniq, a Series A event sourcing software company, we combined open-source signals, a fit-scored target list, and role-specific outreach with paid and social programs. The program produced [more than $1M in pipeline in its first six months](/about/).

Insights ABM builds this system in HubSpot or Salesforce with Scarf, Apollo, and LinkedIn. See our [B2B SaaS industry page](/industries/b2b-saas/) or [GTM engineering services](/lp/gtm-engineering/).

Developers talk about tools on Reddit and LinkedIn. See [Reddit Ads vs LinkedIn Ads for developer audiences](/blog/reddit-ads-vs-linkedin-ads-developer-audiences/) and our [Reddit marketing services](/lp/reddit-marketing-services/).

## FAQ

### How do I find out which companies use my open-source project?

Use an open-source usage analytics tool such as Scarf, which tracks package downloads, documentation views, and other interactions and matches them to companies without storing personal data.

### Should sales contact open-source users?

Yes, but warmly and with something useful: help with production deployment, security, scale, or support. Contact the engineering and platform leaders at well-fitting companies, not every individual developer.

### What's a good signal that an open-source user is ready to buy?

Usage growing across several weeks, multiple people or environments at the same company, visits to enterprise, pricing, or security pages, and a company that fits your ideal customer profile.
