Latent Needs · Needs vs. Wants
Latent Needs
What are latent needs?
- The real problem behind the requested solution (the want)
- Surfaced only through questions; the key is calculating the impact
- Offer an alternative, don’t ignore the request
The moment you receive a quote request, you are already one cell in a comparison table. Working with latent needs means stepping out of that cell and moving to sit beside the person who wrote the request. When the conversation shifts from matching hours, headcount, and unit price to writing down together what should be different at the company after this training, the basis for comparison itself blurs. In practice, the first page of the proposal changes from a “course outline” to a “problem definition.”
Listen to what clients say on two levels. “Team leaders seem to be struggling with one-on-one meetings lately” is a statement of regret. “We need to raise the coaching skills of 40 team leaders this year” carries intent to solve and a deadline. The two carry very different weight. The first alone doesn’t create a budget. When the amount is small, as with a one-off lecture, even a statement of regret can get approved. But once the scale pushes approval up to the executive level, our job extends to turning it into numbers and sentences the training manager can put in a report.
Who you ask matters too. Training managers often sit in a relay role: they pass along symptoms handed down to them, so however hard you dig there, the answer is “I just got this request from above.” You need a 30-minute touchpoint with the line manager or executive who first raised the request to get numbers such as cost, deadline, and the loss from leaving the problem alone. Asking them to open that door is itself the first step of discovery.
Things most often go wrong when latent needs are used to 'prove the customer wrong.' The manager has often already put that request into an executive report and secured the budget, so if we declare 'this is a policy problem, not a leadership problem,' the manager has to overturn their own report. At that moment we stop being an insightful partner and become a vendor who makes the job bigger. Conversely, if we blow the problem up beyond what we can handle, we do the diagnosis and a consulting firm wins the contract. It is safer to put the original request and the reframed proposal side by side on two pages and let the client choose.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Jaehyuk ParkHands-on instructor in B2B technical sales and AI-driven sales strategyThe concept became widely used after 1980s research on large-deal selling, including Neil Rackham’s SPIN research, confirmed that top-performing salespeople surface problems customers haven’t recognized by asking questions.
Consider a hypothetical case. Company A distributes industrial parts, with 210 employees and annual revenue of KRW 80 billion (≈ US$59,853,400). Its talent development team asked for a quote for 'a 4-hour negotiation skills lecture for 35 sales reps, budget KRW 4 million (≈ US$2,990).' Nowhere did the request say why negotiation training was needed right now, and over the past two years the company’s operating margin had fallen from 7% to 4.2%.
- We sent back the 4-hour lecture quote that the Talent Development manager had requested, exactly as specified, but added one line at the end of the email asking how many discount approval requests there had been last quarter.
- Two days later, Manager Kim set up a meeting with Team Leader Park of Sales Planning. Park pulled up the approval ledger on screen: discount approvals had gone from 12 a month to 31.
- When we ran the numbers together, deals carrying discounts totaled KRW 15 billion (≈ US$11,222,500) a year. With the average discount up from 8% to 14%, that meant KRW 900 million (≈ US$673,400) a year was slipping away.
- With the Head of Sales in the room, we pointed out that 'before negotiation skills, you lack criteria for approving prices.' The Head admitted that 'the criteria table hasn’t been touched since 2019.'
- We submitted two proposals side by side, with cost and hours for each: the requested 4-hour lecture, and a 4-month program combining two workshops on redesigning approval criteria with on-site coaching for three sales teams.
- Company A chose the KRW 38 (≈ US$1) million, 4-month program. Six months later, the average discount had fallen from 14% to 9.6%, and monthly discount approvals had dropped from 31 to 18.