Write a falsifiable acquisition hypothesis
For knowledge base software, test whether new hires searching for reliable internal procedures experience a costly enough problem when answers live in old chat threads and new staff repeat the same questions to consider a bounded change. The decision owner hypothesis is an enablement or operations lead responsible for repeat questions, and a possible trigger is that several new hires are onboarding in the same month.
The current alternative, pinned messages and a loosely organized shared document, is the comparison point. Your experiment should discover whether the proposed workflow earns adoption despite switching effort. It should not treat a compliment about the product as proof of demand.
Run a bounded experiment
An example planning window is one week, but the buyer's availability and implementation needs determine the actual timing. Agree on a manageable number of conversations with the team running the test. That number is a planning choice, not an expected conversion rate.
| Stage | Action | Record |
|---|---|---|
| Prepare | Define the scope needed to publish five frequently requested procedures with owners and review dates. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "internal knowledge base" "outdated" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | Which repeated question interrupts an experienced colleague most often? | The actual workflow and cost of the current workaround. |
| Check feasibility | Who owns the answer and knows when it becomes stale? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether a new teammate completes one procedure using the article without asking its author. | A verifiable event, a blocked attempt, or an explicit refusal. |
Set decision rules before reviewing results
A refusal, failed pilot, or invalid hypothesis can be a useful result. Preserve it. Do not replace inconvenient outcomes with a different success definition after the experiment finishes.
- Continue the pilot only when its critical dependency is resolved: search quality cannot compensate for missing owners or outdated source material.
- Stop pursuing a poor-fit account when it belongs to teams expecting automatic expertise from a product that only organizes their existing knowledge.
- If the problem is not recognized in specific examples, revise the audience hypothesis.
- If the problem is recognized but implementation blocks the pilot, revise scope or capability assumptions.
- If the pilot runs, verify the value event: a new teammate completes one procedure using the article without asking its author.
- If value occurs but the buyer will not continue, investigate the recurring need and the proposed commercial terms.
Keep a learning record another person can review
Use the illustrative signal “Every new teammate asks how to issue a refund, and our pinned answer is already outdated. How do we keep procedures owned?” to practice the distinction between evidence and inference before reviewing real records. By contrast, A team requests a wiki without naming anything people need to find. cannot establish the same buying intent.
Record what you planned, what actually happened, the source for each observation, and the decision you made. Keep invitations separate from replies and paid outcomes separate from expressed interest. DemandBolt's project and research workflows can hold the context while you decide the next experiment; the software does not guarantee that an experiment succeeds.
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 .