Write a falsifiable acquisition hypothesis
For invoicing software, test whether administrative staff preparing invoices and following up experience a costly enough problem when the owner cannot tell which invoice is awaiting approval, payment, or correction to consider a bounded change. The decision owner hypothesis is a small business owner responsible for collecting approved invoices, and a possible trigger is that the business takes on recurring clients with different billing terms.
The current alternative, document templates and a payment-status 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 trace a fictional invoice through issue, query, correction, and reconciled test payment. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "invoice tracking" "payment status" "spreadsheet" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | What event changes an invoice from drafted to sent, disputed, or paid? | The actual workflow and cost of the current workaround. |
| Check feasibility | Which source proves payment, and who reconciles partial payments? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether an authorized user can identify the correct next action from verified invoice status. | 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: tax fields, payment methods, and regional invoice requirements must match the supported product.
- Stop pursuing a poor-fit account when it belongs to businesses requiring jurisdiction-specific capabilities that have not been verified.
- 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 authorized user can identify the correct next action from verified invoice status.
- 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 “I lose track of whether an invoice was sent, queried, or paid. I need a clear status before following up with clients.” to practice the distinction between evidence and inference before reviewing real records. By contrast, A search for a free invoice image with no billing workflow need. 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 .