What Has It Cost You? The Questions That Attach a Number

Two sellers run discovery on the same account, the same week, with the same buyer. Both hear the same pain: the fraud analyst team is overwhelmed, morale is cracking, good people are leaving.

Seller one writes in the deal file: "Customer is struggling with analyst workload and attrition. Strong pain identified."

Seller two writes: "4.1 million alerts a year at 22 minutes each — roughly 1.5 million analyst hours — to find the 4% of alerts that matter. Two senior analysts resigned in Q3; replacement cost quoted by their own HR at $180K each. Head of Fraud Ops said the number out loud and winced."

Same pain. Same conversation, almost. But only one of those deal files contains a business case, and it is not an accident which one. Seller two asked a different class of question — and then had the discipline to shut up while the customer did the math.

Here is the rule, and it is worth putting on the wall: pain without a number is a complaint, not a business case. Complaints generate sympathy. Numbers generate budget. Your pipeline is full of deals where the pain is real, confirmed, even urgent — and the deal still dies, because when the buyer walked into the budget meeting you weren't invited to, all they carried was an adjective.

Why "significant pain" closes nothing

Follow the pain through the buyer's organization and you'll see why the number is everything.

Your champion hears you out and is convinced. Now they have to convince their boss. Their boss has seven competing asks this quarter and one question: "What's this costing us?" If the answer is "a lot — the team is really struggling," the ask goes to the bottom of the pile, beneath every ask that arrived with a dollar figure attached. Not because the pain is less real. Because it is less comparable. Budget meetings are ranking exercises, and you cannot rank adjectives.

The number does something else, too: it creates the "why now." A pain that costs "a lot" costs the same "a lot" next quarter, so next quarter is fine. A pain that costs $340K a month costs $1M by the time a three-month delay is over — and suddenly the delay itself has a price tag. Every cost-of-delay sentence I have ever inspected on a healthy deal traces back to one moment in discovery when somebody asked the impact question and waited.

The five doors into the number

"What has it cost you?" is the master question, but asked cold, it often gets a shrug — buyers genuinely don't know the total. The craft is to open a smaller door first. There are five.

Hours. The gentlest entry, because people know their time. "Walk me through what happens when an alert fires. Who touches it? For how long?" Then multiply out loud, together: volume × minutes × people. Buyers who have never once totaled their own process will do it willingly in front of you, one factor at a time. The hours question works because it asks for facts, not conclusions — the conclusion assembles itself.

Dollars. Sometimes direct: "When that outage hit in March, what did it cost?" Sometimes via the loaded rate: "What does an analyst hour cost, fully loaded?" — a figure their finance team publishes internally and your champion can get. Hours times loaded rate is a dollar figure the customer cannot later disown, because both factors are theirs.

Misses. The most powerful and least asked: "What did this problem cause you to not catch, not ship, not win?" The fraud that got through. The renewal that churned because the team was heads-down on noise. The regulatory finding. Misses are where the pain stops being an efficiency story and becomes a risk story — and risk numbers travel to the executive floor faster than cost numbers do.

Headcount. "How many people does this consume today? What did you have to hire — or fail to hire — because of it?" Two resignations at $180K replacement each is a number. So is the req that was approved and never filled because the job, as currently constituted, is unfillable.

Deals lost — or their equivalent. Every function has a version of revenue left on the table. For a sales team it's literal deals; for fraud ops it's the false positives that blocked legitimate customers; for engineering it's the launch that slipped two quarters. "Has this ever cost you something you wanted badly?" The stories that answer this question come with numbers already embedded, because people remember what losing cost.

You will not need all five doors on every call. But the seller who walks in with all five written on the A.X.I.O.M. plan — one quantifying question prepared under each pain hypothesis — never leaves discovery holding nothing but adjectives.

The customer must say the number

This is the part of the craft that separates the professionals, and it is a discipline of restraint.

The moment a buyer describes a painful process, every seller feels the pull to help: "So that's probably costing you, what, a couple million a year?" Resist it. A number you say is a vendor's claim. A number they say is a fact of their business. The difference decides whether the number survives the rest of the deal.

Watch what happens downstream. Your business case lands on the CFO's desk. If the headline number came from your ROI calculator, the CFO's first move is to discount it — vendors inflate, everyone knows vendors inflate, and your credibility is spent defending arithmetic. If the headline number came from the Head of Fraud Ops, in her words, from her data, confirmed in a follow-up email she replied to — the CFO is no longer auditing you. Any attack on the number is now an attack on his own colleague's math. You have left the conversation, and the customer is defending your business case for you.

So the technique is: ask the factor questions, do the multiplication together, and then hand them the conclusion to speak. "So — help me with the math. Four million alerts, twenty-two minutes each. What does that come to?" Then silence. The silence is the hard part. Fill it, and you've bought the number back.

One more move while the moment is warm: haircut it with them. "Let's say we're only half right about the minutes — call it eleven. Is the number still a problem at that level?" A conservative floor the customer set themselves is the single most durable artifact in enterprise selling. Nobody can negotiate you down from a number the buyer already discounted.

Then write it down — verbatim, attributed, dated — and confirm it in the follow-up email. In the deal file, that becomes the evidence behind Identified Pain and Metrics, scored a 2 the day they confirm the email and a 3 when a second stakeholder repeats it. "The customer is frustrated" scores a 1 — assumed — no matter how vivid the frustration was in the room.

The number is the deal's skeleton

Here is why this one discovery habit carries so much weight: the quantified pain is not a stage artifact. It is the load-bearing structure of everything that follows.

The business case is the number, projected. The POV success criteria are the number, made testable. The cost of delay is the number, divided by twelve. The Economic Buyer conversation is the number, presented in the buyer's own dialect. The forecast justification, when your leader asks why this deal is Commit, is the number, on file, in the customer's words. Deals with a customer-stated number close differently — faster, at better prices, with less late-stage drama — because at every decision point, someone inside the account can answer "why are we doing this?" without you in the room.

And deals without one? They are the deals in your pipeline right now where the pain is "confirmed," the champion is "engaged," and the close date has moved three times — because nobody inside the account can articulate what waiting costs, so waiting remains free.

Where to start Monday

Audit your top ten deals for one sentence. For each: what has the current state cost this customer, in their number, in their words, with a name attached? Any deal where the account team answers in adjectives has a discovery gap — send them back to ask the impact question, this week, no matter what stage the deal claims to be in.
Put the five doors on every discovery plan. Under each pain hypothesis on the A.X.I.O.M. one-pager, write the quantifying question in advance — hours, dollars, misses, headcount, or losses. Courage is easier to summon when the question is already written down.
In your next deal review, ask who said the number. Not "what's the ROI" — "who said it, when, and where is it written?" If the answer is "our value calculator," the business case is a vendor claim wearing a spreadsheet, and the deal is softer than the stage says.

The impact question is uncomfortable to ask. You are asking a buyer to price their own wound, out loud, in front of a stranger. Ask it anyway — kindly, specifically, and then silently. The sellers who do are not being aggressive. They are doing the buyer the one favor no demo ever will: turning their complaint into a case that can actually win the budget fight.

A complaint gets you sympathy. A number gets you a signature.

Go deeper. This essay is drawn from The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli — the complete operating system, demonstrated end-to-end on one $8.9M enterprise deal. Get the book, and download the free Field Toolkit — including the Business Value Assessment and the 3 Whys Builder — to attach a number to every pain in your pipeline.