FAQ
Quick answers to common questions about how we work.
Do you need our product to be fully built before we start?
No. We can begin from early prototypes, staging environments, or even screenshots. If nothing is localized yet, we help identify the highest-impact entry points for Japanese users.
What if we don’t have any Japanese version at all?
That’s normal. We start with the parts of the product that actually drive adoption — onboarding, help, tutorials, and UX copy — not only UI strings.
Can you work with AI-generated Japanese drafts?
Yes. If the draft comes from GPT-level tools, we can refine it into coherent, natural Japanese. If the draft comes from DeepL or sentence-by-sentence MT, we usually rebuild it — the structure doesn’t carry over.
If you’re curious how we think about machine translation and AI-assisted work, here’s a detailed look:
DeepL or GPT? Why the Type of AI Translation Matters
Do you need access to the live product?
Ideally, yes. Having access lets us fix friction at the interaction level. If that’s not possible, we can work with screenshots, screen recordings, or a staging environment. Post-launch reviews also work.
What if our team doesn’t have a localization manager?
Most early-stage teams don’t. We work directly with your PM, content lead, or founder. The workflow is simple and doesn’t require a TMS or heavy management.
Can you collaborate as part of a multilingual release?
Yes. Japanese is our core focus, but we can collaborate within multilingual teams when needed. We work with trusted partners for Brazilian Portuguese — the variant most SaaS teams prioritize — and we can connect you with vetted specialists for other Tier-1 languages on request.
Do you handle UX/UI copy, help, tutorials, and onboarding?
Yes. These are often even more important than UI strings when it comes to Japanese adoption. We cover all parts of the user journey where language affects understanding.
How do you ensure tone and consistency?
We maintain a single Japanese voice across UI, help, onboarding, and marketing. If you already have English voice guidelines, we adapt them. If not, we can create lightweight tone notes based on your product style.
Can you review our existing Japanese version?
Yes. We can run a full Japanese UX audit and flag trust-breaking issues, unclear flows, or mismatched tone.
How is pricing handled?
We don’t publish price tables because every engagement is scope-specific. For translation or rewriting work, we typically price per word. For audits, reviews, or structured reports, we price per deliverable.
All pricing is quoted upfront — no surprises.
Do you sign NDAs and handle invoicing internationally?
Yes. IC Eight operates as a registered business and can work directly with international teams, including NDAs, compliance, and clean invoicing.
Where can we see your background?
You can find more about the person behind IC Eight here:
LinkedIn →