Start with one job that already matters
A useful first-customer hypothesis for course platforms is that the educator can deliver videos but cannot see whether learners complete the promised practice. Start by speaking with an independent educator selling a defined learning outcome. The people doing the work are adult learners completing lessons and assignments; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often video links, email submissions, and a completion spreadsheet. 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: “I ran the first cohort over calls and email. Before repeating it, I need a clear place for assignments and completion feedback.” 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 live pilot course is moving into a repeatable cohort. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | adult learners completing lessons and assignments |
| Budget or decision owner | an independent educator selling a defined learning outcome |
| Poor fit | buyers needing unsupported accreditation, guaranteed income, or unmanaged collection of children's data |
| Implementation question | hosting lessons and demonstrating learning are different capabilities |
Offer one bounded pilot
A concrete starting offer is to run one lesson and practice submission with a consenting adult test learner. 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 learner submits the intended work and receives actionable feedback. 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 learner submission shows progress toward the advertised outcome?
- Check feasibility next: What feedback must the educator provide before a learner can continue?
- 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: hosting lessons and demonstrating learning are different capabilities. 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 .