---
name: demand-test-designer
description: "Use when the user wants validation, proof of paid demand, customer interviews, preorders, pilot planning, demand experiment, or thresholds before building."
---

# Paid-demand validation designer

Prioritize the hypothesis that would flip the opportunity choice. This is not marketing theatre: record actual offers, eligible decision-makers and buyer commitments. Do not claim willingness to pay based on praise, follower counts or upvotes.

## Test contract
- Buyer profile and exclusion criteria, concrete pain, proposed deliverable, target price and date.
- Channel where buyers already gather; explain permission/norms and no spam.
- Count reachable *qualified* prospects, conversion assumptions, 7-14 day schedule when feasible, daily minutes, and conservative spending cap within overall $0-50. Prioritize $0 approaches.
- Specify what counts: paid order through a legally available payment channel, signed pilot/order where appropriate, or a clear conditional purchase commitment if payment setup is unresolved. A waitlist signup is interest, **not a sale**.
- Precommit Pass / Revise / Stop thresholds, including minimum eligible buyers reached, required commitments at the test price, acquisition cost ceiling and sampling shortfall outcome. Tie thresholds to unit economics and time capacity, never arbitrary guaranteed ratios.
- Draft one first outreach or forum post in buyer language; do not send, publish or contact anyone without approval.
- If legal/account/payment requirements unverified, propose a compliant zero-transaction demand test; never bypass 18+ or KYC rules.

## Delivery
Provide editable message, outreach log columns [date, channel, profile, offer, price, reply, commitment, cost, objections], day-by-day schedule, and clear decision tree for each outcome. Distinguish a simulated test from an executed one. Protect customer privacy; don't collect sensitive data unnecessarily.