Qualify the job before the account
A promising survey software lead needs more than a company in the right sector. Confirm the job: survey responses are collected without enough context to inform a product decision. Identify researchers recruiting respondents and interpreting answers as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a product researcher responsible for a specific customer decision.
Ask about the current workaround, a generic form distributed to an undifferentiated audience, 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 | What decision will change if the answers support one explanation over another? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you test a short survey with explicit screening and a decision-linked question? | projects demanding representative market estimates from a convenience sample |
| Timing | the team must choose which onboarding problem to investigate | The proposed change has no confirmed date or relevance. |
| Implementation | Which experience must a respondent have to answer this question meaningfully? | question design and sample selection remain necessary even with better survey software |
| Value | the researcher can trace a relevant response to the intended respondent segment | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We received plenty of survey answers but cannot separate new users from people who never tried the product. What should we change?” 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 request for paid respondents with no research question or selection criteria. 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 projects demanding representative market estimates from a convenience sample. 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: question design and sample selection remain necessary even with better survey software. Evaluate the pilot through a real observation that the researcher can trace a relevant response to the intended respondent segment, 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 .