Define the question before collecting names
For developer tools, investigate whether local setup takes multiple undocumented steps before a new developer can run a test. Research is useful when it explains a workflow, its owner, and an unresolved constraint. A list of companies in a sector cannot establish that those companies have this problem.
Begin with developers encountering friction during their daily build loop and check how their work relates to an engineering lead protecting developer time. Map the current process around a README supplemented by messages to the original author. You are looking for the step where the workaround stops being adequate, rather than asking people to validate an abstract product idea.
Search for the language of the problem
Try the queries below in a search engine or the search feature of a relevant professional community. Read the original discussion and its date. Results are starting points for research; these query examples do not claim any particular search volume or the existence of a matching prospect.
| Query to adapt | What to extract |
|---|---|
| "developer onboarding" "local setup" | The failed task, current workaround, author role, and unresolved question. |
| "development environment" "reproducible" "problem" | An evaluation request, required capability, and reason to change. |
| "developer tools" "recommend" "alternative" | Specific constraints in recommendation requests; separate vendor promotions from user experience. |
Write an evidence note you can revisit
Illustrative source text: “Every new contributor spends a day debugging environment setup. Has anyone made this reproducible without maintaining a giant setup document?” Save the actual source URL and date when researching a real example. Keep a short relevant excerpt and your interpretation in separate fields. Do not rewrite your interpretation as something the author said.
The working hypothesis is that new engineers repeatedly hit the same setup failure. The missing information includes whether the author is an engineering lead protecting developer time, whether the need is still open, and which implementation requirements remain unverified. Keep this constraint visible: a developer tool must work within existing security and build constraints.
- Observed: the original words, the visible date, the task described, and any explicit requirements.
- To verify: whether the current process is a README supplemented by messages to the original author.
- Disqualify when the need belongs to teams needing an unsupported language, operating system, or build environment.
- Next step: one context-appropriate question, or no contact when there is no suitable route.
Use a short discovery interview
Ask about a recent event before showing your product. Let the person explain the sequence in their own words; do not treat agreement with a leading question as validation.
- Where did the last new contributor stop before their first passing test?
- Which operating systems and existing tools must the solution support?
- What would need to be true for you to run a documented setup path on a clean, supported development environment?
- How would you verify that a new contributor reaches a passing sample test without undocumented manual steps?
Turn notes into a research decision
Compare independently sourced accounts of the same task. Keep an example that contradicts your hypothesis, such as this ambiguous scenario: A repository receives stars without anyone describing usage or a problem. It may justify more reading, but it is insufficient to label someone a buyer.
At the end of a bounded research session, decide whether to narrow the audience, ask a specific follow-up, change the pilot, or stop. Keep unknowns visible and store only the information needed for that decision. Research quality is measured by a better decision, not by how many names are collected.
About these playbooks and examples
Prepared by DemandBolt with AI assistance as practical planning resources for people building and selling software. The category scenarios and message examples are illustrative, not quotations from real prospects or claims of customer results. Adapt the hypotheses to your product, verify original sources, and review capabilities before making an offer.
The workflow follows our first-customer guide and buying-signal review method. Our PyInvesting and Rae records distinguish actual internal work from targets. Published .