Four weeks from kickoff to a complete brand system. Clients who've gone through a six-month rebrand at another agency think that timeline sounds reckless. When they understand the structure, they realize the six-month version was the reckless one.
Long brand projects aren't long because branding is complex. They're long because of four specific process failures that almost every agency repeats: revision rounds without defined completion criteria, mood boards used as a substitute for strategic conviction, stakeholder approval processes without a defined decision-maker hierarchy, and no clear definition of what "done" looks like at each phase.
Mood boards deserve particular attention. A forty-slide mood board that takes two weeks to produce and two more weeks to align on is not a strategy tool — it's a way to generate the appearance of strategic thinking while deferring the hard work of actually having a point of view. We don't use mood boards. We develop a direction, present it with reasoning, and defend it.
The first week is entirely verbal. No design work starts until we have four things pinned down with precision.
We run a two-hour discovery session with the founders or key stakeholders. The session is built around four questions that we've refined over dozens of engagements:
We leave week one with a positioning statement, one primary buyer persona written in specific behavioral terms, and three brand character keywords. Everything in weeks two through four is derived from these.
The fastest brand projects we've run weren't rushed. They were the ones where the client made a decision and didn't change their mind. Speed is a byproduct of clarity.
Not mood boards. Not "visual territories." Two distinct creative directions, each fully developed enough to make a real decision.
Each direction includes: a logo mark and logotype, a complete type pairing with usage rationale, a six-color palette with accessibility notes, and at least one real-world application — a web header mock, a business card, or a key marketing surface. The application is critical: it forces us to test whether the direction works outside an isolated logo lockup, and it gives the client a concrete reference for how the system will live in the real world.
Each direction is presented with explicit reasoning: why this typeface, what this color system communicates, how the choices connect back to the positioning and persona work from week one. We don't present options without opinions. That's not a presentation — it's a multiple-choice test.
At the end of week two, the client chooses one direction. We don't blend them. Blending is how you get a brand that says two things at the same time and convinces no one of either.
Week three is where the system is built. The logo is refined across all required lockups: primary, horizontal, stacked, icon-only. The type scale is specified across all hierarchy levels. The color palette is documented with exact values, contrast ratios, and usage rules.
We apply the system to four to six real surfaces: web desktop and mobile, email, at least one social format, and one physical collateral piece. These aren't concept mocks — they're production-ready compositions that the client's team can use as reference for any future application.
Three revision rounds happen during this week, all in context. No revising the logo mark in isolation while ignoring how it affects the type pairing. Every change is evaluated systemically.
The final week produces the brand book and all deliverable files. The brand book is not a decorative document — it's a practical reference that answers the question "how do I make this decision without calling you?" for every common scenario a designer, marketer, or contractor might face.
It includes: strategic rationale (the positioning work that drove every design decision), logo usage rules with explicit do/don't examples, the complete type and color system with exact specifications, imagery and photography art direction, voice and tone guidelines, and an extension guide for common applications we didn't build during the engagement.
We deliver a recorded walkthrough of every decision in the system — not just what was built, but why. This is the part most agencies skip. It's also the part that makes the system actually usable by a team that wasn't in the room when it was developed.