How to Choose a Web Design Agency or Studio: 12 Questions to Ask Before You Sign

Choosing a web design agency is difficult because proposals can look comparable while describing very different kinds of work. One supplier may be pricing design and development only. Another may include positioning, copywriting, search migration and senior strategic involvement. A third may appear cheaper because much of the thinking remains your responsibility.

The right choice is not automatically the largest agency, the lowest quote or the most visually impressive portfolio. It is the partner whose approach fits the problem your business actually needs to solve.

This guide gives you 12 questions to ask a web design agency, studio or freelancer before you sign. It also explains how to compare proposals, spot important omissions and decide which type of supplier is likely to suit your project.

What should you look for when choosing a web design agency?

Look for evidence that the supplier can understand the business, clarify what the website needs to communicate, turn that thinking into an effective experience and deliver the technical work without losing existing value.

For an established business, five capabilities usually matter:

• Strategic understanding: the ability to understand the audience, offer, difference, proof and commercial direction.
• Messaging and content: a clear plan for turning that understanding into page structure and persuasive copy.
• Design judgement: design that reflects the position of the business and helps visitors use the site.
• Technical delivery: a reliable build, responsive behaviour, performance, accessibility, CMS and integrations.
• Launch discipline: redirects, metadata, analytics, testing and a controlled handover.

Not every supplier needs to employ all five disciplines in-house. What matters is that the responsibilities are explicit, the people involved are credible and the work joins up.

Freelancer, founder-led studio or larger agency?

There is no universally best model. The right structure depends on the size of the project, the complexity of the organisation and how much senior attention you need.

Freelancer

A good freelancer can offer direct communication, specialist expertise and efficient delivery. This can work particularly well when the brief is already clear and the project sits within one person’s capabilities. The risk is capacity: strategy, copy, design, development, SEO and project management are distinct disciplines, even when one talented person covers several of them.

Founder-led studio

A founder-led studio often combines senior direct involvement with a small network of specialists. It can suit established businesses that want one experienced person to hold the strategic and creative thread while bringing in development or other expertise where needed. Ask who the specialists are, how quality is controlled and who remains accountable throughout.

Larger agency

A larger agency can provide deeper capacity, broader specialist teams and resilience across complex programmes. It may be the right choice for multiple stakeholders, substantial integrations, international rollout or ongoing production needs. Check how much access you will have to the senior people you meet during the pitch and who will actually work on the account.

Do not choose by label alone. A “full-service agency” may still outsource development. A “freelancer” may lead a highly capable team. A “studio” may be larger than it appears. Choose the operating model, people and responsibilities—not the category name.

12 questions to ask a web design agency before you sign

1. Who will lead the project, and will that person remain involved?

Ask who will run discovery, make strategic recommendations, lead design reviews and take responsibility for the finished work. The person who sells the project is not always the person who delivers it.

This matters because websites lose coherence when the commercial understanding gathered at the beginning is passed through several disconnected roles. You should know:

• who your day-to-day contact will be;
• who has final creative and strategic responsibility;
• which specialists will contribute;
• when senior people will be involved;
• what happens if someone becomes unavailable.

Direct senior involvement can be valuable, but it is not the only good model. The important thing is to understand the team you are buying rather than the team presented in the pitch.

2. How will you understand our business, audience and commercial goals?

A supplier cannot design an effective website from a short questionnaire and a list of competitor sites alone.

Ask what discovery involves, who should participate and what decisions it is expected to resolve. A useful process should explore the business’s audience, offer, positioning, service structure, proof, tone, current challenges and future direction.

Listen for more than “we run a workshop”. Ask what comes out of it. Will there be a written strategic foundation, agreed messaging, sitemap or content plan? How will disagreements between stakeholders be handled?

If the business is much clearer in the founder’s head than it is in existing documents, the supplier also needs a way to extract that knowledge rather than simply recycle the old website.

3. Are positioning, messaging and copywriting included?

“Content” can mean anything from supplying a blank spreadsheet to conducting interviews and writing every page.

Clarify:

• who defines the audience and proposition;
• who decides the sitemap and page purpose;
• who writes the first draft;
• how many rounds of copy review are included;
• whether SEO considerations inform the copy;
• who loads and formats the approved content;
• what happens if the current positioning is not clear enough to write from.

If copywriting is excluded, establish whether your team genuinely has the time and skill to supply it. Content is one of the most common causes of delay, and design built around placeholder copy rarely survives contact with the real words.

When the message itself is the problem, Amplify’s guide to deciding whether you need a new website or clearer messaging will help you separate the two.

4. What does “bespoke website design” mean in your process?

Bespoke can refer to original strategy and layouts, or simply to changing colours, fonts and images within an existing system.

Ask whether the supplier begins with a template, a component library, a previous site structure or a blank design system. None of these methods is automatically wrong. A component framework can improve consistency and efficiency. A suitable template can be proportionate for a simple project. The issue is whether the method matches the promise and the needs of the business.

