Eighty percent of Japanese companies use the cloud. For what?

Series「Five numbers to read before entering Japan」 · Part 5 of 5

What matters about cloud use in Japan is what it's used for, and the answer is mostly storing files. Japan's Ministry of Internal Affairs and Communications runs a survey on communications usage every year. In the 2024 results, more than 80% of Japanese companies use cloud services. Ten years earlier the figure was in the 40s.

Eighty percent can prove anything. If you want to say Japan lags on digital, you point out that the US passed 90% long ago. If you want to say it doesn't, you say 80% is mainstream. Neither gets near the question that matters to a software company entering Japan. What are those 80% using the cloud for?

Split by use

The same survey breaks it down. File storage and data sharing: 71%. Internal information sharing and portals: 57.6%. Email: 56.8%. Business systems such as payroll, accounting and HR: just over 50%. Schedule sharing: also just over 50%.

So 80% use the cloud, but most of them use the shallowest layer. They moved their files from local disks to the internet. The companies that have actually put business processes in the cloud are around half, and they cluster in payroll and accounting. Those are areas with statutory formats, where a company doesn't have to define its own process.

At the end of 2025 the SME support agency asked a thousand SMEs whether they were doing or considering DX. 39% said yes. That fits with everything above. Keeping files in the cloud isn't DX, and 60% of SMEs don't feel they need DX.

The usual argument: behind or not

Both sides are answering "what stage is Japan at?" That's a researcher's question. An entrant needs to ask something else. What kind of product can this market absorb right now?

The entrant's question comes before sales

When I design an entry, the order is two maps first, then product, then sales, then organization. At the product step I ask what this market is ready to accept, and what shape my product has to arrive in to be absorbed.

Here is what these numbers describe. Customers are used to putting things in the cloud. They are much less used to handing it their processes. They take to tools that replace something, like storage and communication, and lag visibly on tools that change how they work. There's a structural reason. Business processes in Japanese companies are very company-specific, and every firm does things differently. A SaaS product that asks customers to follow the software's process runs into one sentence in Japan: "our way is different."

HQ's product usually grew up in a market where processes are standardized and customers are willing to adapt to the software. Transplant it unchanged into a market where 80% store files, half run processes, and every process is different, and when it doesn't sell, the sales team isn't really to blame. The product's shape doesn't match what the market will accept.

Shape the product to what the market will accept

So the entry decision this number changes is what to change in the product first.

I'd start at the layer customers already use. Files and email are what 70% use. A new tool that comes in as "manage the files you already have in the cloud" gets through the door far faster than one that comes in as "replace your workflow." Next, make processes configurable instead of preset. Japanese customers will ask to do it their way, and the product needs room for that, even if the home version never did. And sell the substitution first and the change second. In year one you sell "the same as what you do now, but in the cloud." In year two you sell efficiency. Do it the other way round and year one ends at the door with "our way is different."

This is also the other half of the Conway's law post. That post asked which block of functionality the Japan team should own, and this is the answer. Localization means more than translating the interface. It means building the layer that makes processes configurable, and the Japan team should own that block completely.

A question for your own product

Take the product you plan to bring into Japan. Does it let customers put what they already have into the cloud, or does it ask them to change how they work? If it's the second, discount your year-one sales forecast on the assumption that half the market isn't ready.