Japanese companies evaluate and approve SaaS purchases through a structured, consensus-driven process that usually takes longer than a comparable purchase in the US or Europe: as a planning assumption, two to three quarters for a mid-market deal and nine months to a year or more for an enterprise deal.
The longer timeline comes from two practices: nemawashi (根回し, informal consensus-building with stakeholders) and ringi (稟議, formal written approval). It also comes from the size of the buying group. In One Marketing’s 2025 survey of 600 Japanese B2B buyers, the average number of people involved in a purchase rose from 5.6 in the lowest price band (under JPY 3 million) to 14.4 in the middle band and 18.3 in the highest, and 54% of high-price purchases took six months or more from consideration to contract. In Medix’s 2020 survey of IT product selectors, 11 or more people was the most common answer at companies with more than 5,000 employees. Understanding this process decides how you structure outreach and set pipeline timelines.
The Japanese SaaS Buying Process

The buying process unfolds in five phases, each with its own participants and criteria. Foreign SaaS vendors most often underestimate phases 2 and 4, because they have no direct equivalent in Western enterprise sales.
| Phase | Who Is Involved | What They Evaluate | What Sets the Pace |
|---|---|---|---|
| 1. Discovery | IT department, department manager | Feature fit, shortlist via web search and review sites such as BOXIL and ITreview | How urgent the problem is and whether budget exists this fiscal year |
| 2. Nemawashi | Champion plus all key stakeholders | Internal alignment, political feasibility | The number of departments involved and the champion’s standing |
| 3. Evaluation | IT, Legal, Finance, end users | Trial or POC, security check sheet, contract review | How quickly the vendor answers in Japanese |
| 4. Ringi Approval | Management chain; how high it goes depends on the amount and the company’s approval rules | Formal sign-off on the ringisho (稟議書) | The approval route and the budget calendar |
| 5. Contract and Launch | Legal, Finance, IT | Japanese-language contract, billing terms | Legal review and the start of the next budget period |
Nemawashi: The Informal Consensus Layer
Nemawashi combines 根 (ne, root) and 回し (mawashi, going around). The term comes from preparing a tree’s roots before transplanting it. In business, it means consulting every key stakeholder informally before a formal proposal, so that no one is surprised and objections are settled privately before the formal decision. Our nemawashi glossary entry explains it in more depth.
For SaaS vendors, nemawashi means your internal champion will spend real time socializing the purchase across IT, Finance, Legal and department leadership before a formal proposal is written. Vendors who push for quick decisions or try to bypass this process often find that deals stall at the ringi stage, when a stakeholder who was not consulted objects.
The most effective approach is to support the champion’s nemawashi: provide Japanese-language materials for each stakeholder group, offer an executive-level conversation for the final approver, and be patient with the timeline. See also nemawashi in B2B SaaS deals.
Ringi: The Formal Approval System
Ringi is the formal, document-based approval system used in Japanese organizations. A ringisho is a written proposal that circulates through the management hierarchy for sign-off, usually starting below the decision-maker and moving up through department heads and division directors, and, for larger purchases, to the president. Which level must approve depends on the amount and on the company’s own approval rules.
The ringisho for a SaaS purchase typically covers the business case, the total cost, a summary of the security assessment, how personal data will be handled, and a comparison with the alternatives evaluated. By the time it circulates, the decision is largely “confirmed (rather than made)”, as an EU-Japan Centre report puts it. Vendors do not write the ringisho, but they can make sure every supporting document is complete and in Japanese before the champion drafts it. Our guide to ringi decision-making explains what the document needs.
Key Decision-Makers in a Japanese SaaS Purchase
| Role | Primary Concerns | Influence Level | When They Engage |
|---|---|---|---|
| IT Department (champion) | Security, integrations, personal data handling under APPI | Very High | All phases |
| Finance/Procurement | Annual contract, budget, billing format | High | Phases 2 to 5 |
| Legal | Japanese-language contract, data handling terms, liability | High | Phases 3 to 5 |
| Department Manager | End-user productivity, workflow fit | Medium-High | Phases 1 to 3 |
| CEO/Executive | Strategic fit, vendor reputation | Final approver for larger purchases | Phase 4 (ringi) |
| End Users | Ease of use, Japanese UI quality | Medium | Phase 3 (trial) |
What Influences the Final Decision
Five factors often decide whether a Japanese B2B SaaS purchase proceeds or stalls.
Japanese-language product and support. A Japanese UI, documentation and support channel is the baseline. In CSA Research’s survey of business software buyers in eight countries (2008), every Japanese respondent preferred to buy in Japanese, and only 5% were very comfortable buying in another language.
BOXIL and ITreview reviews. Buyers check reviews during discovery and nemawashi, and champions cite them in the ringisho. In ITreview’s March 2026 survey of people involved in IT purchases, 87.4% of those asked said too few reviews had led them to drop a product or lower its priority.
Japanese customer references. Existing Japanese customers who can speak to the vendor’s service and responsiveness are invaluable. A vendor with no Japanese references starts at a disadvantage against competitors who have them.
APPI compliance and data handling clarity. Under Japan’s Act on the Protection of Personal Information (APPI), the buyer must take security control measures for the personal data it handles (Article 23), supervise any vendor it entrusts with that data (Article 25), and follow special rules when personal data goes to a third party in a foreign country (Article 28). So Legal will ask where data is stored, who can access it and how it is protected; unclear answers stall deals at legal review. Our APPI guide covers the details.
Security questionnaire readiness. Japanese enterprise buyers routinely send a security check sheet (セキュリティチェックシート) before they approve a SaaS purchase. Vendors who answer quickly and completely, in Japanese, remove a common source of delay.
Key Takeaways
- Plan for a long sales cycle: As a planning assumption, two to three quarters for mid-market and nine months to a year or more for enterprise deals; in One Marketing’s 2025 survey, 54% of high-price B2B purchases took six months or more.
- Support the internal champion: The IT champion drives the evaluation but cannot decide alone. Equip them with Japanese-language materials for Finance, Legal and executives.
- Nemawashi cannot be rushed: Going straight to the final decision-maker to bypass informal consensus-building usually backfires and damages the relationship with the champion.
- APPI questions are a standard step: Legal review of how personal data is stored, accessed and transferred is part of most Japanese enterprise SaaS purchases. Prepare clear APPI documentation before entering Japan.
- Annual contracts are the enterprise norm: Most large companies budget once a year for an April to March fiscal year; monthly plans suit smaller buyers. See our annual vs monthly billing guide.
Working with Nihonium. We are a Japan go-to-market partner for B2B SaaS companies: Japan go-to-market strategy. Talk to us about your Japan entry.
Sources
- One Marketing, BtoB購買プロセス白書2025 (survey of 600 executives and purchasing staff, released 11 November 2025).
- Medix, 2020 IT product selector survey (516 respondents, November 2019).
- CSA Research, Businesses Prefer Local-Language Purchasing (2008 survey of business software buyers).
- ITcrowd, IT product selection white paper (survey of 300 people involved in IT purchases, March 2026).
- Japanese Law Translation, Act on the Protection of Personal Information: Articles 23, 25 and 28. Also cited: EU-Japan Centre for Industrial Cooperation, From Understanding to Navigating Japanese Business Culture (2018).
Frequently Asked Questions
Can a Japanese SaaS purchase be accelerated past the normal timeline?
Sometimes. An urgent business need, a regulatory deadline or a strong recommendation from an SIer partner can shorten the cycle, and so can an existing relationship with a key stakeholder or a Japanese reference customer in the same industry. Trying to rush the nemawashi phase, however, almost always backfires.
What is a ringisho and how can vendors support it?
A ringisho is the formal proposal that circulates for management sign-off during ringi approval. Vendors do not prepare it, but they can supply complete Japanese-language supporting materials: security assessments, APPI and data handling documentation, ROI calculations and a comparison with the alternatives evaluated.
How should foreign SaaS companies handle the security questionnaire?
Prepare a master Japanese-language answer set before you start selling in Japan. It should cover data location, encryption, access controls, incident response, APPI handling and certifications such as SOC 2 and ISO/IEC 27001. Answering a buyer’s check sheet quickly and completely signals operational readiness to Japanese IT departments.
Do Japanese companies prefer monthly or annual SaaS contracts?
Enterprise and mid-market buyers usually prefer annual contracts, because they fit a budget approved once a year and need only one ringi. Monthly plans lower the barrier for smaller companies and trials, and many vendors land on monthly and convert to annual at renewal. Offering a discount for an annual commitment is standard SaaS practice.
