In Japan, 'we'll take it back' is a handoff, not an answer

Published Sep 24, 2026

The meeting in Tokyo went well, by the rep’s account. At the end, the buyer said they would take it back and consider it internally. The rep said they would follow up in two weeks. The deal moved to “evaluating” at 50%.

Two weeks later the rep called and asked how things were going. The buyer said they had not yet had a chance to discuss it internally. Repeat three times and the deal has been in “evaluating” for a quarter, with three logged calls and no change in stage.

HQ has two readings for that sentence. One camp hears a polite no, and wants the deal closed-lost. The other hears a slow yes, and wants it kept in the forecast. Both readings treat “we’ll take it back” as an answer. It is not an answer. It is a handoff, and your CRM has no field for it.

The subject of “take it back” is not the person in the room

In a US deal, “let me take this back” usually means the person you met will make a decision, or make a recommendation, and return with it. In Japan the person you met is rarely the one deciding. They are the one carrying the deal to the people who will.

What they carry it into is wide. IDEATECH, with Hiroyasu Kitagawa of Demagen Research Institute, surveyed 330 people on 25 and 26 May 2026 who had been involved, with at least one colleague, in buying, replacing or renewing B2B software, SaaS or IT infrastructure and security products at annual contract values of 5 million yen or more. Of them, 58.5% said seven or more people took part in the decision (n=325 for that question). The specialist functions involved were IT 42.2%, finance and accounting 38.2%, security 37.2%, legal 33.2%, procurement 32.0% (multiple answers).

So at the moment your rep hears “we’ll take it back,” the deal has moved to seven or more people nobody on your side has met. There is no handoff document. What your CRM holds is one line, “proposal sent,” and a task dated fourteen days out.

The caveat first: IDEATECH sells research-led PR and this survey doubles as a demonstration of that service, run on an online panel. Read the figures as order of magnitude and ranking. Seven versus three does not reverse. The precise 58.5 is not worth defending.

The wait sits before the ringi, where neither company’s system records it

HQ tends to assume the delay is the 稟議 (ringi), the circulated approval document that Japanese companies use for spend. The Japanese data points somewhere earlier.

Professional Tech Research Institute, part of Bengo4.com, surveyed 312 users of its CloudSign e-contract service between September and October 2024. Asked how long a ringi takes from submission to final approval, the largest group, 52.5%, said two to three days. Respondents skew towards companies that have already digitised approvals, so the real figure across Japanese firms is longer. Even so: once the document is filed, it clears in days.

The time goes before filing. Asked what was wrong with their approval process, 41.0% said too many people are involved before approval completes, and 35.9% said the consultation and groundwork before the ringi is even written takes too long. That pre-document consultation is the Japanese word 根回し (nemawashi), and it is what “we’ll take it back and consider” consists of.

This period appears in no system. Not the buyer’s workflow tool, because nothing has been submitted. Not your CRM, because your stage model has “proposal sent” and then “negotiation,” and nothing between them that belongs to the buyer. The longest stretch of a Japanese sales cycle is invisible from both sides. That is the structural reason “evaluating” lasts a quarter, and it has nothing to do with rep discipline.

A two-week follow-up fails because it is dated on your calendar, not the buyer’s

Fourteen days is a seller-side number. It has no relationship to when anything next happens inside the buyer’s company.

That is why the call has to open with “how is it going.” There is no event to ask about, so the rep asks for a feeling. The Japanese contact answers that they are considering it positively. In a Japanese deal that sentence is neither yes nor no. It is a report that nothing has happened yet. The rep logs “high interest,” moves the probability to 70%, and HQ sees a healthy pipeline. Nobody lied, and the forecast is wrong.

The fix is one instruction to the Japan team: before leaving a meeting that ends in “we’ll take it back,” ask where it is being taken. Who will they talk to. When does that conversation happen, and in what form: a word with their manager, a one-page summary circulated to the department, an item on the agenda of a regular meeting.

If the answer is “I’ll mention it to my director,” ask when they next meet the director. If it is “I’ll share it at next week’s department meeting,” get the date. This is not interrogation. It is logistics, and Japanese contacts respond to it as logistics, especially when the rep adds: “If there is material you could use in that meeting, we will prepare it. What format would help?”

