Qualify the job before the account
A promising employee onboarding lead needs more than a company in the right sector. Confirm the job: a new employee arrives before equipment, access, and introductory tasks are ready. Identify new hires, managers, IT staff, and onboarding coordinators as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a people operations lead coordinating a new employee's start.
Ask about the current workaround, a checklist copied into messages for each department, 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 tasks depend on a confirmed start date, manager, or location? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you run a fictional hire through a role-specific readiness checklist? | teams requiring payroll or employment-compliance services from a checklist product |
| Timing | hiring expands across teams or locations | The proposed change has no confirmed date or relevance. |
| Implementation | Who can confirm each item is actually ready rather than merely requested? | sensitive employee records and account provisioning require appropriate permissions |
| Value | every prerequisite for the first day has a named owner and completion evidence | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “We keep discovering on day one that nobody requested the laptop or system access. How do we coordinate onboarding owners?” 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 general request for welcome-gift ideas. 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 requiring payroll or employment-compliance services from a checklist 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: sensitive employee records and account provisioning require appropriate permissions. Evaluate the pilot through a real observation that every prerequisite for the first day has a named owner and completion evidence, 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 .