We scan new podcasts and send you the top 5 insights daily.
Prospects often state facts like "our sales process is complex." This is not a problem that gets budget. AEs must dig deeper for the root cause (e.g., single-threaded deals) and then the business problem (e.g., low win rate affecting fundraising) to build a compelling case for the CFO.
Prospects often describe wants (e.g., "a more efficient system"), which are not true problems. Asking about the motivation behind their desire forces them to articulate the underlying pain that actually drives a purchase decision.
Sales reps often get stuck trying to ask smart-sounding questions they find online. The real breakthrough is focusing on understanding the prospect's current state and identifying what information is missing to build a business case, which will naturally lead to the right questions.
Companies don't sign six-figure contracts to solve one person's frustrations. To justify a large purchase, you must anchor the sale to tangible business outcomes. Frame discovery questions around the company's goals, not just an individual champion's personal pain points.
At the end of a discovery call, ask two distinct questions. First, validate the problem's importance. Second, qualify its urgency by adding 'right now.' This simple addition uncovers crucial timing and budget cycle information for more accurate forecasting.
Sales conversations often rush to demo a "better" product, assuming the buyer wants to improve. The crucial first step is to help the prospect recognize and quantify the hidden costs of their current "good enough" process, creating urgency to change before a solution is ever introduced.
Discovery has three levels: Situation (what they do), Operational Problem (a day-to-day annoyance for a champion), and Executive Problem (the business impact). Sales reps fail when they solve operational issues without connecting them to the executive-level "so what" that justifies a purchase.
To justify a high price, connect a low-level operational issue (e.g., billing inefficiencies) to an executive-level P&L problem (e.g., revenue leakage) and finally to a critical C-suite metric. This transforms a minor annoyance into a must-solve business problem.
CFOs respond to numbers, not just pain points. Instead of focusing only on your solution's ROI, first translate the prospect's problem into a clear, granular dollar amount. Show them exactly how much money their current challenge is costing them annually.
Getting approval for an operations hire is difficult because they aren't directly tied to new revenue. Instead of a vague promise of "efficiency," build a business case by quantifying the cost of a broken process—like a high lead disqualification rate—and show how the hire will unlock that hidden pipeline.
When a prospect describes an operational pain, present two common, high-impact business consequences you've seen elsewhere. This frames the problem in executive terms and guides them toward revealing a more significant issue, rather than hoping they connect the dots themselves.