Chapter 4
Run a six-step willingness-to-pay study
Turn run a six-step willingness-to-pay study into one evidence-backed research decision in 45–60 minutes, with a concrete output and a clear next action—without sending traffic into a journey you cannot diagnose.
What you’ll get
- Primary decision: Step 1: Recruit people with relevant behavior.
- Working asset: Step 2: Run problem-first conversations.
- Quality check: Step 3: Collect and code exact language.
Before you begin
Bring the current offer hypothesis, the exact decision this research must change, and any existing evidence. Set a 45–60 minutes timer. Separate what you observed from what you inferred; record contradictions instead of averaging them away.
| Decision | Evidence you used | What could change it | Next action |
|---|---|---|---|
| Run a six-step willingness-to-pay study | Past behavior, workaround cost, commitment, or paid behavior | Stronger contrary evidence from a relevant participant | Complete the chapter and assign the next test |
Conversion checkpoint
Research improves conversion when it makes the offer more specific, more credible, or easier to act on. If a finding cannot change the audience, promise, price, proof, or CTA, it may be interesting but is not decision-critical.
Step 1: Recruit people with relevant behavior
Recruit based on the situation, not a vague demographic label. “Creators” is broad. “Creators who attempted to sell a digital download in the last six months” describes relevant behavior.
Recruit from:
- Replies and DMs connected to the problem
- Existing customers with the relevant use case
- Email subscribers who clicked related content
- Communities where participation and research requests are allowed
- Referrals from people who match the behavior
Aim for variety in experience and current alternative. Do not claim a universal sample size. Continue until you can distinguish repeated patterns from isolated comments and new conversations stop changing the decision materially.
Step 2: Run problem-first conversations
Use a consistent discussion outline:
- Context: role, goal, and recent situation
- Trigger: what made the problem matter then
- Process: what they did in sequence
- Cost: time, money, and consequences
- Alternatives: tools, people, content, postponement
- Decision criteria: why one option felt acceptable
- Desired outcome: what “done” would look like
Do not introduce your offer until the problem story is complete. When you do show it, ask for interpretation first: “What do you think this helps you do?” That tests clarity before desirability.
Step 3: Collect and code exact language
Create a simple evidence table. One row per observation or quote:
| Evidence ID | Segment | Situation/trigger | Exact language | Current action | Cost or consequence | Source |
|---|---|---|---|---|---|---|
| E01 | Freelance editor, 1–3 yrs | New lead asks for proposal | “I rewrite the same scope from old PDFs” | Copies prior proposals | Time + inconsistent scope | Interview 01 |
| E02 | Freelance editor, 3+ yrs | Lead goes quiet | “I never know when follow-up feels pushy” | Sets manual reminders | Lost momentum | Interview 02 |
Code what happened, not what you hoped to hear. Keep contradictory evidence. If experienced editors love the idea and newer editors do not understand it, you may have discovered the first segment—not noise to delete.
Step 4: Map alternatives and buying criteria
For each participant, capture:
- What they use now
- What they like about it
- What they tolerate
- What triggers a switch
- What would make a new option feel risky
- Who or what influences the decision
Your competitor is not always another digital product. It may be a saved Google Doc, a free video, a coworker, a manual workaround, or postponing the task.
Step 5: Build one concrete offer test
Turn the strongest pattern into a minimum offer page. Use this formula:
Show the product at a realistic level of fidelity. If the format is a template, show sample fields. If it is a guide, show the table of contents and a sample page. If it is a paid session, show the agenda and deliverable.
Create the test page in Tapmy so the journey resembles the eventual purchase path. Use How to Add a Digital Product to Tapmy and How to Write a Product Page That Makes the Value Clear.
Step 6: Ask for a proportionate commitment
Match the action to product readiness:
- Concept stage: qualified waitlist with a use-case question
- Defined scope: early-access request or scheduled sales conversation
- Buildable with a clear date: transparent preorder or refundable deposit
- Ready product: completed purchase
After the action, ask one short follow-up: “What nearly stopped you?” This often reveals the strongest conversion risk.
Finish line
- The research decision is written in one sentence.
- Observations and interpretations are stored separately.
- Contradictory evidence remains visible.
- The next test has a stopping rule.
Build it in Tapmy
Turn the strongest observed language into a focused offer in Tapmy, use one proportionate CTA, and record behavior rather than collecting another abstract opinion.
