Get paid for the questions and custom requests you already get from followers.

Create your free Brillay link

For creators

Game writers: sell dialogue passes, lore bibles and Ren'Py routes to devs

How game writers, visual-novel writers, worldbuilders and conlangers sell scoped dialogue, lore and branching scripts to indie devs, paid upfront from one link.

Updated November 2026

Get paid for this — with Brillay

How many unpaid barks has “rev-share once we hit Steam” cost you this year? List one barks pass, and the next studio that asks pays upfront before a single trigger line gets written.

Brillay is a link in your bio where followers pay you directly for:

Custom WorkPaid QuestionsGoalsTipsPersonalized Videos

Mid-NaNoRenO, a solo otome dev taps the link in your itch.io bio, attaches her flag sheet to your branching-outline listing and pays by card as a guest, with no signup standing between her jam deadline and your start.

No monthly fee, you only pay a small platform fee when you get paid.

Indie devs rarely hire a writer for a whole game. They hire one for forty barks for the skeleton archer, a pass on the companion who still talks like the tutorial, or a branching outline before their Ren'Py script grows a fourteenth ending. Game writers get paid by putting a word budget and a price on each of those slices, then asking for the trigger list, character sheet and string-ID export at the start; on Brillay the dev picks your barks or quest listing, attaches that CSV and the GDD, and pays before you start. If the dev just needs to know whether hub-and-spoke will triple their word count, they type that one question and you answer it in writing.

Narrative designers, visual-novel writers, worldbuilders and conlangers all work this way: inside someone else's game or world, in Twine, Ink, Ren'Py, Yarn Spinner or a localization spreadsheet, rather than grading a finished script.

What do indie devs actually ask a game writer for?

Most requests come from small teams where the person who built the systems is also the person writing placeholder dialogue at 2am. The asks tend to fall into a few types:

  • Barks. Combat callouts, idle chatter, shopkeeper greetings and "low health" lines, usually 20–60 short lines per character, each tied to a trigger.
  • A dialogue pass. "The mechanics work but every NPC sounds like the same tutorial." You rewrite one character's lines so they have a voice and the string IDs stay the same.
  • Item and flavor text. Weapon descriptions, codex entries, tooltips and achievement names, often with a hard character limit because the UI box is already designed.
  • Quest writing. A side quest's hook, objectives, NPC conversations, journal updates and completion text, with one choice that actually matters.
  • Lore. A faction history, a pantheon or a timeline that the artist and level designer can build from.
  • Branching structure. A map of choices, flags and endings, made before anyone writes a full scene.
  • Naming. Towns, gods, ships and spells that sound like they come from the same world.

What developers send matters as much as what they ask for. Expect a one-page pitch or GDD, character sheets, an export of existing lines (often a CSV with string IDs), the trigger list, character limits per text box, and a note on whether lines will be voiced. Voiced lines need to be shorter and easier to say out loud. They'll also send reference points: "banter like Hades," "skill voices like Disco Elysium," "cozy like Stardew."

The worries are familiar too. Scope creep ("could you also just…"). Rev-share offers instead of pay. Unannounced projects that need discretion. Credit in the end screen. Pricing small, defined pieces is the most direct answer to all four.

Which game-writing jobs should you sell first?

Start with the two or three jobs you already get asked for, and write each one so a developer can tell exactly what they're buying.

Character dialogue pass (Custom Work). One character or one scene, up to a set line or word count, rewritten to a consistent voice. You deliver it in the developer's format with their string IDs untouched, plus a short voice guide (three "says this, never says that" examples) so later lines stay on-voice. They send: the character sheet, the current lines, the trigger list, any character limits and two or three reference voices. Delivery: 3–5 days. Price: you set the price; a common starting point is a flat fee for a fixed amount, such as $75–200 for up to 1,500 words or 40 barks on an indie budget.

Quest writing (Custom Work). One side quest, written end to end: the hook, two to four NPC conversations, objective strings, journal entries and completion text, branching on one meaningful choice. They send: where the quest sits in the main plot, which NPCs are involved, what the player can actually do mechanically (fetch, escort, persuade, fight), the word budget and the file format. Delivery: 5 days. Price: work it out per word for yourself, then show the developer one flat number.

Lore document (Custom Work). One faction, region or religion. For example, 2,000–3,000 words: a one-paragraph summary for the pitch deck, a history with a timeline, beliefs and internal factions, naming conventions, and three story hooks the designer can turn into quests. They send: the existing canon, art references, and a list of what must not change. Delivery: 5 days.

