LEAD GENERATION

Competitor Repo Stargazer Poaching List

Monitors stargazers on a competitor's open-source repo, filters out people who already star yours, enriches the rest.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStar on competitor repoGitHubGitHub
  • LogicExclude users who star your repoGitHubGitHub
  • ActionFetch user profile + companyGitHubGitHub
  • ActionEnrich company firmographicsExa
  • LogicApply ICP filter + tag
  • OutputAdd poaching lead to AttioAttio

What it does

This workflow watches who stars a competitor's repository, removes anyone who already engages with your project, enriches the remaining users and their companies, and assembles a focused outbound list in Attio of prospects evaluating tools in your space.

When to use it

Reach for this when a competitor's repo is a high-signal pool of in-market developers and you want to reach them with a switch or comparison pitch. Works best in crowded dev-tool categories with overlapping audiences.

How it works

  1. 1A GitHub trigger fires when someone stars the configured competitor repo.
  2. 2An action checks whether that user already stars your own repo and filters them out if so.
  3. 3A second GitHub action fetches the remaining user's profile and company.
  4. 4An Exa action enriches the company with firmographics and recent signals.
  5. 5A logic step applies your ICP filter and assigns a competitive-displacement tag.
  6. 6Qualified prospects are written to Attio as a person with a Competitor Stargazer source label.

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
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.