What Questions Should You Ask a Website Design Agency?
The best agency questions reveal what will be delivered, who owns each decision and how the finished website will be tested and supported.
Part of our guide: How Much Does a Small Business Website Redesign Cost in the UK?
Ask a website design agency how it will understand your business, define scope, create content, protect existing traffic, test the result and hand over ownership. The strongest answers explain a process and evidence. They do not depend on vague promises about a beautiful, optimised or future-proof website.
Use the same core questions with every shortlisted supplier. That makes different approaches easier to compare without forcing every agency into an identical solution.
What problem do you think we are solving?
An agency should be able to restate the problem after listening. Its answer reveals whether it understands the business objective or has jumped straight to a preferred design or platform.
Ask which assumptions still need evidence and how discovery will resolve them. A thoughtful uncertainty is more credible than instant certainty.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Who is the website for?
Ask how the agency will identify customer needs, priority tasks and barriers. Look for research, existing evidence and input from customer-facing staff.
Personas are not automatically useful. The important question is how audience understanding changes structure, content and design decisions.
Ensure accessibility needs are included from the beginning.
What is included in discovery?
Discovery might include stakeholder sessions, analytics review, content inventory, customer research, competitor review and technical audit.
Ask which activities are included, who participates and what deliverables follow. Confirm whether discovery can change the quoted build scope.
A workshop alone is not a strategy unless it produces usable decisions.
What exactly will you deliver?
Request a list of pages, templates, components, functions, integrations and content services. Clarify responsive states, forms, error pages and legal pages.
Ask what is explicitly excluded. A clear exclusion is safer than an unstated assumption.
Use the guide to comparing website design proposals to normalise different descriptions.
Who will do the work?
Meet or understand the people responsible for strategy, design, content and development. Ask which work is subcontracted and who remains accountable.
Relevant experience matters more than team size. Request examples that share the project’s real challenges, not merely a similar colour palette.
Confirm who will be the day-to-day contact.
How will you plan the website structure?
Ask how customer tasks, services and existing search value shape the sitemap and navigation. The answer should go beyond copying the current menu.
Confirm when URLs are decided and who approves them. Changing addresses late creates avoidable migration risk.
Ask how related content will be linked and orphaned pages prevented.
Who writes and approves the content?
Clarify whether the agency interviews specialists, writes new copy, edits supplied text or only places finished content. Agree quantities and revision rounds.
Ask how facts and external sources are verified. Content should be original and should cite authoritative evidence when important claims depend on it.
Identify one client-side owner who can consolidate approvals.
How will existing content be handled?
Ask for an inventory and a keep, update, merge or remove decision. Automatic migration can carry old problems into the replacement.
Valuable content and URLs should be protected. Obsolete material needs a deliberate destination or removal decision.
The guide to reusing existing website content provides a practical framework.
How will design decisions be presented?
Understand whether you will see mood boards, wireframes, prototypes or working pages. Ask what each stage is intended to decide.
Confirm how feedback is gathered and what counts as a revision. Real content should appear early enough to test the design honestly.
Avoid approval based only on a single desktop homepage picture.
Which technology do you recommend and why?
The answer should connect technology to content, editing, functions, performance and internal capacity. Be cautious when every project receives the same platform regardless of need.
Ask about dependencies, updates, licences and export. Understand who can maintain the site after launch.
Ask how the proposed platform meets your requirements.
How will editors update the site?
Request a demonstration of common tasks. Confirm which parts staff can change and which require technical help.
More flexibility is not always better. Purposeful components can protect consistency and accessibility.
Ask about training, documentation, preview and approval workflows.
How will accessibility be addressed?
Ask which standard guides the work and how keyboard, focus, contrast, zoom, alternatives and forms are tested. Automated scans alone are not enough.
The Web Content Accessibility Guidelines provide recognised criteria. The agency should explain how these influence design and development.
Confirm how third-party tools and future content are governed.
How will performance be protected?
Ask for performance goals and representative page testing. Discuss imagery, fonts, scripts, hosting and third-party tools.
One homepage score is not a complete method. The agency should investigate causes and avoid sacrificing useful content merely to improve a metric.
Confirm whether performance forms part of acceptance and post-launch monitoring.
What does SEO include?
Ask for specific work: URL preservation, metadata, headings, internal links, canonicals, structured data, robots, sitemap and search monitoring.
Avoid guaranteed ranking claims. An agency can protect technical foundations and improve relevance, but competitors and search systems remain outside its control.
For a replacement, ask how old URLs will be inventoried and redirected.
How will forms and integrations be tested?
Ask how the team verifies customer confirmation, business delivery, validation, consent and failure handling. A form is not complete because its button works.
For each integration, identify account ownership, third-party fees and responsibility when the service changes.
Use realistic test scenarios without exposing live personal data.
How do you manage security and privacy?
Discuss HTTPS, account access, dependency updates, form data, secrets and incident response. The correct controls depend on the site’s functions and data.
Ask what information is collected, where it travels and how long it is retained. Legal accountability remains with the appropriate business roles.
Be suspicious of absolute claims that a website is completely secure.
What hosting do you recommend?
Ask what is included, normal renewal price, backups, monitoring, limits and support. Confirm whether hosting is optional and how the site can move.
The business should control the domain and understand DNS. Email should not be disrupted by a website move.
Read how much website hosting should cost before comparing bundles.
What is the project schedule?
Request phases, decision points and client dependencies rather than only a launch date. Ask what happens when content or approvals arrive late.
Understand how many projects the team handles concurrently and who covers absence.
Fast delivery can be appropriate, but only when scope and inputs support it.
How are changes controlled?
Ask how new requests are estimated and approved. Fixed prices still need assumptions and a change process.
Confirm revision allowances and the effect of changing approved direction. Avoid both open-ended billing and unrealistic unlimited revisions.
Good change control protects the relationship, not just the supplier.
How will the site be tested?
Request the test areas, supported browsers and acceptance criteria. Content, responsive layouts, accessibility, forms, links, redirects and production configuration all need attention.
Ask who records results and verifies fixes. Client review is valuable but should not replace supplier quality assurance.
The pre-launch checklist shows the expected breadth.
What happens at launch?
Ask for deployment steps, ownership, rollback and immediate checks. Confirm how DNS, certificates, redirects, email and analytics are protected.
Ensure the people needed to solve problems are available. Avoid cancelling old services before the new site is proven.
Ask who will manage the transition and what the launch plan includes.
What support follows launch?
Clarify defect coverage, response times, monitoring, updates and optional improvements. Separate included warranty from paid ongoing support.
Ask how urgent issues are reported and who responds outside ordinary hours if that matters.
Understand what happens when the initial support period ends.
What will we own?
Confirm ownership and access for the domain, code, content, design assets, data, analytics and service accounts. Ask what can be exported.
Review licence restrictions and proprietary components. Ensure an exit does not make essential records inaccessible.
Ownership should be reflected in the contract and practical account setup.
Can we speak to relevant clients?
Case studies show selected work. References can reveal communication, problem solving and support after launch.
Ask about projects with similar complexity or migration risk. Respect confidentiality and do not expect disclosure of private details.
Also examine the agency’s live work for usability, speed and clarity.
How do you measure success?
Agree measures connected to the original problem, such as completed enquiries, task success, performance or editing efficiency.
Avoid treating traffic alone as success. Establish a baseline and acknowledge external influences.
Ask how findings lead to decisions after launch.
Frequently asked questions
How many agencies should we speak to?
A small, well-chosen shortlist is usually enough. Give each a clear brief and evaluate depth rather than collecting many superficial quotes.
Should we reveal our budget?
Sharing a realistic range can help agencies propose an achievable scope. Ask them to explain priorities and alternatives within it.
Is industry experience essential?
Not always. Relevant problem-solving, research and technical experience may matter more, although regulated sectors can need specialist knowledge.
Should an agency guarantee rankings?
No responsible supplier can control search rankings. Ask what technical and content work it will complete and how it will monitor results.
What if an answer is unclear?
Request clarification in writing before signing. Ambiguity in scope usually becomes disagreement later.
Choose clarity and fit
The right agency should make the project easier to understand. Its answers should show curiosity, sound judgment, transparent ownership and a credible route from the current problem to a tested website.
Afterworks shows businesses a proposed improvement before they make the full commitment. Read how speculative website redesign works for the details.
