Stop Answering Questions

Picture this: A client asks "do you support X?" Your fingers are already typing the response. They follow up with "could we possibly have 60 day payment terms?" and you're mentally calculating whether your CFO would approve it. Then comes "can we be live by March 15th?" and you're already checking the delivery calendar.

If you're like the vast majority of salespeople, your natural reaction is to give an answer immediately. Yes we support X. Sixty day terms is a challenge but I'll talk to my CFO. Yes, provided you sign by mid-February.

Wrong. Wrong. Wrong.

Why do we default to answering immediately? It's deeply ingrained. We like pleasing people, giving them quick and accurate responses. But in sales, this instinct works against us. When we answer immediately, we trigger what psychologists call 'premature cognitive commitment' - both parties lock into a position before fully understanding the landscape. Worse, we activate the buyer's evaluation mode rather than their exploration mode. They stop sharing and start judging.

A question is a gift from your buyer. They're showing interest, revealing their priorities, and opening a door to deeper conversation. The most importnt thing to do is understand why they're asking the question. There can be all sorts of useful information we'll gather by engaging in the conversation. We can deepen the relationship and avoid making commitments that we don't need to make.

Instead of "Yes we support X" try "That's interesting, how are you handling that requirement today?" Or perhaps "Is that a critical requirement for your team?" Even if you have the feature, the conversation is really important. You'll develop a much better understanding of their use case, their pain points, and what success looks like for them.

Rather than "60 day terms may be a problem" prefer "Are payment terms a major challenge for your organization?" Maybe they're asking out of curiosity. Maybe they know that anything less than 60 days causes huge negotiation challenges with their procurement team. Either way, find out. And definitely don't give anything away in your negotiation yet - remember that the first person to name terms often loses ground.

A better alternative to "Yes we can be live by March 15th" is "What's the importance of that date for you?" Now you'll discover if there's a real driving need in the organization. Perhaps their boss has set that deadline. Maybe another subscription is coming up for renewal. Or possibly an old system is being decommissioned. Each of these scenarios changes how you should position your solution.

In every situation, the best answer to any question is another question.

This isn't slippery or evasive - you're having a genuine conversation to understand the real need. When you show authentic curiosity about their specific situation rather than rushing to prove you can tick their boxes, you build trust. You signal that you care about their success, not just closing a deal.

If you feel that a direct answer is really necessary for some reason, you can always do both. "Yes, we have X - what's the use case you're thinking of?" or "We've considered 60 day terms in the past, but can you tell me what's driving the question?" or "I expect we can make March 15th work, but help me understand the importance of that date."

Please encourage your team and remember yourself: any time you're asked something, it's an opportunity to engage. A question should solicit another question. The information you gain will be far more valuable than the satisfaction of providing a quick answer.

I’d love to hear your thoughts. Comment here or reply.