The Last 10% of Japanese Localization

There's a thing about Japanese enterprise procurement that foreign teams rarely believe until it costs them something: buyers have already formed a judgment before they reach your feature list.

Last week I was reading the Japanese homepage of an enterprise AI cloud — the kind of platform that lists a dozen ISO certifications and links to a "Trust Center." The technology is genuinely frontier. The Japanese isn't broken, either. It mostly reads fine.

And yet a Japanese reader would flinch within seconds. So I counted.

1. In Japan, surface detail is read as a proxy for seriousness

Japanese enterprise buying is often described as deduction-based. Rather than accumulating reasons to say yes, the buyer removes reasons to worry and picks whatever survives. Under the ringi system, a champion has to keep justifying the vendor internally — to people who never sat in your demo. Which means anything hard to defend becomes a liability by itself.

That's where polish starts to matter. Before touching the product, a buyer can't measure your quality directly, so they read what's visible instead. Is the Japanese consistent? Is the terminology stable? How seriously does this company appear to take this market?

It may sound unfair. It isn't uniquely Japanese, though: everyone judges on visible signals when the real evidence isn't available yet. What's distinctive here is the resolution at which that judgment happens.

2. What the count actually showed — the problem wasn't lowercase

Here's the visible text of one homepage, counted (as of 27 July 2026):

Casing counts on one enterprise AI cloud's Japanese homepage (measured 27 July 2026)

Term	Uppercase	Lowercase
AI / ai	21	33
API / api	4	3
ID / id	1	1

I went in expecting a lowercase problem. Japanese IT writing capitalises AI, API, ID, SaaS — always — so lowercase reads as unfinished on its own.

What the count showed was worse. The page isn't consistently lowercase. Uppercase and lowercase coexist on the same page.

The company's own brand name appeared in three different casings — the official form 15 times, all-lowercase 9 times, and a third variant twice. Buyers are reading a page on which the company spells its own name three ways.

Two more symptoms from the same root: one product name appears with both upper- and lowercase variants on a single page — twice over, across two products — and one tagline still carries an untranslated Chinese descriptor.

Four symptoms. One cause: nobody read the whole page, once, before it shipped.

3. Why this hurts most on a page that sells trust

Here's why this example is worth your time.

The page in question is selling zero-trust. It's selling ISO 27001, SOC 2, verified controls, a Trust Center. Thirteen certification badges, lined up.

So the page asserts: we verify things down to the detail. And the Japanese carrying that assertion has not been verified.

Picture the buyer's moment. They're reading about zero-trust access control. In that same block, id and ID don't match. They won't say it out loud. They'll just think: "this is the level of consistency I'd be handing my access control to?"

Is that an unreasonable leap? I don't think so. Localization is a sample of how a company treats work it has decided isn't important. Buyers extrapolate from it to support quality and SLA discipline. A rough Japanese page delivers a message nobody wrote: Japan is an afterthought.

You can win on features and still lose here.

I've had my own Japanese described as "machine-translated." I hadn't noticed until someone told me. You can't see it in your own copy — that's what makes this layer so persistent.

4. The fix isn't a re-translation

The good news: this is not a rebuild. The Japanese works. What's missing is terminology discipline and one final native read.

Before	After
ai and AI coexisting on one page	standardised to AI
api and API coexisting	standardised to API
id and ID in the same block	standardised to ID
brand name in three casings	locked to one official form
product names varying in case	locked to official form
untranslated Chinese descriptor	rendered in Japanese

1. Build a one-page terminology sheet. Lock AI / API / ID / SaaS, your brand name, your product names, and the casing rules. It fits on one side of A4.

2. Have a Japanese native read the whole page once before it ships — someone other than the translator, as a final pass.

That's a day of work, not a project. The reason it goes unfixed isn't cost. It's that nobody inside the company can see that it's costing anything. English speakers can't perceive it; the Japanese hire hasn't started yet. In that gap, deals quietly get harder.

Over the past month I've walked through the Japanese pages of ten companies entering this market. Almost all were missing the same layer, to varying degrees. Which also means: closing it is still a way to stand out.

5. I'll read your last 10% for free

If you're bringing an English-first product into Japan, this layer decides whether enterprise buyers see a serious vendor or a tourist.

I do a free one-page "Japan-readiness read." I'll go through your Japanese pages and send back the specific lines that are costing you points with Japanese buyers. No deck attached. You're welcome to take the notes and do nothing else with them.

This article isn't intended as criticism of any specific company; the same pattern is common among foreign companies in their first year in Japan, which is why the company and its products are unnamed. Figures reflect a measurement of the public page as of 27 July 2026.

Related reading

• We Checked the Japanese Sites of 10 Leading SaaS Companies
• Why Japanese SaaS Users Distrust "Perfectly Correct" Translation
• Navigating Japanese Procurement and the Ringi Process