Foreign SaaS companies almost never fail in Japan because of one bad translation. They fail because of an accumulation of small decisions — a stiff button label here, an untranslated tooltip there — that each look acceptable in isolation. Together, they signal something Japanese enterprise buyers notice immediately: this product was translated, not localized.
After reviewing dozens of foreign SaaS products localized into Japanese, I see the same ten mistakes again and again. They show up across onboarding flows, pricing pages, help centers, and in-app UI. None of them require a product rewrite. But left alone, they quietly cost you trial sign-ups, enterprise credibility, and conversion.
Here are the ten most damaging ones, with before/after examples from real QA projects.
Mistake 1 — CTAs Translated Like Formal Letters
Button copy is where machine translation shows its limits most clearly. English CTAs are short verb phrases — "Contact Sales," "Get Started," "Book a Demo." Translated literally, they turn into stiff noun phrases that no Japanese SaaS product would actually use. A button should read as an action the user takes, not as a polite request addressed to them.
The same logic applies to every CTA in the product. "Get Started" works as 始める, not はじめましょう. "Book a Demo" works as デモを予約, not デモのご予約を承ります. Verb-form consistency across all buttons matters as much as each individual choice. A product where every button follows the same grammatical pattern feels deliberately designed.
Mistake 2 — The Same Feature Named Three Different Ways
Terminology drift is the most common issue I find. It's also the hardest for an untrained eye to catch. It happens when the UI, the help center, and the marketing site get translated by different people, different tools, or the same tool at different times. Each translation is defensible on its own. Together, they make a Japanese user feel like they're working with three different products.
QA note: A terminology glossary fixes this permanently. Once your core 30–50 product terms have one approved Japanese equivalent each, every future translation — human or AI — has a reference point.
Mistake 3 — English Strings Left on Japanese Pages
Untranslated English usually survives in the places translators don't see: empty states, tooltips, error toasts, email templates, and section headings pulled from a different file. To a Japanese enterprise buyer, mixed-language content is a clear signal that the localization is incomplete — and if the localization is incomplete, what else is?
Mistake 4 — Inconsistent Politeness Register
Japanese has multiple politeness levels, and SaaS products can pick a polite register or a plainer one — either choice is defensible. The mistake is rarely picking the wrong level. It's picking inconsistently. When one screen addresses the user formally and the next barks an instruction, the product feels assembled by a committee that never spoke to each other.
Inconsistency creeps in because the register gets decided implicitly. One translator defaults to honorific forms. Another defaults to plain forms. An AI tool picks whichever the source sentence structure suggests. The fix is to decide the register once, write it down, and apply it as a rule — not as a per-string judgment call made dozens of times by different hands.
Mistake 5 — Redundant, Doubled Expressions
AI translation tends to preserve every element of the source and add a Japanese equivalent on top, producing doubled modifiers. Native Japanese readers notice these instantly. They're small, but they add up. Redundancy is one of the fastest ways to signal that copy was machine-generated.
Mistake 6 — Payment Terms Used Interchangeably
In English, "payment" covers everything. In Japanese, 決済 and 支払い are not interchangeable — 決済 refers to the transaction settlement process, while 支払い refers to the act of paying. Using the wrong one in a checkout flow or billing screen is one of the fastest ways to signal that your product does not understand the Japanese FinTech market.
Mistake 7 — Over-Translating Words Japanese Users Expect in Katakana
This is the opposite failure mode of Mistake 3. Some English terms have settled into standard Japanese — ログイン, アップロード, ダウンロード, アカウント. Translating them "more thoroughly" into rare kanji compounds doesn't make the product feel more local. It just makes it feel foreign in a different way. Good localization knows which words to leave alone.
A simple heuristic: if a Japanese professional in your industry would type the English loan word into their own documents and emails, keep it. If your translation introduces a kanji compound that a native speaker has to pause to parse, you've over-translated.
Mistake 8 — Western Punctuation and Typography
Japanese has its own punctuation conventions: the full-width period 。and comma 、, corner brackets 「」for quotation, and a general avoidance of exclamation marks in professional UI. Carrying over English punctuation is a subtle but constant signal that the text was not written by someone working in Japanese.
Mistake 9 — Japanese Text Overflowing the UI
Japanese strings expand and contract unpredictably relative to English. A translation can be perfectly natural and still break the UI — truncated buttons, overflowing menu items, labels that wrap to a second line. This counts as a localization mistake even though the text itself is correct, because what the buyer evaluates is the user experience, not the string in isolation.
The fix is rarely a longer button. It's a localization-aware design spec — character budgets defined per UI component before translation begins — so the Japanese copywriter writes within the real constraint instead of against it.
Mistake 10 — Error Messages Translated Literally
Error messages are where trust is most fragile, and literal translation does the most damage. A direct rendering of casual English error copy reads as vague or unsettling in Japanese. A well-localized error message states what happened, what the user should do next, and does so in a measured tone — especially important in FinTech, where an alarming error message during a payment can end the session entirely.
The Pattern Behind All Ten
Every mistake on this list shares one root cause: the product got localized linguistically, but never reviewed as an experience. The words were translated. The user experience was not checked.
A Japanese localization QA review isn't proofreading. It evaluates the product the way a Japanese buyer would — moving through the actual flows and asking three questions:
- Does this read like a Japanese product? (register, terminology, punctuation, natural phrasing)
- Is it consistent with itself? (same term, same tone, same conventions across every screen)
- Does it work as an experience? (text fits the UI, error states are calm, nothing is left in English)
Fix these ten mistakes and your Japanese product stops signalling "translated" and starts signalling "built for Japan" — usually without any change to the underlying product, and often with a measurable lift in conversion from Japanese visitors.
Next Steps
If you want to know how many of these ten mistakes are currently live on your own Japanese site, a Japanese Website Mini Audit reviews one page against every issue above — and delivers a scored QA report with before/after fixes and a prioritized action list within 3–5 business days.