Write the hypothesis in plain language
Example: 'A small group of local businesses may pay for a clearly scoped website inventory setup if I can show a relevant sample and current price.' This states a possibility to test; it does not assume demand or success.
Define exposure and stop conditions first
Set the maximum time, direct cost, number of people contacted, work promised, and any other exposure before the test. Stop if the activity becomes unsafe, unlawful, misleading, too costly, or outside your authority.
Use a real offer or action only when ready
A pilot can be useful, but label it accurately. If the offer is unpaid, say unpaid. If it is discounted, say why. If it is a demo, do not call it a client case. If payment is involved, make scope, terms, price, refund/cancellation and delivery responsibility clear enough for the context.
Record both positive and negative outcomes
Replies, rejection, silence, paid acceptance, scope objections, delivery difficulty, repeat requests, refund, rework, and actual cost are all evidence. Do not keep only the data that makes the experiment look successful.
No universal revenue threshold
The historical Level 01 source contains many numerical decision rules. DEPTH-02 does not treat a fixed conversion, payback, revenue-per-hour, outreach volume, or experiment count as universal. Use current context, actual costs, risk, and evidence.
Reflection
Questions to sit with
- What exactly am I trying to learn from this test?
- What is the most I am willing to risk?
- What result would make me stop or change direction?