Narrative question (Paid Question). One private question with up to two follow-ups, answered in writing. Typical questions: "My Twine game has 14 endings and I'm drowning. How do I cut it down without losing the feeling of choice?" "How many barks per enemy type before players notice repeats?" "Should my companion's approval be one variable or three?" Paid Questions are text only, so the developer types or pastes the outline into the question. Anything that means reading their files belongs in Custom Work. Reply time: whatever you set, from 1–24 hours or 1–5 days. Price: you set it; a common starting point is $15–40. Some writers start at a founding rate of around $10–15 to collect their first few paid replies, then raise it.

How do you fit a game-writing job into one order?

Each order has one delivery time, chosen from 1–24 hours or 1–5 days, and five days is the longest. There are no milestones and no built-in revision rounds. A full visual-novel route, an 80,000-word RPG script or a complete world bible won't fit in one order, so don't sell them that way. Sell a clearly scoped piece instead: one character, one quest, one route chapter, one faction. When it lands well, the developer orders the next piece. Plenty of indie devs prefer this anyway, because they can check your voice on a small piece before they commit a bigger budget.

A Custom Work listing has a title, a description, what the developer gets, what you need from them, what's excluded and the delivery time. Use the excluded line generously. Good examples:

  • "No implementation in your engine; I deliver the text in your syntax for you to paste in."
  • "Lines for this one character only; other characters' replies stay as you wrote them."
  • "Voice-direction notes not included."

You also write your own correction policy, which the developer sees before paying. A typical one says you'll fix lines that miss the brief you were given, but a new direction counts as a new order. After you deliver, the developer can reach you about that order in a support conversation on it.

Write in the format they'll use: Ink knots and diverts, Ren'Py labels and menus, Twine passages in Harlowe or SugarCube, Yarn nodes, or a spreadsheet keyed to their string IDs. A delivery is one package: a written note, up to 5 files, and/or links. Executable and script files are blocked as uploads, so for engine files a plain-text copy or a link to a branch in their repository is often the cleanest route. Delivered files stay available for 90 days, so remind the developer to pull them into their project.

How much should you charge for game dialogue or lore writing?

Game writing is usually quoted per word, and per-word thinking helps you, but developers decide faster when they see one flat number. Work out your rate privately and multiply it by the word budget for the piece. You set the price; a common starting point for indie dialogue and quest text is roughly 5–15 cents a word. Narrative designers with shipped credits charge more. Hobby visual-novel commissions often start lower. Lore and worldbuilding documents are often priced flat per document, because the thinking takes longer than the typing.

A few things push the price up:

  • Short delivery times. If a developer needs barks before a festival demo, a separate listing with a 24-hour or 2-day delivery can carry a higher price than your standard 5-day one.
  • Heavy branching. A scene with three choices and two flags is more work than its word count shows.
  • Strict constraints. Tight character limits, voiced lines or lines that must work in any order all add work.

When someone offers rev-share or "exposure," you can point them to your smallest paid piece instead. A single NPC pass is easier to say yes to than a contract.

No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate.

None of this is an income promise. What you earn depends on your prices and who asks. The full breakdown is on the pricing page.

Do you need a marketplace or a big following to get game-writing work?

Today a lot of game-writing work moves through freelance marketplaces that rank sellers in search, Discord job channels, cold DMs and invoices sent through payment apps. Each one adds a step between "I'd like this" and getting paid: a ranking that shows the developer someone else first, a scope conversation in DMs, or an invoice to chase.

A Brillay page is your own link. Put it in your itch.io profile, your Discord bio, your portfolio site or your TikTok or X bio. There's no follower minimum and nothing to apply for, so it works from the first developer who asks. They pay by card as a guest, without making an account. Many game writers work under a handle or a studio name. Developers see the public name you choose, on the page and at checkout, not your legal name. Creators in 41 countries can get paid, and developers pay by card from anywhere, which matters when your client is a two-person studio on another continent.

Visual novel writers: route scripts and branching outlines

Visual-novel buyers are often solo developers who already have sprites and backgrounds but no script. That includes otome and dating-sim devs, and jam teams racing a deadline like NaNoRenO. They usually send:

  • The character define block or an excerpt of their script
  • The list of expression tags
  • The affection or flag variables
  • A rough route outline and a target length

Route script (Custom Work). One chapter or section of a route, around 4,000–6,000 words, written in Ren'Py syntax. It uses their character variables and expression tags, with menu choices, jumps and flag changes commented so they can trace the logic. If they work in Ink, deliver knots and diverts instead. A whole 40,000-word route is several orders, one chapter at a time.

Branching outline (Custom Work). A map of every choice, the flags it sets, the affection thresholds, and which choices lead to the good, normal and bad endings. Add a word estimate per branch so the developer knows what the full script will cost before anyone writes it. This is often the best first sale, because it shows a VN dev you understand structure, not just prose.

