Selling into Japan: Nemawashi, Ringi and the Committee You Can’t See

In Japan, most of a buying decision takes place outside the vendor’s line of sight.

You have a champion in a Tokyo account and a meeting booked with the executive who owns the budget. In the US, that is a late-stage deal. In Japan, it may not be. Nemawashi and ringi explain why.

Nemawashi builds the decision. Ringi approves it.

Nemawashi is consensus-building through informal discussion with everyone involved in a decision, usually before any formal meeting. A champion who likes your product is not the same as an organisation that supports the purchase. Internally, the question is not “is this the right software?” but “is this a proposal we can back?”

Along the way, the proposal changes. IT flags an integration issue, operations worries about the training load, and a company-wide rollout becomes a phased one with a different scope and cost. Nobody has gone off your product. The organisation is working out which version of the purchase it can support.

Ringi is the formal step that follows. A written proposal, the ringi-sho, makes the case for the decision and is circulated for approval. If reviewers are not satisfied, it is amended and resubmitted. By the time it reaches the executive, everyone involved has typically already agreed, so the signature confirms a decision more than it makes one.

That does not mean executives are bystanders. Erin Meyer’s Culture Map describes Japan as both strongly hierarchical and strongly consensual: authority is real, but it is exercised on a proposal that has already been prepared for it.

For a vendor, three things follow. The people in your meetings are only some of the people who matter. Middle managers and technical evaluators shape the proposal before it reaches senior review. And the document that gets approved is the customer’s, built from whatever evidence you have given them.

Influence without access

Most of the people who shape the decision are ones you will never meet, and it takes form in conversations you are not party to. Your influence therefore runs through what you leave behind: the quality of your material, the clarity of the proposal it supports and the preparation of the champion who carries both.

1. Equip your champion. They coordinate the consultation, so your job is to arm them, not shortcut them. Give every executive meeting a stated purpose, such as sponsorship, budget or resolving a specific issue, rather than treating it as a way past the process.

2. Reach the people behind the champion. Ask who is being consulted and who is coordinating it. Expect IT, operations and security reviewers to carry weight, and give each of them material written for their concerns. Plan for a local implementation partner where one is expected.

3. Give them a stable proposal. Settle price and scope early. A figure that changes after the proposal starts circulating can send it back through reviewers who had already agreed.

4. Leave room for the process. Pushing for a decision before internal alignment is complete can set the deal back. Ask what still has to happen, and what you can supply to help it happen.

Marketing: build content that works without you in the room

In a consensus-led organisation, your content will be read by reviewers you never meet, in discussions you never join. It has to carry the argument on its own, which is a fundamentally different brief from material written to support a salesperson’s presentation.

Asset	Built for a US committee	Built for nemawashi and ringi
Business case	ROI and payback, presented by the AE	Efficiency claims with explicit assumptions a reviewer can test without a call
Pricing	Negotiable summary, refined late	Stable scope and price, clear enough to quote in a proposal
Implementation plan	High-level timeline in the deck	A detailed plan with named responsibilities for vendor, partner and customer
Security and risk	Questionnaire answers on request	Proactive Japanese-language documentation for each affected function
References	Logo slide and a reference call	Written, circulation-ready references

The test for every asset

Could a reviewer who has never spoken to your team judge the purchase from this material alone?

Three steps to get your team ready

1

Build a Japan enablement kit

Japanese-language pre-reads, security documentation, an implementation plan and references, with a version addressed to each function that will review the proposal.

2

Confirm language needs account by account

Do not infer them from your champion’s English. A fluent contact may still need Japanese material for reviewers who will never join a call.

3

Measure circulation, not just meetings

Track how many stakeholders in each account have consumed your material, even if they have never met your team.

Sales: forecast the proposal, not the pipeline

The signal that matters in a Japanese deal is not the seniority of your contacts or the date of your last meeting, but where the customer’s internal proposal stands and what remains before it can be approved. Four questions, put to the champion on every opportunity, establish it:

1. Does this purchase require a ringi, and at what level must it be approved?

2. Who is being consulted internally, and who is coordinating that consultation?

3. Is the proposal being drafted, revised or circulated for approval?

4. What concerns have been raised, and have they been resolved?

Expect incomplete answers, and treat each gap as risk in the forecast: if you cannot say where the proposal stands, you cannot credibly say when it will close. Silence is no evidence of progress either, since a proposal under review and one that has stalled look identical from the outside.

Three changes for how your team operates

1

Forecast on proposal status

Deal stages should follow the customer’s internal process, not your own sales cycle.

2

Coach reps to ask, not press

In a formal meeting, the productive question is what remains to be done, not when the customer will decide.

3

Supply written answers that can circulate

When a reviewer raises a concern, a clear document your champion can pass on will often do more than another call.

The quiet work behind the deal

In the US, you win the decision-maker. In Japan, you win the people who build the decision.

That emphasis holds even where practice differs. Companies vary by size, sector and ownership, so treat nemawashi and ringi as a lens for discovery rather than a rulebook, and confirm in each account how consultation runs and what approval requires.

Is Japan on your expansion roadmap?

Our Buying Committee Matrix maps how enterprise buying committees differ across EMEA and APJ.

Partnership Fuels Global Growth

Markets evolve. Buyer behaviour shifts. But what drives lasting success is the ability to adapt with confidence and cultural fluency. The most successful SaaS companies don’t just expand, they learn, localize, and listen. They build systems that respect how each region buys, thinks, and grows.

At Accelerato, we help SaaS leaders do exactly that. If you’re ready to turn ambition into traction across EMEA and APJ, we’d love to partner with you.