How to Choose a Web Designer: 12 Questions to Ask Before You Pay
Choose a web designer who can explain what you will receive, what it costs over time, and who controls the site and accounts. Ask to see real work and a written scope before paying. A good-looking sample is useful, but ownership, maintenance, contact forms, and an exit plan matter just as much.
Prepare a short brief before comparing designers
Write down what the site needs to do. A small service business may need to explain its work, show proof, and generate calls or estimate requests. A practice may need appointment links and carefully managed information. Do not ask everyone for a website quote without explaining the actual job.
List must-have pages, features, existing assets, and who will approve the work. Note any deadline and why it matters. Share the same brief with each provider so you can compare like with like. A lower price may simply leave out writing, photography, migration, or ongoing support.
1. Have you built sites with needs like mine?
Ask for relevant examples you can open yourself. Look at them on a phone and follow the main customer path. Similar business needs matter more than an identical industry label. A clear estimate-request site may tell you more than a beautiful shop if you do not sell products online.
Ask what the designer actually did on each project. They may have handled design only, while someone else wrote the content or built the forms. A portfolio is not proof of every skill. If results are discussed, ask how they were measured and what other changes happened at the same time.
2. What exactly is included in the scope?
Get a page list and feature list in writing. Ask how service pages, contact forms, booking tools, and legal pages are handled. Clarify whether the quote includes research, writing, image sourcing, edits, and moving material from an old site. The word complete can mean different things to different providers.
Ask what counts as a change to scope and how it is priced. A new booking system is different from correcting a phone number. Written boundaries help both sides. You should know what approval looks like and what happens if you need more pages or features after work begins.
3. Who writes and checks the content?
Ask whether you supply finished copy or the provider drafts it from an interview. Confirm who checks technical claims, licenses, prices, and service areas. You know the business; the designer should not invent details to fill a layout. Set time aside for a factual review before launch.
If AI tools are used, ask how the output is checked and whether confidential information is protected. AI use alone does not tell you whether the result is good. The important questions are accuracy, originality, and accountability. Never approve made-up testimonials, unsupported claims, or copied competitor text.
4. How will the site work on phones and for more users?
Ask to see the mobile design before the whole project is finished. Check menu use, button spacing, form fields, and text size. A page should be usable without a visitor fighting overlays or zooming in to read normal text. Visual polish should support the task, not interrupt it.
Ask about accessibility testing, including keyboard use, readable contrast, meaningful headings, and labeled inputs. Get a clear description of the work rather than a blanket claim of compliance. Legal obligations vary by business and location, and an automated tool alone cannot prove that every visitor can use the site.
5. How will you test inquiries before launch?
The designer should explain how forms and phone links will be checked. Ask who receives messages, where submissions are stored, and what happens if email delivery fails. A success message on the page is not enough. Someone should confirm that a real test inquiry reached the intended person.
Include a test from a phone and a check of any booking or payment integration. Ask what personal data is collected and whether each field is necessary. Sensitive health, financial, or legal details may need a more suitable system than a general contact form. Set responsibilities before launch, not after a missed inquiry.
6. What does your SEO work actually include?
Ask for specific tasks: clear page titles, useful headings, crawlable pages, internal links, and appropriate redirects when replacing old pages. If you already receive search traffic, ask how important addresses and content will be handled. A redesign should not casually discard pages that customers already use.
Google’s SEO Starter Guide says no secret method automatically ranks a site first. Treat guaranteed first-place promises as a warning. Ask how Search Console access and reporting work, and whether ongoing SEO is separate from the build. Initial setup and continuous content or reputation work are not the same service.
7. Who controls the domain and main accounts?
The business should understand who the domain registrant is and who can manage renewals. Keep recovery details under business control. Ask about hosting, analytics, Search Console, and any booking platform too. A provider can have working access without being the only person who can recover the account.
Use separate user access where the service supports it instead of sharing one password. Enable multifactor authentication. CISA recommends discussing website security responsibilities with the provider. Clear account control protects continuity if a staff member or agency leaves, and it makes support less dependent on one person.
8. What do I own, license, or rent?
Ask whether you own the final site files and content or receive a license while subscribed. Clarify stock photo licenses, fonts, templates, plugins, and custom code. Paying for a website does not automatically answer every ownership question. The contract should state what you can keep and reuse.
If the site uses a hosted builder, ask what can be exported and what cannot. Some layouts and features depend on that platform and may need rebuilding elsewhere. That is not automatically a bad choice, but you should understand it before paying. Ownership and easy portability are related but different issues.
9. What are the full first-year and ongoing costs?
Ask for setup charges, recurring fees, renewal prices, and optional extras. Include hosting, domain renewal, email, paid plugins, maintenance, and third-party booking charges where relevant. Introductory prices can make two offers look similar even when later costs differ. Compare the same period and the same scope.
Any broad budget range should be treated as a planning estimate, not a market fact or a binding quote. For example, a simple brochure-site build might be planned at $1,500–$6,000, while custom integrations can cost more. The brief, region, provider, and content workload can change that estimate substantially.
For a named option, Plainform is $497 per month with a normal $497 setup fee, waived for the first 10 customers. Confirm current eligibility and the written package details. Twelve monthly payments total $5,964; with the normal setup fee, that becomes $6,461 before any applicable taxes or extras.
10. Who handles updates, backups, and problems?
Ask who updates software, checks forms, manages certificates, and restores backups. A hosting fee may cover server availability without covering content edits or plugin repairs. Get a written split of responsibilities. Ask whether backups are separate from the live site and how recovery is tested.
CISA recommends regular backups and recovery tests. Ask how much data could be lost between copies and how long restoration may take, without expecting a promise that nothing can ever fail. Find out how to report an urgent outage and whether support is available during your actual working hours.
11. What is the timeline and approval process?
Ask for milestones rather than one vague launch date. A reasonable plan identifies discovery, content, design review, build, testing, and launch. Clarify what you must provide and when. Missing photos or delayed approvals can affect the schedule even when the designer is ready to work.
Agree on revision rounds and who has final approval. Collect feedback from your team in one place instead of sending conflicting instructions. Ask what happens if either side is delayed or the project stops. The contract should explain payment stages, cancellation, and any work delivered at that point.
12. What happens if I want to leave?
Ask about notice periods, cancellation fees, exports, domain transfer, and access to content. Find out what stops working when a subscription ends. You may need to replace licensed features or rebuild platform-specific parts. A clear exit process is a sign of a well-defined service, not a reason to expect failure.
Use the website cost calculator to compare realistic scenarios over more than the first month. Add your own costs and mark unknown items instead of assuming they are free. Choose the provider whose scope, responsibilities, and long-term arrangement fit the business, not the one with the loudest promise of leads.
After your calls, compare answers in one document. Mark unclear items as unknown rather than assuming they are included. Send the provider a short summary of what you understood and ask them to correct it. Before paying a deposit, confirm the person or company receiving it matches the agreement. Keep copies of the scope, invoices, approvals, and account-access plan. Clear records support a better working relationship and a safer handover.
Common questions
Should I choose the cheapest quote?
Only if it meets your needs and the exclusions are acceptable. Compare writing, testing, account control, support, and recurring costs. A low build price can be sensible for a simple project, but unexpected missing work can change the total.
Is a monthly website service better than paying upfront?
Neither is always better. A monthly service may spread cost and include support, while an upfront build may suit a business that wants more direct control. Compare the contract, included work, exit terms, and total cost over your planned period.
Should a designer guarantee leads?
No designer controls all demand, competition, pricing, and follow-up. Ask for a practical plan to improve customer paths and measure inquiries. Evidence and honest reporting are more useful than a guaranteed sales claim.