Introduction: Why the Agency Decision Matters in 2026
Most businesses choose a web design agency by comparing portfolios and price. The contract, however, is what decides how your project actually goes. It sets the scope, the cost, who owns what, and how much flexibility you have once the site is live. The questions you ask before signing are the cheapest protection you will ever buy, because answers given in a sales call are easy to forget and answers written into a contract are not.
This guide gives you 12 questions in four groups: process and fit, technical and platform, scope and cost, and contract and ownership. Together they work as a scorecard. Put the same questions to every agency on your shortlist and the differences in quality, transparency, and approach become obvious.
Questions 1–3: Process, Strategy, and Fit
Question 1: Do you do UX research and wireframing before moving to visual design? A good agency does not open Figma and start choosing colors on day one. It first learns who your visitors are, what they are trying to do, and where the current site loses them. Wireframes then settle structure and flow before anyone debates fonts. Ask the agency to walk you through this phase and explain how specific layout decisions, such as navigation, page hierarchy, and where a call to action sits, influence user behavior. If the answer is mostly about how good the site will look, expect a site that looks good and underperforms.
Question 2: How do you connect design decisions to our business goals? Whether you want more qualified leads, a higher checkout conversion rate, or a site your team can update without a developer, the design should be built around that goal. Ask for examples of past projects where the agency can describe what the client was trying to achieve, what was changed, and what happened afterward. Be careful with big numbers in case studies. A confident agency will explain how the results were measured and will be honest about what it can and cannot promise for your situation.
Question 3: Who will actually work on my project, and how will we communicate? The people who pitch you are not always the people who build your site. Ask who your project manager is, which designers and developers will be assigned, and whether any work is subcontracted. Then agree on the practical rhythm: how often you will meet, which tools hold feedback and approvals, how quickly the team normally responds, and who can make decisions on your side. This is common-sense advice, not a formal standard, but many stalled projects trace back to unclear communication, not weak design.
Questions 4–6: Platform, Performance, and Technical Capability
Question 4: Which CMS and platform expertise do you have? Confirm this before you sign anything. Whether the agency works in WordPress, WooCommerce, Webflow, Shopify, or a headless setup, ask how many projects they have delivered on that platform and whether the people building yours have done it before. An agency that is strong in one system can be average in another, and you do not want to pay for its learning curve.
Question 5: Why is this platform right for my business? Platform choice is a strategic decision, not just a technical one. It affects how easily your team can edit content, how the site scales, which integrations are possible, and what you will spend on maintenance. WordPress, Webflow, and Shopify are among the options agencies commonly work with today. Webflow, for example, is often recommended for marketing-led sites that need design flexibility and strong content control without heavy developer involvement. Keep in mind that every agency has platforms it prefers. A trustworthy one will explain the trade-offs, including where its favorite platform is not the best fit, and tie its recommendation to your goals, your team, and your growth plans.
Question 6: How do you handle performance, accessibility, SEO, and mobile responsiveness? These should be built in from the start, not added at the end. Fixing speed or accessibility problems after launch usually means reworking parts of the design and code, which costs more than doing it properly the first time. Ask how the agency tests page speed, how it approaches accessibility (for example, whether it works toward WCAG guidelines), what technical SEO groundwork is included, and how it checks the site on real phones and tablets. If you sell to customers in the UK or EU, also ask how cookie consent and privacy requirements are handled.
Questions 7–9: Scope, Exclusions, and Change Orders
Question 7: What is explicitly not included in the proposal? Most budget surprises come from what the proposal leaves out, not what it contains. Ask for a written list of exclusions. Whatever is out of scope today tends to become a change order tomorrow, so it is far better to see it up front. A proposal that lists only inclusions and says nothing about exclusions is a warning sign, because it leaves room for disagreement later.
Question 8: Which commonly assumed items are excluded? Go through the items clients usually take for granted and check each one by name: SEO setup, copywriting, mobile QA, third-party integrations, content migration, image sourcing, and training. Copywriting deserves special attention. Many web agencies do not write your copy, so ask who will, how it will be ready in time, and what happens to the schedule if it is late. This varies by agency, so do not assume. Check each proposal you are comparing.
Question 9: How are change requests priced and approved? Change is normal. Priorities shift, stakeholders add ideas, and testing reveals gaps. What matters is the process. Ask whether changes are billed at a fixed rate or quoted individually, who must approve them on each side, and whether you receive a written estimate before work starts. The best arrangement is one where no extra cost can appear without your sign-off.
Questions 10–12: Contract, Ownership, and Post-Launch
Question 10: Who owns the source code and all deliverables? Your contract should say plainly that you own the source code and all deliverables, including designs, content, and assets, once you have paid. Ownership terms do vary, though. Some platforms, particularly hosted no-code tools, limit what you can export, and some agencies license certain components or use proprietary frameworks. Ask exactly what you will receive at handoff, in what format, and whether you can move the site elsewhere. Have a lawyer review the final contract. This article is a guide to the questions, not legal advice.
Question 11: What happens after launch? A website is never really finished. Ask whether the price includes a warranty period for bugs, what ongoing support and maintenance cost, who handles hosting, security updates, and backups, and whether your team will be trained to manage content. Clear answers here are a good sign that the agency expects to be a long-term partner and not a one-time vendor.
Question 12: Can I see relevant portfolio work and speak with past clients? Look for projects similar to yours in industry, size, or complexity, and ask to talk to one or two of those clients. Good questions for them include whether the project stayed on budget, how the agency handled problems, and whether they would hire it again. An agency confident in its work will make these introductions easily.
As you review proposals, watch for these red flags:
A vague scope with no stated exclusions.
No research or wireframing phase before design begins.
No clear reasoning for why a particular platform was chosen for you.
Ambiguous language about who owns the code and deliverables.
No answer on post-launch support, or reluctance to share references.
Conclusion and Final Checklist Before You Sign
Use the 12 questions as a scorecard. Ask every agency on your shortlist the same questions, rate the answers, and compare the results alongside price. The best choice is rarely the cheapest or the flashiest. It is the agency that is clear about its process, honest about trade-offs, and specific about what you will get. Whatever they tell you, get it in writing before you sign.
Before you commit, run through a short final check:
Confirm that scope, exclusions, and the change-request process are in the contract, not just the sales deck.
Verify ownership and handoff terms with legal review, especially if the project involves a hosted platform or proprietary tools.
Check any outcome claims in case studies by speaking with the clients behind them.
Compare quotes line by line, using current written prices and not generic estimates.
If you are weighing a redesign, a WordPress or WooCommerce rebuild, or a new online store, we would be glad to answer these 12 questions for your project. Explore Upcasted's services or request a project quote, and we will walk you through our process, platform recommendation, scope, and ownership terms in plain language, with everything in writing.