02.09 Consumer Rejection Reasons and Purchase Trigger Moments
Governance metadata | Owner: Marketing Lead | Last reviewed: 2026-10-22 | Next review: 2027-01-31
Core principle: having a pain point does not mean they will buy, and buying does not mean they will repurchase. Most hardware projects die at the wall between "demand validation passed" and "the user actually pays", and that wall is called the rejection reason. This chapter turns "why they do not buy" and "when do they finally think of you" into two maps that can be interviewed, classified, and designed, and connects pre-sale selling points with post-sale returns. Upstream demand validation is in 02.01; downstream selling-point design is in 04.01; return attribution is in 06.02.
1. Why This Map Is Needed: There Is Another Wall Between Pain Point and Order
02.01 Demand Insight answers "is there a real pain point" — using a three-dimension pain-intensity scale and the Mom Test to filter out pseudo-demand.
But projects that pass validation still fail, because three different things are being conflated:
| Concept | The question it answers | Where we stand |
|---|---|---|
| Need | Does he have this problem? | Covered by 02.01 |
| Willingness | Is he willing to pay to solve it? | 🔴 Blank |
| Trigger | When will he think of buying? | 🔴 Blank |
And 06.00 has already pointed out that the main cause of hardware returns is usually not a defect but an expectation gap. Where does the expectation gap come from? From pre-sale promises of things users do not actually need, or are not willing to pay that price for.
Conclusion: if pre-sale does not know the rejection reasons, post-sale will definitely collect the returns. The two must be connected through one single taxonomy.
2. The Five Categories of Rejection Reason
Every single "he did not buy" falls into one of the five categories below. Mis-classifying it leads to exactly the wrong action.
| # | Category | What the user says | The real cause | Verifiable signal | Correct action |
|---|---|---|---|---|---|
| 1 | Price | "Too expensive" / "Let me think about it" | Perceived value < price, rather than a literal lack of money | Repeatedly cites a competitor's price during comparison | Add value evidence, do not discount |
| 2 | Trust | "I have never heard of this brand" / "Let me read the reviews first" | No third-party endorsement or risk backstop | Keeps revisiting the reviews / return-and-exchange policy page | Reviews / certification / trial use / refund guarantee |
| 3 | Compatibility | "I already have one at home" / "It does not go with mine" | An existing substitute or an incompatible ecosystem | Ask "what are you using to solve this now" | Compatibility list / migration plan |
| 4 | Timing | "Maybe next time" / "I'll wait for a discount" | The need is not urgent, or the budget cycle has not arrived | Ask "under what circumstances would you buy right now" | Wake up the trigger scenario, do not chase the order |
| 5 | Substitute | "XX can do that too" | He has not perceived our differentiation | Ask "what is XX missing versus what you want" | Re-rank the selling points, see 04.01 |
Discipline: among the five categories, only category 1 has price as its real cause. Treating categories 2~5 as price problems (i.e., discounting right away) is the most common suicidal response — it burns gross margin and still leaves the real obstacle in place.
Rejection Reason Matrix (Template)
The numeric columns are interview statistics; they must be filled in from actual measurement and must not be pre-filled.
| Category | Mentions | Share | Typical verbatim quote | Segment involved | Current response | Effectiveness |
|---|---|---|---|---|---|---|
| Price | ||||||
| Trust | ||||||
| Compatibility | ||||||
| Timing | ||||||
| Substitute | ||||||
| Total | 100% |
3. Purchase Trigger Moments: When Does He Finally Think of You
A user is not in a buying state at all times. Advertising without a trigger is shouting at people who do not need you.
| Trigger type | Definition | Hardware example | Corresponding content |
|---|---|---|---|
| Problem occurs | The old solution breaks or no longer suffices | Old device fails, not enough capacity, moving house | Failure-scenario content, trade-in |
| Planned purchase | Deliberate search with a clear time point | Renovation, back to school, before the ski season, camping season | Keyword positioning, comparison pages |
| External stimulus | Lit up by third-party content | Reviews, a friend's recommendation, stumbled on it on social media | KOL/PR, see 04.03 |
| Promotional moment | Acts only when a discount appears | Black Friday, Prime Day, the mid-year mega sale | Mega-sale SOP, see 05.05 |
| Season / cycle | Tied to climate, holidays, and lifecycle | Winter battery anxiety, summer outdoors | Seasonal content calendar |
Trigger-Moment Map (Template)
| Trigger type | The specific moment | What he is searching at that moment | Are we present? | Gap action |
|---|---|---|---|---|
| Problem occurs | ||||
| Planned purchase | ||||
| External stimulus | ||||
| Promotional moment | ||||
| Season / cycle |
How to use it: this table directly determines the keyword structure of 04.05 Off-Site Paid Media and the content calendar of 04.02 Social Media. Running paid traffic without a trigger-moment map is handing your budget to the platform algorithm to guess at.
4. Interview Method: Never Ask "Would You Buy It?"
"Would you buy it?" gets you politeness, not data. The Mom Test in 02.01 already gives the overall principle; here we add the dedicated script for rejection interviews.
Four Iron Rules
- Ask about the past, not the future: "When was the last time you ran into this problem?" rather than "If there were one, would you buy it?"
- Ask about behavior, not attitude: "How much money/time did you spend on this?" rather than "Do you think this feature is important?"
- Ask about substitutes, not preferences: "How do you solve it now?" — the existing solution is your real competitor.
- Ask about the rejection, not about satisfaction: "Why did you end up not buying?" — buyers cannot answer this question.
Rejection Interview Script (Ready to Use)
| Order | Question | What you want to get |
|---|---|---|
| 1 | When was the most recent time you ran into this problem? What did you do at the time? | Trigger moment + existing substitute |
| 2 | How much money/time did that resolution take? | True willingness-to-pay anchor |
| 3 | Which products did you look at? Which one did you pick in the end, or why did you not pick one? | Rejection reason classification |
| 4 | If you had to solve it right now, how would you do it? | Urgency |
| 5 | Under what circumstances would you feel you "must buy it"? | Trigger conditions |
Sample discipline: rejection interviews must include non-buyers. Interviewing only buyers is textbook survivorship bias — their reasons cannot explain the other 90% of people.
5. Closing the Loop with 06: Return Reason = Delayed Manifestation of the Rejection Reason
This is the most important mechanism in this chapter. A return is not a post-sale problem; it is a pre-sale promise that failed to be delivered.
Pre-sale: the five rejection reason categories
↓ selling-point design must map one by one
04 Marketing: every selling point binds to one specific rejection reason
↓ the user places the order with an expectation
06 Post-sale: return reasons are classified back into the same five categories
↓
Feedback: which rejection reason category has the largest "promise-delivery" gap
↓
Back to 02/04 to correct the selling points or the productClosed-loop rules:
| Rule | Description |
|---|---|
| One taxonomy | Pre-sale rejection reasons and post-sale return reasons must use the same five categories, otherwise they cannot be reconciled |
| One selling point, one reason | Every core selling point in 04.01 must state which category of rejection reason it offsets; a selling point you cannot map is just self-indulgence |
| Gap first | A category with a high share of rejection reasons and also a high return rate → we are over-promising in that category |
| VOC feedback loop | The VOC in 06.02 is tagged with the five categories, and the monthly dashboard shows how the distribution changes |
6. Deliverables
| Deliverable | Purpose | Delivered to |
|---|---|---|
| Rejection Reason Matrix | Share across the five categories + verbatim quotes + response effectiveness | 02 product definition, 04 selling-point design |
| Trigger-Moment Map | The five trigger types + search terms + presence status | 04.05 paid media, 04.02 content calendar |
| Rejection Interview Notes | Verbatim quotes (no summarizing) | Distilled into a VOC asset |
| Selling-Point-to-Reason Mapping Table | The rejection reason each selling point addresses | 04.01 brand positioning, 02.05 Battlecard |
7. Common Mistakes
| Mistake | Consequence | Correction |
|---|---|---|
| Attributing every non-purchase to "too expensive" | Discounts try to solve trust and compatibility problems and give away gross margin for nothing | Attribute each one against the five categories |
| Interviewing only buyers | Survivorship bias; the real obstacles stay invisible | Non-buyers must be included |
| Asking "would you buy it" | You get politeness instead of data | Ask about past behavior |
| Guessing the trigger-moment map | Paid media never reaches the people who have the need | Derive it backward from search terms and scenarios |
| Two separate taxonomies for pre-sale and post-sale | Nothing can be reconciled and the problem repeats | Unify the five categories |
| A selling point that maps to no reason | Self-indulgent marketing | One selling point, one reason; if you cannot map it, cut it |
Execution Checklist
[ ] The five categories are defined and agreed by everyone: price / trust / compatibility / timing / substitute
[ ] The rejection interview sample includes non-buyers: not only buyers
[ ] The interview script is rewritten per the four iron rules: ask about the past, behavior, substitutes, and the rejection
[ ] The rejection reason matrix is filled in: quotes recorded verbatim, not summarized
[ ] The trigger-moment map is built: the five trigger types + search terms + presence judgment
[ ] The selling-point-to-reason mapping is complete: each selling point states which rejection category it offsets
[ ] Unified with the 06.02 VOC classification: the same five categories
[ ] The gap is identified: which category has both a high share of rejection reasons and a high return rate (over-promising)
[ ] Deliverables handed over: matrix / trigger-moment map / notes / mapping table
Related Documents
- 02.01 Demand Insight: TAM_SAM_SOM Market Sizing and Must-Have Validation
- 02.05 Competitor Battlecard One-Pager Standard Template and Attack/Defense Cards
- 04.01 Brand Positioning: Brand House Pyramid Construction and CES_IFA Trade Show Marketing
- 04.02 Social Media Seeding: Xiaohongshu KFS Model and WeChat Owned-Channel Closed-Loop SOP
- 04.05 Off-Site Paid Media and Search Growth SOP
- 06.02 After-Sales Reputation: Tiered Complaint Handling, NPS Tracking, and the VOC Loop
- 06.00 Customer Service Overview