Qualify the job before the account
A promising knowledge base software lead needs more than a company in the right sector. Confirm the job: answers live in old chat threads and new staff repeat the same questions. Identify new hires searching for reliable internal procedures as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is an enablement or operations lead responsible for repeat questions.
Ask about the current workaround, pinned messages and a loosely organized shared document, 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 repeated question interrupts an experienced colleague most often? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you publish five frequently requested procedures with owners and review dates? | teams expecting automatic expertise from a product that only organizes their existing knowledge |
| Timing | several new hires are onboarding in the same month | The proposed change has no confirmed date or relevance. |
| Implementation | Who owns the answer and knows when it becomes stale? | search quality cannot compensate for missing owners or outdated source material |
| Value | a new teammate completes one procedure using the article without asking its author | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Every new teammate asks how to issue a refund, and our pinned answer is already outdated. How do we keep procedures owned?” 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 team requests a wiki without naming anything people need to find. 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 teams expecting automatic expertise from a product that only organizes their existing knowledge. 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: search quality cannot compensate for missing owners or outdated source material. Evaluate the pilot through a real observation that a new teammate completes one procedure using the article without asking its author, 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 .