Why every lost deal in Japan shows up as "price" in your CRM
The quarterly review shows the Japan closed-lost breakdown. Price is the top reason, by a wide margin. Headquarters approves a discount band for the region, and the next quarter looks exactly the same.
The local reps are not hiding anything. Your global picklist has no value that describes what actually happened.
Rebuild the list around what Japanese buyers drop you for, and give “internal approval stalled” its own entry.
The picklist was designed for a different failure mode
Most global CRM instances carry the same closed-lost values: price, competitor, no budget, timing, no decision, other. That list encodes an assumption. It assumes deals are lost to someone else who won them.
In a Japanese deal, the common ending is different. The evaluation went well, the champion was convinced, and then the request sat at the department head for three months and quietly expired. Nobody won it.
Faced with that, a rep picks the closest available value. Usually price or timing. Headquarters then reads a market signal that was never there and responds with the one lever the report seems to justify. Discounting does not move an approval chain.
What Japanese buyers say when they drop you
A joint survey by IDEATECH and Hiroyasu Kitagawa (published April 2026, n=307, limited to buyers who participated with at least one colleague in B2B purchases of 3 million yen or more; it is a vendor-sponsored survey skewed toward large, multi-stakeholder deals) asked why vendors were cut from consideration. The top answers were missing functionality for the buyer’s problem at 39.1%, the vendor not fitting the buyer’s company size at 34.5%, and no customer example resembling the buyer at 26.4%.
The second and third have no equivalent in a standard picklist. Neither is price and neither is a competitor. Both describe evidence your Japan team was never given.
The same survey found the leading reason a vendor made the shortlist was having a customer example of similar size, at 44.3% (n=298 for that question). The reason buyers drop you and the reason they keep you are two sides of one axis. If the field cannot record that axis, no amount of loss data will point at it.
The largest category is “no one decided,” and Japan makes it larger
Ebsta and Pavilion’s 2024 benchmark (n=4.2 million opportunities across 530 companies; an international study, not Japanese data) attributed 61% of losses to buyer indecision. In the same study, 44% of deals slipped, and slipped deals won 67% less often.
More deals end in no decision than are lost to a named competitor. Yet every CRM has a value for “lost to competitor” and almost none has one for “the buyer never decided.”
Japan widens that gap. In the IDEATECH survey, 60.9% of purchases required two approval layers and more than 80% required two or more. Each additional layer is another place the deal can stop without anyone rejecting it.
Five values, and one of them is the approval
The list we implement has five entries.
- Functionality did not cover the buyer’s problem
- Internal approval stalled or was declined
- Budget was not secured, including timing shifts
- Lost to a named competitor
- The buyer’s project itself stopped
Three operating rules keep it honest.
If you keep “other,” make free text mandatory, promote any answer that appears three or more times in a month to its own value, and delete any value nobody has chosen in six months. The picklist is a design artifact you revise each quarter, not a fixed schema.
When a rep selects the second value, require one more field: which layer it stopped at, chosen from department head, executive, IT, legal, or finance. That single field is what tells you whether Japan needs a security review pack or an ROI worksheet, and it is invisible today.
For the fourth value, require the competitor’s name. If your team cannot name one, it belongs in value five. Most “we lost to a competitor” reports in Japan disappear at this step.
There is no Japanese benchmark for why approvals stall
Public surveys tell you how many approval layers Japanese buyers go through. We have not found a published Japanese primary study that breaks down why a request was rejected or where it stopped.
That number cannot be imported. Your own closed-lost field is the only place it will ever come from, which is precisely why the field is worth designing.
What headquarters should do instead
- Stop reading the Japan loss report as a pricing signal. A picklist without an approval value will always route stalled deals into price. Fix the field before you fix the price book.
- Stop treating a single global picklist as a reporting standard. Regions lose deals for different reasons. Shared values across regions produce comparable charts and unusable insight.
- Stop asking the Japan team to explain the losses in a call. Ask for the layer each stalled deal stopped at. That list is short, specific, and directly buildable into the next quarter’s sales collateral.
Designing what the local team hands the approver is part of Japan GTM and messaging, not a CRM cleanup task.
Closed-lost reasons are set by the picklist, not by the rep. Rebuild the values around what Japanese buyers actually drop you for, and give “internal approval stalled” its own entry.
Related reading
How to keep stalled approvals out of the forecast in the first place is covered in forecast your Japan pipeline on approval progress.
Other notes on the same problem are collected under Sales process.