A brand strategy engagement should produce four things you can hand to someone who was not in the room: a foundation document that says what the company stands for and who it is talking to, an identity system with defined logo, type, and color behavior, a set of real applications that prove the system works, and written guidelines that let other people apply it without asking. If what you receive is a logo file and a color palette, you bought a logo, not a strategy.
Goodthings, a branding studio that runs brand strategy as four gated phases, treats each phase as producing an artifact rather than a milestone. The foundation document exists so that every later decision has something to be measured against. The identity system exists so the brand behaves consistently in situations nobody anticipated. The applications exist because a system that only works on a presentation slide is not finished. The guidelines exist because you will hire someone in eighteen months who needs to get it right on their first day.
Gating matters more than the list. Each phase has to close before the next opens, because the most expensive thing in brand work is not the design, it is redoing design that was built on an assumption nobody had confirmed.
The engagement opens with a focused 60-minute session with the founding or leadership team. No design, no deliverables, no moodboards. The questions are the uncomfortable ones: what does this company actually need to say, who is it saying it to, what has to be true about how it looks and sounds, and what would make a piece of work obviously wrong.
An hour sounds short. It is short on purpose. The constraint forces the group to answer rather than explore, and it surfaces disagreement early, while disagreement is still cheap. If the leadership team is not aligned on what the company stands for, this is where you find out, and finding out in week one costs a conversation instead of a rebuild.
What you get out of it is a written foundation document. Positioning, audience, voice, the non-negotiables. It is the reference every later review points back to, which is what stops reviews from becoming taste debates.
The deliverable people expect is a logo. The deliverable that matters is a system: logo and its permitted variations, a type system with defined hierarchy, a color palette with actual hex and RGB values documented, and a visual language that covers photography, illustration, and layout behavior.
Expect two or three intentional directions, not five. Five directions is a sign the foundation phase did not close properly, because a solid foundation eliminates most of the possibility space before design starts. Two or three well-argued directions produce a decision. Five produce a committee.
The test of this phase is not whether the leadership team likes the logo. It is whether a designer who has never met you can open the guidelines and produce something on brand.
Applications take the identity into real artifacts: collateral, the homepage, the pitch deck, the key brand moments the company will actually be judged on. This phase exists to break things. A palette that looked balanced in isolation turns out to have no workable text color. A logo lockup that read well at presentation scale disappears at favicon size. A voice that sounded confident in the abstract sounds arrogant in a support email.
Finding those problems here is the point. Finding them after launch means fixing them in public.
A brand that is not live is not finished. The last phase is the infrastructure: the site, and the tooling that makes the site do something. For SCALA.AI, that meant a Webflow site with HubSpot and GA4 both operational on launch day rather than two weeks after, because the launch was tied to an $8.5M seed announcement that ran in GeekWire. The brand went from nothing to a full system and a live site in roughly ten weeks.
If web is the larger part of your question, what a Webflow website costs breaks down the drivers, and what to expect in a handoff covers what should arrive at the end of the build.
Worth saying plainly, because vague scope is where these projects go wrong. It does not include unlimited rounds. Gated phases and unlimited revision are incompatible ideas, and an engagement that promises both is really promising neither. It does not include a naming exercise unless naming is scoped and priced as its own phase, because naming has its own legal and availability work. It does not include ongoing campaign production, which is a different shape of engagement. And it does not include making a decision the leadership team is unwilling to make.
One or two people with authority to say yes. That is the single strongest predictor of whether the engagement lands on time, and it has nothing to do with the creative team. When every stakeholder reviews every stage, the approval loop takes longer than the work inside it.
The founding or leadership team needs to be present for the foundation session specifically. Delegating that hour is the most common way an engagement quietly fails, because the foundation document then reflects an interpretation of what leadership believes rather than what it actually believes, and the gap surfaces in phase three when it is expensive.
Ask what you receive in writing at the end of each phase. Ask whether the foundation work happens before any design is shown, and what happens if the two disagree. Ask how many directions you will see and why that number. Ask whether the guidelines will let a new hire or an outside vendor apply the brand without a call. Ask what is explicitly out of scope.
Specific answers mean a real process exists. Vague answers mean you are buying a logo with a strategy label on the invoice. If your actual question is whether you need a full engagement at all, rebrand versus refresh is the better place to start, because a refresh is a genuinely smaller piece of work and plenty of companies only need that.
This is the part most brand projects handle badly. A brand system decays the moment it meets a real content calendar, because every week produces a case the guidelines did not anticipate. Some companies solve this with an in-house hire. Others keep the team that built the system on an ongoing basis so the same people apply it, which is the model behind an embedded creative team: one team holding brand, web, video, and content, with the institutional knowledge already loaded.
AIIR Products has run that way with Goodthings for over five years, one team carrying the identity, the design system, the website, and the trade show presence, including a 10 by 20 foot booth at AHR Expo 2026. Nothing in that list gets re-explained in January. If you are weighing that against a hire, the numbers in fractional versus in-house are the comparison to run. If the question is why the ongoing model outperforms per-project work at all, the embedded model makes that case.
Four gated phases, four artifacts, and a written foundation that every later decision answers to. One or two decision-makers, leadership present for the foundation hour, and scope stated plainly including what is excluded. Guidelines good enough that a stranger can apply the brand correctly. Anything less than that is a logo with a longer invoice.