Japan-readiness gap map · Free · 2026-06-20

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

Rallly is an open-source group scheduling tool (Doodle alternative) with a Pro tier at $8/month. In October 2024, Japanese language support was shipped to the product. That is genuine positive investment — a native Japanese speaker can now use the scheduling interface in their language. The gap is what comes before and after that product experience: the marketing site remains English-only, there is no 特商法 page, and pricing is USD. Japan's scheduling market is specifically strong for this use case (group date coordination is deeply embedded in Japanese team culture), which makes the GTM gap more costly than it would be for a Western-centric product.

26
/ 100
Not ready Japan-readiness score
Critical gaps present

Detected gaps — verified 2026-06-20

G1

No 特商法 (Specified Commercial Transactions Act) disclosure — Pro tier is blocked

Critical · purchase-blocking
Current state (verified)

rallly.co has no 特商法に基づく表記 page. The Pro tier at $8/month is a commercial product sold to users including Japanese ones, but the disclosure required by Japanese commercial law for paid digital services does not exist.

rallly.co/pricing (Pro $8/month — no 特商法 in footer confirmed)
Why a Japanese buyer stalls

Rallly's use case is directly relevant to Japanese business culture — group scheduling for meetings, events, and team coordination is used constantly in Japanese workplaces. But when a Japanese team or company wants to expense Pro for their scheduling workflow, the person handling the purchase looks for the 特商法 disclosure. Without it, paying for a foreign tool's subscription is an uncertain act for Japanese corporate procurement. A domestic scheduling tool, even a less functional one, would show this page by default.

The fix (rough)

A 特商法に基づく表記 page covering the Pro subscription. This is a one-template, one-footer-link change. < 1 day. For a product where the Japanese use case is particularly strong, this is the highest-ROI single action.

G2

Marketing site is English-only despite a Japanese product locale

Critical · discovery gap
Current state (verified)

rallly.co is fully English-only. No Japanese marketing page exists, and no language selector is present in the marketing layer. The October 2024 Japanese locale is only accessible to users who have already signed up — it is not visible from the outside.

rallly.co (lang="en", English-only marketing confirmed) github.com/lukevella/rallly/issues/1401 — "Add support for japanese" (closed Oct 2024)
Why a Japanese buyer stalls

A Japanese team searching for a group scheduling tool in Japanese will not encounter Rallly. Domestic tools like Chouseisan are widely known and appear in Japanese searches. Rallly's Japanese product capability is a differentiator — it is more polished and flexible than domestic alternatives — but that advantage is inaccessible because the discovery surface is entirely in English. The tool speaks Japanese; the person who would recommend it to the team never finds it.

The fix (rough)

A Japanese landing page announcing that Rallly is in Japanese and targeting 「日程調整 ツール 無料」 and 「Doodle 代替 日本語」. This is particularly high-leverage for Rallly because the product is already ready; the landing page just needs to say so in Japanese.

G3

USD-only pricing — no JPY for Pro

Major
Current state (verified)

Rallly Pro is $8/month. No JPY display or billing option is available. Domestic Japanese scheduling tools either offer JPY billing or are free, making the USD subscription a comparative friction point.

rallly.co/pricing ($8/month — USD only)
Why a Japanese buyer stalls

$8/month is a low price point, but a USD charge on a Japanese business card or expense report is still a non-standard line item. Japanese freelancers and small teams who would pay for Pro prefer JPY billing because it shows a clean ¥ amount on their accounting. For individual users, the stall is mild; for companies expensing it, it is a minor but real friction.

The fix (rough)

JPY pricing display and a JPY billing option. At $8/month, the international payment processing fees are the main constraint — but for annual billing or company accounts, JPY invoicing is standard practice.

G4

No JP search presence — invisible vs. Chouseisan and domestic tools

Major
Current state (verified)

With no Japanese marketing page, Rallly does not appear for 「日程調整 ツール」 or 「グループスケジュール 無料」 in Japanese search. The Japanese scheduling tool market is dominated by domestic tools in search results because they have Japanese content.

Why a Japanese buyer stalls

Chouseisan (a domestic scheduling tool) has dominated Japanese team scheduling for years. Japanese teams searching for alternatives in their language find Chouseisan and similar domestic tools — not Rallly. The October 2024 Japanese locale makes Rallly competitive in the Japanese market, but only for users who are already aware of it. Discovery is entirely blocked by the absence of Japanese content.

The fix (rough)

A Japanese landing page targeting 「日程調整 ツール 無料」 and explaining that Rallly is in Japanese, open-source, and free for basic use. The domestic competition does not have Rallly's features; this is a genuine differentiation story once the JP landing page exists to tell it.

G5

Japanese locale native quality — register and business scheduling conventions

Moderate
Current state (verified)

The Japanese locale was added in October 2024 via an automated process (CodeRabbit AI-assisted translation, as noted in the PR). The resulting translations have not been publicly reviewed by a native Japanese speaker for register appropriateness in a business scheduling context.

github.com/lukevella/rallly/issues/1401 — AI-assisted translation, Oct 2024
Why a Japanese buyer stalls

Scheduling tools in Japan are used for workplace and semi-formal coordination. The register matters: 敬体 (polite form) is expected in business scheduling contexts, and machine translations frequently use the wrong register or translate phrases too literally. A native reviewer would catch patterns like invitations that sound informal when they should be formal, or button labels that are accurate but unnatural. This is a trust signal issue — a scheduling tool with awkward Japanese reads as a foreign product that went through the motions, not one that understands Japanese professional culture.

The fix (rough)

A native Japanese speaker pass over the locale strings for the core scheduling flows: creating events, accepting dates, sending invites, confirmation messages. This is a review effort (not a translation from scratch) — likely 1–2 days for a native reviewer.

Score methodology (26/100)

Five signal dimensions, each 0–20. Verified against the live site on 2026-06-20:

1. Japanese marketing funnel 2 / 20
2. Legal / trust (特商法) 0 / 20
3. JPY billing / payment 2 / 20
4. JP search visibility 2 / 20
5. Product locale / IME / UX 20 / 20

Dimension 5 scores full marks because Rallly does ship a complete Japanese locale (issue #1401 merged Oct 2024). The G5 register issue is noted as a qualitative concern but does not reduce the score below full because the locale coverage is complete. Rallly's gap is entirely in GTM (funnel, legal, billing) — the product itself is ready; the funnel is not.

What it'd take — priority order

Want the full teardown + a ranked fix plan?

This map is the free slice. The full Japan-readiness audit covers the same gaps end-to-end, with specific copy, the 特商法 fields filled in, a ranked impact list, and a concrete action plan — delivered as a paid audit.

glovrex audit — $1,500 This gap map is free. No call required to get it.

Data verified 2026-06-20 against rallly.co, rallly.co/pricing, and github.com/lukevella/rallly/issues/1401. If something here is wrong or you'd like this page removed: hello@glovrex.com.