How to quantify pain in discovery
Qualitative pain earns interest; quantified pain earns budget. A CFO does not fund "it is frustrating," they fund "it costs 400,000 dollars a year."
The trick is to build the number with the buyer, using their data, so they defend it internally rather than dismiss it as a vendor estimate.
Short answer
Quantify pain in discovery by getting the buyer to put real numbers on their problem: how often it happens, how much time or money it costs each occurrence, and the annual total. Co-create the math so the buyer owns it. A quantified problem becomes the foundation of your value case and the justification for budget.
Step by step
Establish frequency
Ask how often the problem occurs: per day, per week, per deal. Frequency is the multiplier that turns a small unit cost into a large annual one.
Estimate the unit cost
Get the cost of each occurrence in time, money, or lost opportunity. "How many hours does that take to fix each time?" or "what is a lost deal worth on average?"
Roll it up to an annual figure
Multiply frequency by unit cost to reach an annual total. Do the math out loud with the buyer so they see and validate it.
Confirm and record it
Restate the number, let the buyer adjust it, and capture it on the deal. This figure anchors your proposal and defends your price later.
How to ask for numbers without friction
Frame quantification as building the buyer's own business case: "to help you justify this internally, let us put rough numbers on it." Buyers share data when they see you using it to help them win budget, not to judge them.
How Ardovo runs this
Ardovo turns this from a slide no one opens into how the work actually happens. The stages, exit criteria, and plays live in the deal object, and Rook flags any deal that skips a step, drafts the next artifact, and keeps the data honest, so the cost of the problem is captured in real numbers gets followed instead of forgotten.
Frequently asked questions
Why quantify pain instead of just describing it?
Because budget follows numbers, not adjectives. A quantified problem ("it costs 400,000 dollars a year") gives your champion the ammunition to win funding internally, while a qualitative one ("it is frustrating") is easy for a CFO to deprioritize.
How do I get a buyer to share cost numbers?
Frame it as building their own business case. Say you want to help them justify the investment internally, then estimate frequency and unit cost together. Buyers open up when the math serves their budget fight rather than feeling like an audit.
What if the buyer does not know the exact numbers?
Use conservative estimates and confirm the assumptions with them. A defensible rough figure the buyer helped build is far more useful than no number at all. Let them adjust the inputs so they own the math and will defend it to finance.