Sometimes nothing comes back. No name, no date, no format. Read that as: there is no destination yet. The deal has not been declined, but it is not on anyone’s desk either. Foreign teams sometimes call “we’ll take it back” the politest no in the world. More precisely, it is a state in which whether it becomes a no has not been decided. Whether the CRM says “evaluating” or “no internal owner yet” changes what your forecast call argues about next month.

The material to send depends on the destination, and HQ’s default deck is the wrong one

Once the destination is known, what to send changes.

In the same IDEATECH survey, respondents were asked which content had actually helped as decision material (n=325, multiple answers). ROI calculators and payback estimation tools led at 55.4%, followed by case studies from the same industry or a similar company size at 46.5%. Internal presentation slides and executive summaries came in at 26.8%. Ringi application support material sat at 14.2%.

The deck HQ ships for “helping the champion sell internally” is second from the bottom. Explanatory material built without knowing which room it enters does not get used in that room. What ranks high is material that answers what the room will ask: a number the buyer can compute for their own case, and proof that a company like theirs has done this.

If finance is in the next room, the question will be the basis of the price and its monthly equivalent, not the value story. If IT is, it will be operating load and how the product connects to what already runs. If a department head can decide alone, one page about a similar company is enough. Knowing who sits in the room makes the material thinner, not thicker.

Date the follow-up the day after the internal event, and ask what came up

With a destination and a date, the follow-up goes the day after. Not two weeks out. The day after the department meeting, or two days after the one-to-one with the director.

The question changes too. Not “how did it go” but “what questions came up.” A question is evidence the deal actually reached the room. If finance asked about pricing, the next deliverable has just been specified. “Nothing in particular” means either it was not shared, or it was shared and nobody reacted, and in both cases the deal has not moved.

Japanese deals are read more accurately by whether objections are disappearing than by whether positive words are accumulating. A question surfaces, gets answered, and does not reappear in the next room. That sequence is progress. Three “they are positive” calls carry less information than one “finance asked us this.”

For HQ, two fields on the deal, separate from stage: the date of the buyer’s next internal event, and who the deal will be presented to there. These give you a second axis, independent of rep confidence, that says where the deal sits inside the buyer’s organisation. Adding stages such as “internal review” and “ringi in progress” was considered and rejected: it mixes progress and waiting into one column and makes the pipeline harder to read, not easier.

One more option not taken: a weekly touch-base email to keep the relationship warm. It is not harmful in itself, but an email with nothing to ask arrives, to the Japanese contact, as a weekly reminder that they have not yet managed to move it internally. Applying pressure from outside to the person carrying your deal inside is the slower route, even when it feels like activity.

The wider model, designing revenue around the buyer’s internal process rather than around seller activity, is in Japan Market GTM and Messaging.

In Japan, “we’ll take it back and consider” is not an answer but a handoff into the buyer’s organisation. Date the follow-up the day after the buyer’s next internal event, not two weeks out on your rep’s calendar, and ask what came up rather than how it felt.

This week, ask the Japan team for every open deal stalled after a “take it back”: can they write the buyer’s next internal event as a date. The number of deals where they cannot is the amount of Japan pipeline with no known destination.

Common mistakes

Closing the deal as lost because “take it back” sounded like a no. It is undecided, and the way to find out is to ask where it went, not to wait for a verdict.

Keeping it in the forecast because the contact is “positive.” Positivity is a report that nothing has happened. Progress is objections surfacing and then not recurring.

Shipping the global champion deck. The room it enters is finance, IT or a department head, and each asks a different question. Ask who sits there before sending anything.

Measuring the Japan rep on touch frequency. A weekly call with nothing to ask damages the contact’s standing internally. Measure whether the next internal event is known, and whether the follow-up landed the day after it.

When the destination turns out to be a ringi, what to hand over so that it actually moves is in In Japan, your champion cannot write the business case. Write it for them. This note is about learning where the deal went; that one is about what to send once you know.

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