Win-loss interviews with Japanese buyers: getting past the polite reason

Treat "we lost on price" as the entry point

The reason a rep hears right after a loss is usually short and face-saving. In a Business+IT interview (SB Creative, 1 February 2019, sponsored by Salesforce Japan, in Japanese), Koichi Takahashi of TORiX says that plausible answers such as "the other vendor was cheaper" or "the proposal did not fit our requirements" are in many cases tatemae (建前), the reason meant for outside ears. That is one interview from 2019 and gives no rate. It is the premise of this lesson.

The same pressure acts on the rep. Mazrica's guide to lost-deal analysis (in Japanese, published 26 March 2021, updated 15 June 2026) describes a bias in which a rep who fears that an honest loss reason will hurt their evaluation hides the real one and blames external factors. A buyer who answers briefly and a rep who records briefly leave the one word "price" in the CRM.

Salesforce Japan's list of nine loss factors (30 June 2025, in Japanese) notes that price can stop a decision-maker's ringi from passing, and recommends hearing from the prospect directly. 創業手帳, a Japanese publication for founders, tells of a deal written off as a price loss where the follow-up conversation showed the responsible manager had decided on their own (published 30 May 2025). Both are single cases. No study I could find measures how often "price" stands in for something else, so this lesson claims no rate.

What a ringi buying chain hides from the seller

A ringi is a document that proposes a decision and circulates for approval. Rochelle Kopp of Japan Intercultural Consulting writes that it lays out the case with the data to be considered attached, and that someone who disagrees may simply put it in a desk drawer and never take it out again (first published 27 April 2010, updated 18 July 2020). Dissent that never becomes a stated objection is the part a vendor cannot see.

Two surveys give the picture some shape. HubSpot Japan's 2026 survey of B2B buying in Japan (published 16 July 2026, fieldwork by Macromill, n=1,573, companies with 50 or more employees, self-reported) found that five or more internal people were involved in 46.9% of purchases and two or more vendors were compared in 80.3%. A smaller survey reported by ASCII STARTUP (14 May 2026, run by NK Energy Systems, n=100) found that 30.8% of buyers had told the rep "everything" about what happened internally; the main reason for silence was resistance to sharing before internal agreement existed (61.9%). The second survey is too small to stand for Japan; use it to see where the gap sits.

What the rep holds, then, is the portion of the story the contact decided could go outside the company. What was compared inside the ringi and who stopped it may be only partly known to the contact themselves. The interview's job is to rebuild that sequence in the buyer's own words.

Who asks

The rep who ran the deal should not ask. The buyer will choose an answer that spares the person across the table, and the rep has a stake in the recorded reason (Mazrica, above). Inside the company, product marketing, business planning or a colleague from another team can ask. Open by saying you were not on the deal, you will not sell during the call, and what the answers will be used for. For a US team, the interviewer also needs working business Japanese; an interpreter adds a third party to the call, which is another point to raise with your legal team.

For sensitive accounts, a third party is an option. Clozd, a US win-loss firm, writes that buyers rarely give harsh feedback to the vendor who pitched them and that a neutral third party removes this "politeness bias" (updated 21 April 2026). Clozd sells third-party interviews, so that is a vendor's view. In the Japanese-language searches run for this lesson, no service or guide for third-party lost-deal interviews with Japanese buyers turned up. Do not assume Japanese companies routinely use one.

Ask for the sequence of the decision

Phrase questions as "how did it proceed" rather than "why". "Why didn't you choose us?" asks the buyer for a judgment, which invites the polite answer. "Who drafted the proposal internally, and in what order did it move?" asks for events, and events come with names and documents attached. Neutral wording, refusals, memory gaps and the note sheet are covered in the neutral win-loss interview guide; this lesson adds only what changes for a Japanese buyer.

Takahashi's interview (above) groups its approach under three headings: how close the contest was (接戦状況), the scene of the decision (決定の場面), and the background behind it (裏にある背景). The article body sits behind a login, so the questions under those headings are not quoted here. The examples below were written for this lesson and are not his wording.

1. How close it was

   "How many vendors were still in at the end, and at what stage were we still under consideration?" Check: the answer contains a number and a stage. "It was a good proposal" on its own means asking again how many were left.

2. Where the decision was made

   "In which meeting or document was the decision fixed, and what was attached to the ringi?" Check: a meeting, a document or the drafter's role appears. If none does, record it as a part the contact did not see.

