LEAD GENERATION

New GitHub Stargazers to ICP-Scored Outbound Packet

Watches your OSS repo for new stargazers, enriches each one's company and role, scores them against your ICP.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew stargazer on watched repoGitHubGitHub
  • ActionFetch stargazer profile and orgGitHubGitHub
  • ActionEnrich person and company via ExaExa
  • LogicScore against ICP; drop low-fit
  • ActionUpsert qualified lead in AttioAttio
  • OutputPost research packet to sales SlackSlack

What it does

Every time someone stars your open-source repo, this pulls their public profile, enriches the person and company behind the account, scores the fit against your ideal customer profile, and hands sales a ready-to-action packet for the strong matches.

When to use it

Run this when your dev tool grows through its GitHub repo and stars are a real top-of-funnel signal. It turns vanity star counts into named accounts your team can actually reach out to, without anyone manually checking profiles.

How it works

  1. 1A new star on the watched repo fires the trigger.
  2. 2Fetch the stargazer's GitHub profile, public org, and bio.
  3. 3Run an Exa search on their name plus company to find role, employer, and recent context.
  4. 4Score against ICP rules (company size, industry, seniority). Low-fit accounts stop here.
  5. 5Upsert the qualified person and company into Attio with the enrichment attached.
  6. 6Post a packet to the sales Slack channel with the score, links, and a suggested opening line.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect ExaNeural search across the web.
  3. 3
    Connect AttioReal-time CRM with structured data + powerful views.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.