Game Narrative and Writing Services

Narrative work splits into two roles that get conflated. Narrative design is structural: it decides how story is delivered through play, where branches sit, how quests gate progression, what the player learns and when. Game writing is the prose: dialogue, barks, item descriptions, tutorial copy, codex entries. A good narrative designer can write, and many writers can design, but the brief is different and so is the deliverable.

A third job hides behind both: narrative implementation. Somebody has to get thousands of lines into the game with correct speaker tags, conditions, and triggers, in whatever dialogue system you use. In small teams this falls on the writer. In larger ones it needs a defined owner, because a beautifully written branching conversation that nobody has wired up is a spreadsheet.

How to brief narrative work

Narrative briefs fail when they describe tone but not constraints. Writers need to know the shape of the container before they can fill it.

• Word count budget per content type: main quest, side content, barks, UI copy, item text
• Branch depth and how state is tracked, since branching multiplies word count fast
• The dialogue system and format the studio must write into: spreadsheet, Yarn, Ink, Twine, or a proprietary tool
• Character bible and world rules, or an explicit statement that the writer is creating them
• Voice budget, because a written line and a voiced line have very different downstream costs
• Whether the writer implements their own content or hands off to your team

How narrative work is priced

Narrative is usually billed per word, per project, or on a retainer for ongoing live-service content. Per-word suits high-volume, low-branching content like item descriptions and barks. Project fees suit structural work such as a narrative design document, a quest structure or a character bible, where the value is not proportional to length. Retainers suit live games that ship story content on a cadence.

Two multipliers dominate the final number. Branching content costs far more than its playable length suggests, because most of what is written is never seen in a single playthrough. And voiced content raises the cost of every revision, since a change after recording means a pickup session rather than a text edit.

Where narrative contracts go wrong

• Writing starts before the systems are settled, and half the dialogue references mechanics that get cut.
• Nobody scoped implementation, so finished text sits in a document while the release date approaches.
• Localization was not considered, so the script is full of puns, concatenated strings and idioms that will not survive translation.
• Word count was never budgeted, and a "small" side quest arrives at four times the length the systems can carry.
• The writer never played a build, so tone and pacing are calibrated against a design document rather than the game.

Give the writer a playable build early, even a rough one. If your game ships in more than one language, brief the writer on localization constraints before they write, not after.