Write a falsifiable acquisition hypothesis
For document management, test whether staff collaborating on controlled business documents experience a costly enough problem when teams cannot tell which document version is approved for use to consider a bounded change. The decision owner hypothesis is the operations owner responsible for document access, and a possible trigger is that an external partner needs access to a controlled document set.
The current alternative, folders with dated filenames and approval emails, 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 move one non-sensitive specification through a draft-to-approved workflow. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "document version control" "supplier" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | Who can draft, approve, distribute, and retire this document? | The actual workflow and cost of the current workaround. |
| Check feasibility | What would prove a recipient used the current approved version? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether a recipient opens the approved version while a prior version is clearly retired. | 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: retention, access controls, and export requirements need checking before importing sensitive files.
- Stop pursuing a poor-fit account when it belongs to buyers demanding a certification or records-retention capability the product cannot substantiate.
- 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 recipient opens the approved version while a prior version is clearly retired.
- 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 “Our supplier used an old specification from email. We need one approved version with a record of who changed it.” to practice the distinction between evidence and inference before reviewing real records. By contrast, A request for more cheap storage with no approval or versioning problem. 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 .