Define the question before collecting names
For scheduling software, investigate whether appointments are negotiated across messages and collide with unavailable time. Research is useful when it explains a workflow, its owner, and an unresolved constraint. A list of companies in a sector cannot establish that those companies have this problem.
Begin with coordinators and practitioners confirming bookings and check how their work relates to a service owner managing appointment capacity. Map the current process around a shared calendar plus direct messages. You are looking for the step where the workaround stops being adequate, rather than asking people to validate an abstract product idea.
Search for the language of the problem
Try the queries below in a search engine or the search feature of a relevant professional community. Read the original discussion and its date. Results are starting points for research; these query examples do not claim any particular search volume or the existence of a matching prospect.
| Query to adapt | What to extract |
|---|---|
| "booking software" "shared room" "recommend" | The failed task, current workaround, author role, and unresolved question. |
| "appointment scheduling" "double booking" | An evaluation request, required capability, and reason to change. |
| "scheduling software" "recommend" "alternative" | Specific constraints in recommendation requests; separate vendor promotions from user experience. |
Write an evidence note you can revisit
Illustrative source text: “We now have two therapists using the same room and keep confirming overlapping sessions. What handles both staff and room availability?” Save the actual source URL and date when researching a real example. Keep a short relevant excerpt and your interpretation in separate fields. Do not rewrite your interpretation as something the author said.
The working hypothesis is that a second practitioner or location is joining the schedule. The missing information includes whether the author is a service owner managing appointment capacity, whether the need is still open, and which implementation requirements remain unverified. Keep this constraint visible: timezone rules and resource constraints can matter more than a polished booking page.
- Observed: the original words, the visible date, the task described, and any explicit requirements.
- To verify: whether the current process is a shared calendar plus direct messages.
- Disqualify when the need belongs to organizations requiring clinical records management from an appointment-only product.
- Next step: one context-appropriate question, or no contact when there is no suitable route.
Use a short discovery interview
Ask about a recent event before showing your product. Let the person explain the sequence in their own words; do not treat agreement with a leading question as validation.
- Does a valid booking require a person, a room, equipment, or all three?
- How are cancellations and buffer times handled today?
- What would need to be true for you to configure one service with its staff, room, and turnaround constraints?
- How would you verify that a test booking reserves every required resource and blocks a conflicting slot?
Turn notes into a research decision
Compare independently sourced accounts of the same task. Keep an example that contradicts your hypothesis, such as this ambiguous scenario: An individual wants a personal calendar color scheme. It may justify more reading, but it is insufficient to label someone a buyer.
At the end of a bounded research session, decide whether to narrow the audience, ask a specific follow-up, change the pilot, or stop. Keep unknowns visible and store only the information needed for that decision. Research quality is measured by a better decision, not by how many names are collected.
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 .