Start with one job that already matters
A useful first-customer hypothesis for education software is that teachers see an incorrect answer but lack a clear record of the misconception behind it. Start by speaking with an educator or program lead evaluating a specific teaching workflow. The people doing the work are teachers reviewing practice and planning the next lesson; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often marked worksheets and personal notes about each learner. 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: “Students repeat the same error after feedback. I need to track which misconception was addressed and whether a fresh question was solved independently.” 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 educator is reviewing recurring mistakes across a new practice cohort. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | teachers reviewing practice and planning the next lesson |
| Budget or decision owner | an educator or program lead evaluating a specific teaching workflow |
| Poor fit | buyers seeking guaranteed grades or collection of student records outside an authorized process |
| Implementation question | learning claims need actual evidence; student privacy and institutional permissions must be resolved |
Offer one bounded pilot
A concrete starting offer is to rehearse an educator-owned feedback cycle with fictional learner work before an authorized classroom evaluation. 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: the educator can connect a diagnosed misconception to a separate independent practice check. 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: What fresh task would distinguish understanding from remembering the previous answer?
- Check feasibility next: What learner information is necessary, and who is authorized to access it?
- 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: learning claims need actual evidence; student privacy and institutional permissions must be resolved. 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 .