Grimoire Binding
Your prototype already holds months of design work, spread across docs, boards and your engine. We bind it into Grimoire: restructured, connected to your engine and ready for your AI.
From €4,999 · A year of Grimoire Company included
Today
Design doc
Notion database
Balance sheet
Quest whiteboard
Engine data assets
Restructured, not copied
After Binding
Your game in Grimoire
Two-way sync with your engine
Characters
carry Items · join Missions
Missions
take place in Rooms
Rooms
hold Items and Cards
Cards
change Character stats
Context layer ready for your AI
The problem
Your game is already written. Just not in one place.
By the time you have a prototype or a vertical slice, your game’s content is spread across tools that were never meant to work together.
Documents
Design docs describing systems that have changed since they were written.
Spreadsheets
Databases full of stats, items and balance values, copied by hand.
Whiteboards
Quest flows and character relationships, drawn once and never updated.
Inside the engine
Data assets, prefabs and hardcoded values that only a programmer can reach.
The approach
Not a copy. A better structure.
Moving your content over one-to-one would bring the mess along with it. So Binding starts by rethinking how your game is structured.
We use OOUX (object-oriented UX), a design method we’ve adapted for games. Together with your team, we map what your game is made of.
That map becomes your data model in Grimoire. Where your current structure makes changes hard, we propose a better one and explain why.
Objects
The things your game is made of.
Characters
Missions
Rooms
Relationships
How they connect to each other.
Character
carries
Item
Actions
What players and systems do with them.
Equip
Unlock
Trade
Attributes
The values that define each one.
Health
Cost
Rarity
How it works
From scattered pages to one book
We agree on the timing together when we scope, so it fits your production.
Before kickoff
1
Scoping
A call to agree on your sources, templates and engine. On kickoff day, we take a snapshot of your content.
With your team
2
Workshop
A half-day OOUX session with your designers and a developer. Together we map your game’s objects and how they relate.
Our part
3
Mapping
We design your data model and decide what to restructure. Halfway, we check the direction with you.
Our part
4
Binding
We bring your content into Grimoire, connect your engine and test it in a playable build.
With your team
5
Handover
We walk you through the model: what changed and why. Your context layer is live. Team training is optional.
The promise
After Binding, your team can
Change a design or balance value in Grimoire and see it in a playable build.
Fire golem · Attack damage
12
18
Synced to your engine
In your next playtest
Find everything in one place
All of your game’s content, structured and connected.
Characters
Missions
Rooms
Cards
Let designers ship new content
Build new content with existing mechanics and get it into the game through the same pipeline.
New mission
See what breaks before it breaks
Check what’s affected before you change or remove something. Invalid setups get flagged.
Still used by Missions and Rooms
Ask AI and trust the answer
Answers come from your own data, traced to the entry they came from.
Answer
Mission
Room
without taking on a new integration to maintain.
Scope and price
One price, a clear scope
Limited offer: a year of Grimoire included
Also included
Half-day OOUX workshop
Mid-point check-in
Handover session
Two-way engine sync
Context layer for your AI
Team training, if you want it
We bind a snapshot of your content from kickoff day, with no fixed limit on entries or templates. Custom code in your project isn’t included. More sources or a game in production? We’ll quote it before we start.
Contextual Intelligence
Structure is what makes AI useful
An AI that reads loose docs and spreadsheets has to guess how your game fits together. Once your content is bound in Grimoire, every character, mission and value has a defined place and defined relationships. That is the context your AI works from.
We call this Contextual Intelligence. Binding is the fastest way to get there.
Without structure
AI reads loose pages and guesses how things connect.
doc
sheet
board
?
With Binding
Every answer comes from your game and traces back to its entry.
Answer
Mission
Room
Not a game studio?
Media and tech teams have the same problem: content spread across tools, and AI that can’t see how it fits together. Binding works for you too.
Episodes
Formats
Characters
Learning modules
Product catalogue
FAQ
Questions
Our game is already in production. Can you still do this?
−
Yes. A game in production usually has more content and more sources, so we scope and quote it separately. Book a scoping call and we’ll tell you what it takes.
What if we need more than 2 sources?
+
Do we have to stop working on our game while you bind it?
+
Do you write code in our project?
+
We use a custom engine. Does that work?
+
What do we need to prepare?
+
How much of our team’s time does it take?
+
What happens after the first year?
+
Who does the work?
+
Bring your prototype. We’ll bind it.
A 30-minute call to look at what you have and agree on the scope. You’ll know the price before you commit.