Key points
- Define the technical problem and account conditions before selecting roles.
- Segment engineering buyers from CTOs and VPs to managers, staff engineers, and advocates
- Choose lead data fields and outbound workflows that fit technical evaluation habits
A developer-tooling prospect list should identify teams with a relevant technical problem and the people who evaluate or own that work. Start with the product use case, then investigate account conditions and role responsibility.
A CTO title, an API product or a public GitHub profile is not enough by itself. Keep technical fit, buyer role and available contact data as separate review questions.
Define the engineering problem the account must have
Describe the workflow your tool improves: API observability, developer onboarding, database migration, deployment, internal tooling or another specific task. Identify the conditions necessary for the product to be useful.
- Which architecture, workload or development process matters?
- Does the offer serve a product team, platform team or another function?
- Which implementation or adoption constraints must be checked?
- Which account characteristics are essential and which are optional?
- What evidence would show the account is unsuitable?
Company size and industry can help define a research cohort. They do not prove engineering-team size, production traffic, a particular stack or readiness to replace a tool.
Map the evaluation roles without assuming a fixed committee
| Role group | Possible contribution | Question to investigate |
|---|---|---|
| CTO or VP Engineering | Organisation-level technical direction or adoption ownership | Does this person own the relevant decision or delegate it? |
| Engineering Manager | Team workflow, implementation effort and operating needs | Which team and process fall within the remit? |
| Staff Engineer or Architect | Technical evaluation, design and compatibility evidence | Does the person influence the affected system? |
| Developer Experience or platform leadership | Internal tooling adoption and engineering workflows | Is the need internal, customer-facing or both? |
| Developer Relations or advocacy | Developer-facing education, ecosystem or community work | Is this an evaluator, an influencer or a different audience? |
Include several people only when their roles in the task are understood. An individual contributor can be a relevant evaluator; a senior title does not automatically establish budget or product need.
The DevTools infrastructure guide develops the platform-team angle. The decision-maker responsibility guide provides the broader role context.
Use public technical evidence within its limits
Company engineering articles, documentation, repositories, talks and job descriptions can help explain a technical problem. Keep the exact observation, source and date rather than turning it into a generic intent score.
- A company article can describe a past implementation rather than today's full production stack.
- A job description can name a desired skill without proving a current deployment.
- A repository contribution can show relevant public work without establishing purchase authority.
- A repository star or documentation reference does not prove a live evaluation.
- Missing public activity does not establish that an engineer is inactive or unsuitable.
GitHub's private-contribution visibility documentation explains that control. Use role and account evidence alongside public artifacts.
Build a bounded search and research loop
- Write the technical fit. Define the workflow, necessary conditions and disqualifiers.
- Choose account criteria. Use relevant activity, location and scale context.
- Select role variants. Preserve full titles and team or product qualifiers.
- Investigate coverage. Free count previews show matching contact records, not unique engineering organisations or confirmed evaluators.
- Retrieve a manageable set. Inspect actual companies, responsibilities and required fields.
- Confirm material technical conditions. Retain source evidence and unresolved cases.
- Approve the next action. Apply identity, ownership and campaign requirements.
Use SaaS account discovery when software vendors are the target, or contact search for the more specific account brief. The SaaS list-building playbook covers that account boundary.
Dievio supports stored account and role filters, including employee size, revenue and funding dates. It does not provide native installed-stack, GitHub activity, documentation-engagement, funding-stage or intent filters.
Make the outreach artifact technically useful
Offer something relevant to the researched task: an implementation explanation, compatibility notes, a reproducible example or an actual test with its environment and limitations. Do not invent benchmark results or claim to have inspected systems you have not observed.
Match the detail to the role. An evaluator may need implementation evidence while an accountable leader needs operating scope and adoption implications. Confirm those needs rather than stereotyping them from the title.
Community participation should contribute useful work in its own right. A shared forum or repository does not automatically create a relationship or permission for a campaign.
Keep contact retrieval and review explicit
An available email or phone is not a fresh validation or a guarantee of current employment. Confirm identity, role fit, relevant evidence, preferences and the intended channel before activation.
Known LinkedIn profile URLs can support the documented lookup operation. Do not treat GitHub handles, company domains and LinkedIn URLs as interchangeable person-enrichment inputs.
For repeated work, the API documentation describes supported source operations. Your application owns scheduling, research joins, CRM writes and exception handling; retrieval does not create a native GitHub enrichment or live-role monitoring service.
Measure correct accounts, relevant responsibilities, material research gaps and qualified technical conversations. Avoid invented reply-rate promises, fixed freshness windows or a universal short-sequence advantage for technical buyers.



