Sales Discovery: Open Questions, SPIN Selling and Active Listening

If you could keep only one sales skill, it should be this one. In discovery you learn the customer's situation, their problems, what those problems cost and what they want to achieve. With that information your presentation becomes tailor-made, objections shrink and price matters less, because the customer has seen the value for themselves. This lesson opens the Intermediate level.

1. Open questions
2. The SPIN method
3. Active listening
4. Quantify the problem
5. How the customer decides

The rule: ask more, talk less

In a good discovery meeting, the customer does most of the talking. Every minute you spend on your product before you understand their situation is a minute spent guessing what matters to them.

Closed questions confirm specific facts; open questions uncover. They start with what, how, which, tell me and why (use "why" carefully: it can sound like criticism).

The SPIN method

Developed by Neil Rackham from research on thousands of sales calls and published in SPIN Selling, the method sorts questions into four types:

The magic is in the implication and need-payoff questions: when customers explain in their own words what the problem costs and what they'd gain by solving it, they're convincing themselves, and that carries far more weight than any argument of yours.

A SPIN script to adapt (consumer sale)

SPIN isn't only for B2B. Here's how it sounds at Northstar Analytics Academy, an evening data analytics bootcamp in Austin, with someone who requested information online and agreed to a 15-minute call:

S: "Tell me, why are you looking at data analytics right now?"
   → "There's an analyst opening on my team, and I'm in operations."
P: "What's the hardest part when you work with data today?"
   → "I can do basic Excel, but I freeze on SQL and dashboards."
I: "What happens if the role is posted in three months and you're still
    not comfortable with SQL?" / "What's the pay difference for that role?"
   → "Someone else gets it. It pays about 25% more."
N: "If in 16 weeks you had a portfolio with three real projects you could
    walk through in the interview, what would that mean for you?"
   → "I'd apply with confidence."

Summary: "So the priority isn't a certificate; it's being able to show
SQL and dashboard skills in about three months. Is that right?"

Notice that the prospect, not the seller, put a value on the problem: a role that pays about 25% more. When Jordan hears the tuition later, that's what he'll compare it to.

Active listening

• Full attention: no glancing at your phone or planning your answer while they talk.
• Take notes in the customer's exact words: you'll use them in your proposal.
• Paraphrase: "If I understood correctly, the problem isn't creating invoices, it's matching them to payments at month-end. Is that right?"
• Dig deeper: "Can you give me an example?" "What else?" "How does that affect you personally?"
• Use silence: after an important question, wait. The most valuable answer often comes after an awkward pause.

How to turn vague answers into data

Customers often answer in generalities. If you accept them as they are, your proposal will be generic too. Dig deeper, calmly:

Put a number on the problem

A problem with a dollar figure is far more convincing. Calculate it with the customer, using their data. Back to Dana at Miller Hardware:

Monthly close: 4 days × 2 people × 8 hours = 64 hours a month
Loaded cost per hour of those people (pay, taxes, benefits): $40
Cost of the manual close: 64 × $40 = $2,560 a month = $30,720 a year

If the close drops to 1 day (16 hours): 48 hours saved
= $1,920 a month = $23,040 a year
(not counting avoided penalties or better decisions)

If LedgerPoint costs $600 a month, the customer no longer compares $600 to "nothing": they compare $600 to $1,920 in savings. This calculation is the foundation of your presentation (lesson 6) and your best answer to "It's too expensive" (lesson 7).

Understand how the customer decides

Beyond the need, find out:

• Who's involved and what each person cares about (lesson 2).
• The process: "How do you usually make decisions like this? What are the steps from choosing a vendor to signing?"
• The criteria: "What would a solution need to have for you to choose it?"
• Timeline and reason: "When do you need this solved? What happens if it isn't solved by then?"
• Budget: "Is there an investment range planned?" If not, the cost of the problem helps build one.
• Alternatives: "What other options are you considering?"

Close the discovery

1. Summarize what you understood, in the customer's words: situation, problems, impact and goals.
2. Confirm: "Did I miss anything? What's the most important part of all this for you?"
3. Propose the next step: "With this I can put together a tailored proposal. Could we review it Thursday with Frank?"

Common discovery mistakes

Situation: What's your monthly electric bill? Do you own the roof?
Problem:   How has the bill changed over the last year?
           Have outages ever stopped production?
Implication: How does that increase affect your margins?
           What happens to orders during an outage?
           If rates keep rising, what's the impact over 3 years?
Need-payoff: If you cut the bill in half, where would you invest
           that money? What would it be worth not to depend on the grid?

Quantification: $12,000 monthly bill; a system covering 50% of usage
saves $6,000 a month = $72,000 a year (before financing, incentives
and maintenance).

Decision: Who approves investments this size? Cash or financing?
Is there a committee? When do you want it running?

Summary

• Discovery is the decisive stage: ask more and talk less.
• Use open questions and SPIN: situation, problem, implication and need-payoff.
• Listen actively: notes, paraphrasing, follow-up questions and silence.
• Put a dollar figure on the problem with the customer's data, and turn vague answers into numbers.
• Learn who decides, how, with what criteria and by when; end with a summary and a next step.

Next lesson: Sales Presentations and Proposals That Get Approved. You'll present your solution by tying it to what you discovered and write proposals with the return on investment calculated.