The Buyer's Frame Is Always Too Small
When a buyer reaches out to a vendor, they have already defined their problem. They have thought about it. They have discussed it internally. They have probably written it into a budget request or an RFP. And almost without exception, they have defined it too narrowly.
This is not because buyers are unsophisticated. It is because buyers experience problems at the point of pain. They feel the symptom, not the system failure. A department head who is drowning in manual data entry does not describe their problem as "our revenue operations infrastructure lacks the integration layer necessary to support growth." They say: "We need an OCR tool."
If the seller accepts that framing, they sell an OCR tool. It might be a $50,000 deal. It might be $100,000. It will be a fraction of what the problem is actually worth. Because the problem is never the OCR tool. The problem is everything that happens downstream when the data is wrong, the processes are manual, and the organization cannot scale.
A Case in Downstream Thinking
We once worked with a company that sold document processing technology. Their buyers typically came in looking for an OCR solution. The initial conversations were always small: "We need to digitize these forms." "We need to extract data from these documents." The average deal was modest, and the sales team was working hard just to maintain volume.
We asked the sales team to stop answering the buyer's stated question and start following the problem downstream. Here is what they found:
The buyer needed OCR because they were processing documents manually. Why were they processing documents manually? Because the data in those documents needed to flow into three downstream systems, and there was no integration layer connecting them. Why did that matter? Because manual data entry created errors, and errors created compliance risk. Why did compliance risk matter? Because each compliance incident cost the organization six figures in remediation, and they were averaging several per quarter.
But it went further. The manual process also created a bottleneck. The team processing documents could not keep up with volume during peak periods. What happened during peak periods? Delays. What did delays cause? Missed SLAs with their own customers. What did missed SLAs cost? Revenue. Specifically, penalties in their contracts and churn in their customer base.
By the time the sales team followed the problem to its floor, the conversation was no longer about an OCR tool. It was about a revenue operations platform that eliminated an entire category of operational risk. The deal went from a point solution purchase to a $7 million enterprise engagement.
The "And Then What Happens?" Framework
Following the problem downstream is not intuition. It is a discipline. And it can be taught. The framework is deceptively simple: at every stage of the buyer's problem description, ask "and then what happens?" Keep asking until you reach a dollar figure.
Stage 1: The Stated Problem
This is where the buyer starts. "We need to automate X." "We need a tool that does Y." "Our current system cannot handle Z." Accept the statement. Write it down. Do not solve it yet.
Stage 2: The Operational Impact
Ask: "What happens in your organization when this problem occurs?" This moves the conversation from the tool to the workflow. You will hear about manual workarounds, delays, errors, and rework. These are the first-order consequences, and they are almost always more expensive than the buyer realizes.
Stage 3: The Organizational Impact
Ask: "Who else in the organization is affected by this?" Problems rarely stay contained in one department. Data errors in operations affect finance. Processing delays affect customer success. Compliance gaps affect legal. Each stakeholder you surface expands the scope of the problem and the scope of the deal.
Stage 4: The Customer Impact
Ask: "How does this affect your customers or your ability to serve them?" This is where the problem crosses from internal cost to external revenue. If the buyer's problem causes delays in their own customer delivery, missed SLAs, or degraded service quality, you have found the revenue impact. And revenue impact is where executive attention lives.
Stage 5: The Revenue Floor
Ask: "What does this cost you annually, when you add up the penalties, the churn, the rework, and the opportunity cost?" This is the dollar figure. This is the floor of the problem. And this number is the anchor for your deal, not the unit price of your product.
When you can articulate the buyer's problem at the revenue floor, you are no longer selling a tool. You are selling a solution to a revenue problem. And revenue problems get executive budgets, not departmental ones.
Why Sellers Stop Too Early
Most sellers stop at Stage 1 or Stage 2. They hear the stated problem, maybe ask about the operational impact, and then jump to a demo. The reason is partly habit and partly incentive: it is faster to close a small deal than to invest the time to uncover a large one. Pipeline metrics reward volume. Discovery takes patience.
But the math is clear. One deal at $7 million is worth more than seventy deals at $100,000, and it takes less effort to manage. The investment in downstream discovery pays for itself many times over, not just in deal size, but in deal quality, buyer commitment, and competitive defensibility. A buyer who understands that you are solving a $7 million problem does not switch vendors over a 10% price difference.
Make It Structural
Like everything in enterprise sales, this works best when it is embedded in the process rather than left to individual talent. Build the "and then what happens?" progression into your discovery framework. Make each stage a required field in your CRM. Train managers to review deals against the downstream map, not just the stated need.
The buyer will always tell you the smallest version of their problem. That is not deception. That is perspective. They see the surface because they live at the surface. Your job, as an enterprise seller, is to follow the problem downstream until it reaches the floor. That is where the deal actually lives.
Jeff Aragon, Founder — Jozu Consulting Group