Start with one job that already matters
A useful first-customer hypothesis for employee onboarding is that a new employee arrives before equipment, access, and introductory tasks are ready. Start by speaking with a people operations lead coordinating a new employee's start. The people doing the work are new hires, managers, IT staff, and onboarding coordinators; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often a checklist copied into messages for each department. 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 keep discovering on day one that nobody requested the laptop or system access. How do we coordinate onboarding owners?” 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 hiring expands across teams or locations. That is a hypothesis to confirm, not evidence inferred from the person's job title alone.
| Check | What matters for this category |
|---|---|
| User | new hires, managers, IT staff, and onboarding coordinators |
| Budget or decision owner | a people operations lead coordinating a new employee's start |
| Poor fit | teams requiring payroll or employment-compliance services from a checklist product |
| Implementation question | sensitive employee records and account provisioning require appropriate permissions |
Offer one bounded pilot
A concrete starting offer is to run a fictional hire through a role-specific readiness checklist. 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: every prerequisite for the first day has a named owner and completion evidence. 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 tasks depend on a confirmed start date, manager, or location?
- Check feasibility next: Who can confirm each item is actually ready rather than merely requested?
- 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: sensitive employee records and account provisioning require appropriate permissions. 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 .