FAQ

Narrative design brings the most value to projects where story, worldbuilding, and player choice play a meaningful role. This typically includes RPGs, adventure games, story-driven indie titles, TTRPG projects, or any game built around strong lore and factions.

If it matters to you that players understand why they act, who they trust, and how their decisions shape the world, narrative design is a worthwhile investment.

A screenwriter focuses on crafting a linear story, typically for film, television, or other fixed storytelling formats.

A game writer creates the in-game text: dialogue, quests, item descriptions, codex entries, and lore.

A narrative designer works on a strategic level. They design how the story functions within an interactive system how it branches, how it responds to player decisions, how it connects to gameplay mechanics, and how it supports the overall player experience.

In simple terms:
A screenwriter writes a story.
A game writer writes the text.
A narrative designer designs the storytelling system.

A project usually benefits from narrative design when:

• the story becomes difficult to manage or inconsistent

• quests feel disconnected from the world

• characters lack clear motivations

• player choices have little or no meaningful impact

• the world feels generic or fragmented

Narrative design provides structure, cohesion, and direction. It's not just about improving dialogue it's about ensuring the entire storytelling framework supports the gameplay experience.

I can help you design story, quests, dialogue, characters, lore, and the overall narrative structure in a way that works for both gameplay and production. Whether you need to build a world from scratch, expand existing content, or bring order to narrative chaos, I'll deliver solutions that can go straight into the game. 

Ideally as early as possible even from the initial idea. I can help shape the concept, the core of the world, and the narrative direction in a way that's production-friendly and won't get expensive to rebuild later. That said, I can also jump in mid-production: for story revisions, dialogue rewrites, adding missing content, tightening consistency or as a narrative rescue when the project starts falling apart.

Both. Besides the writing itself (quests, dialogues, lore), I focus on how narrative works inside the game: quest structure, branching, meaningful consequences, pacing, clear player goals, and integration with gameplay systems. The result isn't just nice text in a document it's content designed to be implemented. 

Pricing and timelines depend on the scope meaning the number of quests, dialogue length, branching complexity and on what stage the project is currently in. However, I can propose a clear package with a fixed price, or an ongoing collaboration. I'll also provide a realistic schedule so the team knows exactly what they'll get and when. 

Yes. I create clean, structured narrative documentation that's readable for designers, programmers, and production and stays useful long-term. Typical deliverables include quest logic, dialogue trees, lore bible, character summaries, tone-of-voice guidelines, and solid handoff materials for implementation.

AI is a great tool for brainstorming and quick variations, but it doesn't replace functional narrative design for a specific game. I provide consistency of tone and world rules, meaningful choice design, strong quest structure, and real collaboration with the team so the result fits the scope, production reality, and player experience, not just a generic output. 

I adapt to your team's pipeline: PDF, HTML export, Markdown, YAML, implementation tables (Sheets/Excel/CSV) and exports prepared for implementation.
If needed, I can also provide naming conventions, tagging structure, and simple rules to keep everything clear and easy to maintain.