Qualify the job before the account
A promising field service software lead needs more than a company in the right sector. Confirm the job: dispatchers cannot see job status until technicians return or call. Identify dispatchers and technicians working at customer locations as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a service operations manager allocating field jobs.
Ask about the current workaround, phone calls, a dispatch board, and paper job sheets, 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 updates must a technician make while connectivity is unavailable? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you follow one crew's job from dispatch through offline notes to completion? | buyers requiring live vehicle tracking when the product has no verified tracking integration |
| Timing | the service territory has expanded or a second crew has joined | The proposed change has no confirmed date or relevance. |
| Implementation | What information is needed before a completed job can be invoiced? | offline behavior, device support, and technician effort are central adoption constraints |
| Value | a completed field job syncs with its timestamp and required evidence | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Customers call for arrival updates but we only have yesterday's paper schedule. What works for technicians with patchy reception?” 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 technician advertises availability for contract work. 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 requiring live vehicle tracking when the product has no verified tracking integration. 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: offline behavior, device support, and technician effort are central adoption constraints. Evaluate the pilot through a real observation that a completed field job syncs with its timestamp and required 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 .