Qualify the job before the account
A promising recruiting software lead needs more than a company in the right sector. Confirm the job: interview feedback arrives too late to give candidates a clear next step. Identify recruiters and interviewers sharing candidate progress as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a recruiting lead coordinating a defined hiring pipeline.
Ask about the current workaround, an applicant spreadsheet with feedback in email, 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 candidate wait because a handoff was unclear? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you rehearse one fictional candidate through a role-specific interview and feedback flow? | buyers expecting automated employment decisions or access to candidate data without authorization |
| Timing | several hiring managers open roles concurrently | The proposed change has no confirmed date or relevance. |
| Implementation | Who should see candidate information and who only needs interview tasks? | candidate privacy, permissions, and existing applicant-system imports need checking |
| Value | a hiring owner receives the required feedback and records a next step | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Candidates wait a week because interview feedback is scattered across emails. We need owners and reminders for each stage.” 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 job advertisement alone treated as evidence the employer wants a new recruiting system. 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 buyers expecting automated employment decisions or access to candidate data without authorization. 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: candidate privacy, permissions, and existing applicant-system imports need checking. Evaluate the pilot through a real observation that a hiring owner receives the required feedback and records a next step, 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 .