Your Japan battlecard is read in a room your rep never enters

Published Aug 29, 2026

The Japan pipeline stalls in evaluation, so headquarters ships the competitive battlecard, translated. Nothing moves.

The reflex after that is usually to improve the card. More rows, sharper claims, a fresher win-loss angle.

The card is not the problem. Nobody in Japan is going to carry it into the room where the decision is made.

In Japan the comparison is finished before your rep is invited

A joint survey by IDEATECH and Hiroyasu Kitagawa of Demagen Soken (published 16 April 2026, fielded 23 to 26 March 2026, n=307, restricted to Japanese employees and executives who took part with at least one colleague in a purchase of B2B products with annual contract value or one-off implementation cost of 3 million yen or more; run by a firm whose business is survey-based PR, so read it for order of magnitude) found that roughly 90% had drawn up a list of several vendors before speaking to any of them. Around 70% shortlist two or three. By the time serious conversations with a vendor begin, the buying process is on average about 40% complete.

In the same survey, 91.2% used generative AI or AI search during the evaluation. The most common use was comparison, at 47.6%.

So the comparing is done, and it was done without you. A battlecard arriving after that reads as homework the buyer already handed in.

Japan eliminates on features and selects on evidence

That does not mean features are irrelevant, and the pairing here is worth sitting with.

In the same n=307 survey, the top reason for cutting a vendor from the list was insufficient functionality, at 39.1% (multiple response). Next came “the company is the wrong size for us” at 34.5%, and “no reference at a similar company” at 26.4%.

Now the second survey. IDEATECH and Demagen Soken published a follow-up on 9 June 2026 (fielded 25 to 26 May, 330 valid responses, covering B2B business software, SaaS, IT infrastructure and security purchases at 5 million yen or more per year; base varies by question). Asked which materials had no influence on the purchase decision, respondents put general industry trend reports first at 49.5% and the feature comparison chart second at 46.2%.

Both are true at once. Features are how you get eliminated. They are not how you get chosen.

Asked what made the winning vendor the winner, the first survey’s decided buyers (n=298, up to three selections) put “a reference customer of similar size” first at 44.3%, ahead of clear functionality at 40.3% and industry track record at 29.5%.

The top answer is not on your battlecard. Neither is company size, and neither is the domestic incumbent your competitive intelligence team does not track, which in Japan is often a spreadsheet, a kintone app, or something an integrator built in 2014.

What your champion needs is a document they can be seen holding

The follow-up survey asked which content actually helped buyers judge. An ROI calculator came first at 55.4%, a success story from their own industry and company size second at 46.5%, and slides for explaining the decision internally third at 26.8%.

The common thread is not subject matter. It is whether the buyer can operate the thing themselves.

Which makes sense once you picture the meeting. Your champion is asked why this vendor. They produce a vendor-branded grid where the vendor wins every row. The conversation stops being about your product and becomes about their judgement, and whether they simply repeated what a salesperson told them.

The people asking are frequently people your reps have never met. In the same follow-up, the specialist functions involved included IT at 42.2%, finance and accounting at 38.2%, legal at 33.2% and procurement at 32.0% (multiple response).

So the card does not get used. Not because it is badly made, but because using it costs the champion something.

Ship a criteria sheet, and write the “no” yourself

The fix is structural, not editorial.

Stop putting your company and your competitors in the columns. Put the buyer’s requirements in the rows, in the words they used on the call. “Does not create double entry with our existing order management system.” “Can start without an IT security review.” Keep their vocabulary. The moment you translate a row into your own feature name, your champion can no longer read it aloud in their own meeting.

Three columns only: meets, meets with conditions, does not meet.

The value sits in the middle column. Write what would have to be true, in implementation terms, for the requirement to be met. That is the one part neither a competitor’s website nor a language model can produce, because only someone who has actually deployed the thing knows it. Your champion can lift that cell straight into their answer to internal objections.

And do not leave “does not meet” empty. Name one or two honestly. A sheet with that column filled is the only version that becomes the buyer’s own document rather than yours.

Two alternatives are worth naming and rejecting.

Anonymising rivals as Vendor A and Vendor B avoids friction and destroys the sheet’s usefulness, because the first question in the internal meeting is which one Vendor A actually is.

Sending it on the first call is worse. It sets the contest as feature count, which is the criterion you get eliminated on at 39.1%, not the one you get chosen on. It waits until you know you are on the shortlist.

This is the same work as getting Japan GTM and messaging right, because both start from what the buyer has to carry through their own organisation.

A comparison document is not how a Japanese buyer decides. It is how your champion defends the decision when you are not in the room.

Common mistakes

Translating the global battlecard instead of rebuilding it. The rows were written to beat a competitor your Japanese buyer may not be evaluating, in language their finance and legal readers will not recognise.
Leaving every row green. A document where you win everything cannot be shown by the one person whose credibility is on the line.
Treating “no reference our size” as a marketing gap. At 26.4% for elimination and 44.3% for selection, in Japan it behaves like a product requirement.

The sheet is an attachment to something larger, which is the approval document your champion has to write. Drafting it for them is covered in in Japan, your champion cannot write the business case.

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