Week 3
~4 min readOutcome-Based Selling in Practice
Knowing the framework is one thing. Using it under pressure is another. This week, you will rewrite your go-to questions, practice outcome-focused conversations, and start building a playbook you can use on every call.
This Lesson
Question Rewrite Formula
Every question you ask can be rewritten to uncover the desired outcome instead of confirming the symptom. The formula has three steps: (1) Identify the product feature you are trying to sell. (2) Find the business activity that feature improves. (3) Ask about the activity's current state, frequency, cost, or impact, and never mention the feature. Here is the rule: if your question contains a product name, a technical spec, or vendor jargon, rewrite it. Every time. Example: instead of "Would you like to see our AI analytics dashboard?" ask "When something breaks in production, how long does it take your team to find the root cause today?" The first question is about your product. The second question is about their reality. That is the difference between a pitch and a diagnosis.
Three Use Case Domains
AI use cases tend to cluster around three domains, and knowing them helps you pattern-match faster during conversations. Observability: "When something breaks in production, how long does it take to find root cause?" Automation: "How much time does your team spend each week pulling, formatting, and distributing reports?" Compute: "When your data science team submits a training job, how long are they waiting?" Notice the pattern. The BEFORE question is about your product. The AFTER question is about their world. A simple test: could the customer answer your question without knowing what you sell? If yes, it is a good question. If no, rewrite it. These three domains cover the majority of AI use cases you will encounter. Learn them, and you will never be stuck for a diagnostic opening question again.
Role-Play Practice
Reading about outcome-based selling is easy. Doing it under pressure is hard. That is why practice matters. In the worksheet, you will run through role-play scenarios where you practice rewriting product-led questions into diagnostic questions in real time. The goal is not perfection. The goal is to build the muscle memory so that when you are on a live call and your instinct says "pitch the feature," your training says "ask about the outcome." Most reps need 10 to 15 reps before the new pattern feels natural. Start with low-stakes conversations and work your way up. By the end of this week, you should be able to catch yourself mid-sentence and redirect.
Use Case Selling Playbook
Your Use Case Selling Playbook is a living document. It has four sections: (1) Your top three domains and the diagnostic questions for each. (2) A signal-to-category map that connects common customer phrases to Revenue, Efficiency, or Risk categories. (3) Personalized objection responses written in your own words. (4) A 30-day action plan with specific accounts and dates. This is not a template you fill out once and forget. It is a tool you refine after every customer conversation. The best reps in this program update their playbook weekly. By Week 4, yours should feel like a competitive advantage that no one else on your team has.
Before vs. After Questions
See the difference in action. BEFORE: "Would you like a demo of our monitoring platform?" AFTER: "When an outage hits production at 2am, what does your escalation process look like today?" BEFORE: "Our solution automates report generation." AFTER: "How many hours does your team spend each week manually compiling data from different systems?" BEFORE: "We integrate with your existing data lake." AFTER: "When your data science team needs to run a new model, how long does it take to get the data they need?" In every case, the BEFORE question is about your product. The AFTER question is about their pain. The AFTER question opens a conversation. The BEFORE question closes one.
The 60-Second Audit
You do not need to wait until after a call to evaluate your questions. Use the 60-Second Audit in real time. After you ask a question, silently check three things: (1) Did I mention my product or any feature by name? If yes, rewrite. (2) Could the customer answer this question without knowing what I sell? If no, rewrite. (3) Does this question uncover scope, frequency, or cost? If no, go deeper. This takes practice. At first, you will catch yourself after the fact. Then you will catch yourself mid-sentence. Eventually, diagnostic questions become your default. The 60-Second Audit is the bridge between knowing the framework and living it.
Key Takeaways
If your question contains a product name or technical spec, rewrite it. Every time.
The test: could the customer answer your question without knowing what you sell? If not, it is a product question, not a diagnostic question.
The 60-Second Audit helps you catch and correct product-led questions in real time, not just in hindsight.
Your Use Case Selling Playbook is a living document. Update it after every customer conversation.
Most reps need 10 to 15 practice reps before diagnostic questions feel natural. Start with low-stakes conversations.
Meet your AI Coach
Ask anything about this week's content—outcome-based discovery, the Bridge Framework, and more.