The questions to ask a web design agency before you sign a proposal are the difference between a project you remember fondly and a project you talk about in past tense at startup dinners. Most failed agency relationships were doomed in the discovery call, not at handover. The warning signs were there, the buyer just did not know which seven questions to ask. After 200+ projects priced and over a hundred client wins and losses, this is the exact list we wish every prospect asked us, and the answers we give in writing.
You should ask all seven. Mediocre agencies will hedge on one or two. Good agencies answer all seven cleanly inside the first conversation. The right answers protect you. The wrong answers (or the absence of any answer) save you from signing something you would regret in month six.
Why do most founder-agency relationships go sideways?
Three failure modes account for most agency disasters we see when clients come to us for a rebuild.
The agency oversold senior involvement. The pitch had two senior names. The delivery was led by a junior project manager and a contract designer. By week six, the founder noticed the work did not match the pitch quality. By week ten, scope creep had eaten the budget. By week fourteen, the project was 40% over and 4 weeks late.
Ownership of code and assets was never written down. The site shipped, the agency moved on, the founder asked for the source code six months later for a small change, and discovered the contract said the agency retained the code "for ongoing maintenance purposes." Now every change costs $300 and a 5-day wait.
Revisions ate the timeline. The contract said "two rounds of revisions" but never defined what counted as a revision. Three sentences of feedback became "round one" and the agency invoiced for round three by week eight. Both sides ended up angry.
All three failures show up in the same questions. Ask the seven below before you sign and you remove most of them.
Who actually owns the code, design files, and brand assets?
The right answer: you do, fully, on delivery, with no licensing strings or ongoing fees. That answer should appear in writing in the proposal, not just in conversation.
Some agencies retain code ownership and license you the right to use it. This is a red flag for most founders. It means you cannot move the site to another developer without the agency's cooperation, you cannot modify the codebase yourself, and you have no backup if the agency goes out of business. We hand over a fully-owned GitHub repository at handover with the client as the primary owner. That is the bar.
Brand assets follow the same rule. Logos, type files, photography rights, illustration rights, all should be yours on delivery with appropriate licenses for the third-party assets (stock photography, fonts) named in the proposal.
Red flag answers: "We retain ownership for maintenance purposes." "You get a license, not the code." "Source code is part of our retainer." Green flag answer: "You own everything on delivery. We hand over the GitHub repo, the Figma file, and the brand assets with full transfer of ownership."
What is the performance target the agency commits to?
The right answer: specific Lighthouse numbers on mobile, with a written performance budget enforced before sign-off.
An agency that cannot quote a specific Lighthouse score on mobile under a 4G connection is not measuring its own work. The bar in 2026 is Lighthouse 90+ mobile, LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, all per Google's Core Web Vitals documentation. We hit 92 to 95 on every doubleSix Studio mobile build. Some agencies hit 60. The 30-point gap is the difference between a site that ranks and one that does not.
If the agency hedges with "we focus on user experience over Lighthouse scores," translate that to "we are not equipped to measure our work and prefer you not measure it either." That is the answer that should end the conversation.
Red flag answers: "We do not chase Lighthouse scores." "Performance depends on your hosting." "We can optimise after launch." Green flag answer: "Lighthouse 90+ on mobile, sub-second LCP on 4G. Written into the proposal, verified on staging before sign-off."
Who specifically does the work, and who shows up to delivery meetings?
The right answer: names. Real names, of real humans, with their roles, who will be on the project from kickoff to handover.
The "senior bait, junior switch" is the most common agency anti-pattern. The pitch features two principals with great taste. The delivery is led by a junior who has been at the agency for nine months. By the time the founder notices, the project is too far along to swap teams.
Ask for the name of the lead designer, lead engineer, and project manager. Ask which weekly meetings each of them will be on. Ask whether the principals you are speaking with right now will be on the project beyond kickoff. The answers should be specific.
Bonus question: ask how many active projects each named team member is on right now. If a senior designer is on 6 projects simultaneously, your project gets 16% of their attention. If they are on 2, you get 50%. Both are real models, just price them differently.
Red flag answers: "Our team will handle it." "We rotate based on availability." "The principals oversee everything." Green flag answer: "Sarah leads design, Marcus leads engineering, Priya is your project manager. All three are in every weekly call. Sarah is on two other projects right now, the others are on one."
How does the team handle revisions and scope changes?
The right answer: a specific number of revision rounds at specific stages, with written definitions of what counts as a round, plus a clear process for scope changes.
"Unlimited revisions" is the worst answer. It sounds generous and means the opposite. With unlimited revisions, the agency has no discipline to land the work, the founder has no incentive to converge, and both sides end up in scope wars by week eight. We have seen "unlimited revisions" projects go 60% over budget on every single occurrence.
A tight answer: 2 rounds at concept (initial direction and refined direction), 2 rounds at build (visual QA and final polish). New scope outside those rounds gets quoted separately at a clear hourly or daily rate. Both sides know where the line is.
Scope changes are inevitable on real projects. The right process is a 24-hour written quote on a change request, a yes-or-no decision, and a paper trail. The wrong process is "let us work it in and figure it out later," which is how budgets disappear.
Red flag answers: "Unlimited revisions." "We work it out as we go." "We do not nickel and dime." Green flag answer: "Two rounds at concept, two at build, written definitions of each round. New scope is quoted in writing inside 24 hours, you decide before we proceed."
What is the post-launch handover process?
The right answer: documentation, video walkthroughs, admin access, training session, and a defined aftercare period with named response times.
Most agency disasters happen after launch, not during. The site goes live, the agency moves to the next project, and three weeks later the founder cannot figure out how to add a new team member to the CMS. The agency replies in 5 days with a quote for a 20-minute task.
A real handover for a mid size site includes: a written README documenting how the site is structured, video walkthroughs of the CMS for the editor team, admin access transferred to the client's email, a 60-minute training session, and a defined aftercare window (30, 90, or 365 days depending on tier) with response times for support requests.
Watch for hidden retainer pressure. Some agencies make handover deliberately weak so you have to pay them monthly to keep the site running. The right model is full handover with optional retainer, not partial handover with mandatory retainer.
Red flag answers: "We handle hosting and updates ongoing." "Documentation is part of the retainer." "You can always reach out." Green flag answer: "Full handover at launch: docs, video walkthroughs, admin access transferred, 60-minute CMS training, then 90 days of aftercare with 24-hour response times. Retainer is optional after that."
Where is the source code hosted, and who has admin access?
The right answer: a GitHub or GitLab repository owned by the client, with the agency added as a collaborator. Same for hosting, domain, and any third-party services.
This is the question most founders forget to ask, and it bites them at month nine. The agency built the site on its own GitHub. Domain was registered in the agency's GoDaddy account. Hosting bill goes to the agency's credit card. When the relationship ends, the founder has 30 days to disentangle four separate services and discovers each one has fees attached.
The clean version: every service that the site depends on is owned by the client's email and credit card. The agency is added as a collaborator with admin or maintainer access. When the work is done, the agency is removed. No transition fees, no migrations, no awkward conversations about who owns what.
Domain registrar in the founder's name. Hosting in the founder's name. CMS account in the founder's name. GitHub repo in a doublesix-style organisation owned by the founder, with the agency added as collaborator. Done.
Red flag answers: "We will handle the technical setup." "The hosting is included in our package." "We use our own infrastructure." Green flag answer: "Everything is set up under your accounts. Domain in your registrar, hosting on your Cloudflare, GitHub repo in your organisation. We are added as collaborators and removed at handover."
What are the warning signs an agency is wrong for you?
Five red flags worth walking away from, even if everything else looks great.
- The proposal is 30 pages of stock copy. If the agency cannot write a focused 4-page proposal that addresses your specific brief, the work will be similarly unfocused.
- The price came in suspiciously low. A site sold as fully custom should come with a design made for your business, not a stock theme with your logo swapped in. The 3-year cost will hit you later.
- The portfolio shows 50 projects, all in different styles. Either the agency is taking everything that walks in the door (low judgement), or the work is mostly subcontracted (low quality control).
- The pitch promises rankings, conversions, or specific traffic numbers. No agency can guarantee those outcomes ethically. Anyone who does is either lying or about to do something that gets your domain penalised.
- The team that pitches is not the team that delivers. Confirmed by question 4. If the senior names disappear after kickoff, the work will too.
Red flags vs green flags at a glance
| Topic | Red flag answer | Green flag answer |
|---|---|---|
| Code ownership | "We retain it for maintenance" | "You own everything on delivery" |
| Performance target | "We focus on UX over Lighthouse" | "Lighthouse 90+ mobile, written into the proposal" |
| Who does the work | "Our team handles it" | Named individuals with roles and current project load |
| Revisions | "Unlimited revisions" | "Two rounds at concept, two at build, scope changes priced in writing" |
| Handover | "Reach out anytime" | Docs, video walkthroughs, admin transfer, training, aftercare with SLA |
| Source hosting | "We use our infrastructure" | Client owns repo, hosting, domain, CMS accounts |
| Pricing posture | "Price depends on what you need" | Fixed price in writing within 48 hours of discovery |
The shortest filter: if the agency answers all seven cleanly in the first call, they are likely a fit regardless of the agency's logo size. If they hedge on three or more, walk regardless of how good the work in the portfolio looks.
How to compare proposals once you have the answers
You should walk away from the first round of conversations with three to five proposals on similar scope. To compare them honestly, sort by total clarity first, then price.
Stack the proposals in three columns. Column one: the agencies that answered all seven questions cleanly and gave you a specific named team. Column two: the agencies that answered most questions but hedged on one or two. Column three: the agencies whose proposals are more sales document than scope document. Throw out column three. Compare price within column one. If the price spread within column one is more than 50%, ask the higher-priced agencies what they are including that the others are not. Usually the answer is real senior involvement, real performance work, or real aftercare. Sometimes the answer is brand pricing, which you do not want to pay for.
The shortest version
The questions to ask a web design agency are not about getting a discount. They are about flushing out the gap between what the agency promises and what they can deliver. Seven questions, asked the same way of every shortlisted agency, will save you 6 figures of pain over a 3-year horizon. To talk through your specific brief and see how we answer all seven, our contact page is the fastest route, and our services page lists what we ship at each tier.