Qualify the job before the account
A promising customer support software lead needs more than a company in the right sector. Confirm the job: customer requests lose an owner when a conversation crosses shifts. Identify agents sharing an inbox across shifts as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is the support lead who owns response quality and staffing.
Ask about the current workaround, a shared mailbox plus a spreadsheet of unresolved tickets, 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 | Walk me through the last ticket that changed owners: where did context get lost? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you route one low-risk support queue through an explicit owner and handoff checklist? | teams seeking outsourced support staff when the product only supplies software |
| Timing | a second support shift is being introduced | The proposed change has no confirmed date or relevance. |
| Implementation | Who would approve testing one queue, and what customer data could it contain? | importing historic messages and enforcing agent permissions may be prerequisites |
| Value | a second agent resolves a handed-off request with its original context intact | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We are adding evening coverage and need a way to hand off unresolved emails without two agents replying.” 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 company posts a customer-service job without describing its workflow. 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 seeking outsourced support staff when the product only supplies software. 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: importing historic messages and enforcing agent permissions may be prerequisites. Evaluate the pilot through a real observation that a second agent resolves a handed-off request with its original context intact, 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 .