Will your product survive its first translation?

Five questions. The same checks we run on day one of every sprint. Get your score instantly — leave your work email and we will send the full breakdown.

1. Where do your product strings live today?

Hardcoded across the codebase — nobody knows the full count. Mostly in string files, but marketing and legal copy live elsewhere. Centralized in one system, extracted per release. Centralized with keys, comments, and screenshots for translators.

2. Has a native speaker ever reviewed your product in context?

No — machine translation or bilingual colleagues only. Once, in a spreadsheet, out of context. Yes, for one market, on live screens. Yes — in-context review is part of our release process.

3. How does your UI handle 40% longer text?

It doesn’t — buttons truncate and layouts break. We find out from users after launch. QA checks key screens manually before release. Automated screenshot tests catch it on every build.

4. Do dates, currencies, plurals, and RTL layouts work today?

We format everything the American way. Some locales work; edge cases surprise us. Our frameworks handle it, but we rarely verify. Verified per locale in staging before every launch.

5. Is there a shared glossary for brand and product terms?

No — every translator invents their own terms. An informal list, rarely enforced. Yes for one language, not the rest. Yes — locked and enforced across all locales.

WORK EMAIL (TO RECEIVE THE FULL BREAKDOWN)

– / 100

Get the Playbook

Parlato

Features Team Playbook Readiness Score Privacy Terms