Nobody at a Japanese company can say yes alone

You have been introduced to the right person. They are interested, they understand the product, and they have the title you would expect a decision-maker to have. They still cannot say yes.

This is not a failure of your qualification process. Japanese companies distribute authority differently, and the person who champions a proposal is usually not the person who approves it. Understanding the mechanism changes what you send, who you send it to, and how you read the silence afterwards.

What is ringi?

A documented approval process in which a proposal is written up and circulated for sign-off by everyone with an interest, before it becomes a decision.

The document is a ringisho. It is drafted by the person proposing the action — often someone fairly junior — and it moves through the relevant managers and departments, each of whom marks their approval. When it has collected the required approvals, the decision exists. Not before.

The word for the informal consensus-building that happens alongside it is nemawashi, literally “digging around the roots” before transplanting a tree. That is the part outsiders never see: the quiet conversations that ensure the document will pass before it is formally circulated.

Why is the proposal written by a junior person?

Because the process is designed to surface objections early and distribute ownership, not to concentrate judgement at the top.

A senior manager who imposes a decision owns its failure alone and has bypassed the people who will implement it. A proposal that has been circulated has been examined by everyone affected, and by the time it is approved, those people have already agreed. Execution is consequently fast — which is the trade the system is making for slow approval.

For you, the practical consequence is that your contact’s real question is not “do I want this?” It is “am I willing to write this up and carry it round the building?” Those are different questions with different answers.

What does this mean for what you send?

Your material is not addressed to your contact. It is addressed to the people they will show it to, and it should be built to survive that journey without you.

Concretely, a proposal that circulates well is complete, specific and quiet. It contains the specifications, the price basis, the supply terms, and the answers to the obvious objections. It contains claims a sceptical colleague in another department could verify. It reads as low-risk.

What travels badly: marketing language, superlatives, urgency, anything that requires the reader to have met you, and anything that would embarrass the person forwarding it. Enthusiasm does not survive circulation. Evidence does.

Which objections should you pre-empt?

The ones that come from departments you are not talking to. This is where foreign suppliers lose proposals they never knew were in trouble.

• Quality assurance: what certifications exist, what happens with a defective unit, who inspects
• Logistics: lead times, minimum orders, stock holding, customs treatment
• Finance: payment terms, currency, who carries the exchange risk
• After-sales: who answers the phone in Japanese when there is a problem
• Legal: which jurisdiction, what the contract looks like
• Continuity: what happens if you lose interest in Japan in two years

The last one is asked more often than foreign companies expect, and it is asked seriously. Japanese buyers have watched overseas suppliers enter the market, sell for eighteen months, and withdraw — leaving the buyer holding warranty obligations. Addressing it explicitly is disproportionately effective.

How long does circulation take?

Weeks to months, scaling with the size of the company and how novel the proposal is.

A small owner-run company may be genuinely quick, because the owner is the process. A large corporation evaluating its first foreign supplier in a category may take a quarter or more, and that is not a signal of disinterest.

Two structural factors compress or stretch this. The Japanese fiscal year usually ends on 31 March, and budget cycles cluster around it — a proposal arriving in February may wait for the new year’s budget. And Golden Week in early May, Obon in mid-August and the new year period each remove roughly a week of internal momentum.

How can you tell whether it is actually circulating?

By whether your contact asks you for the things they would need in order to write it up.

Requests for specification documents, certification copies, price breakdowns, sample units, or reference customers are the strongest available signal. So is being introduced to someone in another department — that is nemawashi happening, and you are being shown to the person whose objection matters.

Conversely, warmth without requests is not a signal. A contact who is enthusiastic but has never asked you for a document has not started writing anything.

Should you try to reach the top instead?

Generally no. Going over your contact’s head tends to end the process rather than accelerate it.

An approach that arrives at a senior executive gets referred back down to the department that would handle it — which is where you already were, except your contact now knows you went around them. In a system built on distributed consent, that is a costly move.

The exception is genuine executive-level introduction, where a mutual contact makes the connection at the top and it is then passed down with visible endorsement. That works because it arrives with sponsorship rather than as an escalation. It requires a relationship you either have or do not.

How do you help your contact instead?

Make their internal job easier and lower-risk. Everything follows from that.

Give them a document they can attach without rewriting. Answer questions in writing so the answer can be circulated rather than paraphrased. Provide anything that reduces perceived risk: certifications, a named support contact, a trial arrangement, a smaller first order than you would prefer.

That last point is worth dwelling on. A pilot order is often the fastest route to a yes, because it converts a large irreversible decision into a small reversible one — and small reversible decisions require fewer approvals. Insisting on committed volumes early is frequently what stalls the proposal.

Does this apply to smaller companies?

Less formally, but the underlying logic holds.

A twenty-person company will not produce a formal ringisho. The owner may decide over lunch. But even there, the expectation of internal agreement before commitment persists, and the same risk questions get asked — often more sharply, because a small company has less capacity to absorb a bad supplier.

The difference is speed, not structure. What does not change is that specific, verifiable, low-risk proposals outperform persuasive ones.

What should you actually change?

Three things.

1. Write for the third reader. Assume your document will be read by someone who has never spoken to you and is looking for reasons to object.
2. Answer the continuity question before it is asked. State what your commitment to the Japanese market is and what support exists locally.
3. Make the first step small. Ask for a trial, a sample evaluation, a limited first order. Reserve the large ask for after the first internal yes.

Where does outside help make a difference?

In two places: the quality of the circulating document, and having a local answer to the continuity question.

A proposal written in Japanese by someone who understands what a ringisho has to survive is a different artefact from a translated brochure. And a named Japanese company as your point of contact in the market answers “what happens when there is a problem?” concretely rather than in principle.

Our distributor discovery service prepares the material in Japanese and handles the correspondence, including the telephone follow-up that keeps a proposal visible during a long internal process. If what you need is a standing local presence so the continuity question has an answer, the Japan Desk assistant gives you a Japanese contact point by the month.