Tally × Japan — A Japan-Market Teardown
Contents
1. Executive summary
Tally is one of the most generous products in its category, built by a small bootstrapped team in Belgium — and Japanese users are already finding it. Japanese comparison media recommend it, Japanese how-to articles explain it, and a Japanese guide devoted to Tally states plainly that its use is growing among Japanese individuals and small teams. None of that conversation happens on Tally's own site, because Tally's own site does not speak Japanese.
You don't need to create Japanese demand. You need to stop outsourcing it to comparison sites.
This is not a market-creation problem. The demand exists, is documented, and is currently being served — framed, ranked, and monetised — by third parties. What is missing is a Japanese front door, and the encouraging part of this teardown is how little is missing: the product itself already supports Japanese where respondents see it. Almost everything below is copy, presentation, and one template — not engineering.
The three headline findings
- There is no Japanese page to land on. Japanese buyers search in Japanese, by job — 問い合わせフォーム 無料 ("inquiry form, free"), アンケート作成 無料 ("create a survey, free"). Every one of those searches lands on a comparison site, not on Tally. Tally's narrative in Japan is being written by Jicoo, Qiita, and independent bloggers.
- Tally's strongest claim is never made in Japanese. "Unlimited forms and submissions, completely free" is a headline in a market where the leading domestic tool's free plan allows 1 form and 30 responses a month. Said in Japanese, it is the whole pitch. Today, no Japanese sentence says it anywhere on tally.so.
- The reasons Japanese buyers hesitate are specific, known, and unaddressed. Japanese form conventions (姓・名分割, フリガナ, postal-code address lookup, a confirmation screen), trust signals framed for Japan's 個人情報保護法 (APPI) rather than GDPR, and basic billing reassurance for Japanese accounting (経理). Japanese reviewers name these gaps one by one. Tally can answer nearly all of them — it simply never has, in Japanese.
| Priority | Finding | Why it comes first |
|---|---|---|
| P0 | F1 — No Japanese landing page | Every other fix needs a page to live on; this is where the demand currently leaks |
| P0 | F2 — "Free and unlimited" unsaid in Japanese | The single highest-value sentence Tally could publish in this market |
| P1 | F4 — Japanese form conventions unaddressed | The practical objection Japanese how-to articles warn readers about |
| P1 | F5 — Trust signals framed for the EU, not Japan | Inquiry forms hold other people's personal data; trust decides B2B adoption |
| P1 | F6 — Pricing in USD only, no billing reassurance | The domestic incumbent wins by default at the moment of purchase intent |
| P2 | F3 — "No signup required" misreads in Japanese | A one-line fix inside the hero microcopy |
| P2 | F7 — English builder UI never pre-empted | Reviewers make it the headline; on Tally's own page it would be a footnote |
| Quick win | One Japanese LP + one Japanese template (§5) | Weekend-scale, captures all of the above in miniature |
A note on tone, because it matters to how this document should be read: nothing below is a failure. It is captured value left on the table by a product that is, by the evidence of its own Japanese coverage, already liked in Japan.
2. The seven friction points
F1. There is no Japanese page for Japanese visitors to land on
What Tally says today
"The simplest way to create forms"
"Say goodbye to boring forms and surveys. Meet Tally — the free, intuitive form builder you've been looking for."
— Homepage hero, tally.so
The entire first impression is in English, and there is no Japanese landing page. Japanese coverage has to compensate for this: Jicoo's 17-tool comparison of form builders captions its Tally screenshot 「出典：Tally の公式サイト（英語）」 — "Source: Tally's official site (in English)" (jicoo.com).
What a Japanese buyer actually sees
A Japanese small-business owner does not search "form builder." She searches by the job she has to finish — 問い合わせフォーム 無料, アンケート 作成 無料, 申し込みフォーム 作成 — in Japanese, on Google Japan. None of those queries can land on tally.so. So she lands on a comparison site, reads Tally's story as retold (and ranked against domestic rivals) by someone else, and forms her impression inside a frame Tally did not choose. The costs compound quietly: the search value, the trust, and the narrative control are all outsourced, for free, to intermediaries.
The fix
One Japanese landing page (a /ja path is enough) written natively in Japanese — not a translation of the English homepage — that answers, in order: what it costs (nothing, and what "nothing" includes), what jobs it does in Japanese job words, whether respondents can use it in Japanese, and who operates it. Section 4 of this teardown provides the hero for that page, ready to use. Section 5 shows how small the whole page can be.
F2. The category-breaking claim — free and unlimited — never gets said in Japanese
What Tally says today
"Paywalls getting in the way? Not anymore. Tally gives you unlimited forms and submissions, completely free."
— Pricing page, tally.so/pricing
What a Japanese buyer actually sees
She sees the domestic baseline. formrun, the best-known Japanese form tool, offers a free plan of 1 form and 30 responses per month (per Formlova's comparison of the official pricing pages: formlova.com). Against that baseline, "unlimited forms and submissions, completely free" is not a feature bullet — it is the entire advertisement. Japanese users who have discovered Tally cite exactly this as the reason: a Japanese how-to article explains that "無料のままフォームの数も回答の数も無制限に使えることから、日本でも個人や小さなチームのあいだで使う人が増えています" — "because forms and responses stay unlimited for free, use is growing in Japan among individuals and small teams too" (atsoho.com). The claim is already persuading Japanese users. It is persuading them on someone else's website, in someone else's words.
There is also a craft point: "Paywalls getting in the way?" is an idiom, and idioms do not survive literal translation. This claim does not need translating. It needs re-writing, in the plain comparative form a Japanese buyer trusts (see §4).
The fix
Put the sentence, in Japanese, at the top of the Japanese page and next to the pricing: フォームも、回答も、無制限。ずっと無料です。 — "Forms and responses, unlimited. Free, for good." Then state the free plan's permanence explicitly near the price — 無料プランに期限はありません ("the free plan has no expiry") — because Japanese users, conditioned by domestic tools, default to assuming a free tier is a trial in disguise.
F3. The hero's microcopy creates a Japanese-specific misunderstanding
What Tally says today
"No signup required"
— Microcopy under the hero call-to-action, tally.so
What a Japanese buyer actually sees
In English, in context, this means "try building a form before you register." Read cold by a Japanese business user evaluating a tool that will hold her customers' inquiry data, it can just as plausibly mean "there is no account; nothing is formally managed" — the precise opposite of reassurance. Japanese B2B buying treats account-keeping, data custody, and an identifiable operator as preconditions, not fine print. A phrase designed to lower friction can, across the language gap, raise it.
The fix
Split the two ideas, and say both — which the proposed hero microcopy in §4 does:
- 試すだけなら登録不要 — "No registration needed just to try it" (the trial really is frictionless).
- データはアカウントで安全に管理 — "Your data is kept safely in your account" (the custody really is formal).
Two short clauses, and the ambiguity is gone.
F4. Japanese form conventions — the actual reason Japanese users hesitate — are never addressed
What Tally says today
"Contact info. Collect names, addresses, phone numbers, emails & links."
— Homepage block list, tally.so
What a Japanese buyer actually sees
A Japanese inquiry form is not a generic contact form. The conventions a Japanese respondent expects — and a Japanese business is embarrassed to omit — are specific:
- 姓・名の分割 — family name and given name as separate fields
- フリガナ — phonetic readings of names, for correct pronunciation and sorting
- 郵便番号からの住所自動入力 — address auto-fill from the postal code
- 会社名・部署名 — company and department fields for B2B inquiries
- 確認画面 — a review-before-submit confirmation screen
This is not speculation about what Japanese users might want. A Japanese how-to article dedicated to using Tally for Japanese inquiries warns its readers about exactly this gap: "名前と住所の項目は自分で組み立てる必要があります…姓と名を分ける、ふりがなを聞く、郵便番号から住所を入力する、といった作りが一般的です" — "you have to assemble the name and address fields yourself… splitting family and given names, asking for furigana, and entering addresses from postal codes are the standard construction" (atsoho.com). In other words, the market's own documentation of Tally treats Japanese conventions as the thing a user must work around.
The fix
Tally's blocks and logic can already build nearly all of this — the fields, the furigana line, the layout. What is missing is not capability; it is a sentence, in Japanese, on a Japanese page, saying so — backed by proof. The strongest form of that proof is a pre-built Japanese template (§5): one click, and the conventions are visibly handled. Until then, every Japanese evaluator has to take the workaround on faith, or take a reviewer's warning as the final word.
F5. Trust signals are EU-anchored and never translated into Japanese buying logic
What Tally says today
"As a Belgium-based (EU) company, we fully comply with GDPR requirements and store all form data in Europe."
"Your data is encrypted both in transit and at rest."
— Pricing page FAQ, tally.so/pricing
And on the homepage, every testimonial voice is non-Japanese — for example, "Ben Lang, Angel investor, previously at Notion."
What a Japanese buyer actually sees
An inquiry form is where a business places other people's personal data. A Japanese SMB checking whether it may do that with a foreign tool runs a specific checklist, and "GDPR" is not the currency on it. She looks for: the operating company's name and home presented plainly (運営会社情報); a privacy policy she can read in Japanese; an explicit statement of where data is stored and how it is protected; and some orientation toward Japan's own 個人情報保護法 (APPI) expectations. She also looks, instinctively, for one face like hers — and currently finds none: not a single Japanese testimonial on the page.
The irony is that Tally's underlying story is strong. EU hosting and encryption in transit and at rest is, stated plainly, a reassuring answer. It is simply never stated in the frame the Japanese buyer is checking against.
The fix
- Add a company-identity block in Japanese above the footer: operating company (Tally BV, Belgium), what it is, and how long it has operated. Japanese buyers actively hunt for this before entrusting inquiry data.
- Reframe the existing security facts in plain Japanese: データは欧州のサーバーに、通信時・保存時の両方で暗号化して保管 — "Data is stored on servers in Europe, encrypted both in transit and at rest." Same facts, buyer's frame. Link a Japanese summary of the privacy policy. Keep any APPI-related wording descriptive of practices — do not claim certifications or compliance status Tally has not itself stated.
- Reserve one testimonial slot for a Japanese user — a single short quote with a name and role, used with permission, outweighs ten imported ones for this audience.
- Keep the founders visible. A small team's signed, human voice reads in Japan as sincerity — an asset, as long as it is rendered as sincerity rather than slang.
F6. Pricing is USD-only, with no Japanese accounting reassurance
What Tally says today
Pro: "$24 per month" (billed annually; Japanese comparisons list $29 monthly)
— Pricing page, tally.so/pricing
The price is shown in US dollars only, with no yen reference point and no billing explanation aimed at a Japanese buyer.
What a Japanese buyer actually sees
A Japanese small business budgets in yen and expenses through accounting (経理). At the exact moment of purchase intent, her questions are mechanical: roughly how much is this in yen? Is the displayed price tax-inclusive or tax-exclusive (税込/税抜)? Can I pay by card? Will I get a document my accountant will accept? Silence on these points does not merely confuse — it hands the domestic incumbent, which bills in yen with familiar paperwork, a free win at the decision point.
What can now be confirmed — and what remains open
From Tally's own billing documentation (tally.so/help/billing-and-payment-info): after each successful payment, an invoice is emailed immediately, invoices can be downloaded at any time from Settings → Billing → Manage subscription, and issued invoices cannot be amended — so billing details should be entered correctly before subscribing. These are good, concrete answers. A Japanese buyer currently has no way to find them from the pricing page.
One question remains genuinely open, and this teardown will not guess at it: whether Tally's invoices satisfy Japan's qualified-invoice system (インボイス制度／適格請求書) is not stated in Tally's public documentation and should be confirmed with Tally directly before anything public is claimed either way.
The fix
- Show the USD price and an indicative yen figure with an honest disclaimer: 例）Pro 月額 $29（年払いの場合は月あたり $24）※日本円は目安です（為替により変動します） — "Example: Pro $29/month ($24/month billed annually). Yen figures are indicative and vary with the exchange rate."
- State the tax treatment explicitly — Japanese B2B readers should never have to wonder whether a price is 税込 or 税抜.
- Publish a short Japanese billing FAQ built from the confirmed facts above: card payment, the invoice arriving by email after each payment, invoice downloads from the dashboard, the cannot-be-amended note (framed helpfully: "please check your billing details before subscribing"), cancellation timing — and, once confirmed, the qualified-invoice answer.
F7. The English builder UI is a known objection the site never pre-empts
What Japanese reviewers say today
"管理画面やヘルプは英語が中心" — "The admin UI and help are English-centric."
— Qiita's five-tool form comparison, listing this as Tally's one drawback against formrun's "日本語の管理画面で使いやすい" ("easy to use, with a Japanese admin UI"): qiita.com
What a Japanese buyer actually sees
The crucial fact sits buried mid-homepage, in English: "50+ supported languages. Translate the default form messages for respondents worldwide." (tally.so) — and Tally's own help page confirms Japanese is among the supported languages for respondent-facing default text: buttons, error messages, closed-form and thank-you pages (tally.so/help/supported-languages). So the honest picture is: the builder works in English; the forms your customers fill in can be fully Japanese. That is a manageable, even minor, caveat for most small teams. But because Tally never says it in Japanese, third-party reviewers say it instead — and in their telling, it becomes the headline objection rather than a footnote.
The fix
Say it on the Japanese page, in Japanese, before anyone else frames it:
管理画面は英語ですが、回答する人が見る画面は日本語にできます
— "The builder is in English, but the screens your respondents see can be in Japanese."
Pair it with one short Japanese quick-start guide ("your first inquiry form in 10 minutes"), and the objection is answered at the moment it forms — by Tally, in Tally's words.
3. A note on method
This sample is based on Tally's public homepage and pricing page, and on the Japanese coverage of Tally that any Japanese buyer would find first. Every criticism above is paired with the fix, and every factual claim carries its source. Where a fact could not be confirmed from Tally's own documentation — the qualified-invoice question in F6 — it is flagged as open rather than filled in. That discipline is the product: a Japanese buyer reading a teardown-grade page extends the same standard of care to the company that published it.
4. The proposed Japanese hero section
The principle: do not translate the English hero. Re-sell the same product in the order a Japanese buyer evaluates it — (1) the price contrast with local incumbents, (2) what it does, in job words, (3) reassurance that respondents can use it in Japanese, (4) a zero-risk trial.
Headline
フォームも、回答も、無制限。ずっと無料です。
Subheadline
文書を書くように質問を並べるだけで、問い合わせ・アンケート・申し込みフォームが完成します。回答する方が見るボタンや案内文は、日本語表示に対応しています。
Primary CTA
無料でフォームを作る
CTA microcopy
アカウント登録なしで試せます／クレジットカード不要／フォーム数・回答数は無制限（フェアユースの範囲内）
Line by line — what each part says, and why it works
- フォームも、回答も、無制限。ずっと無料です。
"Forms and responses, unlimited. Free, for good."
A literal translation of the current hero — 「いちばんシンプルなフォームの作り方」 ("the simplest way to create forms") — would be accurate and forgettable; every Japanese competitor also claims to be simple. The Japanese headline instead leads with Tally's structural advantage, the one fact that beats the local incumbents' capped free tiers (F2). ずっと ("for good / permanently") is doing deliberate work: it pre-answers the assumption that free means trial. - 文書を書くように質問を並べるだけで、問い合わせ・アンケート・申し込みフォームが完成します。
"Just line up your questions the way you'd write a document, and your inquiry, survey, and application forms are done."
The subheadline replaces the abstract category label "form builder" with the three job words Japanese users actually search and buy by — 問い合わせ (inquiries), アンケート (surveys), 申し込み (applications) (F1) — and keeps Tally's genuine differentiator, the document-like building experience, in concrete terms. - 回答する方が見るボタンや案内文は、日本語表示に対応しています。
"The buttons and guidance text your respondents see can be shown in Japanese."
This sentence answers F7 inside the hero itself. It states, up front, the one localisation fact a Japanese evaluator most needs — her customers will face a Japanese form — instead of leaving "50+ supported languages" buried mid-page in English. Note the polite 回答する方 ("the person responding") rather than a casual term for users: the register itself signals that this page understands Japanese business manners. - 無料でフォームを作る — "Create a form for free."
The CTA names the job and the price in four words. No idiom, no abstraction, nothing to misread. - アカウント登録なしで試せます／クレジットカード不要／フォーム数・回答数は無制限（フェアユースの範囲内）
"Try it with no account registration / No credit card needed / Unlimited forms and responses (within fair use)."
Three separate reassurances, each doing a different job: the trial is frictionless, no payment risk is being taken, and the unlimited claim is repeated where a sceptical reader looks for the catch — with the fair-use qualifier stated honestly rather than hidden, because Japanese buyers trust a stated limit more than an unstated one. This also resolves the F3 ambiguity: registration-free trial, never registration-free custody.
5. The quick win — shippable this week
One Japanese landing page, and one Japanese template. Nothing else. No UI localisation programme.
The page (a /ja path is enough) carries only what this teardown has already written:
- The hero from §4, verbatim.
- A short section answering F4: Japanese form conventions — name split, furigana, postal-code address entry, confirmation screen — with a screenshot of a Japanese form built in Tally.
- The trust block from F5: company identity in Japanese, and the storage/encryption facts reframed in plain Japanese.
- The billing FAQ from F6, built from Tally's confirmed documentation.
- The F7 sentence — 管理画面は英語ですが、回答する人が見る画面は日本語にできます — placed where the objection forms.
The template: one pre-built Japanese inquiry form (お問い合わせフォーム), linked from that page, pre-configured with 氏名（姓・名） (name, split), フリガナ (furigana), 会社名・部署名 (company and department), 郵便番号→住所 (postal code → address), contact fields, and a 個人情報の取り扱いへの同意 (consent to the handling of personal information) step.
Why this, and why it is enough to start
- It captures, in miniature, the exact search demand that comparison sites currently harvest on Tally's behalf (F1) — the page is the front door, and everything else in this document hangs on it.
- The template converts the biggest friction point (F4) into a one-click demonstration. A Japanese evaluator does not have to believe the conventions are handled; she can open the template and see them handled.
- It gives the existing Japanese ecosystem — the bloggers, comparison writers, and how-to authors already covering Tally — something of Tally's own to link to. Today that ecosystem explains Tally without Tally. One page and one template recruit it instead.
- The scale is honest: this is a weekend-scale publishing task using copy that already exists in §4, not a localisation department. If it earns traffic and signups, it has also written the brief for everything larger.
6. What the paid teardown adds
This sample covers one product's homepage and pricing page, from the outside, in the open. The paid TOKYO READ teardown is the same lens applied to the whole Japanese journey, delivered ready to implement:
- The full landing page — every section, not only the hero, rewritten natively in Japanese: features in Japanese job words, comparison framing against the domestic tools your buyers actually shortlist, FAQ, and footer trust block.
- The pricing page and billing FAQ — yen-indicative presentation, tax wording, and a Japanese billing FAQ drafted from your confirmed answers (including the qualified-invoice question), so the purchase moment stops leaking to domestic incumbents.
- Onboarding — a Japanese quick-start path and first-form guide, so the users the new page wins are not lost to an English-only first ten minutes.
- A Japanese search map — the queries Japanese buyers actually use, mapped to the pages that should answer them, so the front door keeps working after launch day.
Delivery is 72 hours from brief, as fixed, paste-ready copy with the reasoning attached — the same format as this document, at full depth. The fee is ¥120,000, once, with no retainer required.
Tally's Japanese demand is already there, being answered by other people's websites. The only question this teardown leaves open is how long it stays that way.
Read your own product this way
The full teardown — landing page, pricing page, and onboarding, with ready-to-paste Japanese copy — is ¥120,000, delivered in 72 hours, with one revision round included and no retainer required.
Applications are currently taken by a short application form. No payment is taken at application.
About TOKYO READ
TOKYO READ is run day-to-day by M, an AI operator based in Tokyo, under the supervision of a product manager who takes responsibility for the design and the quality of everything it delivers.
His career spans both sides of this work. At IBM Japan (2020–2023), he worked as an IT consultant across two practices: UX consulting — e-commerce and omnichannel design for large enterprises — and data analytics, including machine-learning projects such as scheduling optimisation for a pharmaceutical company and demand forecasting for a logistics company. Since 2023 he has been at Recruit, the Tokyo-founded group behind Indeed and Glassdoor, where he now works as a product manager on domestic marketplace businesses (automotive and bridal), after earlier work in back-office quality and new-business planning.
He is a graduate of Keio University's Faculty of Economics. He studied in Perth, Australia, and has crossed cultures since his student days, when he exchanged with students from UC Berkeley, Stanford, and the University of Cologne.
Every teardown is produced by M and reviewed under that supervision before it is delivered.
Sources
Fetched or cited 2026-11-11 / 2026-11-12:
- Tally homepage — tally.so
- Tally pricing — tally.so/pricing
- Tally billing and payment information (primary source for the invoice facts in F6) — tally.so/help/billing-and-payment-info
- Tally supported languages help — tally.so/help/supported-languages
- Jicoo (JP) form-tool comparison — jicoo.com/magazine/blog/form-creation-tools
- atsoho (JP) Tally Japanese inquiry-form guide — atsoho.com/blog/tally-forms
- Qiita (JP) form-service comparison — qiita.com
- Formlova (JP) form-service comparison (formrun free-tier limits) — formlova.com/ja/blog/comparison-form-services
Company background in the underlying research (bootstrapped, Ghent-based, founded by Marie Martens and Filip Minev, small team, no VC funding) is from Tally's own blog: blog.tally.so — team-size and ARR figures in third-party coverage vary by source and date and are not relied on for any claim in this teardown.