Qualify the job before the account
A promising email marketing software lead needs more than a company in the right sector. Confirm the job: every subscriber receives the same message despite different product needs. Identify marketers segmenting opted-in audiences as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a lifecycle marketer accountable for relevant subscriber communication.
Ask about the current workaround, one mailing list and manual campaign exclusions, 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 verified customer event should change the next email? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you preview a single lifecycle sequence on permitted test contacts with two different stages? | buyers seeking unsolicited bulk sends or unsupported data imports |
| Timing | the product adds a second customer segment or onboarding path | The proposed change has no confirmed date or relevance. |
| Implementation | How are permission, unsubscribes, and suppression handled in the current system? | deliverability and permission handling require proof beyond an attractive editor |
| Value | the correct test segment receives its expected preview while an excluded contact remains suppressed | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Our trial users and paying customers get the same onboarding sequence. I need segmentation based on their actual stage.” 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 a database of email addresses to blast. 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 seeking unsolicited bulk sends or unsupported data imports. 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: deliverability and permission handling require proof beyond an attractive editor. Evaluate the pilot through a real observation that the correct test segment receives its expected preview while an excluded contact remains suppressed, 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 .