Start with one job that already matters
A useful first-customer hypothesis for knowledge base software is that answers live in old chat threads and new staff repeat the same questions. Start by speaking with an enablement or operations lead responsible for repeat questions. The people doing the work are new hires searching for reliable internal procedures; the person feeling the friction and the person authorizing a purchase may be different.
The existing alternative is often pinned messages and a loosely organized shared document. 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: “Every new teammate asks how to issue a refund, and our pinned answer is already outdated. How do we keep procedures owned?” 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 several new hires are onboarding in the same month. 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 searching for reliable internal procedures |
| Budget or decision owner | an enablement or operations lead responsible for repeat questions |
| Poor fit | teams expecting automatic expertise from a product that only organizes their existing knowledge |
| Implementation question | search quality cannot compensate for missing owners or outdated source material |
Offer one bounded pilot
A concrete starting offer is to publish five frequently requested procedures with owners and review dates. 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: a new teammate completes one procedure using the article without asking its author. 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 repeated question interrupts an experienced colleague most often?
- Check feasibility next: Who owns the answer and knows when it becomes stale?
- 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: search quality cannot compensate for missing owners or outdated source material. 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 .