Ask to see work at an intermediate stage—not only finished homepages. Sitemaps, wireframes, component systems and mobile layouts reveal how the supplier thinks. Then ask how the design will express your specific positioning rather than merely reproduce the supplier’s house style.

5. Who will build the website, and how is quality controlled?

Many excellent studios use specialist developers. Outsourcing is not a problem when it is transparent, well managed and subject to proper quality control.

Ask:

• whether development is in-house or delivered by a specialist partner;
• when the developer becomes involved;
• who checks the build against the approved design;
• which browsers and devices are tested;
• how accessibility and performance are assessed;
• who fixes defects before and after launch.

The strongest answer explains the relationship between design and development. A beautiful static design is not the finished product. It must work responsively, remain manageable in the CMS and retain its quality across real content and screen sizes.

6. How will scope, revisions and decisions be managed?

Ask what the quoted scope includes and how change is handled. A proposal should define pages or templates, content responsibilities, functionality, review stages and major deliverables clearly enough for both sides to recognise additional work.

Also ask how feedback is gathered. Unlimited revisions can sound reassuring, but it does not replace a decision process. Good project management establishes who approves work, how conflicting feedback is resolved and when a stage is considered complete.

You should understand:

• the number and purpose of each review stage;
• who needs to attend or approve;
• how consolidated feedback is supplied;
• what counts as a revision versus a change of scope;
• how delays by either party affect the timeline;
• how additional work is estimated and authorised.

A clear process is not inflexibility. It protects the time needed for judgement and prevents late uncertainty from destabilising the project.

7. Which platform will you use, and who owns the website?

Do not choose a platform by fashion or feature count. Ask why it suits your content, editing needs, integrations, internal capability and likely future development.

Clarify:

• who owns the account and domain;
• whether you can export or move the site;
• which functionality depends on paid third-party tools;
• what the ongoing hosting, licence and maintenance costs are;
• what your team will be able to edit;
• whether ordinary updates require the original supplier;
• how security and platform updates are handled.

A managed platform may reduce technical maintenance. An open-source system may offer more hosting choice. Webflow may suit a design-led marketing site with a structured CMS. The right answer depends on the project. What matters is that the trade-offs are explained before you become committed.

8. How will you protect our existing SEO and search visibility?

A redesign can improve search foundations, but it can also remove pages, change URLs and lose value that has taken years to build.

Ask the supplier to review Search Console, analytics, backlinks and the current sitemap before the new structure is finalised. The migration plan should cover:

• which existing pages attract relevant impressions, traffic or links;
• which URLs will remain unchanged;
• a page-by-page 301 redirect map;
• titles, descriptions, headings and canonical tags;
• structured data where appropriate;
• image alt text and accessibility;
• analytics, consent and conversion tracking;
• sitemap submission and post-launch monitoring.

Be cautious of guaranteed ranking claims. No agency controls Google or AI recommendation systems. A credible supplier should explain what it can improve—clarity, structure, evidence, technical quality and discoverability—without promising an outcome it cannot guarantee.

Your website redesign brief should name any current search value that needs protecting before proposals are compared.

9. How will mobile experience, performance and accessibility be handled?

“Responsive” should mean more than shrinking a desktop design.

Ask how navigation, content order, interaction, typography, forms and media will be considered on smaller screens. Find out whether page speed is tested, how images and video are optimised and which accessibility standard or practical checks guide the work.

Not every project will commission a formal accessibility audit, but every professional build should address fundamentals such as heading structure, keyboard use, contrast, labels, focus states and alternative text.

Ask to test recent work on your own phone. The quality of the mobile experience often reveals more than the desktop portfolio.

10. What CMS, integrations, analytics and training are included?

List the operational requirements before signing: forms, CRM, email marketing, booking, recruitment, gated content, multilingual content, payments, analytics or other systems.

For each integration, establish:

• whether it is included in the proposal;
• who configures the third-party account;
• what data moves between systems;
• how consent and privacy are handled;
• which subscription costs apply;
• who supports it if the connection later fails.

Ask for the CMS to be demonstrated using tasks your team will actually perform. “Easy to edit” is too vague. Can you add a case study, create a service page, change navigation, update metadata and preview work safely? Confirm what training and documentation are provided at handover.

11. What will the website cost after launch?

The project fee is only one part of the decision. Ask for a simple schedule of recurring and optional costs, including:

• hosting and platform licences;
• premium fonts, plugins or applications;
• maintenance or support retainers;
• security, backups and updates where relevant;
• future design or development rates;
• content, SEO or optimisation work;
• charges for adding users, languages or functionality.

Also ask what happens immediately after launch. Is there a defect period? Who monitors forms, redirects, analytics and Search Console? How quickly will genuine launch issues be addressed?

A lower initial fee can be entirely appropriate, but only if you understand what has been excluded and what the website will cost to operate. The guide to website costs in the UK explains why apparently similar projects can carry very different prices.

12. What evidence shows you can solve this kind of problem?

Do not limit this to whether the agency has designed a site in your sector. Relevant sector knowledge can help, but a supplier may have stronger evidence in a comparable buying journey, service model or strategic challenge.

Ask for a case study that explains:

