Private pilot
GitHub developer lead research
Research a repository’s public audience and assess fit for your product. Review verified profiles, relevant projects and public contact evidence where available.
Bring the context
Start with the right evidence.
A target repository, or your product and ideal customer so your agent can suggest repositories. Confirm the repository and budget before audience research. Review the first 20 leads before continuing a larger job.
A request to try
“Research developers around our repository. Explain each match using public projects and verified profile links.”
The repository-audience route uses the private GitHub audience pipeline. Confirm the repository and cumulative provider budget first. A star is interest, not buying intent. The separate five-prospect discovery pilot does not replace this workflow.
Before you begin
What do I need to get started?
A target repository, or your product and ideal customer so your agent can suggest repositories. Confirm the repository and budget before audience research. Review the first 20 leads before continuing a larger job.
What result will I receive?
A searchable, enriched lead table, public contact evidence, relevant projects, CSV export and coverage notes.
How does pricing work?
Review the task scope, available balance and maximum cost in your agent before execution. Installing a connection does not start a task.