3. What was behind it

   "Did anything change in your internal situation or priorities around the time of the decision?" Check: the timeline runs forward from events to the outcome. An account reasoned backwards from the result is recorded with that note attached.

4. Price, once, as a comparison and a person

   "Who asked for the cost-effectiveness material, and what figure was it compared against?" Check: the answer names a comparison, a person or a document. If all you get is "it was expensive", stop there and record that.

Hand the transcript to Claude in Japanese, with speaker labels, rather than in translation. Anthropic's multilingual guidance says that stating the input and output languages explicitly improves reliability, and recommends native script over transliteration (checked 7 October 2026). For a repeating study, keep the guide, the reason list and the note sheet in one Claude Project, set up as in the Project setup lesson.

Prompt: tag a Japanese transcript against the reason list

Below is a lost-deal interview transcript in Japanese, with speaker labels.
Using only the items in the attached loss-reason list, tag each passage
that fits one. Quote the buyer's own words, in Japanese, under every tag.
Where the words do not support a tag, write 不明 (unknown) and do not guess.
Do not add an interpretation of what the buyer "really meant".
Reply in English, keeping the quotations in Japanese.

Claude reads only the text it is given. Pauses, hedges and the remark made after the recording stopped survive only if the interviewer adds them in brackets the same day. A terse answer is normal in this setting and goes into the record as it is.

A loss-reason list with ringi in it

None of the Japanese lost-deal analysis pages opened for this lesson (Salesforce Japan, Mazrica, Sansan, Hitachi Solutions, StartLink) lists ringi as a loss reason of its own. They have price, competition, product and features, timing and sales execution, and nowhere to put "the contact backed us and the ringi stalled". The list below is this lesson's proposal. It has not been tested at any company. Keep it next to the CRM picklist and map interview statements onto it.

• Insufficient material for the ringi: the contact could not produce a cost or vendor comparison
• Did not reach the decision-maker: the review stopped beyond the contact
• Weak recommendation from the contact: they backed another candidate
• Shelved for lack of internal agreement: never drafted, rather than rejected
• Incumbent retained: switching effort was the deciding factor
• Price: record what it was compared against and who requested the figure
• Features and requirements: name the requirement that was not met
• Timing: budget year or overlap with another project
• Unknown: the buyer did not know, or did not say

Do not force an interview into one tag. Record a finding such as "the contact recommended us, but could not produce a cost comparison against the other vendor for the ringi" with the quotation and a note that this is one person's account. Setting that beside the CRM's "price" is the central result of the study; win-loss interviews versus CRM loss reasons covers the comparison itself.

Recording, notes and Japan's personal-information law

The name, role and voice of the person you interview can be personal information under Japan's Act on the Protection of Personal Information (APPI). This lesson does not say what the law requires of you.

• Purpose: what will you tell the buyer the recording and notes are for, and when and how will you tell them?
• Research, not selling: how will you make clear that the call is research and that taking part is voluntary? The Japan Marketing Research Association publishes a code for its members that is worth reading as a benchmark.
• Transfers: if a transcript goes to a vendor or a tool outside Japan, what consent or notice does your counsel want first?
• Third-party information: if the buyer starts reciting a competitor's confidential quote, you can stop and leave it out of the notes. Ask your counsel how to handle it.
• Thanking interviewees: if you plan to offer anything of value for taking part, ask your counsel whether Japan's rules on premiums and representations apply to a B2B lost-deal interview.

Where Steve fits, and where it does not

Nothing in this method needs software. What stops holding is the work around twenty or more interviews: scheduling, reminders and same-day notes. The DIY remedy is one shared note sheet, one Claude Project and a native-speaking third party for the sensitive deals.

Steve Win/Loss does a narrower job. As the site describes it, when a deal closes won or lost in HubSpot or Salesforce, Steve invites the buyer to an AI interview. The AI interview asks follow-up questions to clarify a response. Your team reviews what buyers said. You click Generate Summary when new responses arrive, and a buyer theme lands in the battle card's Objection Handling for your team to review.

Three points apply as of the site check on 7 October 2026. The invitation comes from your own Steve workspace, so it is not a neutral third party. The site does not state the interview language. Questions about data handling and personal-information law are for your legal team and the provider. It does not replace the interview this lesson teaches; it covers the deals nobody would have interviewed. If collection is the step that stops, see Steve Win/Loss.