Qualify the job before the account
A promising event management software lead needs more than a company in the right sector. Confirm the job: registration changes do not reach the check-in and session lists. Identify registration staff and session coordinators as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is an event organizer accountable for attendee operations.
Ask about the current workaround, a registration form exported into several spreadsheets, 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 attendee changes must appear at the door immediately? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you rehearse one session with test registrations, a transfer, and a walk-in? | organizers seeking an audience marketplace when the product only manages known registrants |
| Timing | an event adds multiple ticket types or concurrent sessions | The proposed change has no confirmed date or relevance. |
| Implementation | How will check-in work if the venue connection fails? | ticketing, payment, and offline check-in support must match the actual event |
| Value | a changed registration appears correctly in the session's check-in view | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “People change workshops after registering, but the door volunteers still have the original lists. How can we keep them aligned?” 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 attendee asks what time a conference begins. 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 organizers seeking an audience marketplace when the product only manages known registrants. 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: ticketing, payment, and offline check-in support must match the actual event. Evaluate the pilot through a real observation that a changed registration appears correctly in the session's check-in view, 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 .