Launching in Japan? Machine translation kills trust on day one. I localize your SaaS, web app, or eCommerce UI into natural Japanese — written by a native speaker who also ships production Next.js apps.

PROOF = THE DELIVERABLES • Before/after UI copy samples in my service gallery (EN → natural JP) • Developer-ready exports: JSON (next-intl, i18next, react-intl), CSV/XLSX — placeholders preserved • EN→JP glossary with tone notes your team can reuse on every release

WHAT YOU GET (one-time sprint) • Up to ~1,500 words / UI strings (buttons, nav, onboarding, errors, empty states) • Native Japanese — not Google Translate; tone matched to B2B vs B2C • Developer-ready delivery: same file structure you sent in, JP values filled in • EN→JP glossary with context notes for your team and future releases • Layout check: string length and placeholder tokens verified so JP text doesn't break your UI • 2 revision rounds within 7 business days of first delivery

WHY ME I'm a Japanese native and full-stack engineer — not a generic translator. I know when "Sign up" vs "Get started" matters in a button row, how {count} placeholders must stay intact, and when katakana vs kanji reads naturally in product UI.

PERFECT FOR Overseas founders entering Japan, SaaS teams without in-house JP copywriters, agencies handing off i18n to someone who understands both product UI and code.

Before we start: send your string export (JSON/CSV), target audience, tone (formal / friendly), and any brand glossary. I confirm scope and string count before work begins.

Timezone: Tokyo (JST) · async-friendly with US/EU mornings.