Is Twenty CRM ready for the Japanese market?
— a Tokyo native's gap map

twenty.com/fr is a full French-language marketing site, including pricing. twenty.com/es exists for Spanish. The pricing page declares hrefLang tags for en, fr-FR, and es-ES. twenty.com/ja returns a 404. Japan is absent from the same localization strategy that produced two other European markets.

twenty.com/fr (full French marketing site, live) twenty.com/pricing (hrefLang: en, fr-FR, es-ES — ja absent)

Japan is the world's third-largest economy, with higher average SaaS ARPU than France or Spain. A Japanese CRM evaluator who knows Twenty exists and arrives at the site finds a product that has invested in French and Spanish markets but not Japanese. This signals that Twenty does not consider Japan a priority market — which is itself a barrier for Japanese enterprise procurement, which prefers vendors with local commitment.

A twenty.com/ja marketing page using the same template as the French and Spanish pages. The underlying translation infrastructure appears to exist — this is an execution gap, not an architecture gap.

GitHub issue #13665, filed in 2026 and closed in April 2026, documented that Japanese UI text rendered as raw Unicode escape sequences — for example, the "Add new field" button on the Opportunities page displayed as 新規フィールドを追加 instead of the actual Japanese characters. The issue is closed, but its existence is a signal that the Japanese locale is not part of the regular QA cycle.

github.com/twentyhq/twenty/issues/13665 — Unicode escape sequences in Japanese UI

A Japanese user who switches the product to Japanese and encounters raw escape sequences will immediately report it as broken and lose confidence in the locale support. Even if the fix is shipped, the fact that this bug existed suggests Japanese-locale testing is not part of the release process — meaning similar regressions can re-appear. For a CRM that will hold customer relationship data, "the Japanese version might randomly break" is not acceptable.

Japanese locale CI test (screenshot regression or string-render check) as part of the release pipeline. This prevents the class of bug recurring even if new strings are added incorrectly.

twenty.com footer links to Privacy Policy and Terms of Service. No 特商法に基づく表記 disclosure is present, despite a $9/user/month Cloud tier that is sold to businesses including Japanese ones.

twenty.com (footer checked — Privacy Policy, Terms only)

A CRM holds customer data, deal data, and internal relationship intelligence. Japanese procurement of a CRM involves legal review. The 特商法 page is the first thing that review looks for. It signals that the vendor has registered their obligation to Japanese law on commercial transactions. Without it, the vendor is in an undefined legal space for the Japanese procurement team.

A 特商法に基づく表記 page covering the Cloud subscription product. Standard template, < 1 day. Link from footer, ideally alongside a Japanese-language terms page.

Cloud Pro is listed at $9/user/month, Organization at $19/user/month. All pricing is USD. The French page shows the same USD prices — so even the localized markets are not getting JPY. No JPY display or currency toggle exists.

twenty.com/pricing ($9/user/month USD)

Twenty is positioning against Salesforce and HubSpot, which both offer JPY invoicing in Japan. A Japanese company CFO comparing CRM options will notice that Twenty requires a USD charge while competitors offer JPY. It is a friction point that tips evaluation toward the competitor even when the product itself is preferred.

JPY pricing display. For the /ja marketing page (once it exists), showing prices in ¥ alongside $ is a page-level change. For billing, a JPY invoice option for annual contracts.

With no /ja marketing page, Twenty does not appear in Japanese-language search for 「CRM オープンソース」, 「Salesforce 代替」, or 「顧客管理 SaaS」. The French and Spanish investments generate search visibility in those markets; Japan gets none.

CRM evaluation in Japan happens through search and recommendation. A team evaluating Salesforce alternatives searches in Japanese. Twenty does not appear. They find Japanese-localized competitors or domestic tools. Twenty's absence from this search moment is a direct consequence of not having a /ja page — the same structural decision that produced the French and Spanish pages already exists; Japan is simply excluded.

twenty.com/ja using the same localization pipeline as /fr and /es. This also captures the Salesforce-alternative search traffic that the French page captures for that market.