Chapter 4
Turn a conversation into the right invitation
fit-to-invitation decision tree is the practical output of this chapter. Complete it in one focused work session so you can decide when to recommend the product, offer a free resource, ask another question, or stop, without forcing an offer into a conversation that has not earned it.
What you’ll get
- A completed fit-to-invitation decision tree you can use in the next chapter.
- A documented decision about when to recommend the product, offer a free resource, ask another question, or stop.
- A pass or fail signal: every invitation follows explicit evidence of problem, relevance, and timing.
- A concrete first action: Summarize what you heard, connect one product outcome to it, and give the person an easy yes/no choice.
Listen for fit and timing
Ask how they handle the job today, what breaks, what they have tried, and what a useful result would look like. Do not interrogate them through a rigid questionnaire. Reflect their wording back and check that you understood.
When the fit is clear, make the offer specific:
Send people to one product page, not a menu of unrelated links. Review How to Write a Product Page That Makes the Value Clear before outreach.
Apply this chapter to your store
Start with the evidence you already have: the current Tapmy setup, the exact customer path, the messages people see, and the records created after an action. Do not redesign the entire system while you are still trying to locate the constraint.
Implementation move: Summarize what you heard, connect one product outcome to it, and give the person an easy yes/no choice.
Write the decision beside the evidence that supports it. If a teammate cannot reproduce the conclusion from the same evidence, the work is not yet operational. The deliverable should be specific enough to hand to another person without a meeting.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Evidence | The current state is visible and reproducible | Capture the real route, screen, record, or message before changing it |
| Decision | when to recommend the product, offer a free resource, ask another question, or stop is written in one sentence | Reduce the scope until one owner can choose |
| Execution | Summarize what you heard, connect one product outcome to it, and give the person an easy yes/no choice. | Assign a time and owner, then complete the smallest end-to-end version |
| Verification | every invitation follows explicit evidence of problem, relevance, and timing | Return to the failed boundary and retest only after the cause is changed |
Common failure mode
Interpreting politeness or curiosity as purchase intent. This hides the actual constraint and creates false confidence. Use the chapter output as a gate: do not move forward until the decision is explicit and the pass signal is visible.
20-minute implementation sprint
- Open the current Tapmy path and capture the starting state.
- Complete the smallest version of the fit-to-invitation decision tree.
- Record the decision, owner, and next review date.
- Test the pass signal once from the customer’s point of view.
- Save the evidence where the person running the next chapter can find it.
