Chapter 3
Validate demand before building the whole ladder
Part of How to Build an Offer Ladder.
Finish this chapter with a evidence interview and build sequence you can use immediately to validate demand before building the whole ladder, while avoiding creating price tiers that do not represent real customer progress.
What you’ll get
- A completed evidence interview and build sequence, not a list of abstract ideas.
- One explicit decision rule for validate demand before building the whole ladder.
- A 45-minute execution sequence you can repeat yourself or hand to a teammate.
- A quality gate that tells you whether to move forward, run one small test, or revise the input.
Use this chapter as a working session
Open the document, spreadsheet, or Tapmy workspace where this decision will live. Replace sample language with the exact offer, buyer, channel, price, and evidence you have today. If a fact is missing, label it as an assumption and assign the smallest test that can resolve it.
| Time | Work | Concrete output |
|---|---|---|
| 0–10 min | Collect buyer words, traffic data, sales conversations, support questions, and current page copy. | A short evidence list with source and date. |
| 10–20 min | Make the single decision this chapter is designed to resolve. | A one-sentence decision and reason. |
| 20–35 min | Build the evidence interview and build sequence with real names, numbers, links, and owners. | A usable operating asset. |
| 35–45 min | Review it from the buyer’s point of view and run the quality gate. | A keep, test, or revise decision. |
Look for evidence in customer language
Review:
- questions before purchase;
- support requests after purchase;
- repeated custom-work requests;
- reasons people do not buy;
- steps customers complete next;
- products commonly bought together;
- calls or messages in which people ask for more help.
Turn evidence into a hypothesis: “Customers who complete X then need Y.” Test the smallest version of Y before developing a large program.
Build one step ahead
If you have no paid product, build the first useful paid outcome. If it sells and customers succeed, build the next logical step. A diagram of a future ladder is useful; a warehouse of unvalidated products is not.
Use a pre-build interview
Ask current or intended customers:
- What are you trying to complete?
- What have you tried?
- Where are you stuck?
- What would useful support look like?
- What would make the result worth paying for?
Do not ask only “Would you buy this?” Explore past actions and current constraints.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The evidence interview and build sequence is ready to use. | Put it into the Tapmy journey and measure the next observable behavior. |
| One important input is assumed | The direction is testable, not yet proven. | Run the smallest test that can confirm or reject that assumption. |
| The asset serves several audiences, offers, or goals | The scope is too broad. | Narrow to one buyer, one job, one offer, and one reporting window. |
| The result depends on a claim you cannot show or deliver | Trust and delivery risk are higher than the upside. | Rewrite the promise around a supportable outcome. |
Quality standard
- The evidence interview and build sequence names one buyer and one job.
- Every number has a timeframe, currency, or denominator where needed.
- Every link and handoff has an owner.
- The next action is visible without rereading the chapter.
- The decision can be measured through customer behavior.
- No claim is stronger than the evidence.
