Write a falsifiable acquisition hypothesis
For recruiting software, test whether recruiters and interviewers sharing candidate progress experience a costly enough problem when interview feedback arrives too late to give candidates a clear next step to consider a bounded change. The decision owner hypothesis is a recruiting lead coordinating a defined hiring pipeline, and a possible trigger is that several hiring managers open roles concurrently.
The current alternative, an applicant spreadsheet with feedback in email, 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 rehearse one fictional candidate through a role-specific interview and feedback flow. | Inputs, access, owner, time boundary, and stop conditions. |
| Research | Use "interview feedback" "scattered" and inspect the original source. | Source, date, observed problem, and unresolved questions. |
| Discover | Where did the last candidate wait because a handoff was unclear? | The actual workflow and cost of the current workaround. |
| Check feasibility | Who should see candidate information and who only needs interview tasks? | Confirmed requirements and unsupported needs. |
| Evaluate | Check whether a hiring owner receives the required feedback and records a next step. | 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: candidate privacy, permissions, and existing applicant-system imports need checking.
- Stop pursuing a poor-fit account when it belongs to buyers expecting automated employment decisions or access to candidate data without authorization.
- 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 hiring owner receives the required feedback and records a next step.
- 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 “Candidates wait a week because interview feedback is scattered across emails. We need owners and reminders for each stage.” to practice the distinction between evidence and inference before reviewing real records. By contrast, A job advertisement alone treated as evidence the employer wants a new recruiting system. 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 .