Nemawashi: What Happens After Your Japanese Inquiry Goes Quiet

A Japanese company contacted you. The first exchange went well, you sent a specification sheet and a price, there were two or three rounds of sensible technical questions, and then nothing. Four weeks have passed. Your emails get short, polite replies that do not say yes and do not say no.

In most sales pipelines, that pattern means the deal is dead. In a Japanese B2B pipeline it often means the opposite: the buying organisation has started working on your proposal internally, and the work is invisible to you by design. The process has a name, nemawashi (根回し), and understanding it changes what you should do during the silence.

This article covers what happens inside the buyer’s organisation while you wait, how to read the difference between a deal in progress and a deal that is finished, and what to put in your contact’s hands so they can win the argument you are not in the room for.

What nemawashi is, and why it looks like nothing is happening

The word comes from horticulture. Digital Daijisen defines the original sense of nemawashi as cutting back the spreading roots of a tree one or two years before transplanting it, so that fine roots develop and the tree survives the move. The business sense follows directly: taking care of things in advance, in informal settings, so that a negotiation or a meeting goes smoothly when it finally happens.

In a Japanese company this is not a personality trait of a particular manager. It is how proposals are built. Before anything is formally tabled, the person sponsoring it talks individually to each colleague whose agreement will matter: the section chief in procurement, the quality assurance manager, the engineer who will have to work with your product, the finance controller, sometimes a director two levels up. Each conversation is a chance for that person to raise an objection privately, where refusing costs nobody any standing.

The practical consequence for a foreign supplier is uncomfortable. Visible activity stops at exactly the moment internal activity starts. Your contact goes quiet because their effort has shifted from you to their colleagues. From your side of the ocean, the strongest signal that your proposal is being taken seriously looks identical to being ignored.

The time this takes is not incidental. GLOBIS Europe cites Alex Warren, a former senior vice president at Toyota, describing Toyota spending nine to ten months on planning where competitors spent three, with engineers and line workers consulted before a proposal ever reached management. Toyota’s own management principles put it as making decisions slowly by consensus while considering all options, then implementing rapidly. A purchasing decision at a mid-sized industrial buyer is smaller than a Toyota programme, but the shape of the process is the same.

Nemawashi and ringi: two halves of one decision

Nemawashi has a formal counterpart. Once informal agreement exists, it is written up as a ringisho (稟議書), a proposal document that circulates for approval. Japanese workflow documentation describes the sequence as four stages: drafting (起案), circulation (回覧), approval (承認), and final authorisation (決裁). The document moves upward through the relevant departments, each approver marking it, until the person with authority signs it off and it becomes a decision of the company rather than of an individual.

The sequencing matters more than the paperwork. By the time a ringisho circulates, the substantive argument has usually already been had in the informal conversations. The document tends to record agreement rather than create it. Objections that were going to surface have surfaced, and the people signing have generally been spoken to beforehand.

For a supplier this has one clear implication. If you are holding back your strongest technical evidence for a formal presentation, or waiting for a decision meeting to make your case, you are aiming at the wrong moment. Your window of influence sits earlier, during the quiet period, and it operates through one person.

Your contact has become your advocate, and they are arguing without you

The engineer or sales manager who wrote to you is now carrying your proposal into rooms you will never enter, answering questions you will never hear, in Japanese. Their professional credibility is attached to your product. If it fails after they championed it, that is their problem to carry, internally and for a long time.

This reframes what your materials are for. Everything you send from this point has to survive being read without you present. A slide that works because you talk over it is worthless. A brochure written to create interest is the wrong genre entirely, because interest already exists. What your contact needs is evidence that answers a specific colleague’s specific objection, in a form they can forward or attach.

In technical purchases the deciding question is frequently not whether your product is the best available. It is what happens if it fails, and who absorbs the consequences. A buyer who switches to a foreign supplier and gets a bad lot has a supply problem, a customer problem, and an internal problem about why they changed. Materials that address performance but say nothing about failure leave your advocate holding half an argument.

What your first reply sets up

The quality of the silence is partly decided before it starts. A first inquiry from a Japanese company is frequently a test of how you handle information, not only a request for a price, and the reply you send becomes the first document that circulates.

Two habits are worth changing. The first is answering only the question that was asked. A request for a price on one item, answered with one price, gives your contact nothing to work with when a colleague asks about lead time or minimum order quantity. Answering the adjacent questions in the same message costs you little and saves a round trip that might take two weeks.

The second is qualifying aggressively on the first contact. Asking about volumes, budget, and timelines before you have given anything is normal practice in many markets and lands badly here, because at that stage the buyer may not know their own answer yet. The evaluation is often exploratory until the internal case is built, and the volume figure gets fixed late.

Send a complete, specific, dull reply. Confirm what you understood the requirement to be, state what you can supply against it, name the specifications you would need from them to be precise, and give a realistic lead time rather than an optimistic one. Precision early is read as reliability, and reliability is the thing being assessed.

One more point applies to inquiries arriving through a trading company or an agent rather than from the end user directly. Your contact may be relaying questions from a customer you cannot see, which makes documentation that stands on its own more important, not less. The questions will arrive filtered, and so will your answers.

Reading the silence: in progress, or finished

No single signal is conclusive. Read them together, and pay more attention to the shape of the questions over time than to their content.

The hedging point deserves care, because foreign suppliers routinely over-read it in both directions. A soft reply is not automatically a no. What makes it meaningful is the combination: soft language plus no new questions plus no new names plus no requests for material. Any one of those alone is noise.

