We Checked the Japanese Sites of 10 Leading SaaS Companies. Most Failed.

Quick Answers

What did the teardown of 10 SaaS companies' Japanese sites find?

Five of ten companies had no Japanese site at all (404 or error page), one had removed a previously existing Japanese page, and most of the remaining Japanese pages contained copy that reads as machine-translated to native speakers — including grammatical errors in the first screen.

Why does this matter for SaaS companies?

Japan is the world's third-largest software market, and Japanese B2B buyers screen vendors by the quality of their Japanese web presence before ever contacting sales. Both a missing site and a machine-translated one fail that screen — one silently, one visibly.

How can I check my own site?

Take the free 2-minute Japan Readiness Score self-assessment at hirakilocalization.com/readiness-score, or request a free 1-page Japan Readiness Check reviewed by a native specialist.

TL;DR

I reviewed the Japanese web presence of ten leading SaaS companies as a native Japanese localization QA specialist, exactly as a Japanese buyer would encounter them. The results: five companies (Klaviyo, Typeform, Brevo, QuillBot, and Loom) have no Japanese page at all. ClickUp's former Japanese site now redirects to an English support page. Calendly's /ja URL resolves to a random user's booking page. Of the companies that do maintain Japanese pages — Pipedrive, Deel, and monday.com — every one shipped copy on its first screen that a native speaker reads as machine translation, including an outright grammatical error. The pattern is consistent: companies that invest heavily in product and global growth treat the Japanese web presence as a checkbox, and Japanese buyers notice within seconds.

Key Takeaways

• Half of the companies checked have no Japanese presence at all — meaning Japanese-language search traffic in their categories flows entirely to competitors.
• Every Japanese page we found had first-screen quality issues — not buried deep in documentation, but in the hero headline, the page title, or the consent banner.
• Grammatical errors survive in headline positions for months — because no native speaker with authority to fix them is looking.
• The failure is invisible from headquarters — the pages "exist," the translation vendor "delivered," and no Japanese buyer files a complaint. They just leave.
• The bar is low, which is the opportunity — in categories where every competitor ships machine-translated Japanese, one native-quality page is a visible differentiator.

The Method: Ten URLs, One Browser, No Mercy

The setup was deliberately simple. No crawlers, no audits of thousands of strings — just the first thing any Japanese prospect does: open the company's Japanese page and read the first screen. I checked the /ja path (or Japanese subdomain) of ten SaaS companies spanning CRM, HR tech, project management, email marketing, forms, video, and writing tools. For each, I recorded whether a Japanese page exists, what the page title says, what the hero headline says, and whether the copy would pass as written by a native speaker.

All findings below reflect what was live in early July 2026. Pages change; some of these issues may be fixed by the time you read this — which would be the best possible outcome for this article.

The Scoreboard

Company	Japanese page	What a Japanese buyer sees
Klaviyo	None — 404	An English "Sorry, that page isn't actually here" error. No official Japanese content anywhere.
Typeform	None — error page	An English "Sorry, we couldn't find that page!" error suggesting popular English pages instead.
Brevo	None — 404	An English 404 — despite Brevo maintaining localized sites in German, French, Spanish, and Italian.
QuillBot	None — 404	An English "It appears you are lost..." page. Notably, QuillBot sells a translation feature.
Loom	None — 404	"You weren't supposed to see this." An English 404 with a joke — while parent company Atlassian runs a full Japanese site.
Calendly	Not a company page	calendly.com/ja resolves to an individual user's personal booking page. The company's own Japanese namespace belongs to a random account.
ClickUp	Removed	The former Japanese site now lands visitors on an English support page. A localized presence existed — and was taken away.
Pipedrive	Exists — reads as MT	A first-screen trust statistic rendered with a grammatical error (detailed below), and copy with consistent translationese rhythm.
Deel	Exists — reads as MT	An awkward, literally-translated hero headline — and a cookie consent banner still in English on the Japanese page.
monday.com	Exists — reads as MT	A page title that translates the English tagline word-by-word into something no Japanese marketer would write.

