FAQ

Quick answers to common questions about how we work.

Working Together

Do we need a long-term contract?

No. Most teams start with a small review of one page or one product area.
But when there’s a good fit, ongoing collaboration — monthly check-ins, quick reviews, content planning — tends to create the best results.

Who will we be working with?

All work is handled by a single senior operator with 25+ years of experience in translation and product-facing content.
No junior hand-offs. No anonymous offshore teams.
You always know who is responsible for your Japanese UX.

How do projects usually start?

Most teams begin with a small UX review of one product area — such as onboarding, help, or an LP.
You receive clear, practical recommendations, and we can iterate together from there if it makes sense.

What should we send you first?

Anything your Japanese users see — landing pages, onboarding flows, help docs, UI copy, emails, or error messages.
If some of it was AI-generated and you’re not sure it’s working, send it over.
IC Eight will flag where trust or clarity may be at risk.

Can you help us handle more of this in-house over time?

Yes.
IC Eight’s goal is to help your team work confidently with Japanese UX — while staying available for the areas where expert review really matters.

AI, MT & Automation

Do you use AI such as GPT or MT?

We use AI where it makes sense.
However, nothing is ever shipped without native professional review.
The details of our workflow are not public, but AI supports the work — it never replaces human judgment.

Do we have to abandon our current MT setup?

No — but IC Eight doesn’t do MT post-editing.

And that’s not simply a style or nuance preference. It’s because MT output is structurally unreliable.

When machine translation interacts with variables, tags, placeholders, or fragmented strings, it frequently:

  • mistranslates technical elements
  • drops words or full segments
  • breaks meaning across split sentences
  • produces Japanese that no longer fits the UX context

Fixing that sentence-by-sentence is risky — because you can never be fully confident nothing else broke along the way.

So instead of repairing MT output, IC Eight usually recommends generating the Japanese directly with LLMs — guided by intent, tone, risk context, and UX clarity from the start. This removes the MTPE failure-points entirely.

If what you need is traditional MTPE, a different vendor will be a better fit.

So how much is AI doing — and how much is human?

Think of it as a layered process:

  1. AI produces the first draft — guided by clear goals, tone, and audience context
  2. AI assists with review, highlighting possible risks or inconsistencies
  3. A senior human expert makes final decisions — shaping clarity, tone, and trust

This approach saves time — but final responsibility always stays human.

Can you work with AI-generated or MT Japanese drafts?

Yes — many teams already use them.
IC Eight can assess what is safe to keep, what needs adjusting, and where regeneration or rewriting is more reliable.
We do not run MTPE pipelines as a default model.
Quality and user trust always come first.

What IC Eight Actually Does

Do you translate our content into Japanese?

IC Eight focuses on Japanese UX — language that users in Japan can clearly understand and feel confident acting on.
Sometimes that means translation.
Sometimes it means restructuring the message so it works better in Japanese.
The goal isn’t literal equivalence.
The goal is adoption and trust.

What types of content do you focus on?

Mainly the parts of your product that influence adoption:

  • onboarding
  • help & docs
  • UI & product copy
  • user education
  • emails & notifications
  • release notes

IC Eight can also review landing pages and product marketing where language affects user confidence.

Is the workflow fully automated?

No.
AI can assist drafting and checking — but final responsibility always rests with a senior native professional.

Trust, Quality & Access

How do you ensure tone and consistency?

We maintain a consistent Japanese voice across product and support content.
If you already have voice or style guidance, we align with it.
If not, we keep things lightweight and pragmatic.

Do you need access to the live product?

It helps — but it isn’t required.
We can also work from staging, prototypes, screenshots, or screen recordings.

Can you review our existing Japanese?

Yes.
IC Eight can run a Japanese UX review to identify trust risks, clarity issues, or adoption friction — and recommend practical improvements.

Logistics

How is pricing handled?

We don’t publish price tables because scope varies.
Reviews are usually fixed-fee.
Translation-style work may be word-based.
All pricing is quoted upfront.

How fast can you turn things around?

For a single-page review, turnaround is typically 24–48 hours.
For ongoing work, IC Eight adapts to your release pace — whether you ship daily or weekly.

Do you sign NDAs and work internationally?

Yes.
IC Eight operates as a registered business and works directly with global teams.

About IC Eight

Who is IC Eight for?

Teams who value:

  • clarity
  • trust
  • thoughtful UX
  • lightweight collaboration
  • expert human review

Startups and product teams are a natural fit.

Where can we learn more about the people behind IC Eight?

You can find professional background details here:
LinkedIn →