Context · Brand System

Your brands branch out.
Shared rules follow.

Brand voice management from group to product. Agents draft from your files. Your team approves.

Every brand, product and brand voice.Defined once.

  • 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.

  • 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.

Binding rules pass down the tree. Each product writes only what is its own.

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:

  • Group (Group)
    • Positioning (Document, binding below). Inherited by Sub-brand A, Sub-brand B
    • Tone of voice (Document, binding below). Inherited by Sub-brand A, Sub-brand B
    • Guardrails (Document, binding below)
    • Personas (Document). Inherited by Personas, Personas
    • Visual identity (Visual identity). Used by Templates, Templates
    • Design system (Design system). Used by Templates, Templates, Templates, Templates
    • Media library (Media). Shows Product A1, Product B1, Product B2
    • CEO (Speaker). Publishes on LinkedIn, Website
    • LinkedIn (Channel). Published by CEO
    • Website (Channel). Published by CEO
    • Sub-brand A (Sub-brand). Inherits Positioning, Tone of voice
      • Positioning (Document, binding below). Inherited by Product A1, Product A2, Product A3
      • Messaging house (Document, binding below)
      • Personas (Document). Inherits Personas
      • CMO (Speaker). Publishes on Instagram, Newsletter, Website, TikTok
      • Instagram (Channel). Published by CMO
      • Newsletter (Channel). Published by CMO
      • Website (Channel). Published by CMO
      • Templates (Templates). Follows Visual identity
      • Product A1 (Product). Media from Media library. Inherits Positioning
        • Product sheet (Document)
        • Positioning (Document)
        • Packshots (Media)
        • Templates (Templates). Follows Design system
      • Product A2 (Product). Inherits Positioning
        • Product sheet (Document)
        • Packshots (Media)
        • TikTok (Channel). Published by CMO
      • Product A3 (Product). Inherits Positioning
        • Product sheet (Document)
        • Packshots (Media)
        • Templates (Templates). Follows Design system
    • Sub-brand B (Sub-brand). Inherits Positioning, Tone of voice
      • Positioning (Document, binding below)
      • Tone of voice (Document, binding below). Inherited by Product B1, Product B2, Product B3
      • Messaging house (Document, binding below)
      • Personas (Document). Inherits Personas
      • Brand lead (Speaker). Publishes on Instagram, TikTok, Newsletter
      • Product lead (Speaker). Publishes on TikTok, Website
      • Instagram (Channel). Published by Brand lead
      • TikTok (Channel). Published by Brand lead, Product lead
      • Newsletter (Channel). Published by Brand lead
      • Templates (Templates). Follows Design system, Visual identity
      • Product B1 (Product). Media from Media library. Inherits Tone of voice
        • Product sheet (Document)
        • Positioning (Document)
        • Packshots (Media)
      • Product B2 (Product). Media from Media library. Inherits Tone of voice
        • Product sheet (Document)
        • Packshots (Media)
        • Website (Channel). Published by Product lead
      • Product B3 (Product). Inherits Tone of voice
        • Product sheet (Document)
        • Packshots (Media)
        • Templates (Templates). Follows Design system

From your files to an approved version.

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.

Choose how it gets built

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.

Every change comes with a why

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.

Approve the version agents read

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.

It stays current.You stay in charge.

  • 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

The agent behind your Brand System. It drafts from your files. A person approves.

All agents

Questions about the Brand System

What is a Brand System in Monobase?

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.

How does brand voice management work across sub-brands?

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.

What is in the canonical set?

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.

Can we import our brand book?

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.

Does the agent build the Brand System on its own?

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.

Do agents change approved documents without us?

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.

Are speakers and channels created from our PDF?

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.

Does the Brand System learn from our feedback?

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.