I support game development teams when complex ideas are hard to explain, the words feel off, or characters don’t sound like real people.
I turn mechanics and backend requirements into player-facing language that teaches through action and keeps momentum moving.
I edit translated English around player intent, interface context, market expectations, and repeatable terminology—not literal phrasing alone.
I turn an intended personality into practical guidance a whole team can apply consistently.
I build research-led character foundations informed by interviews, real-life context, and careful attention to cultural specificity. The goal is emotional truth without stereotype.
I identify where language creates confusion, inconsistency, unnecessary friction, or tonal mismatch—and turn the findings into prioritized recommendations.
I learn the player, mechanic, production constraints, existing voice, and definition of success.
I write in context, surface ambiguities early, and collaborate with the people implementing the work.
You receive usable copy plus the reasoning, systems, or documentation needed to keep it consistent.
That is enough to start. Send me the flow, screen, feature, or character that is not landing. I can help identify whether the issue is clarity, hierarchy, terminology, tone, localization, or something the team needs to define first.
Yes. My published case studies are anonymized, and I can work within your confidentiality, access, and documentation requirements.
Yes. I work with the people responsible for design, development, localization, narrative, QA, sound, and music so the words support the full experience—not only the copy deck.
No. Tell me what players are struggling with or what your team is trying to improve. We can talk through the problem and see whether I am the right fit.
Tell me what is confusing players, weakening the experience, or slowing down your team. We can talk through the problem and see whether I’m the right fit.
Let’s See If We’re a Fit