Qualify the job before the account
A promising ai writing tools lead needs more than a company in the right sector. Confirm the job: draft generation is quick but checking factual claims and brand fit takes too long. Identify writers adapting approved source material to a specific brief as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is an editorial or marketing lead accountable for publishable copy.
Ask about the current workaround, generic prompts followed by manual document review, 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 statements in the last draft required the editor to find supporting evidence? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you prepare one short draft from an approved brief with a claim-to-source review? | buyers requiring fabricated expertise, copied material, or automatic publication without editorial judgment |
| Timing | the team produces recurring content from a growing set of approved materials | The proposed change has no confirmed date or relevance. |
| Implementation | What must be approved before a draft can be published? | generated wording can be fluent while unsupported; source review remains part of the task |
| Value | an editor accepts or corrects each material claim before approving the draft | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We can generate drafts, but editors spend ages checking whether the claims came from the supplied brief. What keeps the source visible?” 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 to generate thousands of indistinguishable articles automatically. 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 requiring fabricated expertise, copied material, or automatic publication without editorial judgment. 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: generated wording can be fluent while unsupported; source review remains part of the task. Evaluate the pilot through a real observation that an editor accepts or corrects each material claim before approving the draft, 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 .