Design that makes mechanics mean something.
Narrative design, worldbuilding, dialogue, quests and GDDs — the connective tissue between story and systems.
Overview
Story and systems, designed together.
Our narrative designers and writers work in Arcweave and Twine, alongside the game designers who own systems, quests and puzzles. That means dialogue that reflects mechanics, quests that teach systems, and GDDs that a team can actually build from — proven in our own choice-driven title shipped on Steam.
GDD creation
Design documents with scope, loops and progression defined tightly enough to estimate and build.
Narrative & worldbuilding
Setting, factions, characters and lore that hold together — and hold up under player scrutiny.
Dialogue & branching
Choice-driven writing structured in Arcweave and Twine, ready for engine export.
Quest & puzzle design
Quests, puzzles and level beats that pace the game and pull players forward.
In engine
On the page, in the game.
Full portfolio on ArtStation
Packages
Simple, transparent pricing.
- GDD SprintScoped design document a team can build fromfrom$1,800
- Narrative & DialogueWorldbuilding and branching dialogue, engine-readyfrom$2,000
- Quest & Level DesignQuests, puzzles and level beats, documentedfrom$1,500
How we work
A pipeline built for speed and craft.
We integrate fast, communicate clearly and deliver reliably — onboarding in 1–2 days, weekly deliverables, and work-in-progress previews every 24 hours.
Concept & Pre-production
Goals, scope and the core loop locked first — GDD, references and a plan you can hold us to.
Blockout & Assets
Grayboxes, prototypes and concept passes that prove the idea before full production begins.
Production
Art, animation, code and audio built in weekly sprints — in your pipeline or ours.
Polish & Ship
Optimisation, QA, porting and store assets — until it plays as good as it looks.
Questions
Design & writing, answered.
Can you work inside our existing lore?
Yes — we onboard on your bible, flag contradictions, and extend the world in its own voice.
Do you write for localisation?
We write with string budgets, variables and locale constraints in mind, and structure files for clean handoff.
What's a typical engagement?
Anything from a GDD sprint to embedded narrative support across a production — hourly, fixed or weekly.
Let's talk
Let's build what's next.
Tell us what you're making. We usually come back within 24 hours with ideas, timelines and a quote.
- We act as an extension of your team, not a vendor.
- Quotes within 24 hours, onboarding in 1–2 days.
- Work-in-progress previews every 24 hours.
Prefer it quick and informal? So do we: