20 Questions to Ask a Web Designer Before You Hire (And the Answers That Should End the Call)
Ask about price and scope, ownership and access, process and timeline, what happens after launch, and proof of real work. Twenty questions, five blocks. The questions are the easy part. What matters is knowing which answer means yes, which means ask again, and which means end the call.
TL;DR
- The questions are not the hard part. Knowing what a good answer sounds like is the part that saves you money.
- Ownership is the one thing you cannot fix later. Domain, hosting and analytics go in your name on day one, or you are renting your own business.
- "Everything is included", "all changes are free" and "unlimited revisions" are the three sentences that cost the most. None survives month two.
- Ask what a change costs next year. The build price happens once. That one repeats for as long as you own the site.
- Question 20 is the best one: tell me about a project that went badly. Nobody who has shipped much struggles with it.
What should you ask a web designer before hiring?
Twenty questions, in five blocks: price and scope, ownership and access, process and timeline, what happens after launch, and proof.
Most lists give you the questions. Almost none tells you what a good answer sounds like. That is the part that matters, because a bad supplier will answer all twenty cheerfully and you will still sign the wrong contract.
So each question below has three lines: why you are asking, the answer to listen for, and the answer that should end the call. At the bottom is a table you can print or paste into your phone.
One rule before you start. Ask the question, then stop talking. Most of the signal is in whether they answer the question you asked or a nicer question next to it.
Block 1: Price and scope
Most of the damage happens here, quietly, in the gap between what you thought you were buying and what was written down.
1. Is this a fixed price or an estimate?
Why you ask: Different products. A fixed price moves the risk of the job being bigger than it looked onto the builder. An estimate leaves it with you.
Listen for: A number, and the words "against this scope, in writing".
End the call if: They will not commit to either. "It depends where we land" after a full brief means you are funding their discovery.
2. What is not included in this number?
Why you ask: Exclusions cost more than inclusions. The usual six are content, copywriting, photography, third-party licences, data migration, and post-launch fixes.
Listen for: A list, unprompted. Good builders like this question because it protects them too.
End the call if: "Everything's included." Nothing includes everything. That answer means the exclusions arrive later, as invoices.
3. How is a change request priced, and who decides it is a change?
Why you ask: You will change your mind. Everyone does. The question is whether that costs you a conversation or an argument.
Listen for: A rule you can apply yourself: inside the agreed scope it is free, a new page or integration is quoted before anyone builds it.
End the call if: They say every change is free. That is a promise from someone who intends to say no later.
4. What do I pay, and when?
Why you ask: Payment schedule is the only real leverage you have once work starts.
Listen for: Milestones tied to something you can see. Never a schedule tied to dates alone.
End the call if: 100% up front on a first project. Be wary of 100% on delivery too: it sounds generous and usually means your job gets dropped the moment a paid one appears.
Our answer: fixed price up front against a written scope, paid 40/30/30, with a working demo you can click before each payment. Full ladder is on our pricing page.
Block 2: Ownership and access
Short, boring, and the most expensive block to skip. Ownership problems show up two years later, when you want to leave.
5. Who owns the code, the design files and the content when we are done?
Why you ask: Under US law, work by an independent contractor belongs to the contractor unless a written agreement says otherwise, and paying the invoice does not change that. See the US Copyright Office circular on works made for hire.
Listen for: "You do, on final payment, and it says so in the contract."
End the call if: They own it and licence it back to you. That is a hostage arrangement with a friendly name.
6. Whose name are the domain, hosting, and analytics accounts in?
Why you ask: The domain is the one thing you genuinely cannot rebuild. Everything else can be recreated in a week.
Listen for: "Yours, from day one. We get invited in." Your email, your card, you as owner.
End the call if: "We manage all that for you, don't worry about it." Worry about it. Who owns your website covers the full account list to check.
7. Can someone else work on this site next year without a rebuild?
Why you ask: You are asking whether they build on something standard or something only they understand.
Listen for: A named, common stack. WordPress, Shopify, Webflow, a mainstream JavaScript framework. Plus a repository you can access.
End the call if: The answer includes "our proprietary platform" and it has no users outside their client list.
8. What happens to my site if you stop trading?
Why you ask: Small studios close. Freelancers take jobs. A decent supplier will not take the question as an insult.
Listen for: "You already have everything. Nothing of yours lives only with us."
End the call if: They get defensive. The reaction tells you more than the answer.
Our answer: 100% code and IP ownership from day one, in accounts registered in your name, on your card. If you fire us on a Tuesday you lose nothing but us.
Block 3: Process and timeline
Most projects do not fail on skill. They fail on the handoffs, and on nobody saying out loud who is waiting for what.
9. Who actually does the work, and can I talk to them?
Why you ask: The person selling is often not the person building. Sometimes the builder is a subcontractor in another timezone who has never read your brief.
Listen for: A name, a role, and a yes.
End the call if: "You'll be assigned an account manager." You are paying for a layer between you and the work.
10. What is the timeline, and what is most likely to make it slip?
Why you ask: The second half is the real question. Anyone can say six weeks.
Listen for: Honest risk naming, and most of it pointed at you: content, photos, feedback delays, a decision nobody has made yet.
End the call if: "Nothing, we always deliver on time." Every builder has been late. The ones who admit it have a process for it.
11. What do you need from me, and by when?
Why you ask: Missing copy and photos stall more projects than any technical problem, and both are your side of the table.
Listen for: A specific list with dates attached, ideally sent to you in writing after the call.
End the call if: "Just send whatever you have." That is how a four-week project becomes a ten-week one. Our guide on what to have ready before you hire a web designer is the list they should be asking for.
12. When do I see something real, not a mockup?
Why you ask: A picture of a website is not a website. Projects look perfect in a design tool for six weeks, then fall apart on a phone.
Listen for: A URL you can open on your own phone, early, and then repeatedly.
End the call if: The first working version arrives at the end. That is not a process, that is a reveal, and reveals are for weddings.
13. How many rounds of revisions, and what counts as one?
Why you ask: "Three rounds" means nothing until you know whether your six-email thread is one round or six.
Listen for: A definition: one round is one consolidated set of feedback, in one document, per page.
End the call if: "Unlimited revisions." A project with no end has to defend its budget somewhere, usually in the quality.
Our answer: senior engineers only, no account managers, WhatsApp for everything, a working demo before each payment. The Overnight Site is $399, live in 24 hours or it is free. The Engine starts at $699 and lands in 2 to 4 days.
Block 4: After launch
Launch is not the finish line, it is the point where the ongoing costs start. Ask these before you sign, not in month three.
14. If something breaks in the first month, what happens?
Why you ask: Things break after launch. Forms stop sending, a plugin update takes down a page, an image never loaded on Safari.
Listen for: A stated warranty period, and what it covers. Bugs in what they built should be free. New features should not be.
End the call if: "Support is a separate contract" and the separate contract starts the day you launch.
15. What does hosting and maintenance cost per month, and what is in it?
Why you ask: The build price happens once. This one repeats for as long as you own the site, and over five years it is often the bigger number.
Listen for: A monthly figure, a list of what it covers, and how many hours of changes are included.
End the call if: The monthly is mandatory to keep the site online and you cannot move it elsewhere. That is rent on your own asset. Ranges are in what a small business website actually costs.
16. Can I edit the site myself? Show me now.
Why you ask: The word "yes" and the reality of changing a phone number are frequently different things.
Listen for: Them sharing a screen and changing a headline in under a minute.
End the call if: Editing anything means emailing them. Every price change, every new opening hour, every staff update becomes a small invoice and a two-day wait.
17. What are you doing about speed, accessibility and search, specifically?
Why you ask: These three get promised in every proposal and measured in almost none.
Listen for: Named standards and a test you can run yourself: Google's Core Web Vitals thresholds for speed, WCAG for accessibility, and for search, a boring answer about titles, page structure and one page per thing you sell.
End the call if: They promise a Google ranking. Nobody can sell you a position they do not control.
Our answer: 30-day warranty on anything we built, no mandatory hosting lock-in, and you can edit your own content. If we cannot show you the edit live on the call, do not believe us.
Block 5: Proof
Portfolios are the easiest part of an agency to fake, so ask about them the way an auditor would.
18. Show me a site you built that is still live today.
Why you ask: Portfolio screenshots survive long after the client has left, rebuilt, or gone under.
Listen for: Live URLs, opened on the call. Then check the page source: the generator tag says whether the site was hand-built or assembled from a template.
End the call if: Every example is an image, a Dribbble shot, or a site that is now a parked domain.
19. Can I speak to the client from that job?
Why you ask: One five-minute call with a past client beats every testimonial on their site.
Listen for: A yes, or an honest no with a reason such as an NDA, plus an alternative reference.
End the call if: They offer written testimonials instead and none of them has a full name, a company and a working link.
20. Tell me about a project that went badly.
Why you ask: The best question on the list. It is unanswerable by someone who has not shipped much.
Listen for: A specific story, a share of the blame taken, and a rule they changed afterwards.
End the call if: Every past problem was the client's fault. You are the next client.
Our answer: Kanfa and Axiom Jewellery are live and written up, Streets of Punk is a cinematic build at streetsofpunk.com, and Henny Bot is the one with real numbers attached: on-chain volume up 1,200%, $300k peak daily volume, about 5 minutes saved per transaction. Ask us question 20 and you will get a real answer.
What these answers cost in 2026
Prices vary by market and by how much of the work you do yourself. These are the shapes you will see quoted, and what each one usually means for you.
| What you are being quoted | Typical shape in 2026 | Who carries the risk | Ask this |
|---|---|---|---|
| Fixed price, small business site | Low hundreds to a few thousand, one number | The builder | Fixed against what scope, in writing? |
| Hourly or day rate | Rate plus an estimated range | You | What is the cap, and what happens past it? |
| Monthly "website plan" | A small monthly, often 3 years minimum | You, quietly | Do I own the site if I stop paying? |
| Hosting | A few dollars to tens of dollars a month | Shared | Can I move it elsewhere without a rebuild? |
| Maintenance and support | Monthly, usually with an hours allowance | Shared | What is included, and what is billed on top? |
| Copy and photography | Almost always excluded by default | You | Is writing in the number I was quoted? |
| Changes after launch | Per hour, or free inside a warranty | You | How long is the warranty and what voids it? |
The pattern is not "cheap versus expensive". It is who is carrying the uncertainty. Every quote that looks suspiciously low has moved that weight onto you somewhere, and the table above is where to look for it.
The question sheet, ready to take to the call
Copy this. Print it, or paste it into a note on your phone. Tick the middle column as you go, and if you tick two things in the right-hand column, stop.
| Ask | Good answer | Walk away if |
|---|---|---|
| 1. Fixed price or estimate? | A number, against a written scope | Neither, after a full brief |
| 2. What is not included? | A list, given unprompted | "Everything is included" |
| 3. How are changes priced? | A rule you can apply yourself | "All changes are free" |
| 4. Payment schedule? | Milestones tied to something you can see | 100% up front, first project |
| 5. Who owns the code and design? | You, on final payment, in the contract | They own it and licence it back |
| 6. Whose name are the accounts in? | Yours, from day one | "We handle all that for you" |
| 7. Can someone else take it over? | A named, common stack plus repo access | A proprietary platform with no other users |
| 8. If you stop trading? | You already hold everything | They get defensive |
| 9. Who does the work? | A name, a role, and you can talk to them | An account manager in between |
| 10. What makes the timeline slip? | Honest risks, most of them yours | "Nothing, we are never late" |
| 11. What do you need from me? | A dated list, sent after the call | "Send whatever you have" |
| 12. When do I see something real? | A live URL, early and often | One big reveal at the end |
| 13. What counts as one revision round? | A written definition | "Unlimited revisions" |
| 14. First month, something breaks? | A stated warranty and what it covers | Support billed from day one |
| 15. Monthly cost and contents? | A figure and a list | Mandatory monthly, no exit |
| 16. Can I edit it myself? | They show you, live, in a minute | Every edit is an email to them |
| 17. Speed, accessibility, search? | Named standards you can test | A guaranteed Google ranking |
| 18. A live site you built? | URLs opened on the call | Only images and dead domains |
| 19. Can I call that client? | Yes, or an honest no plus a reference | Anonymous testimonials only |
| 20. A project that went badly? | A real story and a rule they changed | Every problem was the client's fault |
How to actually run the call
Do not read twenty questions down a phone. You will sound like a procurement form and they will start performing.
Run it in this order. Open with proof, because if the work is not real nothing else matters. Then ownership, the one thing you cannot fix later. Then price and scope, then process. Leave the after-launch questions until they think the meeting is over, which is when people answer honestly.
Ask all twenty of the same shortlist. Three quotes against three different conversations are not comparable, and the cheapest one is usually cheapest because it understood the least. If you want the sequence before the shortlist stage, hiring someone to build a website covers the four routes and what each realistically costs.
A supplier who reads your brief and comes back with a question you had not thought of, or tells you to cut a page, is worth more than one who says yes to everything. The second kind has not read it closely enough to find the problem yet. They will find it later, at your expense.
FAQ
What questions should I ask a web designer before hiring them?
Cover five areas. Price and scope: is this fixed or an estimate, what is excluded, how are changes priced, and what is the payment schedule. Ownership: who owns the code and whose name are the domain and hosting in. Process: who does the work, what makes the timeline slip, and when do you see something live. After launch: warranty, monthly costs, and whether you can edit it yourself. Proof: a live site, a client you can call, and a project that went badly.
What is the biggest red flag when hiring a web designer?
Refusing to put ownership in writing. If the studio holds the domain, the hosting login or the code and licences it back to you, every future decision runs through them, including the decision to leave. The second biggest is a portfolio made entirely of images. Ask for live URLs and open them on the call. A close third is a guaranteed Google ranking, because nobody can sell you a position they do not control.
Should I ask for a fixed price or pay hourly for a website?
Ask which one you are being offered, and make them say it plainly. A fixed price moves the risk of the job being bigger than it looked onto the builder, which is usually what a small business wants. Hourly leaves that risk with you, so if you go hourly, ask for a cap and what happens past it. Either is workable. What is not workable is a number that turns out to have been an estimate only after you have paid the deposit.
Who should own my website domain and hosting accounts?
You, in your name, on your card, from day one. The designer gets invited in as a user and can be removed. The domain is the only part of a website you genuinely cannot rebuild, so it matters more than the code. If a supplier tells you not to worry about it because they handle all that, that is the moment to worry about it. Ask them to add you as owner before any money moves, not after launch.
How many revision rounds should a web design quote include?
Two or three, with a written definition of what one round is. The number is meaningless on its own. One round should mean one consolidated set of feedback, sent in one document, per page. Without that definition, a six-email thread becomes six rounds and you are into extra fees. Be more suspicious of unlimited revisions than of two: a project with no end has to defend its budget somewhere, and that somewhere is usually the quality of the work.
Is it rude to ask a web designer for client references?
No, and the reaction tells you as much as the reference does. A studio that has done the work will hand you a name, or explain honestly that an NDA blocks that one and offer a different client. Five minutes with a past client beats every testimonial on a website, because you can ask the questions the testimonial avoided: did it launch on time, what did it end up costing, and would they hire them again.
What should I have ready before the first call with a web designer?
A one-sentence description of your business, the single action you want visitors to take, a page list, real photos, whatever copy exists, three reference sites with a reason for each, your budget, and a deadline tied to something real. Suppliers price uncertainty, so the more of that you supply, the tighter the quote comes back. Send the identical brief to everyone on your shortlist, otherwise the quotes are not comparable and the cheapest is usually cheapest because it understood the least.
Take this sheet to whoever you are already talking to. If you want a second opinion on the answers you got back, send us the quote and we will tell you what we would push back on. Free, same day, on WhatsApp or at ishan@dappasol.com. If we are the wrong shop for your project we will say so and point you somewhere better.
Got it. A senior engineer will reach out shortly. Prefer to talk now? WhatsApp us →