• the original business problem;
• the supplier’s role;
• the decisions it made and why;
• what changed from the initial brief;
• the completed work;
• the result or client evidence;
• what it learned.

Then speak to a recent client if the decision is substantial. Ask about communication, judgement, accuracy of scope, handling of difficulties and the quality of support after launch—not only whether the client liked the design.

How to compare web design proposals fairly

Put each proposal against the same set of responsibilities. Compare the work, not only the total.

Check whether each proposal includes:

• discovery and strategic outputs;
• positioning and messaging;
• copywriting and content loading;
• sitemap and wireframes;
• bespoke design and mobile states;
• development and CMS configuration;
• integrations;
• SEO migration and redirects;
• testing and accessibility checks;
• analytics and launch;
• training and post-launch support;
• project management and revision stages.

If one proposal is materially cheaper, identify the missing responsibilities. You may be comfortable owning them internally, but they have not disappeared. They have moved.

Also compare the assumptions. One supplier may have allowed for six unique page designs; another may be offering six pages built from two templates. One may write the copy; another may only paste in text you supply. One may include the redirect plan; another may treat SEO as a separate service. These are not small differences.

Website agency warning signs

No single sign proves that a supplier is wrong for you, but several together should slow the decision down:

• a solution is recommended before the business problem has been explored;
• the proposal contains attractive language but vague deliverables;
• the price depends on you supplying content without testing whether that is realistic;
• the pitch team disappears from the proposed delivery model;
• “bespoke” is used without explaining the design method;
• the platform is presented without discussing trade-offs or ownership;
• SEO means adding keywords at the end rather than protecting and structuring the site;
• there is no redirect or analytics migration plan;
• mobile, performance and accessibility are treated as automatic;
• the supplier guarantees rankings, traffic or leads;
• important recurring costs are absent;
• you are pressured to sign before responsibilities are clear.

A good supplier should be willing to say when your assumption is wrong, when a feature is unnecessary or when part of the problem needs resolving before the website is designed. Agreement is pleasant. Judgement is more valuable.

Before you make the final decision

Ask your own team four questions:

1. Do we trust this supplier’s judgement? Not just their taste or technical competence.
2. Do they understand what has changed in the business? The new site needs to represent the next stage, not decorate the last one.
3. Are responsibilities explicit? Especially strategy, copy, approvals, integrations, SEO migration and post-launch support.
4. Does their way of working suit ours? Consider access, pace, stakeholder involvement and the quality of the conversation so far.

The website will be shaped by hundreds of decisions that cannot all appear in a proposal. Choose the people whose judgement you want applied when those decisions arise.

Frequently asked questions

How do I choose the right web design agency?

Choose the agency, studio or freelancer whose skills and process fit the problem you need to solve. Compare who will lead the work, how they understand the business, whether messaging and copy are included, how design and development join up, and how they manage SEO migration, ownership, costs and support.

What questions should I ask a web design agency?

Ask who will deliver the work, how discovery and messaging are handled, what bespoke design means, who develops the site, how scope and revisions work, which platform will be used, who owns the result, how search value will be protected, what testing is included, what you can edit, what ongoing costs apply and what evidence supports the supplier’s claims.

Should I choose a freelancer or a web design agency?

Choose according to the project rather than the label. A freelancer can be ideal for a clear, contained brief. A founder-led studio can provide senior continuity with specialist support. A larger agency may suit complex stakeholder, integration or capacity requirements. Confirm the actual team and responsibilities in every case.

How many web design proposals should I get?

Usually two or three well-matched proposals are more useful than a large tender list. Before inviting proposals, use a clear brief and select suppliers whose work, operating model and likely budget level fit the project. Too many options can produce superficial comparisons and consume substantial time on both sides.

Should I tell a web design agency my budget?

Yes, an honest range helps a credible supplier propose a proportionate scope and tell you whether the ambition is realistic. A budget is not permission to spend every pound. Ask what would change at different investment levels and which elements are essential, optional or better phased.

What should be included in a web design proposal?

A useful proposal should explain the problem, recommended approach, scope, deliverables, responsibilities, team, stages, timing, fees, recurring costs, assumptions and terms. For a redesign, it should also address content, SEO migration, redirects, analytics, testing, training and support.

Can a web design agency guarantee leads or Google rankings?

No. A supplier can improve the website’s clarity, relevance, evidence, usability, technical foundations and discoverability, but it cannot control demand, competitors, search engines or buyer behaviour. Treat guaranteed rankings or enquiry volumes with caution.

Choose the thinking behind the website

A portfolio shows what a supplier has made. A proposal shows what it has allowed for. The conversations between them reveal how it thinks.

For an established founder-led business, that thinking matters because the website is not only a visual project. It has to translate the business’s expertise, audience, value, proof and direction into something a prospective client can understand and trust.

If you are still defining the project, begin with the practical website redesign brief. If the concern is more fundamental, use the diagnostic on why your website is not generating the right enquiries.

When you are ready to discuss the work itself, explore Amplify’s bespoke Website Design approach or start a conversation about your project.