Japanese enterprise sales: references matter alongside 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, features did their job: they kept you from being cut. What decided the rest was whether a company of similar size in the same industry already uses you.

Features get you cut. Precedent keeps you in.

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) is worth reading in two halves.

The top reasons a vendor was dropped mid-evaluation (multiple response) were “lacked the features our problem required” at 39.1%, “did not seem to fit our company size” at 34.5%, and “no case study from a company like ours” at 26.4%.

The top factors in adding the eventual winner to the shortlist (n=298 for this question, up to three answers) were “a case study from a similar-sized company existed” at 44.3%, “the features were clear” at 40.3%, and “a track record in our industry” at 29.5%.

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

Features are the first filter: miss there and you are out.

Past that filter, the second and third reasons for dropping a vendor and the first and third reasons for keeping one all ask the same question: does a company like ours already use this?

One line worth drawing. The survey asked why vendors were shortlisted or dropped, not what the final approver looked at before signing.

That precedent carries the ringi (formal circulated approval) is an interpretation, based on the next number: in the same survey, 60.9% of companies require exactly two approval stages and over 80% require two or more.

Once your contact is convinced, they still have to explain the decision upward.

“A company your size, in your industry, uses us this way and got this result” is a sentence they can paste straight into that explanation.

For a foreign SaaS company, this changes what the translated global comparison chart is for.

It keeps you from being dropped on features. It does not, on its own, keep you on the shortlist.

Your framework already has the stage. Japan has more steps in it.

None of this is foreign to a Western sales methodology. MEDDPICC tracks the decision process, the paper process, and the champion, and many teams already run a Mutual Action Plan with the buyer.

If someone at HQ says “we already do this,” they are partly right.

The difference is how many stages and departments that process has to pass through.

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%).

63.6% took three to eight months to evaluate, and by the time serious conversations with a vendor begin, the buying process is already about 40% complete on average.

The champion model still holds in Japan. What changes is how many rooms one champion has to walk into.

Treated as one line in a qualification checklist, it does not keep up. Run it as a stage of its own.

Track consensus, not sales activity

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 two fields to the opportunity, alongside your sales stage.

• Approval stage (picklist): working team agrees, department head approved, executive approved, final approval.
• Date entered this stage (date): the rep fills it in whenever the approval stage changes.

Days stalled is the gap between that date and today. Compute it with a formula in the CRM or in a weekly export; either works.

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

Forecasting on this axis is covered in Forecast your Japan pipeline on approval progress, not rep confidence.

Count your case-study inventory by industry and size

To hand over precedent, you need precedent on the shelf. Count it in cells, not in totals.

• How many you need. Lay out your open deals and recent losses in a grid of industry by employee-size band. Every cell with zero case studies is a gap. A large library does not help if the cells where your pipeline sits are empty.
• What each one must contain. Industry, employee size, number of users, the team that runs it day to day, what else they compared, and how they got it through internal approval. These are the fields a buyer uses to decide whether a case is “like us.” The interview questions are in Japan case studies: give buyers enough detail to assess the fit.
• How to get permission. At the start of the interview, ask which level the customer will allow: named, anonymized with industry and size only, or usable only in live sales conversations and non-public material. An anonymized case with industry and size still works for matching.
• Who owns it. One person in sales ops or marketing keeps a single sheet: the grid, and the permission level of each case. Reps nominate a customer after every win. Interviews take the customer’s time, so say up front what you will ask and what you plan to publish.

Early on, most of your references will be from outside Japan.

Whether a Japanese buyer treats a US or European logo as “a company like ours” is not something this survey asked. Treat it as untested, and ask in the first meeting what the buyer will compare you against.

Make nemawashi a designed motion

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

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 the cell that matches their industry and size.

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.

Check both technical requirements and the buyer’s need for comparable references. Include support for the internal approval in the account plan.

Common mistakes

• Choosing between the comparison chart and case studies. The chart keeps you from being dropped; the case studies keep you in. Missing features is the top reason vendors get cut, so abandon the chart and you are cut first. How to make the chart usable inside the buyer is in Your Japan battlecard is read in a room your rep never enters.
• 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.” While you wait, your contact is assembling the explanation for the next level on their own. Decide before you wait what you will hand them: the ringi draft and the case study from the matching cell.

Related reading

The common mistake is to lead with a free trial instead of precedent. A free trial alone won’t get your Japan deal approved covers what to send instead.

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