Key takeaway
Most attempts to build a brand system from scratch fail on sequence. Founders start with whatever blank page bothers them most, usually a visual palette or a mission statement, instead of building in the order the rest of the system actually depends on. The working sequence is Positioning first, then Audiences and Competitors, then Messaging and Voice + Tone, with Product written alongside and Visual Identity running in parallel. Approval rules come once the libraries have settled enough to be worth governing. Skip the order and you'll produce seven libraries that don't agree with each other.
Nobody starts a brand system with a blank canvas anymore. Most founders start with a logo file from a freelance designer, a tagline someone workshopped in a Slack thread, and a vague sense of three adjectives the company is supposed to be. That's raw material, and the instinct to fill the gaps by tackling whatever feels most urgent produces a specific, predictable failure: a voice guide with no positioning behind it, a mission statement nobody derived any messaging from, and a set of brand colors picked before anyone decided who the brand was actually for.
Building a brand system from scratch usually fails on sequence. Each of the seven types of brand context depends on the ones before it, and building out of order produces libraries that technically exist and don't agree with each other.
The order problem
Treat the seven libraries as independent checklist items and you'll fill each one from whatever's easiest to write that day. Visual Identity gets attention first because it's satisfying and someone on the team already has design instincts. Voice + Tone gets written next as a page of adjectives because that's the fastest thing to produce under deadline. Messaging comes out of a single brainstorm. Positioning, Audiences, and Competitors get skipped entirely, because nobody assigned them to a specific person and they don't feel like brand work.
The result looks complete from a distance. Open it up and the voice guide describes a confident, bold company while the messaging leads with hedged, feature-by-feature claims because nobody had decided what the brand was actually competing on. Two people who both read the same "complete" brand system produce contradictory work, and neither one is wrong, because the system never established which claim should win.
Sequence fixes this because later libraries are supposed to derive from earlier ones. Messaging should be a translation of Positioning for a specific audience weighing specific alternatives. Voice + Tone should express the character Positioning describes. When you build in dependency order, each library has something upstream to check itself against. When you build in whatever order feels urgent, nothing checks against anything.
Start with Positioning
Positioning sets where the brand competes and why it wins, covering the category, the value propositions, the differentiators, and the mission, values, and story behind them. It also holds the brand's disposition: what it claims first, what it concedes, how it handles being wrong, and what it refuses to do. Everything else translates from it, so it has to come first. It's also the layer most founders skip because "where do we compete and why do we win" feels less concrete than "what do we say."
Picking a primary and secondary brand archetype and naming the tension between them in one sentence gets you into this layer faster than a values workshop does, because a named tension works as a decision rule. An authority-primary, craft-secondary company resolves a pricing objection by asserting its strength and then pointing to the specific detail it does better than anyone. A community-primary, authority-secondary company resolves the same objection by naming the gap out loud and trusting the relationship to hold. Both are coherent, and neither is right or wrong. But you can't write a voice guide, a messaging framework, or a sales script until you know which one your company actually is. The Bestiary quiz is a fast way to get a first answer, and the answer is worth revisiting once you've got a few months of real decisions to check it against.
Write a one-paragraph positioning statement beside the archetype pair. Name the category, the value you deliver, and the differentiator you can prove.
Audiences and Competitors come before Messaging
Once Positioning is set, the next libraries are Audiences (who you're talking to, in enough specificity that "everyone who needs this" isn't an acceptable answer) and Competitors (who you're compared against and how you frame them). Both have to exist before Messaging, because a message is a positioning claim aimed at a specific buyer who is weighing specific alternatives.
Brand-from-scratch efforts often skip this step, because audiences and competitors feel like sales or research work, and the founder doing both jobs at once defaults to writing messaging straight from instinct. The result is a value proposition that sounds fine in isolation and falls apart the moment someone asks who specifically it's for and what it's being weighed against. Brand guidelines that skip straight to voice and messaging tend to read well and produce generic output, because the layer that should have constrained the claims was never built.
Write Audiences and Competitors as short, specific records before you touch Messaging. A real description of your primary buyer, including the objection they actually raise, and a list of the alternatives they compare you against will save you from rewriting your messaging library twice.
Messaging and Voice + Tone, with Product alongside
With Positioning, Audiences, and Competitors in place, Messaging and Voice + Tone have something to translate. Messaging turns the positioning into claims for each audience, with proof points that hold up against the competitors you named. Voice + Tone turns the brand's character into language, with rules for how the register shifts between a sales email and a support reply.
Product runs alongside these two. It records what the offer is and does, its features, and what each one is called, and you can start it as soon as Positioning names the category. Messaging draws its proof from Product, and Voice + Tone draws its naming rules from it, so keep it current while both are being written.
Visual Identity runs in parallel, approvals come last
Visual Identity, the actual colors, typography, and imagery direction, doesn't depend on the verbal libraries the way Messaging and Voice + Tone do. It can be built in parallel with Positioning rather than waiting in line behind it. That helps, because it's also the library most teams already have some version of from launch.
Approval workflows, usage rights, and versioning rules are the part to hold until last. They describe how the workspace is managed, and none of that means anything until you know what you're governing. A team that writes an approval process before finishing Positioning and Messaging ends up governing a brand system that's still going to change shape twice more before it settles.
Building from scratch vs. inheriting a mess
Most teams reading this aren't actually starting from zero. They're starting from a fragmented system: a logo file, an old positioning deck, a voice guide someone wrote two jobs ago, all partially done and disagreeing with each other in ways nobody's mapped. The seven-library sequence still applies, just as a remediation order instead of a construction order.
Audit what exists against all seven libraries first, the same way you'd run a brand health score, and gaps often cluster in Positioning, Audiences, and Competitors, the libraries teams tend to skip because they don't feel like brand work. Fill those gaps in dependency order rather than in whatever order they happen to be missing. Fixing a thin Messaging library before Positioning exists just produces a second messaging library that needs fixing again in six months, once Positioning finally gets written and contradicts it.
Building or rebuilding with the library structure explicit from the start turns "we need to work on our brand" from an open-ended, feeling-based project into a specific, ordered list of records to write, in an order where each one checks against the one before it. Once all seven exist and agree with each other, they become a repository you can store, version, and hand to any tool or person without each one reinventing what the brand is supposed to mean.
Building in the right order takes roughly the same effort as building out of order. The difference shows up eighteen months later, when your voice guide, your messaging, and your sales deck still say the same thing about who you are. Join the Tonika waitlist to build your seven libraries in the sequence that actually holds together.
FAQ
What's the right order to build a brand system in?
Start with Positioning, since it sets the category, value propositions, and differentiators every other library translates from. Build Audiences and Competitors next, because Messaging depends on both. Messaging and Voice + Tone follow, with Product written alongside them. Visual Identity can be built in parallel with any of the verbal libraries since it doesn't depend on them. Approval workflows come last, once there's an actual system to govern.
Why does the order matter if all seven libraries eventually get filled?
Later libraries are meant to derive from earlier ones. Messaging should translate Positioning into claims for a specific audience weighing specific competitors. Voice + Tone should express the character Positioning describes. Building out of dependency order produces libraries that are individually complete but contradict each other, because nothing was checked against an upstream reference when it was written.
Which library do most brand-from-scratch efforts skip?
Positioning, Audiences, and Competitors get skipped often, because they read as strategy or sales work and don't have an obvious single owner. Teams jump straight to Messaging and Voice + Tone instead. The claims and tone sound reasonable in isolation and fall apart once someone asks who the message is for and what it's competing against.
Do I need to start over if my existing brand system is a mess instead of a blank page?
No. Audit what exists against all seven libraries, find the gaps, and fill them in the same dependency order you'd use starting from scratch: Positioning, then Audiences and Competitors, then Messaging and Voice + Tone, with Product alongside and Visual Identity in parallel. Fragmented systems often have gaps clustered in Positioning, Audiences, and Competitors, since those are the libraries teams tend to skip.
JSON-LD Schema
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Building a brand system from scratch: the 7-library approach.",
"description": "Build a brand system from scratch without wasting the first draft. Fill your 7 libraries in dependency order, starting with Positioning.",
"author": {"@type": "Person", "name": "Nicole Cathcart"},
"publisher": {
"@type": "Organization",
"name": "Tonika",
"logo": {
"@type": "ImageObject",
"url": "https://tonika.io/logo.svg"
}
},
"datePublished": "2026-10-01",
"dateModified": "2026-10-01",
"mainEntityOfPage": "https://tonika.io/blog/build-brand-system-from-scratch",
"keywords": ["build brand system", "build a brand system from scratch", "brand context repository", "7 libraries of brand context", "brand archetypes", "brand system for startups"]
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What's the right order to build a brand system in?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Start with Positioning, since it sets the category, value propositions, and differentiators every other library translates from. Build Audiences and Competitors next, because Messaging depends on both. Messaging and Voice + Tone follow, with Product written alongside them. Visual Identity can be built in parallel with any of the verbal libraries since it doesn't depend on them. Approval workflows come last, once there's an actual system to govern."
}
},
{
"@type": "Question",
"name": "Why does the order matter if all seven libraries eventually get filled?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Later libraries are meant to derive from earlier ones. Messaging should translate Positioning into claims for a specific audience weighing specific competitors. Voice + Tone should express the character Positioning describes. Building out of dependency order produces libraries that are individually complete but contradict each other, because nothing was checked against an upstream reference when it was written."
}
},
{
"@type": "Question",
"name": "Which library do most brand-from-scratch efforts skip?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Positioning, Audiences, and Competitors get skipped often, because they read as strategy or sales work and don't have an obvious single owner. Teams jump straight to Messaging and Voice + Tone instead. The claims and tone sound reasonable in isolation and fall apart once someone asks who the message is for and what it's competing against."
}
},
{
"@type": "Question",
"name": "Do I need to start over if my existing brand system is a mess instead of a blank page?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Audit what exists against all seven libraries, find the gaps, and fill them in the same dependency order you'd use starting from scratch: Positioning, then Audiences and Competitors, then Messaging and Voice + Tone, with Product alongside and Visual Identity in parallel. Fragmented systems often have gaps clustered in Positioning, Audiences, and Competitors, since those are the libraries teams tend to skip."
}
}
]
}