Write a falsifiable acquisition hypothesis
For procurement software, test whether department staff requesting purchases and managers approving them experience a costly enough problem when purchase requests arrive without a clear budget owner or approval record to consider a bounded change. The decision owner hypothesis is a procurement manager responsible for purchasing controls, and a possible trigger is that new departments are gaining purchasing authority.
The current alternative, email threads and an approval spreadsheet, 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 route one purchase category through named budget owners and approval thresholds. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "purchase requests" "approval" "spreadsheet" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | Which amount, category, or department changes the required approver? | The actual workflow and cost of the current workaround. |
| Check feasibility | Where does an approved request become an actual purchase order? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether an approved request produces a complete handoff record for purchasing. | 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: approval software must fit the accounting and purchasing systems already in use.
- Stop pursuing a poor-fit account when it belongs to teams expecting supplier discovery or financing from an approval-only workflow.
- 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: an approved request produces a complete handoff record for purchasing.
- 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 “We cannot tell which laptop requests are approved before the invoice arrives. Looking for a request-to-approval workflow.” to practice the distinction between evidence and inference before reviewing real records. By contrast, A vendor lists procurement as a target audience on its homepage. 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 .