Scenario: AE with a deal accumulating price objections
Trigger: AE says "We keep getting price objections on this deal. The customer is very price-sensitive. How do I handle it?"
Process:
(Step 1) Read call-notes-2025-03-12.md. Extract 4 objections: "That's very expensive for what it does," "I'm not sure we can justify this cost," "Is there a cheaper version?", "The budget is tight β this is hard to sell internally."
(Step 2) Examine seller statements immediately preceding each. Find: seller opened with a 5-minute product overview listing 8 product Features (processing speed, storage capacity, integration count, API options, support tier, uptime SLA, security certifications, deployment options). No Problem Questions asked in the first 15 minutes. Classify: Feature-heavy opening β price concerns.
(Step 3) Pattern: All 4 objections are price concerns. Dominant behavior: Feature overuse before any need development. The customer's price sensitivity was amplified by the Feature dump, which primed them to ask "is this worth the cost?" before having any sense of what the cost of NOT solving their problem would be.
(Step 4) Prevention plan: Remove the product overview from the first 15 minutes. Replace with 3-4 Problem Questions about the customer's current workflow and where they're losing time or quality. Add Implication Questions for each confirmed problem. Before any product mention, elicit at least one Explicit Need.
(Step 5) Write objection-prevention-plan-acme-corp.md.Output: Prevention plan showing that price sensitivity is seller-amplified (Feature dump), not inherent customer resistance. Recommendation: invoke spin-discovery-question-planner to build a question bank before the next call.
Scenario: Sales manager reviewing a rep's call with repeated "not worth it" objections
Trigger: Manager says: "Listen to this transcript β the prospect keeps saying it's not worth switching. What's going on?"
Process:
(Step 1) Extract 3 objections from transcript: "We're really quite happy with our current system," "I don't see enough value to justify a switch," "It'd be a lot of hassle for marginal improvement."
(Step 2) Find seller statements before each. All three are Advantages: "Our system would eliminate that manual reconciliation for you," "You'd get real-time visibility across all your accounts," "We integrate directly so there's no import step." Scan for prior customer-expressed Explicit Needs: buyer mentioned "our reconciliation takes longer than it should" (Implied Need β problem statement, not a want). No Explicit Need expressed before any Advantage was offered.
(Step 3) Pattern: All 3 objections are value doubts. Dominant behavior: Advantages offered before Explicit Needs developed. The rep heard an Implied Need and jumped to the solution. The customer hasn't internalized the cost of the problem, so the solution seems unnecessary.
(Step 4) Prevention: Rep should have used Implication Questions to develop the reconciliation problem ("What does that extra time cost you across 50 accounts per month?" "What happens when a reconciliation error reaches a client?") and then Need-payoff Questions to get the customer to express the want ("If reconciliation were automatic, what would you do with that time?"). Only after explicit want is expressed should the capability be presented.Output: objection-prevention-plan-prospect-review.md. Coaching for manager: the rep has the Advantage habit β trained to give "Benefits" but actually giving Advantages. Recommend fab-statement-classifier audit of rep's standard pitch and then spin-discovery-question-planner session for this account.
Scenario: Early-call objection pattern
Trigger: AE says "The prospect shut down the conversation almost immediately β I barely got through my intro before they were resistant."
Process:
(Step 1) Extract: "Look, I'm not sure I need to hear a whole pitch right now," "We're not really in the market for new tools this quarter," "Our budget is locked."
(Step 2) Seller statement before first objection: "We help companies like yours cut their invoice processing time by up to 40% with our workflow automation platform." This is an opening benefit statement β a premature Advantage in the first 2 minutes of the call.
(Step 3) Pattern: Early-call objections caused by premature solution presentation (opening benefit/Advantage statement).
(Step 4) Prevention: Do not mention the product, its capabilities, or any value claims in the first third of the call. Open by establishing the right to ask questions. Use Problem Questions first. The customer needs to feel invested in the problem before hearing about the solution.Output: Prevention plan showing this is a classic premature-solution pattern. Recommend discovery-call-opening-planner for the next call to redesign the opening.
