Start with one job that already matters
A useful first-customer hypothesis for scheduling software is that appointments are negotiated across messages and collide with unavailable time. Start by speaking with a service owner managing appointment capacity. The people doing the work are coordinators and practitioners confirming bookings; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often a shared calendar plus direct messages. 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: “We now have two therapists using the same room and keep confirming overlapping sessions. What handles both staff and room availability?” 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 a second practitioner or location is joining the schedule. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | coordinators and practitioners confirming bookings |
| Budget or decision owner | a service owner managing appointment capacity |
| Poor fit | organizations requiring clinical records management from an appointment-only product |
| Implementation question | timezone rules and resource constraints can matter more than a polished booking page |
Offer one bounded pilot
A concrete starting offer is to configure one service with its staff, room, and turnaround constraints. 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 test booking reserves every required resource and blocks a conflicting slot. 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: Does a valid booking require a person, a room, equipment, or all three?
- Check feasibility next: How are cancellations and buffer times handled today?
- 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: timezone rules and resource constraints can matter more than a polished booking page. 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 .