Choosing a Web Design Provider: 20 Questions to Ask Before You Sign
Twenty practical questions to ask a web designer, freelancer or agency, what good answers look like, and how to compare providers on process, ownership and support.
The best way to choose a web design provider is to ask the same set of questions of every candidate and compare the answers in writing. Good providers answer plainly, show live work, explain who will do what, and put ownership and costs in a contract. Vague answers, pressure to sign quickly and unwillingness to share references are warning signs. This guide gives you twenty questions, grouped by theme, with notes on what a strong answer sounds like.
Why questions matter more than portfolios
A portfolio shows what a provider has made, but it does not show how projects go. Missed deadlines, unclear communication and surprise bills rarely appear in a gallery. Questions reveal process, honesty and fit. Pay attention not only to what they say but also to how quickly and clearly they reply during the sales stage, because that is usually the best case.
Questions about experience and fit
1. Can you show me three live sites you built for businesses like mine? Look for live links you can open on your phone, not just screenshots. Similar size or industry is helpful, but quality and clarity matter more than a perfect match.
2. Who will actually work on my project? In agencies, the person who sells is not always the person who builds. A good answer names roles and shows the team's relevant experience.
3. How many projects do you handle at once? Capacity affects speed and attention. A busy provider may still be excellent, but they should be honest about timing.
4. Can I speak to two recent clients? Providers who hesitate to offer references deserve a closer look. When you call, ask about deadlines, surprises and what the client would change.
5. Do you specialize in a platform or type of site? Specialists tend to deliver faster and with fewer issues on their platform. If your needs are unusual, ask whether they have done something similar.
Questions about process and communication
6. What does your process look like from start to launch? Expect phases such as discovery, design, build, content, testing and launch, each with defined outputs.
7. How will we communicate, and how quickly do you respond? Ask for a named contact, a regular update schedule and the tools they use. A clear response window is better than "we are always available."
8. How many design revisions are included, and what happens after that? Unlimited revisions sound generous but can lead to endless projects. A defined number with a rate for extras is usually healthier.
9. What do you need from me, and by when? This question shows whether they have a structure. Content, feedback and approvals are the client's responsibility, and delays on your side move the launch date.
10. How do you handle changes in scope? Good answers describe a written change request with a price and timeline before the work begins.
Questions about price and payment
11. What exactly is included in the price, and what is not? Ask for a line-by-line list. Common exclusions include copywriting, photography, search setup, training, third-party licenses and hosting.
12. What are the recurring costs after launch? Hosting, maintenance, plugin licenses and support plans should be listed with amounts and renewal terms.
13. What is the payment schedule? A common structure is a deposit, milestone payments and a final payment at launch. Be cautious about paying everything up front.
14. Do you charge for hosting, and who controls the hosting account? A provider can host your site for convenience, but you should be able to access and move it.
Questions about ownership and risk
15. Who owns the design, code and content when the project is finished? You should expect to own what you paid for, aside from licensed components such as themes or plugins, which have their own terms. Get this in the contract.
16. Will the domain and accounts be registered in my name? The right answer is yes. See contract and ownership terms.
17. What happens if we part ways during or after the project? Ask how files, logins and documentation are handed over and whether any fees apply.
18. What backup and security practices do you follow? Look for regular off-site backups, updates, and secure handling of passwords. Providers should also explain how their own accounts are protected.
Questions about results
19. How do you build for search, speed and accessibility? Good answers mention mobile layouts, fast loading, proper page titles, redirects from old pages and accessible design. Be wary of guarantees about search rankings. No one outside the search engines can promise a specific position.
20. What support do you provide after launch? Ask about a bug-fix window, training, response times and costs for later changes.
A simple scoring sheet
Rate each provider from 1 to 5 on these criteria and add up the totals. This will not make the decision for you, but it forces you to compare consistently.
| Criterion | Weight | Provider A | Provider B | Provider C |
|---|---|---|---|---|
| Relevant live work | 3 | |||
| Clear scope and pricing | 3 | |||
| Communication and responsiveness | 2 | |||
| Ownership terms | 3 | |||
| References | 2 | |||
| Post-launch support | 2 | |||
| Fit with budget | 2 |
Multiply each score by the weight, then add the results. For example, if Provider A scores 4 on relevant work (weight 3) it contributes 12 points. A provider with a lower price but weak ownership terms may still score lower overall, and that is the point.
Red flags during selection
- Guaranteed first-page search results.
- Pressure to sign today to lock in a discount.
- No written proposal or contract.
- Refusal to name past clients.
- Insisting that the provider keep ownership of your domain.
- Unusually low price with a long mandatory subscription.
- Work portfolio that appears to belong to someone else; check that the sites are theirs.
Our red flags and scams guide covers these in more depth.
Worked example: two proposals for the same project
A nonprofit needs a 10-page site with a donation page. Provider X quotes $4,800, includes training and gives the nonprofit ownership of all accounts. Provider Y quotes $2,900, but the contract says Provider Y retains ownership of the code and charges $120 per month for hosting with a 36-month minimum, plus a $900 fee to transfer the site elsewhere.
Over three years, Provider Y costs 2,900 + (36 x 120) = $7,220, and moving the site would add another $900. Provider X costs $4,800 plus the nonprofit's own hosting, perhaps $400 a year for $1,200 over three years, for $6,000 total. The cheaper headline price turns out to be the more expensive and more restrictive deal. Asking questions 12, 14, 15 and 17 would reveal this.
When to consult a professional
For large projects or when a contract includes limitation of liability, indemnity, auto-renewal or intellectual property clauses you do not understand, a brief review by an attorney can prevent costly problems.
Frequently asked questions
Is the cheapest provider a bad choice?
Not necessarily, but low prices call for extra checking of scope, references and ownership.
Should I choose a provider based on awards?
Awards can be interesting but they do not replace references and live results.
Is it fine to hire someone I found on a freelance marketplace?
Yes, many good providers work there. Apply the same checks: live work, references, scope and ownership terms.
How long should I wait for responses?
A business day or two is reasonable. Slow answers during sales are a bad sign.
Sources
- Federal Trade Commission — advertising claims, contracts and scam alerts.
- Better Business Bureau — business profiles and complaint history.
- U.S. Small Business Administration — guidance on choosing vendors and contractors.
