Qualify the job before the account
A promising customer success software lead needs more than a company in the right sector. Confirm the job: renewal risks are noticed only after a customer stops responding. Identify success teams reviewing account needs before renewal as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a customer success manager accountable for renewals and adoption.
Ask about the current workaround, account spreadsheets and individual calendar reminders, 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 observed customer action would make you intervene before renewal? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you review five approaching renewals using explicit adoption evidence and a next action? | teams without accessible usage or customer interaction evidence for the proposed workflow |
| Timing | renewals grow beyond the number one account manager can track manually | The proposed change has no confirmed date or relevance. |
| Implementation | Can the team explain and act on each proposed health indicator? | unexplained health scores can hide data gaps and create false confidence |
| Value | an account owner records and addresses a verified adoption blocker before the review date | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We missed that a customer's rollout stalled until their renewal call. How do small CS teams track adoption blockers?” 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 advertises a customer success role without mentioning its customer lifecycle. 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 without accessible usage or customer interaction evidence for the proposed workflow. 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: unexplained health scores can hide data gaps and create false confidence. Evaluate the pilot through a real observation that an account owner records and addresses a verified adoption blocker before the review date, 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 .