Qualify the job before the account
A promising developer tools lead needs more than a company in the right sector. Confirm the job: local setup takes multiple undocumented steps before a new developer can run a test. Identify developers encountering friction during their daily build loop as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is an engineering lead protecting developer time.
Ask about the current workaround, a README supplemented by messages to the original author, and what would make changing it worthwhile. Do not assign a budget or procurement timeline from company size, funding, or job title alone.
Use a category-specific qualification rubric
Use the calculator below to organize your judgment after reading the source. Unknown evidence should remain unknown. Its weights are a transparent prioritization convention, not a prediction of purchase probability.
| Dimension | Evidence to seek | Reason to pause |
|---|---|---|
| Problem | Where did the last new contributor stop before their first passing test? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you run a documented setup path on a clean, supported development environment? | teams needing an unsupported language, operating system, or build environment |
| Timing | new engineers repeatedly hit the same setup failure | The proposed change has no confirmed date or relevance. |
| Implementation | Which operating systems and existing tools must the solution support? | a developer tool must work within existing security and build constraints |
| Value | a new contributor reaches a passing sample test without undocumented manual steps | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Every new contributor spends a day debugging environment setup. Has anyone made this reproducible without maintaining a giant setup document?” That supports investigating the problem, but it does not yet settle purchasing authority or technical compatibility. A reviewer should ask the two discovery questions above and preserve the answers beside the source.
Compare that with: A repository receives stars without anyone describing usage or a problem. This weaker example should not receive the same pain or timing score. A relevant public topic is not evidence of a current evaluation.
Even a strong problem signal should be rejected when the need belongs to teams needing an unsupported language, operating system, or build environment. Qualifying out prevents a misleading promise and preserves time for a prospect the product can help.
Create a reviewable handoff
A qualified opportunity should contain the original evidence, a summary of the job, confirmed and unknown constraints, the buyer/user distinction, and an agreed next step. Keep a score attached to those facts so another teammate can challenge the conclusion.
Propose a pilot only when the critical gap is addressed: a developer tool must work within existing security and build constraints. Evaluate the pilot through a real observation that a new contributor reaches a passing sample test without undocumented manual steps, and keep that observation separate from the initial qualification score.
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 .