Qualify the job before the account
A promising design collaboration lead needs more than a company in the right sector. Confirm the job: feedback refers to different versions and is difficult to turn into a clear revision. Identify designers and reviewers iterating on shared assets as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a design operations or creative team lead.
Ask about the current workaround, screenshots sent through email with notes in several threads, 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 | How does a reviewer know which version needs a decision? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you review one fictional asset through a revision with explicit comment resolution? | buyers seeking asset creation when the product only supports review and collaboration |
| Timing | external reviewers join a time-sensitive creative project | The proposed change has no confirmed date or relevance. |
| Implementation | What evidence shows a comment was resolved or intentionally declined? | file formats, external access, and version identity must fit the team's existing design tools |
| Value | the approver signs off on the same version the designer considers final | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “The client commented on last week's screenshot while our designer revised a newer version. How do we keep feedback attached to the right asset?” 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 free design work unrelated to collaboration tooling. 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 asset creation when the product only supports review and collaboration. 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: file formats, external access, and version identity must fit the team's existing design tools. Evaluate the pilot through a real observation that the approver signs off on the same version the designer considers final, 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 .