Market research for startups: test the risk before the next commitment
Use recent customer episodes to identify the startup assumption that matters next, then choose a prototype, access task or deliverable pilot.
If you are building appointment reminders for small repair businesses, your next risk may be whether a shop can connect them to its existing workflow. A total-addressable-market number will not settle that. The illustrative startup plan below takes you from recent customer episodes to a product or access decision, then a bounded pilot.
Separate the five assumptions before building
The appointment startup’s decision diary
Milestone | Artifact and decision |
|---|---|
Days 1–2 · alternatives and incidents | Artifact brought to the meeting: Assumption map and existing reminder process Decision it can change: Which risk to investigate |
Days 3–4 · recent-episode interviews | Artifact brought to the meeting: Workaround, process owner and adoption conditions Decision it can change: Prototype, access work or target change |
Day 5 · founder decision | Artifact brought to the meeting: Supported / contradicted / unresolved assumptions Decision it can change: One bounded next commitment |
Use this as an adaptable first-week plan, not a promised turnaround for a commercial study.
Assumption | Evidence and next commitment |
|---|---|
Missed appointments are a meaningful problem | Evidence to seek and what would challenge it: Inspect recent missed-appointment episodes and records; existing reminders may already solve it. Next commitment: Continue problem discovery |
The owner can change the process | Evidence to seek and what would challenge it: Interview buying roles and workflow owners; a franchise or software vendor may control it. Next commitment: Define a reachable buyer |
A reminder fits the workflow | Evidence to seek and what would challenge it: Observe a prototype task; staff may need duplicate data entry. Next commitment: Build a limited integration |
Buyers will pay for the benefit | Evidence to seek and what would challenge it: Compare a defined offer and price tradeoffs, then an actual pilot offer; the problem may cost less than the service. Next commitment: Commit to delivery |
The service can deliver the promise | Evidence to seek and what would challenge it: Run a technical and operational pilot; data access or operations may fail. Next commitment: Consider a wider launch |
Separate founder preferences from evidence. “We prefer owner-led shops” is a targeting choice; it does not establish that those shops experience the problem.
The assumptions do not have equal timing. A buyer problem that is already solved can stop the idea now. A data-access dependency can block delivery even when the problem matters. A willingness-to-pay question is premature if the team cannot specify what it can provide. Pick the assumption most able to invalidate the next commitment.
Use discovery to learn what the shop already does
- Tell me about the most recent missed appointment in your business.
- How did you discover it, and what happened next?
- What do you currently do to prevent it?
- Who chooses and maintains that process?
- What have you tried that did not work?
- What would need to change before you adopted another process?
- Who else would need to approve the change?
Recruit beyond friends and early enthusiasts. Include people who use alternatives and people who do not consider the problem important. A contrary case may save more effort than another favorable quotation.
Ask about the most recent missed appointment before pitching reminders. The consequence, workaround and process owner tell you whether a problem is real enough to investigate. Include shops whose current system works, not just friendly founders and early enthusiasts.
“That sounds useful” describes a pitch reaction. A recent incident with manual staff effort explains the task the product could change. Conditional interest in calendar connection identifies an adoption dependency. Keep those outputs separate instead of counting every favorable sentence as validation.
Buffer: attention, pricing interest and payment are different signals
Buffer began as a way to queue social posts without scheduling each one individually. In founder Joel Gascoigne’s February 2011 account, the team moved through three different kinds of evidence:
Observed step | What it could support |
|---|---|
People left their email after seeing the proposed product. | Some reachable visitors wanted to hear more. The product had not yet been used or bought. |
Some visitors selected a paid plan on an added pricing page. | The named offer and price deserved further investigation. A pricing-page click was still not a payment. |
A customer paid after the working product launched. | At least one person completed a real purchase. Gascoigne reports the first payment within four days of launch. |
This is a historical founder account with no controlled comparison or representative conversion estimate. It makes the next commitment easier to see: early reactions supported building a limited product; an actual transaction supplied a different kind of evidence after delivery became possible.
For the reminder startup, favorable interviews can justify a prototype. The next test must then expose the calendar connection, staff tasks and deliverable offer that the shop would actually adopt. Keep those requirements attached when moving from an interesting idea to a pilot.
A first week with a real choice at the end
Days 1–2: inspect incident records, existing reminder options and the assumptions in the map. Days 3–4: interview accessible owner-led shops with different processes, including shops whose current reminders work. Ask about the last missed appointment and who can change the workflow.
Day 5: decide whether to prototype a workflow, resolve an integration dependency or stop pursuing this audience. In the worked plan, the next candidate is one workflow for owner-led shops using manual reminders; the wider launch waits for usable integration and actual pilot participation. This is an adaptable plan, not a promised research turnaround.
For a DTC commuter bottle, apply the same logic to recent leak episodes, a complete lid/volume/delivered-price offer and physical leakage and bag-fit tests. Use our qualitative market research guide and our market research guide to connect the episode to the next commitment.
At the decision meeting, put each assumption into supported enough for the next commitment, contradicted or unresolved. A usable manual-reminder workflow can justify a prototype. Unavailable required integration calls for an access investigation or deferral. A problem solved by current tools calls for stopping or a different target hypothesis.
If access fails, report that access problem and the unresolved question. A thin set of agreeable conversations should not be renamed complete discovery.
Offer a deliverable pilot rather than another hypothetical question
Define the workflow, eligible shop, tasks the shop must complete, terms and support the team can actually provide. Then observe whether a participant takes the necessary steps and uses the service. Payment belongs in the pilot where the offer and authorization make it appropriate; stated willingness is a different measure.
A calendar condition cannot disappear from the offer because the prospect liked the reminder idea. Resolve who controls it and whether the proposed integration is feasible. If staff must enter appointments twice, observe that task before assuming the product saves time.
Keep stopping useful. If the reachable shops do not have a worthwhile unsolved problem, do not buy more concept preference to revive it. If delivery is the block, preserve the problem evidence and the condition that would reopen the idea.
The founder’s next brief
For the scheduling service, the team might decide to prototype one workflow for owner-led shops whose current process requires manual reminders. The gate is usable integration and a deliverable pilot, not a slide claiming a huge market.
Synthetic research can explore possible objections and compare propositions when suitable grounding exists. It does not create actual customer discovery, technical validation or purchase behavior.
Use a research plan, B2B role map and our concept testing guide. The SBA planning resources offer official market-research starting points. Discuss a managed synthetic study with Sapien around the specific assumption your next commitment depends on.
The output is one prototype or access task with an owner, not a report claiming a broad market. Bring the assumption map and complete offer to any partner so the commissioned comparison addresses the commitment the founder can still change.
