Qualify the job before the account
A promising community platforms lead needs more than a company in the right sector. Confirm the job: useful member answers disappear in a fast-moving conversation stream. Identify members asking questions and organizers maintaining participation as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a community operator responsible for a clear member purpose.
Ask about the current workaround, a chat group and manually curated pinned messages, 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 | What repeatable member interaction makes this community worth returning to? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you organize one recurring member-help activity with searchable outcomes? | buyers expecting a platform to supply an audience or guarantee engagement |
| Timing | the community adds recurring programs or paid membership | The proposed change has no confirmed date or relevance. |
| Implementation | Who moderates, curates, and responds when participation causes a problem? | software cannot substitute for a clear member purpose and active moderation |
| Value | a member finds a prior useful answer or completes an intended introduction | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “New members ask questions that were answered last week, and useful introductions get buried. We need a better way to organize member help.” 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 large follower count assumed to mean a functioning community. 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 expecting a platform to supply an audience or guarantee engagement. 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: software cannot substitute for a clear member purpose and active moderation. Evaluate the pilot through a real observation that a member finds a prior useful answer or completes an intended introduction, 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 .