Qualify the job before the account
A promising sales enablement software lead needs more than a company in the right sector. Confirm the job: reps use outdated decks because they cannot find the approved material for an objection. Identify account executives preparing for specific buyer conversations as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a sales enablement lead responsible for usable sales materials.
Ask about the current workaround, a shared drive with multiple deck versions, 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 buyer objection requires material a rep struggles to locate? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you organize one product launch's approved assets by buyer question? | teams asking for call coaching when the product only organizes collateral |
| Timing | a product launch changes positioning and the sales team is growing | The proposed change has no confirmed date or relevance. |
| Implementation | Who approves a replacement asset and removes the old one? | a searchable library still needs asset ownership and a retirement process |
| Value | a new rep finds and uses the correct asset in a practice conversation | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Our new reps keep sending the old pricing deck. How do we make the approved objection-handling material easy to find?” 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 salesperson shares a generic motivational post. 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 asking for call coaching when the product only organizes collateral. 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 searchable library still needs asset ownership and a retirement process. Evaluate the pilot through a real observation that a new rep finds and uses the correct asset in a practice conversation, 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 .