Why Japanese Enterprise Buying Is Slow: It's the Queues

Large Japanese companies don't decide slowly. They wait slowly. Between a good first meeting and a signed contract sit three queues: the internal approval document called the ringi, a proof of concept, and the IT department's security questionnaire. If you plan your first year in Japan around how fast decisions get made, you will hire the wrong people.

Where does the time actually go?

Mostly into waiting for the next person. The approver is busy this week. The meeting moved to next month. The one person in IT who reads vendor questionnaires has six others ahead of yours.

I don't know of any official statistic on how long enterprise purchases take in Japan, and I've looked. What exists are surveys run by software vendors. The samples are small and the vendors have something to sell, so read them for direction only. They do point the same way.

In August 2026, NTT Data Business Brains asked 221 business and administrative managers about the most common approval request in their department. 64.4% said it needed three or more approvers. 61.1% said approval took two days or more, and 28.7% said a week or more. The striking number: 76.0% said at least half of the approval stamps on the form were there to confirm or circulate, not to decide.

That survey covers internal approvals of every kind. A purchase from an outside vendor adds a contract, a budget line and an information security review. It does not get shorter.

So when your Japan team writes "client is going through internal process" in the weekly report, they are usually telling the truth. The problem is that headquarters reads it as "closing next week."

Who writes the ringi?

Not you. The ringi is written by someone inside the client, usually a section manager in the department that wants your product. In Japanese this person is the kian-sha, the one who drafts. They have to explain on paper why the company should buy, why from you, what it costs and who is responsible if it goes wrong. Then it travels up the chain set by the company's approval authority rules. The bigger the amount, the more senior the final signer and the more stamps along the way.

Foreign vendors tend to miss this part. Your real competitor at this stage is the drafter's calendar. Writing the ringi is extra work on top of their actual job. If your materials are thin, it sits. If they can't answer a question from their boss, they book another meeting with you.

So half of enterprise selling in Japan is writing for the drafter. An estimate of the benefit. How it connects to the systems they already run. Who to call when something breaks. Case studies from their own industry. In Japanese, in a form they can paste straight into the ringi. A salesperson who is great at demos and price negotiation has little to do here.

Design the proof of concept from the end

Japanese clients like a PoC because it gives the drafter evidence the company tested the thing itself. That's reasonable. What goes wrong is a PoC with no definition of success. Three months later the report says "some effect was confirmed, we'd like to try a wider scope," and another three months begin.

The ones that move have a few things in common. Test items and pass criteria are agreed in writing before the start, ideally in the client's own KPIs. Scope is one department or one workflow. Price is clear: free is fine, but the document says what happens after a pass, including a rough price for production. And the security questionnaire and draft contract go in during the PoC. Don't wait for it to end. Run the queues in parallel or they add up end to end.

If you can't get any of that agreed, I'd think twice about the PoC. You are probably testing whether the client has budget this year, not whether your product works.

Why the security questionnaire never ends in one round

Because the people reading it don't share a ruler either.

The questionnaires are multiplying for a reason. Japan's Information-technology Promotion Agency (IPA) publishes a yearly list of the top ten security threats to organizations. In the 2026 edition, released in January, attacks through the supply chain and outsourcing partners ranked second, on the list for the eighth year running. Companies that got hurt through a vendor tighten the door. In a SecureNavi survey of 780 people in January and February 2026, 68% said requests to fill in security questionnaires had increased.

Now the other side of the desk. In June 2026 the same company asked 400 people who run vendor and system security reviews. Only 22.5% said their criteria were clear enough that anyone could make the call. 60.5% felt the review work would stop keeping up if nothing changed. At companies with 1,000 to 9,999 employees it was 68.3%.

In sales terms: you submit your answers, a different person in IT reads them, and ten follow-up questions come back. Which country the data sits in. Who can access it. How many hours until you notify an incident. Which third-party certification you hold. Each one costs an email round trip and about a week.

The fix is boring. Build a library of standard answers in Japanese. Have certifications and audit reports ready before anyone asks. Put data location and incident notification on one page. Name one person who can answer technical questions in Japanese. That person doesn't have to be in sales.

What this means for your first-year headcount

If a deal takes a year, you need fewer people in year one, and different ones.

The common pattern is to hire a row of salespeople on quarterly quotas, the way you would at home. But if a large account takes a year to close, year one brings in close to zero of them. Those salespeople are building pipeline for year two. Hire five and you have prepaid five person-years for next year's revenue. By month six they've missed quota twice, half of them leave, and their pipeline leaves with them.

What I'd do instead: one enterprise seller who understands how a ringi moves and can write Japanese material for the drafter, plus one presales person who can answer questionnaires and design a PoC. Take two or three clients all the way through. Log the date each gate opened and closed. Then decide how many to add in year two. I've argued before that your first hire in Japan should not be a salesperson, and why the order runs product, then sales, then organization.

All the survey numbers above come from vendors, with a few hundred respondents each. They don't represent Japanese companies as a whole. The numbers that will actually help you are five dates from your own first three deals: first visit, questionnaire received, PoC start, ringi drafted, contract signed. When headquarters asks when the big one will close, those dates are the only answer you can defend.