In Japan, deals are won on precedent rather than features

Your product has the strongest feature set in the category. You win the technical evaluation.

Then the deal stalls for months and closes with a weaker competitor.

If this keeps happening in Japan, the problem is not your product.

In the Japanese approval process, the deciding factor is not whether your features are best. It is whether a company of similar size in the same industry already uses you.

The number that actually decides the deal

A joint survey by IDEATECH and Hiroyasu Kitagawa (published April 2026, n=307, limited to employees and executives who participated with at least one other person in B2B purchases of 3 million yen or more, so this reflects larger, multi-stakeholder deals; it is also a vendor-sponsored survey) found that the top reason a vendor was selected was “a case study from a similar-sized company existed,” at 44.3% (this question was limited to respondents who reached a final decision, n=298).

The mirror image is just as sharp.

The second most common reason a vendor was dropped from consideration was “it did not seem to fit our company size,” at 34.5%.

And 62.5% of buyers said industry-specific information influenced their decision.

Feature clarity mattered (40.3%), but it did not lead.

For a foreign SaaS company, this inverts the usual playbook.

A global feature comparison, translated into Japanese, argues on the axis Japanese buyers weight least.

The sentence that moves a Japanese approval is not “we have capability X.” It is “a company your size, in your industry, uses us this way and got this result.”

Deals die on indecision, not on price

The biggest reason deals stall is not features or price. It is that the buying organization cannot reach an internal decision.

Ebsta and Pavilion’s “2024 B2B Sales Benchmarks” (n=4.2 million opportunities, non-Japanese companies) found that 61% of lost deals were lost to “indecision.”

44% of deals slipped their forecast date, and slipped deals were 67% less likely to close.

This is not Japanese data, but the pattern, that stalled decisions kill revenue, holds everywhere.

In Japan, that “cannot decide” time is structurally built into the process as ringi (formal circulated approval) and nemawashi (informal groundwork).

In the IDEATECH survey, over 80% of companies require two or more approval stages (60.9% require exactly two), and 63.6% take three to eight months to evaluate.

By the time serious conversations with a vendor begin, the buying process is already about 40% complete on average.

Your Japanese deals are not long because your pitch is weak. They are long because they run through this structure.

Track consensus, not sales activity

A US pipeline assumes that when the sale moves forward, the deal moves forward. Demo delivered, proposal sent, pricing negotiated: sales activity is deal progress.

Japan breaks that assumption. Your CRM says “proposal sent,” but inside the buyer, the working team has merely nodded, the department head is watching, IT has an open concern, legal review is pending, and the executive briefing is next month.

What you need to track is not your activity. It is “who has not yet said yes.”

Add a second axis to the CRM, alongside your sales stage, that records how far internal approval has climbed on the buyer’s side.

A stalled deal then reads as “in ringi, stage 2, day 34” instead of “no update,” and your forecast can carry realistic exit dates.

Make nemawashi a designed motion

Internal-consensus support should be engineered into the process, not left to instinct or to a single champion.

Western frameworks hand the job of moving the organization to one buyer-side champion and stop there.

In Japan, developing one champion is not enough, because the decision spans multiple departments.

In the IDEATECH survey, roughly 80% of buyers had two to four departments involved, led by IT (45.6%), business units (37.5%), and corporate planning (29.0%).

Your enthusiastic contact is often not the decision-maker.

So add one stage between selection and contract, called internal consensus building, and make the following standard sales motions.

Map the departments and roles involved. Identify each one’s unspoken “no.”

Then hand your champion a draft of the ringi document together with a one-page case study from a similar-sized company in the same industry.

In Japan this is not an optional service. It is the stage where the deal is actually won.

How to redesign the full process around this sits on top of Revenue Architecture thinking.

Japanese approval passes on precedent, not on the best feature. Build internal-consensus support into the sales process as its own stage, separate from the product pitch.

Common mistakes

• Polishing the feature comparison. In a Japanese approval, precedent beats feature superiority. Building an inventory of similar-size, same-industry case studies moves more deals than sharpening the comparison grid.
• Treating your contact as the decision-maker. With two to four departments involved, an eager champion cannot carry the deal past another department’s unresolved “no.” Watch the spread of consensus, not the enthusiasm of one person.
• Waiting out “let me take this back internally.” Waiting lets the deal slip, and slippage lowers win rates. Decide before you wait what you will hand them: the ringi draft and the matching case study.

Related reading

The common mistake is to lead with a free trial instead of precedent. Your free trial won’t close the deal in Japan covers what to send instead.

Other notes on the same problem are collected under Sales process.