Start with one job that already matters
A useful first-customer hypothesis for field service software is that dispatchers cannot see job status until technicians return or call. Start by speaking with a service operations manager allocating field jobs. The people doing the work are dispatchers and technicians working at customer locations; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often phone calls, a dispatch board, and paper job sheets. Treat that as a competitor with real advantages: it is familiar, already available, and does not require a migration. Your first conversation should uncover a specific reason the buyer would accept the effort of changing it.
Recognize a plausible early adopter
The following is an original illustrative scenario, not a quotation from a prospect: “Customers call for arrival updates but we only have yesterday's paper schedule. What works for technicians with patchy reception?” It is useful because it describes a workflow and a need. Verify the author's role, date, context, and whether the problem remains unresolved before treating it as an opportunity.
A possible reason to act is that the service territory has expanded or a second crew has joined. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | dispatchers and technicians working at customer locations |
| Budget or decision owner | a service operations manager allocating field jobs |
| Poor fit | buyers requiring live vehicle tracking when the product has no verified tracking integration |
| Implementation question | offline behavior, device support, and technician effort are central adoption constraints |
Offer one bounded pilot
A concrete starting offer is to follow one crew's job from dispatch through offline notes to completion. State the required inputs, who will participate, what access is needed, and how the pilot can be stopped. Agree on the boundary before asking for customer data or a production integration.
Define the first proof of value as this observable event: a completed field job syncs with its timestamp and required evidence. A positive reply, a demo attendance, and a completed pilot are different observations; record them separately.
- Write the buyer hypothesis and the current workaround in one project brief.
- Use this discovery question before presenting a solution: Which updates must a technician make while connectivity is unavailable?
- Check feasibility next: What information is needed before a completed job can be invoiced?
- Ask whether the person wants to explore the bounded pilot. Record their answer, including a refusal, without converting it into a sale.
Decide what to learn from the first attempt
The strongest reason to pause is an unresolved implementation issue: offline behavior, device support, and technician effort are central adoption constraints. Change the scope or qualify out the prospect when that gap prevents the pilot from delivering value.
If buyers recognize the problem but decline the pilot, investigate the offer and switching effort. If they do not recognize the problem, revisit the audience. If they complete the pilot but do not continue, inspect the value delivered and the next recurring job. Avoid expanding outreach until the evidence tells you which assumption changed.
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 .