Qualify the job before the account
A promising document management lead needs more than a company in the right sector. Confirm the job: teams cannot tell which document version is approved for use. Identify staff collaborating on controlled business documents as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is the operations owner responsible for document access.
Ask about the current workaround, folders with dated filenames and approval emails, 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 | Who can draft, approve, distribute, and retire this document? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you move one non-sensitive specification through a draft-to-approved workflow? | buyers demanding a certification or records-retention capability the product cannot substantiate |
| Timing | an external partner needs access to a controlled document set | The proposed change has no confirmed date or relevance. |
| Implementation | What would prove a recipient used the current approved version? | retention, access controls, and export requirements need checking before importing sensitive files |
| Value | a recipient opens the approved version while a prior version is clearly retired | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Our supplier used an old specification from email. We need one approved version with a record of who changed it.” 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 more cheap storage with no approval or versioning 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 buyers demanding a certification or records-retention capability the product cannot substantiate. 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: retention, access controls, and export requirements need checking before importing sensitive files. Evaluate the pilot through a real observation that a recipient opens the approved version while a prior version is clearly retired, 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 .