Chapter 6
Learn from every result
first-customer evidence log is the practical output of this chapter. Complete it in one focused work session so you can decide which rejection, objection, silence, and purchase reasons should change the offer or outreach, without repeating the same pitch while calling low response a volume problem.
What you’ll get
- A completed first-customer evidence log ready for the next chapter.
- A documented decision about which rejection, objection, silence, and purchase reasons should change the offer or outreach.
- A pass or fail signal: after every 10 conversations you can name the dominant bottleneck and one test for the next batch.
- A first implementation move: Tag each outcome by reason—wrong problem, weak timing, unclear value, price, trust, or route—not only by status.
Tag the reason, not only the status
Use outcome tags such as:
- Problem not important
- Timing not now
- Outcome unclear
- Format mismatch
- Price concern
- Trust/proof missing
- Purchased
- Referred someone else
After ten substantive conversations, compare the words prospects used with the copy on your product page. Change one high-impact element—audience, promise, preview, proof, or price explanation—then run the next ten conversations. Do not change everything after each opinion.
Apply this chapter to your store
Start with the live customer path, not a hypothetical version. Open the relevant content, profile, Tapmy page, email, or operational record and capture what a buyer sees now. Keep the scope to one campaign and one decision so the result can be measured.
Implementation move: Tag each outcome by reason—wrong problem, weak timing, unclear value, price, trust, or route—not only by status.
Connect the decision to evidence: customer language, transition counts, questions, observed behavior, or a completed end-to-end test. If another person cannot understand why you chose the action, add the missing evidence rather than more strategy language.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Scope | One buyer, one campaign, and one next action are named | Narrow the work before creating more assets |
| Evidence | The current state is visible in a live route or record | Capture the source, destination, and decision point |
| Decision | which rejection, objection, silence, and purchase reasons should change the offer or outreach is written clearly | Remove competing goals and choose one priority |
| Verification | after every 10 conversations you can name the dominant bottleneck and one test for the next batch | Rework the weakest boundary, then retest it |
Common failure mode
Recording ‘not interested’ without the context needed to improve targeting or messaging. It creates activity without reliable learning. Use the chapter deliverable as a gate: the work is complete only when the decision is written, applied to the live path, and verified with the stated signal.
20-minute implementation sprint
- Open the live route or record and capture the starting state.
- Complete the smallest useful version of the first-customer evidence log.
- Apply the decision to one campaign or Tapmy path.
- Test the pass signal from the buyer’s point of view.
- Save the evidence and the next review date.
