---
title: Why Foreign SaaS Stalls in Japan After Ten Customers
description: Foreign SaaS in Japan wins ten customers fast, then stalls at the mainstream. Moore's chasm, JUAS budget data, ringi, and the sales team each side needs.
image: https://nobusato.jp/hubfs/covers-2026-10/crossing-the-chasm-japan-saas-cover-en-2026-10.png
---

[Nobu Sato](https://nobusato.jp/en?hsLang=en)

[Profile](https://nobusato.jp/en/profile?hsLang=en) [Method](https://nobusato.jp/en/blog/method?hsLang=en) [Articles](https://nobusato.jp/en/blog?hsLang=en) [Glossary](https://nobusato.jp/en/blog/glossary?hsLang=en) [Contact](https://nobusato.jp/en/contact?hsLang=en)

[日本語](https://nobusato.jp/ja/blog/crossing-the-chasm-japan-saas)[English](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas)[中文](https://nobusato.jp/zh/blog/crossing-the-chasm-japan-saas)

Launching in Japan

In this article

1. [Where is the chasm?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s1)
2. [Who sits on the far side in Japan?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s2)
3. [How does a mainstream Japanese company buy one SaaS product?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s3)
4. [The two sides need two different sales organizations](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s4)
5. [How to cross](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s5)

[Launching in Japan](https://nobusato.jp/en/blog/tag/launching-in-japan)

# Why Foreign SaaS Stalls in Japan After Ten Customers

Foreign SaaS in Japan

[Nobu Sato](https://nobusato.jp/en/profile?hsLang=en)9 min read

Contents5

1. [Where is the chasm?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s1)
2. [Who sits on the far side in Japan?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s2)
3. [How does a mainstream Japanese company buy one SaaS product?](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s3)
4. [The two sides need two different sales organizations](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s4)
5. [How to cross](https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas#s5)

A foreign SaaS company's first year in Japan usually goes fine. Ten or twelve customers sign: subsidiaries of companies from back home, a few startups, one or two IT managers who like new things. Year two targets a hundred and ends at twenty. The sales team didn't get worse. The first ten customers and the next hundred are different animals, and in Japan the gap between them has a name and a procedure.

## Where is the chasm?

Between the early adopters and the mainstream. Geoffrey Moore's Crossing the Chasm (1991, third edition 2014) makes one argument: a new technology product can sell to the small group that likes to try things first, and the same approach will fail with the much larger group that buys on practical grounds. The book is still in print after thirty years. The gap hasn't closed.

Moore built on Everett Rogers' diffusion of innovations. Rogers split adopters into five groups: innovators 2.5%, early adopters 13.5%, early majority 34%, late majority 34%, laggards 16%. Moore drew his line between 13.5% and 34%. People on the left buy possibility and will gamble on an incomplete product. People on the right buy the fact that someone like them already uses it and nothing went wrong. They want a whole product, references from their own industry, and someone to call when it breaks.

The theory is contested, and I should say so. Rogers himself rejected it: past research, he wrote, shows no support for a chasm between adopter categories, and innovativeness is continuous. I use the chasm as a sketch, not a law. In Japan the sketch happens to fit unusually well.

## Who sits on the far side in Japan?

Mainstream Japanese companies, meaning the ninety you were counting on in year two. They are spending. The Japan Users Association of Information Systems (JUAS) surveyed 957 listed and comparable companies for its 2026 IT trends report. 52.6% raised their IT budget for fiscal 2025, and the budget diffusion index of 43.3 was the highest planned figure in ten years.

Look at where the money goes. The top reason for raising the budget was refreshing or expanding existing systems, cited by 66.3%. Growth in cloud services came next at 45.0%, then AI-related spending at 36.3%. Asked what DX is for, the most common answer was cutting costs in existing businesses, 36.1%. Entering new businesses or rebuilding the business model: 13.5%. On development, roughly seven in ten said they aim to combine in-house work with outsourcing. The incumbent system integrator isn't going anywhere.

So the far side looks like this. Budgets up. Money to old systems first. New tools welcome if they cut cost. Vendors unchanged. That is Moore's pragmatist. [Over 80% of Japanese companies already use the cloud](https://nobusato.jp/en/blog/eighty-percent-use-cloud-what-for?hsLang=en), and Fuji Chimera Research puts Japan's public cloud market at 3.44 trillion yen in fiscal 2024, heading for 6.25 trillion by fiscal 2030. The same release notes that large companies are adopting "Fit to Standard," reshaping their processes around SaaS defaults rather than customizing. The far side is buying. It just buys differently.

Early customers are 16% of adopters. On the far side, new budget goes to old systems first

Top: Rogers' five adopter categories (%, Diffusion of Innovations, 5th ed., 2003). Bottom: reasons listed companies raised their fiscal 2025 IT budget and the purpose of DX (multiple answers, %, JUAS IT Trends Survey 2026, 957 companies)

Where your first ten customers sitOther

**Adopter categories**　16% left of the chasm, 84% right

- Innovators

  2.5%
- Early adopters

  13.5%
- Early majoritypragmatists; the chasm starts here

  34%
- Late majority

  34%
- Laggards

  16%

**Where far-side budget goes first**　Japanese listed companies, fiscal 2025

- Reason for higher budgetrefresh or expand existing systems

  66.3%
- Reason for higher budgetmore cloud services

  45.0%
- Purpose of DXcut costs in existing business

  36.1%
- Purpose of DXnew business or business model

  13.5%

Your first ten are on the left. The next hundred are on the right. The right side is buying, just not the way the left did.

Figure 1. In Rogers' categories, innovators and early adopters add up to 16%, and Moore placed the chasm between that 16% and the 34% early majority. Among 957 Japanese listed companies in the JUAS 2026 survey, the top reason for raising the fiscal 2025 IT budget was refreshing existing systems (66.3%), and the top purpose of DX was cutting costs in existing business (36.1%), with new business at 13.5%.

## How does a mainstream Japanese company buy one SaaS product?

Through four gates, over nine to eighteen months. First, someone in a user department has to sponsor it and be able to explain internally why. Second, the IT department runs a security review: a questionnaire of dozens to a few hundred items on where data lives, who can access it, and how incidents are reported. Third, procurement and legal read the contract, in Japanese, with an SLA, exit terms and data ownership. Fourth, ringi, the circulating approval document that collects seals one level at a time. I wrote in [the first-year budget piece](https://nobusato.jp/en/blog/first-year-budget-overrun-in-japan?hsLang=en) that mid-sized companies and up take nine to eighteen months from first visit to signature. SaaS gets no exemption.

From overseas this reads as "Japanese companies are cautious." I'd put it differently. They are pragmatists in Moore's sense, and they only buy in a form where someone on their side can carry the responsibility.

There's a gate that isn't on the flowchart: the incumbent system integrator. Most Japanese companies' systems were built and are maintained by an SIer. A new SaaS product gets sold by the SIer, accepted by the SIer, or blocked by the SIer. In [the country with the most century-old companies](https://nobusato.jp/en/blog/country-of-century-old-companies?hsLang=en), supplier relationships are hard to pry loose, and software is no different.

Two public cases show the crossing. Slack launched its Japanese version in November 2017, and by January 2019 it was calling Japan its second-biggest market. The Japanese customers it names include Mercari and Sansan, classic left-of-chasm companies, and also Musashi Seimitsu, a manufacturer based in Toyohashi with more than 16,000 employees that rolled Slack out company-wide in 2018. Manufacturing, 16,000 people: the far side. Slack then announced a Japan data region planned for the first quarter of 2020. ByteDance's Lark is on the same road. Lark Japan keeps all data on servers inside Japan, and in March 2025 it signed the listed company NEXYZ.Group as a "platinum partner," so a Japanese company sells to Japanese companies. Both did what Moore calls the whole product: the Japanese language, local data, partners and rollout support that sit outside the software itself.

## The two sides need two different sales organizations

On the left, the founder or someone sent from HQ sells directly. Show the product, find agreement, sign. The right side needs a different cast. An enterprise account executive who has sold inside large Japanese companies, knows the rhythm of ringi, and can draft the paper the customer's champion has to submit internally. A partner manager whose whole job is SIers and resellers. A presales engineer who answers the questionnaire and writes the technical documentation. A customer success manager who owns rollout, training and the first renewal. The left side needs none of these four roles. The right side can't skip any.

One condition is harder than hiring: the Japan entity must be able to set service levels and partner terms itself. Far-side customers ask whether Japan can decide when something goes wrong. "We'll check with headquarters" ends the ringi. I laid out which decisions belong in Japan and which at HQ in [Product, sales, organization: why this order](https://nobusato.jp/en/blog/method-product-sales-org?hsLang=en).

The failure patterns repeat. Promote the left side's best seller to country manager ([I wrote about that one separately](https://nobusato.jp/en/blog/dont-promote-your-best-seller-to-country-manager?hsLang=en)); the way they sell doesn't exist on the right. Set right-side quarterly targets at left-side closing speed; the team breaks up within six months. Attack large, mid-sized and small companies at once with one salesperson each; attention spreads thin and no tier gets crossed. [Pick one tier for the first two years](https://nobusato.jp/en/blog/smes-are-99-percent-who-do-you-sell-to?hsLang=en) is the rule that matters most in SaaS.

## How to cross

Moore's prescription is narrow on purpose. Don't spread. Pick one vertical, solve its most painful problem completely with a whole product, win one or two mainstream reference customers, and use their case to move into the next vertical. He calls it bowling: knock down the first pin.

Applied to Japan, my view is this. One tier, one vertical, for two years. Treat customers tied to your home country as revenue and never as evidence; they don't prove that a mainstream Japanese company will buy. Discount the first reference customer if you must, in exchange for a public case study with their name on it. And the first KPI for your Japanese sales hire should be a drawn map of one mainstream prospect's ringi path: who initiates, who reviews, who approves, and how many weeks each step takes. Without that map there is no road to the next hundred.

Two notes to myself. Rogers' objection stays with me; the Japanese chasm may be a slope rather than a line, and I can't say at which step you count as across. And one thing has nothing to do with the product. A Chinese vendor gets a few extra questions on the security sheet: which country the data sits in, which law governs, who the parent company is. Concern or pretext depends on the customer. Inside the ringi, they are questions you need an answer to before you walk in.

Sources (as of October 2026)

- [Japan Users Association of Information Systems (JUAS), IT Trends Survey 2026 (fiscal 2025 survey), summary (April 2026, 957 companies)](https://juas.or.jp/cms/media/2026/04/JUAS_IT2026summary.pdf)
- [CommercePick, report on the JUAS IT Trends Survey 2026 flash results: budget DI and reasons for increases (February 9, 2026)](https://www.commercepick.com/archives/85146)
- [@IT, report on the JUAS IT Trends Survey 2026: purpose of DX, in-house vs outsourced development (June 11, 2026)](https://atmarkit.itmedia.co.jp/ait/articles/2606/11/news048.html)
- [Fuji Chimera Research Institute, press release on "2025 Cloud Computing: Current State and Outlook, Market Edition" (September 5, 2025)](https://www.fcr.co.jp/pr/25090.htm)
- [Ministry of Internal Affairs and Communications, 2024 Communications Usage Trend Survey, key points (May 2025)](https://www.soumu.go.jp/main_content/001011527.pdf)
- [Geoffrey A. Moore, Crossing the Chasm (1991; 3rd ed. 2014), and Rogers' rebuttal, Wikipedia entry](https://en.wikipedia.org/wiki/Crossing_the_Chasm)
- [Everett M. Rogers, Diffusion of Innovations, 5th ed. (2003), chapter 7, "Innovativeness and Adopter Categories"](https://www.powells.com/book/diffusion-of-innovations-5th-edition-9780743222099/2-5)
- [Slack, 10 million daily active users, Japan as second-biggest market, Musashi company-wide rollout (January 29, 2019)](https://slack.com/intl/zh-cn/blog/news/slack-has-10-million-daily-active-users)
- [Slack, growth in Asia: Japanese launch on November 17, 2017, Japanese customers including Mercari and Sansan, planned Japan data region (October 16, 2019)](https://slack.com/intl/es-bo/blog/news/slacks-growth-in-asia)
- [NEXYZ.Group and Lark Japan partnership press release: platinum partner, data stored in Japan (March 17, 2025)](https://www2.infomart.co.jp/web/jp/images/upload/3162/140120250317595120_20185418.pdf)

---

Author

[Nobu Sato](https://nobusato.jp/en/profile?hsLang=en)

Launching in Japan, starting with people and systems. I write about building organizations, sales teams and technology organizations in Japan, in English, Japanese and Chinese.

[Profile](https://nobusato.jp/en/profile?hsLang=en)[Contact](https://nobusato.jp/en/contact?hsLang=en)

## Read next

1. 01[Your first hire in Japan should not be a salesperson](https://nobusato.jp/en/blog/first-hire-in-japan-should-not-be-sales?hsLang=en)8 min
   
   HQs hire sales first in Japan. Then customers ask for Japanese materials, a local contract, a support promise, and ...
2. 02[What one hire in Japan really costs: 1.2x to 1.5x salary](https://nobusato.jp/en/blog/true-cost-of-hiring-in-japan?hsLang=en)5 min
   
   A ¥6m hire in Japan costs about ¥7.1m a year from year two and ¥9.2m in year one with an agency. Employer social ...
3. 03[Why your first-year budget in Japan runs over by half](https://nobusato.jp/en/blog/first-year-budget-overrun-in-japan?hsLang=en)5 min
   
   In one market-entry survey, over half budgeted under 50M yen and 65% later needed 1.5x or more. The gap is people cost, ...

[Column guide: Launching in Japan](https://nobusato.jp/en/blog/guide-launching-in-japan?hsLang=en) · [Glossary](https://nobusato.jp/en/blog/glossary?hsLang=en) · [The method behind the articles](https://nobusato.jp/en/blog/method?hsLang=en)

[← All articles](https://nobusato.jp/en/blog?hsLang=en)

## Writing about launching in Japan, in three languages.

[Profile](https://nobusato.jp/en/profile?hsLang=en) [Get in touch](https://nobusato.jp/en/contact?hsLang=en)

Nobu Sato

Writing about launching in Japan, in three languages.

[info@nobusato.jp](mailto:info@nobusato.jp) [Substack](https://nobusato.substack.com)[Newsletter](https://www.linkedin.com/newsletters/the-japan-entry-memo-7519750783555518464/)[Medium](https://medium.com/@nobusato5888)[LinkedIn](https://www.linkedin.com/in/realnobusato/)[X](https://x.com/nobusato5888) [RSS](https://nobusato.jp/en/blog/rss.xml?hsLang=en)

[Profile](https://nobusato.jp/en/profile?hsLang=en)[Method](https://nobusato.jp/en/blog/method?hsLang=en)[Articles](https://nobusato.jp/en/blog?hsLang=en)[Glossary](https://nobusato.jp/en/blog/glossary?hsLang=en)[Contact](https://nobusato.jp/en/contact?hsLang=en)

Views here are my own and don’t represent any organization I work or have worked for.

© 2026 Nobu Sato. All rights reserved.·[Privacy and disclaimer](https://nobusato.jp/en/privacy?hsLang=en)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en",
    "name" : "Home",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en/blog",
    "name" : "Articles",
    "position" : 2
  }, {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas",
    "name" : "Why Foreign SaaS Stalls in Japan After Ten Customers",
    "position" : 3
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas",
  "@type" : "WebPage",
  "about" : {
    "@type" : "Thing",
    "name" : "Launching in Japan"
  },
  "author" : {
    "@id" : "https://nobusato.jp/#person"
  },
  "description" : "Foreign SaaS in Japan wins ten customers fast, then stalls at the mainstream. Moore's chasm, JUAS budget data, ringi, and the sales team each side needs.",
  "inLanguage" : "en",
  "isPartOf" : {
    "@id" : "https://nobusato.jp/en/blog",
    "@type" : "Blog",
    "name" : "Articles"
  },
  "keywords" : "Launching in Japan",
  "name" : "Why Foreign SaaS Stalls in Japan After Ten Customers",
  "url" : "https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nobusato.jp/#person",
  "@type" : "Person",
  "alternateName" : [ "佐藤伸明", "Nobu Sato", "左滕" ],
  "description" : "Japan market launches: organization, sales and technology",
  "knowsAbout" : [ "Japan market entry", "Organization design", "Talent acquisition", "Sales organization building", "Technology organization building", "Japanese labor law" ],
  "name" : "Nobu Sato",
  "sameAs" : [ "https://www.linkedin.com/in/realnobusato/", "https://x.com/nobusato5888" ],
  "url" : "https://nobusato.jp/en/profile"
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Nobu Sato",
    "url" : "https://nobusato.jp/en/blog/author/nobu-sato"
  },
  "dateModified" : "2026-10-29T14:49:51.385Z",
  "datePublished" : "2026-10-29T14:49:51.000Z",
  "headline" : "Why Foreign SaaS Stalls in Japan After Ten Customers",
  "image" : [ "https://nobusato.jp/hubfs/covers-2026-10/crossing-the-chasm-japan-saas-cover-en-2026-10.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://nobusato.jp/en/blog/crossing-the-chasm-japan-saas",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://nobusato.jp/hubfs/seo/logo-nobusato-2026-10.png"
    },
    "name" : "nobusato.jp"
  }
}
```