Ten companies. Zero passed cleanly. For balance: during the same research session I also checked Hotjar, Gamma, and Smartsheet, all of which maintain notably better Japanese pages — proof that this is a solvable problem, not an inevitable one.

Teardown 1 — The Grammatical Error in the Trust Statement

Pipedrive's Japanese homepage leads its social proof with a customer count. The Japanese sentence structure used, however, contains a voice error — the passive form is attached to the wrong subject, producing the equivalent of "over 100,000 companies are being used" instead of "used by over 100,000 companies."

This is a one-line fix. What it tells a Japanese buyer, sitting in the most trust-critical sentence on the page, is that no native speaker with authority over the page has read it. The social proof line — the sentence designed to build confidence — is the sentence that breaks it.

Teardown 2 — The English Cookie Banner on the Japanese Page

Deel's Japanese page opens with a hero headline that strings four nominalized actions together in a way that mirrors English syntax rather than Japanese rhythm — recognizably a literal rendering of "hire, manage, pay and equip — anyone, anywhere." It is understandable. It is not natural. For an HR and payroll platform, where trust in operational precision is the entire product, "understandable but not natural" is an expensive place to be.

But the sharper finding is the consent banner: the first interactive element a Japanese visitor encounters on the Japanese page is a cookie notice in English. This is almost always a configuration issue — consent management platforms ship Japanese language packs — which makes it a minutes-long fix that instead greets every Japanese visitor as evidence the Japan presence is cosmetic. For a company whose product manages international compliance, the irony writes itself.

Teardown 3 — The Page Title Nobody Sighted

monday.com's Japanese page title renders the English positioning line into Japanese so literally that the result reads as decoration rather than meaning — the kind of phrase that fills space without telling a Japanese buyer what the product does or why it matters. Page titles are the single highest-leverage line of Japanese on any site: they are what appears in Google results, browser tabs, and shared links. A title that reads as translated is a first impression that reads as unserious — before the visitor even arrives.

The Five Companies That Aren't There At All

The absent half of the list deserves its own reading. Klaviyo has built one of the strongest e-commerce marketing platforms in the world, with obvious fit for Japan's massive Shopify ecosystem — and a Japanese search for the product finds nothing official. Brevo maintains localized sites in at least four European languages, so the localization muscle exists; Japan simply hasn't made the list. Loom's absence is stranger still, because its parent company Atlassian runs one of the more complete Japanese sites in SaaS.

ClickUp is the cautionary tale in reverse: a Japanese presence that existed and was withdrawn, leaving Japanese users to land on English support content. And Calendly's case is the one I'd frame for any web team: if you don't claim your /ja namespace, someone else effectively will — theirs currently serves a private individual's booking page.

The common thread: absence is not neutral. Japanese-language demand in these categories exists and searches in Japanese. It simply lands on whichever competitor bothered to show up.

What This Means If You Sell Software Globally

Two failure modes, one root cause. Companies without Japanese pages lose silently — no traffic, no signal, no complaints. Companies with machine-translated pages lose visibly — they attract Japanese visitors and then disqualify themselves in the first screen. In both cases the root cause is the same: nobody with native reading ability and organizational authority owns the Japanese surface.

The optimistic read: the bar in most SaaS categories is currently so low that modest, well-executed investment is immediately visible. One native-quality landing page with a correctly localized title, Japanese consent UI, and copy written for Japanese buying logic outperforms most of what this teardown found.

Score Your Own Site in Two Minutes

Every issue in this teardown maps to one of ten dimensions we check in every audit: web presence, copy nativeness, title and metadata localization, legal and consent UI, JPY pricing display, form handling, Japanese support content, style consistency, Japanese search keyword fit, and Japan-relevant social proof.

We turned those ten dimensions into a free self-assessment: answer ten questions, get a 0–100 Japan Readiness Score, and see which gaps Japanese buyers will notice first. It takes two minutes and requires no signup: hirakilocalization.com/readiness-score.

FAQ