Choose a branding agency by testing how it thinks about your business problem, not by choosing the portfolio you like most. A capable agency should be able to explain how it will research the audience, clarify the position, make design decisions, test the identity in real touchpoints, manage ownership and rollout, and measure whether the system is being used correctly.
The best questions reveal the agency’s process, assumptions, evidence, and limits. They also help you compare proposals that use different language or package the work differently. This guide gives business owners a practical way to prepare the brief, interview agencies, review scope and pricing, identify risk, and select a partner that fits the actual job.
Clarify the problem before contacting agencies
An agency cannot create a useful proposal when the brief says only “we need better branding.” Write a short internal diagnosis first. It does not need to contain the solution, but it should explain the context.
Cover these points:
- What changed in the business, market, offer, or customer?
- What is not working in the current message or identity?
- Which customer touchpoints are affected?
- What must remain recognisable or technically stable?
- Who makes decisions and who will use the finished system?
- What dates, events, contracts, or platform changes affect the schedule?
- What budget range can the business responsibly support?
Separate symptoms from causes. “Our social posts look inconsistent” may be an asset-control problem, a missing design system, or a changing strategy. “We attract the wrong leads” may require positioning and service-page work rather than a new logo. An honest agency should help refine the diagnosis instead of accepting every assumption as fact.
Review the branding and visual identity service and the broader services overview to see how strategic, visual, website, and marketing needs can overlap without becoming the same deliverable.
Questions about strategy and research
1. How will you diagnose the real brand problem?
Listen for a process that uses existing business evidence, customer language, competitor alternatives, stakeholder knowledge, and commercial context. Ask which decisions the research will support. Research should not be a decorative phase that produces a presentation without changing the direction.
A useful answer explains the methods, participant selection, limitations, synthesis, and approval points. It should also say what the agency needs from your team and how much access is required.
2. How do you separate positioning from identity?
Positioning decides what the business should be known for and why a priority customer should choose it. Identity makes that decision recognisable through verbal, visual, and behavioural signals. Ask the agency what happens if the positioning is unclear. If it begins visual exploration without resolving the message, feedback may turn into subjective arguments about style.
3. What assumptions are you making about our audience?
A proposal often contains assumptions because the discovery work has not happened yet. That is acceptable when they are labelled. Ask the agency to identify what it believes, what it knows, and what it will verify. Be cautious when a team makes strong claims about your customers after one introductory call.
4. How will you handle disagreement among stakeholders?
Brand projects bring together founders, sales, marketing, delivery, and sometimes investors or partners. Ask who should contribute, who decides, and how feedback will be gathered. A long group call where everyone gives visual preferences is not a decision model. The agency should create criteria, record decisions, and show how unresolved business questions will be escalated.
Questions about creative work
5. Can you explain the reasoning behind relevant work?
Do not ask only for projects from your industry. Ask for work with a similar problem, audience complexity, number of touchpoints, or organisational constraint. Then ask what the agency learned, which options it rejected, how the final system served the brief, and what limitations remained.
A portfolio proves taste and execution. A case study should reveal thinking, scope, and application. Use the Vedam Vision portfolio and case-study library as reference points when deciding what evidence you need from any shortlisted team.
6. How many directions will you show, and why?
More options do not automatically mean better value. Ask how each direction will represent a distinct strategic route, what will be complete enough to evaluate, and how the selection will be made. Avoid a process where the agency produces many superficial logo options and asks you to choose by taste.
7. How will the identity work beyond a logo?
Ask to see the system across the touchpoints your business needs: website, proposal, social post, sales deck, report, email, signage, product interface, or packaging. The scope should define typography, colour roles, imagery, layout, components, and templates at a level the team can implement.
8. How do you test accessibility?
W3C guidance recommends sufficient contrast, clear navigation, identifiable controls, labelled form elements, responsive layouts, and useful alternatives for images and media. Ask whether the agency tests actual text, buttons, forms, charts, and responsive components, not just the logo on a colour palette.
Questions about scope, pricing, and ownership
9. What exactly is included and excluded?
Request a deliverable list with quantities, formats, variants, review rounds, responsibilities, and acceptance criteria. Clarify whether copywriting, naming, legal searches, photography, illustration, animation, website implementation, printing, and rollout support are included.
Also ask what the agency expects your team to supply. A lower proposal may depend on you providing research, copy, project management, or production that another proposal includes.
10. What happens when the scope changes?
Good projects still discover new needs. Ask how changes are documented, estimated, approved, and scheduled. The answer should protect both sides. Informal additions create budget surprises, rushed work, and disagreement about what “finished” means.
11. What intellectual-property rights will we receive?
Clarify ownership, licences, source files, fonts, stock assets, photography, illustration, software, templates, and third-party materials. Ask when rights transfer and which items remain licensed rather than owned.
WIPO explains that trademarks distinguish the goods or services of one enterprise from another and that protection is obtained through relevant registration systems. Branding agencies are not automatically legal advisers. If naming or trademark availability is part of the project, establish who performs searches and when qualified legal review is required.
12. Which files and documentation will we receive?
Ask for a clear handover list: master logos, exports, colour specifications, font information, image guidance, templates, component libraries, brand guidance, editable source files, and usage rights. Confirm the tools and versions. A business should not discover after launch that everyday updates require unavailable software or an unplanned retainer.
Questions about delivery and implementation
13. Who will do the work?
Meet the people responsible for strategy, writing, design, project management, and implementation where possible. Ask which work is completed internally, which work is delegated, and who remains accountable. The most senior person in the sales meeting may not be involved after the contract is signed.
14. What does the timeline depend on?
Request milestones, decision dates, review windows, dependencies, and launch requirements. Ask how delays from either side affect the plan. A timeline should include research, decision-making, production, quality assurance, handover, and rollout, not only design presentations.
15. How will you protect the current website and search visibility?
If the work includes a domain change, URL change, or platform migration, ask for the URL map, redirects, canonical updates, sitemap plan, analytics controls, Search Console steps, backups, testing, and rollback plan. Google Search Central advises preparing and testing the new site, mapping old URLs to relevant new destinations, using server-side permanent redirects, checking canonicals and robots rules, and monitoring the move.
A visual refresh does not require a URL restructure. Ask the agency to justify technical changes separately from design changes. The working process can help you discuss implementation and verification as explicit phases rather than an afterthought.
16. How will our team learn to use the new system?
Guidelines alone may not change behaviour. Ask about training, recorded walkthroughs, templates, examples, source-file organisation, contribution rules, and ongoing ownership. The finished brand should reduce repeated questions for your team, not create a new dependency for every small asset.
How to compare proposals fairly
Create one comparison sheet. Put each proposal against the same categories:
- Understanding of the business problem.
- Research and positioning depth.
- Creative system and real-world application.
- Accessibility and technical quality.
- Named team and responsibilities.
- Deliverables, quantities, file formats, and ownership.
- Decision process and review rounds.
- Timeline, dependencies, and change control.
- Rollout, training, and post-launch support.
- Price, payment schedule, assumptions, and exclusions.
Do not score only the number of deliverables. A long list can hide shallow thinking, while a smaller scope may solve the core problem more responsibly. Ask agencies to clarify missing details before making assumptions in their favour or against them.
Red flags worth taking seriously
- The agency guarantees commercial results that branding alone cannot control.
- It begins with visual styles before understanding the audience and offer.
- It cannot explain who will perform the work.
- The proposal uses vague deliverables such as “complete branding” without definitions.
- Ownership, licensing, source files, or third-party assets are unclear.
- The timeline leaves no room for research, decisions, testing, or handover.
- Every project follows the same visual formula regardless of the business problem.
- The team dismisses accessibility, implementation, or search migration as someone else’s concern.
- It avoids discussing limitations, risks, or what is outside its expertise.
A red flag does not mean the agency is dishonest. It means the risk needs a clear written answer before commitment.
Questions to ask references
If references are appropriate and permission has been granted, ask about behaviour rather than a general recommendation:
- Did the team understand the business problem before proposing solutions?
- Were decisions, responsibilities, and changes documented?
- Did the people introduced at the start remain involved?
- Were files, licences, and documentation delivered as agreed?
- Could the internal team use the system after handover?
- How did the agency respond when an assumption or direction was wrong?
Respect confidentiality. An agency may be unable to share private commercial details or connect you with every client.
Make the final choice based on working fit
The right branding agency is not necessarily the largest, cheapest, most awarded, or most visually similar to your taste. It is the team whose method, expertise, capacity, communication, and scope fit the problem you need to solve.
Before signing, confirm that the success criteria, deliverables, owners, rights, fees, review model, dependencies, handover, and implementation plan are written clearly. Then make one internal person responsible for timely decisions and consolidated feedback.
You can request a website and brand audit, browse more buying and implementation guidance in the Vedam Vision blog, or use the contact page to discuss the scope your business actually needs before comparing proposals.
