Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Avoid pushing to quantify business impact with operational contacts who don't focus on it. A controller cares about chasing receipts, not overall revenue loss. Tailor discovery to the persona's actual sphere of influence and save the big business case for the economic buyer.

Related Insights

To truly resonate with an economic buyer, align your solution to the specific KPIs they are personally accountable for. These metrics often differ from those of your champion or general corporate objectives like revenue and cost savings, requiring tailored messaging.

Don't just broadcast information to stakeholders. Use presentation time for discovery. Ask direct questions like "Is this relevant?" and observe body language to learn what truly matters to them. Each meeting is a chance to refine your understanding of their priorities for the next interaction.

While preventing a single multi-million dollar mistake is a product's biggest value, it's easier to sell based on quantifiable time savings. The justification "this costs one-fourth of a new hire" is a straightforward business case for a budget holder, making the sale simpler.

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.

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.

Stakeholders respond to the language of business impact. Instead of pitching an initiative to "improve the onboarding experience," frame it as a way to "grow our business customers in this sector." This small change in communication connects your work directly to the goals stakeholders care about.

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.

To capture an executive's attention, connect operational-level problems to their strategic business impact. A slow development cycle isn't just a process issue; explain how it directly causes delayed time-to-market, higher costs, and lost market share to competitors, which are the metrics an economic buyer truly cares about.

Reps often pull C-suite objectives from investor decks to seem strategic. However, including objectives your solution can't impact (e.g., sustainability for a sales tool) confuses the buyer. It shows you did research but failed to connect it to real value, which weakens your position.

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.