Write a falsifiable acquisition hypothesis
For customer support software, test whether agents sharing an inbox across shifts experience a costly enough problem when customer requests lose an owner when a conversation crosses shifts to consider a bounded change. The decision owner hypothesis is the support lead who owns response quality and staffing, and a possible trigger is that a second support shift is being introduced.
The current alternative, a shared mailbox plus a spreadsheet of unresolved tickets, 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 low-risk support queue through an explicit owner and handoff checklist. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "shared inbox" "handoff" "recommend" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | Walk me through the last ticket that changed owners: where did context get lost? | The actual workflow and cost of the current workaround. |
| Check feasibility | Who would approve testing one queue, and what customer data could it contain? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether a second agent resolves a handed-off request with its original context intact. | 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: importing historic messages and enforcing agent permissions may be prerequisites.
- Stop pursuing a poor-fit account when it belongs to teams seeking outsourced support staff when the product only supplies software.
- 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 second agent resolves a handed-off request with its original context intact.
- 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 are adding evening coverage and need a way to hand off unresolved emails without two agents replying.” to practice the distinction between evidence and inference before reviewing real records. By contrast, A company posts a customer-service job without describing its workflow. 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 .