Branding guide · evidence and decision
Use these questions before choosing a branding agency, signing a rebrand proposal, approving an identity refresh, or starting a brand strategy contract.
decision · proof · use
The biggest branding agency red flags are a proposal that sells a new identity before identifying the business problem, no recognition test for existing assets, no written proof that the current brand is the cause, no search and AI migration plan, no acceptance criteria, no rollback rule, and no named decision owner. Before signing, make the agency answer in writing: what must change, what must not change, what evidence supports the move, what surface will be tested, what bad outcome stops rollout, and what proof must exist before the new story goes public.
A proposal can sound polished while leaving the expensive risk unnamed. The owner needs the agency to answer the decision questions in writing before the contract turns a weak problem reading into production.
The first question is not whether the work looks better. The first question is whether the agency can prove the current brand is causing a real commercial problem: fewer qualified leads, weaker trust, wrong category memory, sales friction, hiring drag, shelf confusion, or search invisibility.
A useful agency can defend what should change, what should stay, what should be tested, what they would refuse, and what would make the work stop. A risky agency sells a new surface before naming the old cue, phrase, proof point, route, or buyer habit that still works.
A bad branding agency brief usually sounds reasonable: make us modern, premium, disruptive, simplified, future-facing, or more elevated. Those words are not a problem reading. They become useful only when tied to a buyer behavior, a market comparison, a proof gap, and a launch test.
If the agency cannot separate recognition risk, proof burden, buyer behavior, search memory, AI summaries, acceptance criteria, and rollout control, the proposal is not ready for signature.
These cases show why the agency question must reach beyond taste and into recognition, trust, audience, buyer behavior, and delivery control.
Use the images as inspection layers, not decoration: buyer question, cited source, case evidence, and repair path.
These are not gotcha questions. They make the proposal prove its problem reading before the owner pays for execution.
01
The proposal jumps to logo, name, palette, voice, or website style before naming the business problem.
Demand one written problem reading: the current brand is hurting this buyer decision, on this surface, with this evidence.
02
The agency wants to replace assets without testing whether customers already use them to find, remember, or trust the company.
Require a before-and-after test on the real surface: search result, package, sign, app icon, sales deck, homepage, or referral phrase.
03
The proposal talks about positioning but never lists the proof the market can inspect.
Ask for the source inventory: reviews, cases, objections, offer pages, guarantees, operations, demos, documentation, awards, and third-party profiles.
04
The scope is a menu of workshop, strategy, logo, colors, type, guidelines, and launch assets with no acceptance criteria.
Each deliverable should tie to a decision: what it must clarify, what risk it lowers, and how the owner accepts or rejects it.
05
The agency accepts vague founder language like make us premium, modern, disruptive, elevated, or future-facing without pushing back.
A serious agency should refuse at least one assumption, timeline, audience claim, or visual request because it creates risk.
06
The pitch relies on beautiful case images but does not explain the starting problem, constraint, market behavior, or result.
Ask for one case where the agency protected a working cue, killed a risky idea, or changed scope after evidence contradicted the brief.
07
The proposal ignores old names, snippets, review profiles, redirects, comparison searches, brand entities, and AI summaries.
Require a migration checklist for old-to-new language, third-party profiles, schema, redirects, citations, sales collateral, and answer-engine surfaces.
08
The agency plans to present concepts to stakeholders but not test whether buyers understand, trust, compare, or act faster.
The test should measure a real decision: recognition, category clarity, trust, price confidence, lead quality, checkout confidence, or referral recall.
09
The agency can define the launch but not the metric that pauses, reverses, or narrows the rollout.
Write the stop rule before launch: if recognition, leads, conversion, search demand, sales velocity, or support confusion moves past a threshold, who acts and by when.
10
The work keeps moving because everybody likes part of it and nobody owns the final no.
Name the person who can say PASS, ADJUST, or STOP after evidence is reviewed, even if creative work has already started.
A decision page has to prevent a bad approval, not merely define a term.
The weak version starts with a familiar sentence: the logo feels old, the website looks tired, the name sounds generic, the message feels flat, or AI describes the brand like everybody else. Those may be real symptoms. They are not yet a decision reason.
The useful move is to name the broken layer. Is the customer unable to recognize the brand, trust the proof, understand the offer, repeat the name, cite the source, or take the next action? Each answer points to a different repair.
Do not let the team buy a new surface while the old constraint stays untouched. If the problem is proof, the work is proof. If the problem is retrieval, the work is source and category clarity. If the problem is recognition, the work is protecting the cue before changing it.
The stop rule should be written before the spend moves: what signal pauses the project, who owns the decision, and what happens if the change makes branded search, qualified leads, trust, or buyer comprehension worse?
Gap, Tropicana, British Airways, Leeds United, Hertz / Accenture show why the same surface move can mean different things under different constraints.
Ask what problem the rebrand solves, what will be preserved, what evidence supports the change, how the work will be tested, and what kill condition stops a bad rollout.
Choose the agency that can explain the business problem, show evidence, protect useful recognition, name what should not change, test the new direction, and define the stop rule before launch.
Branding agency red flags include selling identity before problem reading, vague strategy language, no recognition test, no proof inventory, no buyer behavior test, no search and AI migration plan, no acceptance criteria, no rollback rule, and a proposal that treats taste as evidence.
Rebranding agency red flags include replacing known assets without pricing the recognition loss, ignoring old-name search demand, skipping customer testing, promising a bigger story without proof, and launching without a stop rule.
A proposal is weak when it sells modernization without naming the buyer behavior, recognition cue, trust problem, evidence gap, rollout risk, or metric that would prove the change is working.
A bad brief uses words like premium, modern, disruptive, elevated, or future-facing without naming the buyer problem, the proof gap, the protected asset, the test surface, and the decision owner.
Ask whether the issue is identity, positioning, proof, product, search visibility, AI visibility, website conversion, or customer trust before asking for a new name, logo, or visual system.
It should prove the current brand problem, the old assets worth preserving, the risk of changing them, the evidence behind the new direction, the migration plan, and the test that decides whether rollout should continue.
Yes. Written answers reduce taste arguments and make the approval decision easier to check later.