Choosing a web design agency: questions, evidence and ownership
Choose the team that can explain the work, show relevant evidence and make responsibilities clear. An attractive portfolio is a useful starting point, not the whole decision.
Talk through your website briefIn this guide
Give each agency the same short brief
Describe your audience, services, current website and the useful action customers should take. Add essential connections, content responsibilities and any target date with its reason. Separate requirements from ideas you are still exploring. This gives each agency a consistent starting point without requiring you to write a technical specification.
For a professional firm, our website-structure guide helps organise services and evidence. A shop or application needs different questions; ask the agency to identify those differences before it recommends a build approach.
Ask what the team actually contributed
For each relevant example, ask which company delivered it, what the proposed team did and what can be shown with permission. A design concept can demonstrate judgement and visual direction. It does not establish a client relationship or a measured business result.
Previous-company experience can be relevant when the role is clear. Keep it separate from the agency's own client work. If a project is confidential, ask the agency to explain its method or demonstrate a fictional workflow instead of disclosing restricted information.
You can meet BrandFlame's team and try our labelled enquiry workflow demonstration. The demonstration uses fictional inputs; it is not a customer case study or proof of commercial results.
Compare responsibilities as well as features
Ask who will lead discovery, design, development, content and testing, and how outside contributors are managed. You need a clear route for decisions and feedback, including what happens when the person who approves content is unavailable.
| Question | Useful evidence to request |
|---|---|
| What are we buying? | Deliverables, exclusions and acceptance criteria |
| Who writes and approves content? | A responsibility list covering copy, images and factual claims |
| How do we review progress? | Review stages, decision owners and change handling |
| What will be tested? | A relevant acceptance checklist and how unresolved issues are recorded |
| Who operates the site? | Editing, hosting, access and support responsibilities |
| What happens if we move supplier? | Export options, account access and agreed handover arrangements |
A confident answer is less useful than a specific one. Ask the agency to walk through an ordinary enquiry, a validation error and a failed connection. An acknowledgement should reflect what actually happened; a button click is not evidence that an enquiry reached its intended destination.
Make ownership and access explicit
Ask which accounts your business will control and which services will be provided through the agency. Record domain access, hosting arrangements, source-code and content rights, design files, image and font licences, and third-party subscriptions in the proposal or agreement.
Do not assume that paying for design transfers every third-party licence, or that every platform can be exported in the same way. Ask what you receive, in what format and under which agreed terms. Have contractual questions reviewed by your own appropriate adviser where needed; a supplier checklist is not a substitute for the agreement.
Ask how quality will be checked
The test plan should reflect actual user tasks: reading services, using navigation on a phone, operating controls with a keyboard, correcting form errors and reaching the expected confirmation. Agree how performance will be measured and which devices or assistive-technology checks are included. A single automated score does not describe the whole user experience.
The W3C's accessibility planning resources describe accessibility as work with defined roles and ongoing responsibility. Ask who checks the content and interactions and how identified issues will be addressed, rather than accepting an unsupported blanket assurance.
For a redesign, ask how existing useful URLs and enquiries are protected. Our redesign checklist gives you a practical launch-review structure.
Use a short evidence log
For each shortlisted agency, record the requirement, answer, evidence and unresolved question. Use “confirmed”, “needs clarification” or “outside scope” rather than an unexplained numerical score. A supplier who clearly identifies a limitation may be easier to work with than one who says yes to everything.
A fictional example: two agencies show polished restaurant designs. One explains the menu-editing workflow and checks the venue's reservation provider. The other promises a booking integration without asking which provider is used. Resolve that uncertainty before comparing the quoted totals. This is an illustrative selection exercise, not a claim about a real agency.
Finish the shortlist with operating questions
Confirm the handover, initial support arrangements, process for later changes and responsibility for renewals. Ask how faults are reported and what is outside the care agreement. Keep ownership and support answers beside the quote so they do not disappear after selection.
Budget comparison is a separate task: use the website cost worksheet to compare build, recurring and usage-based charges on the same basis. When you are ready to discuss scope, our website design service sets out the approach to planning, development and handover.
Prepared by BrandFlame with AI assistance. Checklists are planning tools; examples are illustrative unless identified as documented work. Your proposal defines the agreed services and responsibilities.