The question that gets you a real answer

“Do you have an update?” and “Have you reached a decision?” are difficult questions to answer honestly mid-process. Your contact cannot tell you the outcome because the outcome does not exist yet, and saying so repeatedly is awkward. The usual result is a polite non-answer, which tells you nothing and costs you a little standing each time.

Ask about the process instead of the outcome. These are answerable without disclosing anything:

• “Is there any material that would help you explain this internally?”
• “Which department is looking at it now?”
• “Is there anything in our documentation that has raised a question we have not addressed?”
• “Is there a date by which you would need something from us, so we can plan production capacity?”

Each of these lets your contact be useful without committing the company. The first one is the most productive, because the honest answer is often specific: quality assurance wants lot data, or finance wants the landed cost, or someone asked whether you have supplied a Japanese customer before.

What to send while the ringisho is circulating

For technical products, documentation is not supporting material. It is the substance of the evaluation, and it is what circulates when you are not there. The list below reflects what tends to be requested by Japanese industrial buyers.

• A one page summary in Japanese. Not a translated brochure. Product, application, the two or three specifications that matter for their use case, certifications, lead time, and your contact details. Your advocate should be able to attach it to an internal mail without explanation.
• Specifications with tolerances stated explicitly, including behaviour at the edges of the range and outside it. A range without a statement of what happens at its limits invites the reviewer to assume the worst.
• Lot-level test data rather than typical values. Typical values describe a product. Lot data describes a process, which is what a quality department is actually assessing.
• Standards and certifications with numbers and dates, and a clear statement where a standard used in your market has no Japanese equivalent. Silence on that point becomes an open question in the review.
• A failure and remediation section. Defect rate history, what happens when a lot is rejected, replacement lead time, who pays for what, and how a problem is escalated across a time difference. This is often the section that decides the argument.
• Delivery performance data. On-time delivery rate and lead time variability, not just a nominal lead time.
• Reference customers, with industry proximity mattering more than size or fame.
• Landed cost, not unit price. Packaging, minimum order quantity, customs classification, applicable duty, and who acts as importer of record. A unit price that turns into an unpleasant surprise at the border damages the person who sponsored you.

None of this is exotic. Most technical manufacturers already hold this information. The recurring problem is that it sits in an engineering folder rather than in a form that survives circulation through five departments in a language the supplier does not read.

Five things that push the decision backwards

Chasing on a weekly cadence. Follow-up intervals calibrated to a Western pipeline read as pressure. Pressure applied to a consensus process tends to produce the safest available answer, and the safest answer to an unresolved question is usually no.

Escalating over your contact’s head. Writing to a director because the working-level contact is slow undercuts the person conducting your nemawashi. It can also embarrass them in front of the colleagues whose agreement you need.

Revising the offer mid-circulation. A new price or a changed specification arriving while a ringisho is moving can require the document to be redrafted and re-approved. What feels like a helpful improvement can cost weeks.

Discounting against a deadline. An unprompted price cut to force a close raises a question you do not want raised: what the original price was based on, and whether anything else in the proposal is similarly flexible.

Changing who is on your side of the relationship. Handing the account to a different salesperson mid-process resets trust that was built individually, and your new person will not know which objections have already been settled.

How long it takes, and what you get for it

There is no reliable single number. It varies with the size of the purchase, how many departments the change touches, whether you are displacing an incumbent supplier, and whether the buyer has bought from a foreign supplier before. Displacing an established domestic supplier takes longer than filling a gap nobody currently serves.

What is more predictable is the shape. The work is front-loaded, the decision phase is slow, and once a decision exists, implementation moves quickly because the objections were resolved before approval rather than after it. The same thoroughness works in your favour afterwards: a supplier relationship that took nine months to establish is not casually replaced by a competitor’s quotation, because switching would require the whole process to run again.

That is worth weighing when you decide how much effort a single Japanese inquiry deserves. The cost of entry is high and the cost of displacement is high, and those are the same property viewed from two directions. The broader mechanics of that trade-off are covered in our guide to doing business in Japan, and the sequencing of a full entry in the Japan market entry guide.

Doing this without a Japanese speaker in the company

Most of what has been described happens in Japanese, in conversations you are not part of. That is a structural constraint rather than an effort problem, and it shows up in the data. In JETRO’s FY2025 survey of foreign-affiliated companies in Japan, published in February 2026, 40.3 percent of respondents named language and communication barriers as a challenge of Japan’s business environment, second only to exchange rate volatility at 52.1 percent, from 1,423 responses to that question. Those are companies with an established presence and Japanese staff on payroll. An exporter handling inquiries from abroad has less visibility, not more.

Translation addresses part of this and not the most important part. A translated document gives you the words. It does not tell you that the question about replacement lead time came from a quality manager who was burned by an overseas supplier in 2019, or that the phrase your contact used in their last email was a request for help rather than a status update. Reading the situation requires someone who has sat on the Japanese side of this process.

For manufacturers with a real Japanese opportunity and nobody in-house who works in Japanese, that capability can be brought in without hiring for it. KAIZEN Digital OÜ provides Japan market entry support for technical B2B companies, including reading and responding to live inquiries, preparing the internal-facing documentation a Japanese buyer’s evaluation actually consumes, and telling you plainly when a deal has stopped moving.

The single most useful adjustment is smaller than any of that. When a Japanese inquiry goes quiet, treat the silence as a question about your documentation rather than a question about their interest, and ask your contact what would help them internally. The answer is usually specific, usually actionable, and usually something you already have.