Bring the files you have
Drop brand books, strategy decks exported to PDF and workshop notes. The Brand agent reads PDF, Markdown and plain text, then asks only what your files don’t answer.
Context · Brand System
Brand voice management from group to product. Agents draft from your files. Your team approves.
Product A1’s citrus taste with no sugar. A 330 ml can, launching in June.
Taste seekers who quit sugar but not summer.
Real fruit you can taste, where zero-sugar rivals taste of sweetener.
0 g sugar and 12 % juice. Never “healthy”.
Product A2 inherits Brand A’s Tone of voice and Positioning, so I’ll write only what is its own.
The draft is in the document. Keep or discard each change, then approve it.
Group, sub-brands, divisions, verticals and products, as deep as your company goes. Each level holds its own documents and reads the binding ones above it.
Brand definition. Ten documents, from strategy and positioning to tone of voice, messaging house, personas and guardrails. Agents read the widgets inside them, like the tonality axes.
Six documents per product, from product definition and point of view to ICP and competitive intel. A product inherits its brand’s voice and writes only its own.
Speakers and channels. Who speaks for the brand, with brand voice guidelines drafted from their own posts, and where the brand publishes. The agent suggests both; you confirm them.
Mark a document binding and every level below reads it, read-only. A product inherits its brand’s tone of voice and positioning, and the agent writing for it reads them first.
Diagram of the structure Monobase holds, shown for a fictional company: a group, two sub-brands and their products, with binding documents passing down. Select a part to see what it is and where it applies. Select a dot to read what it is and where it applies; pinch or use the zoom buttons to zoom.
The structure as a list:
Drop brand books, strategy decks exported to PDF and workshop notes. The Brand agent reads PDF, Markdown and plain text, then asks only what your files don’t answer.
Let the agent draft every chosen document in one go, or go step by step and approve each one before the next. Either way, you confirm the structure first.
Less sugar than a soda. Real fruit you can taste: 12 % juice, squeezed. Cold, bright and made for summer.
Summer in a can, all year. Brand A makes real-fruit drinks for people who want it cold, bright and a little sour.
12 % juice, no sweeteners. Every can says where its fruit was grown.
Less sugar than a soda. Real fruit you can taste: 12 % juice, squeezed. Cold, bright and made for summer.
Each agent change arrives as a tracked change in the text. Its card says why, which sources it read and what it assumed. Keep it or discard it, block by block.
Real fruit you can taste: 12 % juice, squeezed. Cold, bright and made for summer.
Summer in a can, all year. Brand A makes real-fruit drinks for people who want it cold, bright and a little sour.
Kept changes stay in the draft. Only Approved moves the production version that agents and new campaigns read, and a campaign keeps the versions it started on.
Proposals. Competitor findings and new files arrive as edits with their sources.
Comments. Each comment stays on its passage when the text moves.
Playbook. One read-only view of what is approved, in progress or missing.
Check rules. The agent turns a document into rules Brand check applies.
Audiences. One registry for every product and campaign, with where each is used.
Agents
Reads your brand documents, researches competitors and drafts changes, with sources.
The Brand System is where Monobase holds what your brand is and how it speaks: your structure from group to product, the brand and product definitions, audiences, speakers and channels, as documents agents read before they write. Agents propose changes; your team approves them.
Brand voice management in Monobase runs through the tree: mark Tone of voice binding at the level that owns it, and every sub-brand and product below reads it read-only and adds only what is its own. Speakers keep brand voice guidelines of their own, drafted from their posts.
Ten brand-level documents, such as strategy, positioning, tone of voice, messaging house, personas and guardrails, plus six per product: product definition, point of view, ICP, competitive intel, a sales deck and a Value Proposition Canvas.
Yes. Drop it into the Brand agent’s intake as PDF, Markdown or plain text, up to 32 MB per file. The agent reads it, asks what is missing and drafts the documents from it.
No. A person confirms the structure and which documents to draft. With “Draft every document” the agent then writes them without stopping, and every change still waits in its document to be kept or discarded.
No. Every agent change arrives as a tracked change with its reason and sources, and a person keeps or discards it. Kept changes stay in the draft; only Approved moves the production version that agents and campaigns use.
No. The agent suggests speakers and channels from your sources, and you confirm them. Speakers are who speaks for the brand, each with a tone of voice and a mandate for where they publish; channels are the networks and accounts the brand publishes on.
Not yet. Ratings on outputs are stored but not used; learning from feedback is planned. Today the brand changes only through edits a person keeps and approves.
Optional cookies help us measure the site and our campaigns. Read more about cookies
Cookie settings
Essential storage only remembers this choice. The rest runs only if you switch it on.