Indie game teams
Steam page, capsule-adjacent copy, screenshots, demo strings, UI labels, and launch-week text.
Who This Is For
A focused native-Japanese check before public Japanese users see it.
Built for overseas indie game developers and AI/SaaS founders who already have Japanese copy, AI responses, screenshots, or strings, and want a written risk pass before launch.
AI product founders
Chatbot replies, support AI answers, onboarding bot responses, AI search results, and LLM feature samples.
Lean launch teams
Written redlines and issue logs your team can implement without adding live meetings to the schedule.
Two Products Only
Choose the audit that matches your launch surface.
The work is intentionally narrow: native Japanese redlines, severity notes, rewrite suggestions, and implementation-ready comments.
Steam Japanese Launch Audit
A native Japanese review of Steam-facing copy and launch materials, focused on clarity, genre fit, tone, trust, and purchase hesitation points.
- Steam store copy, screenshots, short descriptions, and launch text.
- Priority issues with severity, reason, and suggested rewrite.
- Optional in-game string, UI context, and demo LQA add-ons.
Japanese AI Response Redline Audit
A native Japanese review of generated replies from chatbots, assistants, support AI, AI search, onboarding bots, or LLM features.
- Checks for unnatural phrasing, over-certainty, vagueness, tone drift, and trust issues.
- Before/after redlines and reusable Japanese style guidance.
- Samples can be shared as CSV, JSON, spreadsheet rows, docs, or screenshots.
What You Get
A written trail your team can actually implement.
The deliverable is not a vague opinion pass. It is a structured audit that shows what to change, why it matters, and how severe the issue is.
Redlines
Before/after rewrites, wording notes, and native phrasing suggestions for Japanese users.
Issue log
Severity, location, current text, suggested text, and reason, suitable for spreadsheet or issue-tracker handoff.
Decision notes
Tone, terminology, uncertainty, UI length, and context notes so implementation choices stay traceable.
Fixed Pricing
Clear packages. Clear scope limits.
The same three fixed packages are available for either primary product. Larger projects can use scoped add-ons or a separate quote.
Lite
$199
A small public-material or sample-response audit.
Steam scope
Up to 500 source words or 5 screenshots.
AI Response scope
25 AI responses or 7,500 Japanese characters.
- Priority issues and key risk notes.
- Selected before/after rewrites.
- Written Q&A for 7 days, up to 3 questions.
Standard
$499
A broader launch page or AI response-set audit.
Steam scope
Up to 1,200 source words plus optional 10 screenshots.
AI Response scope
100 AI responses or 30,000 Japanese characters.
- Severity-classified issue notes.
- Style and terminology guidance.
- Mini re-check and written Q&A for 14 days.
Release Gate
$1,200
A pre-launch risk gate before a Steam launch, demo, or AI product release.
Steam scope
Up to 2h demo review or 250 strings / 2,500 source words.
AI Response scope
250 AI responses or 75,000 Japanese characters.
- Risk matrix, checklist, and priority issue log.
- Launch text or fallback-policy suggestions where relevant.
- Implementation re-check and written support for 21 days.
In-Game Add-ons
Game text can be reviewed without handing over your build pipeline.
I can review string files, screenshots, short gameplay captures, or demo builds and deliver written redlines plus an issue log. I do not directly edit Unity, Unreal, Godot, or production builds. Your team keeps implementation control.
In-Game String Redline Pass
$350
100 strings or 1,000 source words.
In-Game UI Context Pass
$500
30 screenshots plus 100 strings.
Demo LQA Pass
$700
Up to 2h demo review, up to 30 issues.
Patch Text Pass
$250
50 strings or 500 source words.
Fix Check
from $149
A light re-check after your team implements changes.
Implementation Handoff Sheet
$120
Redlines shaped into developer-ready task rows.
AI Response Definition
What counts as one AI response?
One AI response means one generated reply from a chatbot, assistant, support AI, search AI, onboarding bot, or LLM feature.
Counted as AI responses
- One chatbot reply.
- One AI support answer.
- One onboarding bot message.
- One AI search, summary, or recommendation result.
- One spreadsheet, CSV, or JSON row containing an AI-generated reply.
Counted as source words or screenshots
- UI labels and button copy.
- Landing-page copy.
- Fixed FAQ or help articles.
- Steam store descriptions.
- Static onboarding or notification copy.
Samples
Small examples of the redline format.
Real audits include notes about context, severity, and why a change is safer for Japanese users.
Before
Finland 1994. The golden era of action is back.
After
1994年、フィンランド。あの荒々しくも熱いアクションの時代が、再び幕を開ける。
The rewrite adds atmosphere without changing the premise.
Before
私はあなたを手伝うことができます。何が必要ですか？
After
お手伝いします。まず、何をしたいかを1つ教えてください。
Shorter wording sounds more natural and gives the user a clear next step.
Async Written Support Only
No live calls are needed to make wording decisions traceable.
Standard support happens in writing through the channel your team already uses. That keeps every Japanese issue, decision, and follow-up visible.
Supported channels
- Google Docs comments
- Google Sheets comments
- Notion
- GitHub Issues
- Slack or Discord text channel
Not included
- Voice calls.
- Video calls.
- Standard 30-minute or 60-minute consultation calls.
- Direct pushes to your repository or production environment.
Useful because
Japanese phrasing decisions are easier to implement when they are written next to the exact string, screenshot, response, or issue.
Process
Simple enough for a launch week, structured enough for a team.
Send a public page, sample AI responses, screenshots, string files, or a demo key. I confirm the scope in writing before the audit starts.
Send sample
Share the Steam page, AI response set, screenshots, or string file.
Confirm scope
I confirm the product, package, limits, file format, and delivery channel.
Receive audit
You get redlines, severity notes, issue rows, and rewrite suggestions.
Ask in writing
Use the included async support window for follow-up questions and re-checks where included.
FAQ
Clear boundaries before work starts.
Launch QA Japan reduces Japanese-language risk. It does not guarantee sales, reviews, wishlists, press coverage, or Japanese market success.
Is AI translation enough?
Sometimes it is enough for internal drafts. Public launches need a native check for tone, genre expectations, trust, UI length, uncertainty, and wording that may sound unnatural even when the meaning is technically correct.
Can you review only a Steam page?
Yes. A Steam page is often the first Japanese touchpoint. The audit focuses on visible copy, screenshots, genre clarity, purchase hesitation, and the language signals Japanese players see before they try the game.
Can you review in-game text?
Yes, as scoped add-ons. I can review CSV, XLSX, JSON, PO, XLIFF, screenshots, gameplay captures, or demo builds and return written redlines plus an issue log.
Do you directly edit Unity, Unreal, Godot, or production builds?
No. I do not directly edit game engine projects, production builds, repositories, or live product environments. Your team keeps implementation control.
Do you provide voice or video calls?
No. Standard support is async written support only through email, comments, Notion, GitHub Issues, Slack, or Discord text channels.
Do you guarantee Japanese market results?
No. The service can identify and reduce Japanese-language launch risks, but it does not promise sales, reviews, wishlists, rankings, or market success.
Send a page, string file, screenshot set, or AI response sample.
I will confirm whether it fits Steam Japanese Launch Audit, Japanese AI Response Redline Audit, or a scoped in-game add-on.