Qualify the job before the account
A promising project management software lead needs more than a company in the right sector. Confirm the job: handoffs are agreed in chat but never appear in the delivery schedule. Identify project leads coordinating work across specialists as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a delivery manager accountable for client deadlines.
Ask about the current workaround, a project spreadsheet alongside several team chat channels, 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 | Which missed handoff changed a delivery date last month? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you model dependencies and owners for one upcoming client milestone? | buyers requiring portfolio accounting when only task coordination is available |
| Timing | the team is running several client projects at once | The proposed change has no confirmed date or relevance. |
| Implementation | Would all participating teams update a shared dependency record? | a new tracker fails if teams still maintain their authoritative schedule elsewhere |
| Value | a downstream owner acknowledges a dependency before its deadline | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Our designers finish on time, but engineering does not see the handoff until the deadline slips. How do other agencies track dependencies?” 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 founder asks for a nicer to-do list for personal errands. 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 requiring portfolio accounting when only task coordination is available. 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 new tracker fails if teams still maintain their authoritative schedule elsewhere. Evaluate the pilot through a real observation that a downstream owner acknowledges a dependency before its deadline, 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 .