Prospects often misdiagnose their own problems. For example, they might think they need more leads when the real issue is poor conversion. Like a doctor, a good salesperson accepts the described pain but challenges the prospect's self-diagnosis to offer a more effective, underlying solution.
Before answering a prospect’s question (e.g., "Do you have analytics?"), clarify the intent behind it. The underlying need can vary wildly, and answering without context risks providing an irrelevant or incorrect solution, which can derail the call and erode trust.
After a prospect describes a problem, summarize it back to them using specific industry frameworks or terminology (e.g., MEDDPIC). This demonstrates deep expertise, builds credibility beyond personal rapport, and invites them to either confirm your understanding or correct you, revealing more crucial details.
To challenge a prospect's approach without making them feel attacked, use softening language and frame your point from experience. Saying, "We were working with another customer with a similar pain, but we discovered..." turns a direct confrontation into a helpful, experience-based insight that builds trust.
When a prospect shares multiple important points in a long monologue, jot down single-word reminders on a note card. This allows you to stay focused on the current topic while ensuring you can strategically circle back to other "golden nuggets" later without forgetting them or derailing the conversation.
Avoid demoing on a first call unless you are certain you can solve a prospect's specific, deeply understood pain point in under five minutes. A generic or rushed demo is worse than no demo, as buyers will draw negative conclusions. Only show the product if you can create an "oh shit" moment of realization for the buyer.
To overcome skepticism around complex products like AI, leverage internal networks for social proof. Have your CTO ask their engineering contact at the target company to send a note to the economic buyer (e.g., the CRO) vouching for your company's technical credibility. This cross-functional validation builds immense trust.
Don't just ask about priorities related to your product. Ask for their absolute top priority overall, regardless of your solution. If your solution addresses their #4 problem, but #1 is a massive project like a CRM migration, you know the deal is likely disqualified or needs to be pushed out, saving you time.
When faced with the "we can build this ourselves" or "we can use ChatGPT" objection, don't argue about features. Simply ask, "If it's valuable and easy to build, why haven't you built it yet?" This forces the prospect to confront the real-world complexities and resource constraints, validating the need for your solution.