Brand system in 72 hours
Three days from a name and a paragraph to a brand you can ship with: wordmark, type, color, voice, and a token file the code reads.
A brand is a set of decisions that keep getting made the same way. Most early companies do not need a long process to arrive at those decisions. They need someone to make them, write them down, and put them where the code can read them.
We run a 72-hour brand system for Vinyatan ventures and for Create partners launching something new. It is not a brand strategy engagement. It is the minimum set of decisions a team needs to ship a product, a site, and a first campaign without arguing about blue.
What 72 hours produces
- Positioning: one sentence, one paragraph, three proof points.
- Naming check: the name is available where it matters and does not mean something unfortunate.
- Wordmark and a mark, as SVG, with clear-space and minimum-size rules.
- Type: a display face, a text face, a mono face, and a scale.
- Color: a base palette, semantic roles, and light and dark themes that pass contrast.
- Voice: principles, a do-and-do-not list, and twenty rewritten sentences.
- Tokens: a JSON file the codebase and the design tool both read.
- Proof: a landing page, a social template, and an email header built from the tokens.
Hour zero
Before the clock starts we need three things: the name, a paragraph on what the company does and for whom, and a list of five brands the founder admires and two they cannot stand. That last list is more useful than any brief. It tells us where the taste boundary is, which is the thing a brief never says.
Day one: position and direction
Day one is positioning and direction. We write the sentence and the paragraph first, then generate three visual directions that each take the positioning seriously. Not three moods. Three arguments about what the company is. Each direction is shown as a full landing page and a social post, because a logo on a white square tells you nothing about how a brand behaves under real copy.
The founder picks one by the end of day one. Not a blend. Blends produce brands that look like everyone else, and the whole point of choosing against a real page is that the choice is about behavior, not taste.
Day two: the system
Day two builds the system inside the chosen direction. The wordmark is refined and drawn as proper vectors. The type scale is set and tested at real sizes on real copy. The palette expands into semantic roles: background, surface, text, muted, accent, success, warning, danger, each in light and dark. Every pair is checked for contrast. Anything that fails is fixed, not excused.
Voice gets its own block of time. We pull every sentence the company has already written, sort what sounds right from what does not, and turn that into rules with examples. Models generate the first pass of the twenty rewrites. A person edits every one, because voice is the part of a brand that models flatten fastest.
Day three: tokens and proof
Day three is where most brand work stops short. We ship the tokens file, wire it into the codebase and the design tool, and build three real things from it. If the landing page looks wrong, the tokens are wrong, and we fix the tokens rather than the page.
The tokens file is the deliverable engineers actually use. Everything else in the package explains it. When a venture moves into a Build sprint the next week, the sprint starts from these tokens and nobody has to ask what the accent color is.
Voice
Voice rules are only useful if they are specific enough to fail. Be human is not a rule. Never open with a question is. The do-and-do-not list is short and every line has an example attached, because a rule without an example gets interpreted differently by every writer and every model.
- Do: lead with the noun. Short sentences. Numbers as digits.
- Do: say what the product does before what it means.
- Do not: exclamation marks, hedging adverbs, or the word seamless.
- Do not: describe the customer's feelings. Describe their situation.
What we do not do in 72 hours
- Research the category. You know it; we ask you.
- Explore more than three directions. Three is enough to find the edge.
- Design a full component library. Tokens first; components follow in a Build sprint.
- Write a manifesto. The positioning paragraph is the manifesto.
- Produce a hundred-page guideline document. Nobody reads them, and the tokens file is the guideline.
How it holds up
The 72-hour system is meant to be revised. Most ventures change the palette or the voice within six months as they learn who their customers actually are. That is fine. The tokens file makes the change a pull request instead of a redesign. What rarely changes is the direction chosen on day one, because it was chosen against a real page and real copy, not a mood board.
The test on day three
Someone who has never seen the brand builds a page from the tokens and the voice doc alone. If it looks and reads like the brand, the system works. If it needs a designer standing over it, it does not, and we go back to the tokens.
We run this playbook on our own ventures before we run it for anyone else. The next step after a brand system is usually the landing page, and the playbook for pages that load in under a second picks up where this one ends.