Qualify the job before the account
A promising subscription management lead needs more than a company in the right sector. Confirm the job: a plan change leaves support unsure what was billed and what access should be available. Identify billing support staff investigating subscription changes as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a finance operations or subscription product lead.
Ask about the current workaround, manual comparison of payment records and an account spreadsheet, 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 provider record is authoritative for a paid invoice and subscription state? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you reconcile a provider test subscription through one supported plan change? | businesses whose billing provider or regional requirements are unsupported |
| Timing | the business introduces upgrades, prorations, or multiple subscription tiers | The proposed change has no confirmed date or relevance. |
| Implementation | How are failed payments, upgrades, and access changes reconciled today? | money amounts and entitlements must reconcile to the payment provider; a dashboard alone is insufficient |
| Value | support can explain a test invoice and its corresponding access state from verified records | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Customers ask what happened after an upgrade, and support has to reconstruct it from three systems. We need a clear subscription timeline.” 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 consumer asks to cancel a personal streaming subscription. 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 businesses whose billing provider or regional requirements are unsupported. 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: money amounts and entitlements must reconcile to the payment provider; a dashboard alone is insufficient. Evaluate the pilot through a real observation that support can explain a test invoice and its corresponding access state from verified records, 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 .