Script edit in Ren'Py format (Custom Work). You tighten the voice, fix typos and adjust pacing in their existing script without breaking a single label or jump. Per-word pricing is common in the VN scene, but a flat price per chapter keeps it simple for the buyer.

Worldbuilding consultants: magic systems and world bibles

Worldbuilding buyers are wider than game studios. They include fantasy authors mid-draft, game masters running homebrew campaigns, and developers who need a setting before they need dialogue.

Answer on a magic system's logic (Paid Question). This is where Paid Questions fit best. Take a beginner who has just started a wind-based magic system and asks where to go next. Your written answer can set out:

  • The cost of using it and its source
  • Who can't use it
  • What wind can't do. Can it lift a person? Does it fail underground or in still air?
  • How it would change warfare, sailing and trade

Their two follow-ups cover the inevitable "but what if someone…" round. They describe the system in the question itself, so there's nothing to attach.

World bible document (Custom Work). Scope it to one slice: the magic system rules, one nation, or one pantheon with its myth cycle. Include a glossary, a timeline, a rules table and a list of open questions the client still has to decide. For game masters, write for play rather than reading: factions with goals, a rumors table, and three places the party might go next. For developers, flag which lore the player actually sees and which is background only.

Conlangers: naming languages and translated phrases

Conlang buyers include novelists who need names that sound consistent across a map, game developers who need inscriptions, chants or a phrase an NPC mutters, and indie filmmakers who need lines an actor can actually say.

Naming language with sound rules (Custom Work). Deliver:

  • The phoneme inventory
  • Phonotactics (the allowed syllable shapes)
  • A few sound rules and a romanization
  • A small set of roots and affixes
  • 30–50 names for people and places, each with a gloss
  • Pronunciation in IPA plus a plain respelling for readers who don't know IPA

You set the price; a common starting point for a naming language is a flat $100–250.

Phrases and translations (Custom Work). A set number of lines, each with an interlinear gloss, a literal translation and a pronunciation guide. Custom Work deliveries can include audio of 20 minutes or less, so a short recording of you reading the lines can be part of the package. A full language with grammar, morphology and a lexicon is a long project. Sell the naming language first and a grammar sketch as the next order.

Can you also take tips or fund your own game?

Many game writers have their own Twine game, interactive fiction or visual novel on itch.io. Tips let players send a one-time thank-you, with nothing for you to deliver and no membership for them to join. A Goal works for your own project, such as "Commission sprites for my VN demo." Followers make one-time contributions toward it, every contribution is yours whether or not the goal is reached, there's no deadline unless you set one, and there's nothing to ship. Personalized Videos rarely fit this work unless you also voice characters, in which case an in-character message can become a small extra.

How do you start selling game writing on Brillay?

  1. Create your page under the name you write as.
  2. Add one Custom Work listing for the job you're asked for most, such as a dialogue pass. Fill in what the developer gets, what you need, what's excluded and the delivery time.
  3. Add a Paid Question at a lower price for structure and craft questions.
  4. Write your correction policy so it's clear before anyone pays.
  5. Put the link in your bio and on your portfolio. The next time a developer DMs "how much for…", reply with the link instead of a quote.

The details of each offer are on the Custom Work and Paid Questions pages. The developers who hire you for lore often commission art too, so pricing guides like concept art commissions for indie game devs and pixel art tilesets are useful for seeing what your buyers are used to paying. If you also write fiction for readers, see writers and BookTok creators. When you're ready, start your Brillay page.

Frequently asked questions

Can I deliver the script in Twine, Ink or Ren'Py format?

Yes. Write in the developer's syntax and deliver the text as a note, files or a link. Executable and script files are blocked as uploads, so for engine files a plain-text copy or a link to a branch in their repository usually works best.

How much does Brillay cost for a game writer?

There's no monthly fee and no paid tier. A platform fee applies only when a developer actually pays you, at the rates in the pricing section above. Card processing is separate.

Does the developer need a Brillay account to hire me?

No. They read your listing, send their brief and files, and pay by card as a guest.

Can I work under my handle or studio name?

Yes. Developers see the public name you choose on your page, at checkout and on their receipt. Your legal name is used only for identity verification and payouts.

Who owns the lines I write?

You decide, and you should say so in the listing description: whether the client gets full rights to the text, whether you can show excerpts in your portfolio, and how you'd like to be credited.

Can a whole visual novel or world bible be one order?

No. The longest delivery time is five days, so sell one route chapter, one character or one slice of the world per order, and let the developer order the next piece when they're ready.

Start getting paid for the questions and requests you already get

Create your free Brillay link. No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate.

Create your free Brillay link