Qualify the job before the account
A promising scheduling software lead needs more than a company in the right sector. Confirm the job: appointments are negotiated across messages and collide with unavailable time. Identify coordinators and practitioners confirming bookings as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a service owner managing appointment capacity.
Ask about the current workaround, a shared calendar plus direct 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 | Does a valid booking require a person, a room, equipment, or all three? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you configure one service with its staff, room, and turnaround constraints? | organizations requiring clinical records management from an appointment-only product |
| Timing | a second practitioner or location is joining the schedule | The proposed change has no confirmed date or relevance. |
| Implementation | How are cancellations and buffer times handled today? | timezone rules and resource constraints can matter more than a polished booking page |
| Value | a test booking reserves every required resource and blocks a conflicting slot | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We now have two therapists using the same room and keep confirming overlapping sessions. What handles both staff and room availability?” 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: An individual wants a personal calendar color scheme. 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 organizations requiring clinical records management from an appointment-only product. 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: timezone rules and resource constraints can matter more than a polished booking page. Evaluate the pilot through a real observation that a test booking reserves every required resource and blocks a conflicting slot, 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 .