Use these categorized questions to vet any web designer for fit, timeline, cost, technical quality, and post-launch support. Group your questions into seven areas: discovery approach, portfolio proof, process and revisions, technical and SEO practices, accessibility, ownership and handoff, and post-launch pricing. Request written answers so you can compare candidates side-by-side. Look for a documented process, two to three revision rounds, and clear WCAG awareness. Those three signals separate a professional from a hobbyist fast.
TL;DR:
- Most designers who lack a documented process, clear revision limits, and WCAG awareness tend to be hobbyists rather than professionals.
- Asking for live project URLs, detailed roles, and measurable results helps verify a designer’s real-world capability beyond polished mockups.
- A precise project timeline with milestones and a clear revision policy indicates a reliable process and minimizes scope creep risk.
- Selecting a platform that aligns with your business needs and verifying SEO, speed, and accessibility practices are critical for long-term success.
- Full ownership of source files, transparent pricing, and documented support policies prevent costly disputes and ensure control over your website.
Table of Contents
- Questions For A Web Designer About Your Business Goals
- Portfolio Proof: Live Sites, Roles, And Results
- Process, Timeline, And How Revisions Work
- Platform Choice, Performance, And SEO Basics
- Accessibility Questions Every Designer Should Answer
- Ownership, Source Files, And Admin Handoff
- Post-Launch Support, Maintenance, And Pricing
- Communication, Roles, And What You’re Responsible For
- Pricing, Contracts, And Red Flags To Watch For
- How To Score And Compare Candidate Answers
- Why Written Answers Beat Sales Pitches Every Time
- A Web Design Partner Built Around Direct Ownership
- Where To Go For Deeper Standards Reading
- Sources
- FAQ
Questions For A Web Designer About Your Business Goals
Before anyone opens a design tool, your designer should understand what your business actually needs from a website. A designer who jumps straight to color palettes without asking about your customers or your goals is a designer who builds pretty things that don’t perform.
Discovery is the foundation of every good web design project, and it’s the phase most candidates skip past too quickly. This is where you separate order-takers from partners who think strategically about your business.
Ask these questions early:
- How will you research my business, my competitors, and my target customers before design starts?
- Can you show me an example of a discovery document or brief you’ve created for a past client?
- What does success look like to you for this project, and how will you measure it (leads, bookings, sales, calls)?
- What do you need from me, and by when, to keep the project moving?
A strong answer names specific research methods (competitor audits, customer interviews, analytics review) and ties design decisions to business outcomes, not just aesthetics. A weak answer sounds like “we’ll figure that out as we go” or that focuses only on visual style.
Pro Tip: Ask the designer to walk you through how a past project’s goals shaped an actual design decision, like a homepage layout or a call-to-action placement. If they can’t connect strategy to a specific choice, discovery was probably a checkbox exercise, not a real process.
Pay attention to whether they ask about your content and image timeline during this conversation. Designers who wait until the deadline to ask for your product photos or team bios are setting you up for delays later.
Portfolio Proof: Live Sites, Roles, And Results
Anyone can show you a polished screenshot. What you need is proof the site actually works in the real world, and proof that the person sitting across from you did the work.
Start with these questions:
- Can you send me live URLs, not just images or mockups, for three to five recent projects?
- What was your specific role on each project? Did you handle design only, or design and development, or did an agency team split the work?
- Do you have a case study showing measurable results, like traffic growth, conversion improvement, or lead volume?
- Can you connect me with a past client I can contact directly?
A designer who hesitates to share live URLs or dodges the “what was your role” question is worth a second look before you sign anything. Toptal’s guide to web designer interview questions recommends scenario-based prompts precisely because portfolios alone don’t reveal how someone actually solves problems under real constraints.
Once you have the URLs, do your own quick audit. Open each site on your phone and check whether the layout adapts cleanly. Run a Lighthouse or Core Web Vitals check to see how fast the page loads. Glance at the page title and meta description in the browser tab and search results to confirm someone thought about basic SEO.
These five minutes tell you more than a sales call ever will. A site that loads slowly, breaks on mobile, or has a generic “Home” page title suggests the portfolio piece was rushed or the designer’s follow-through doesn’t match their pitch.
Process, Timeline, And How Revisions Work
A vague timeline is one of the clearest warning signs in web design. If a designer can’t describe their process in specific phases, they don’t have one. That means your project timeline lives entirely in their head, subject to change whenever they feel like it.
Ask for a written process broken into stages:
- Discovery and strategy. What research and planning happens before any design work starts?
- Wireframes or content structure. Do you see a layout plan before visual design begins?
- Design mockups. How many concepts do you review, and in what format?
- Development. Who builds the live site, and how do they test it before showing you?
- Quality assurance. What gets checked before launch (browsers, devices, broken links, forms)?
- Launch and handoff. What happens on launch day, and what do you receive afterward?
Ask for calendar dates tied to each phase, not just a total project length. A designer who says “eight weeks” without milestone dates is giving you a guess, not a plan.
Then clarify revisions directly: how many rounds of feedback are included at each stage, and what happens if you want changes beyond that limit? A few rounds of revisions are typical for most small business projects, generally limited to a small number such as two or three. Beyond that, expect a change-order process with additional cost, and get that policy in writing before you start.
Pro Tip: Ask what counts as “in scope” versus a billable change. A designer who can answer this instantly, without hedging, has been burned by scope creep before and built a system to prevent it. That’s a good sign, not a red flag.
Platform Choice, Performance, And SEO Basics
The technology behind your site matters more than most owners realize, mostly because it determines how much control you’ll have later and how fast your pages load for visitors.
Ask what content management system or platform the designer recommends, and why it fits your business specifically rather than being their default answer for every client. WordPress remains a common choice for small business sites because of its flexibility and the sheer number of people who know how to maintain it, but it isn’t automatically right for every project.
Cover these technical questions directly:
- What CMS or platform do you recommend, and what ongoing maintenance does it require?
- How do you optimize page speed, through image compression, responsive images, or caching?
- How do you measure and improve Core Web Vitals before launch?
- What SEO basics are included: title tags, meta descriptions, structured data, and redirect mapping if this replaces an existing site?
- If this is a redesign, how do you handle URL redirects so I don’t lose existing search rankings?
Page speed and mobile usability directly affect how Google ranks your site and how long visitors stick around, which is why Core Web Vitals has become the shorthand the industry uses for measuring real-world performance. A designer who can’t explain, in plain terms, how they’d improve a slow-loading image gallery probably hasn’t thought much about performance at all.
Responsive design deserves its own line of questioning too. Ask specifically how they approach mobile-first design rather than assuming a desktop layout will simply shrink down cleanly. A site built desktop-first and adjusted for mobile as an afterthought often shows cramped navigation, tiny tap targets, or text that requires zooming.
Migrations deserve extra scrutiny. If you’re redesigning an existing site, ask exactly how old URLs will map to new ones. A missed redirect plan can quietly tank search traffic you’ve spent years building, even when the new design looks fantastic.
Accessibility Questions Every Designer Should Answer
Accessibility isn’t a nice extra anymore. It affects how many customers can actually use your site, and it carries real legal weight for U.S. businesses.
Ask whether the designer targets Web Content Accessibility Guidelines (WCAG) 2.1 level AA, which is the accepted technical standard most organizations aim for when building accessible digital experiences. A designer who’s never heard of WCAG is a designer who hasn’t been tested on this front, and that gap can become your liability later, not just theirs.
Cover these specific questions:
- Do you design and test to WCAG 2.1 AA, and what tools or manual checks do you use to verify it?
- Can you show examples of past projects where accessibility was a specific requirement?
- Does your quote include an accessibility audit, or is remediation billed separately if issues come up after launch?
Section 508 outlines the U.S. federal accessibility framework, and while it technically governs federal agencies, it shapes the broader legal expectations that apply to many private businesses too, especially those serving the public. A designer who understands this landscape will talk about screen reader compatibility, color contrast ratios, and keyboard navigation without you having to prompt every point.
Accessibility work also tends to overlap with SEO in ways owners don’t expect. Clear heading structure, descriptive alt text on images, and readable link text help both screen readers and search engine crawlers understand your site’s accessibility at the same time, an overlap explored in Babylovegrowth’s accessibility and SEO guide.
Ownership, Source Files, And Admin Handoff
Here’s a scenario that plays out more often than it should: a small business owner wants to switch web designers years later, only to discover the original designer holds the only login credentials, and the source files sit on a server the business doesn’t control. Don’t let that be your story.
Ask these ownership questions before signing anything:
- Who legally owns the final design files, source code, and any custom imagery once the project is complete?
- Will the ownership terms be written into the contract, not just implied in a conversation?
- What admin accounts will I receive: CMS login, hosting account, domain registrar, and backup access?
- Will you provide documentation for how the site was built and how to deploy updates?
- Is copywriting or image sourcing included in your quote, or do you recommend specific vendors for content?
You want full ownership of your creative assets with no ongoing licensing string attached and no dependency on one person to keep your site running. That standard should apply regardless of who you hire, and it’s worth writing directly into your contract rather than trusting a verbal promise.
Before launch, request a simple written website launch checklist that spells out every account, password, and file you should have in hand. If a designer resists handing over admin access “for now,” treat that resistance as the answer to a question you didn’t have to ask out loud.
Post-Launch Support, Maintenance, And Pricing
A website is not a “set it and forget it” purchase. Plugins need updates, security patches come out regularly, and something will eventually break, usually at the worst possible time. Ask about support before you need it, not after.
Cover these questions directly:
- Is ongoing maintenance included, or is it billed as a separate retainer? What does that retainer cover specifically?
- What’s your response time for a critical issue, like a site going down or a broken checkout form?
- Are security updates and backups part of your standard service, or do I need to arrange those separately?
- What recurring costs should I budget for beyond your fee, such as hosting, domain renewal, or plugin licenses?
A designer with a real maintenance offering can describe response times and backup frequency without pausing to think. Vague answers like “we’ll get to it when we can” mean you’re on your own the moment something goes wrong, likely during a busy sales week.
Pro Tip: Ask what happens if you decide NOT to purchase a maintenance plan. A designer who still gives you a straight answer, without pressure tactics, respects your decision either way. One who suddenly gets vague about updates and security is using maintenance fees as leverage rather than an honest service.
For a deeper look at what a healthy support arrangement includes, this guide to website maintenance for small businesses breaks down what should be covered in a typical package versus what counts as extra.
Communication, Roles, And What You’re Responsible For
The best design skills in the world won’t save a project buried in miscommunication. Before work begins, get clear on exactly who you’re talking to and what they expect from you in return.
Ask these questions about how the relationship will actually run:
- Who is my main point of contact day-to-day, and is any part of this project subcontracted to another freelancer or agency?
- How often will we meet, and through what channel (email, phone calls, a project management tool)?
- How do you handle feedback when I have multiple people on my team weighing in with different opinions?
- What exactly do I need to provide, and by what dates, to keep the project on schedule?
That last question matters more than owners tend to realize going in. Missing content deadlines is one of the most common reasons small business web projects slip past their launch date, and it’s rarely the designer’s fault when it happens. If you know upfront that you owe photos by week two and final copy approval by week four, you can plan around it instead of scrambling.
Watch for how a designer talks about subcontracting. There’s nothing wrong with a small studio bringing in a specialist for a specific task, but you deserve to know who’s actually touching your project and who’s accountable if something goes wrong.
Pricing, Contracts, And Red Flags To Watch For
Money conversations feel uncomfortable, but a designer who avoids specifics here is telling you something important. Get an itemized quote, not a single lump number, so you can see exactly what you’re paying for.
Ask directly:
- Can you provide an itemized quote breaking down design, development, content, and any add-ons separately?
- What’s the payment schedule? Is there a deposit, and are remaining payments tied to specific milestones?
- Who owns the domain name, and do I have direct account access to it, regardless of who registers it?
- What’s your cancellation policy if the project needs to end early, and is there a warranty period after launch covering bug fixes?
Practitioner guides on vendor vetting consistently point to five areas where projects fail most often: pricing and scope confusion, timeline slippage, ownership disputes, endless revision cycles, and abandoned post-launch support. Every question in this article maps back to one of those five failure points.
Here’s a quick reference for red flags versus healthy signals:
| Red Flag | Healthy Signal |
|---|---|
| Vague scope with no written deliverables list | Detailed scope document tied to the contract |
| “We keep the source files” | Full ownership transfer written into the agreement |
| “Unlimited revisions” with no defined process | Two to three revision rounds, clearly scoped |
| No mention of a warranty or bug-fix period | Defined warranty window after launch |
| Payment demanded entirely upfront | Deposit plus milestone-based payments |
If two or more of these red flags show up in a single conversation, treat it as a signal to keep interviewing other candidates rather than a quirk to overlook.
How To Score And Compare Candidate Answers
Written answers only help if you actually compare them side-by-side instead of going with gut feeling after each call. A simple scoring rubric turns a stack of vague impressions into a real decision.
Score each candidate on three axes, zero to five points each:
- Experience fit (0 to 5): How closely does their portfolio match your industry, project size, and platform needs?
- Process clarity (0 to 5): Did they give you a written, phased process with real dates, or a loose verbal outline?
- Post-launch support (0 to 5): Is ongoing maintenance clearly defined with response times, or left as an afterthought?
Weight process clarity and post-launch support slightly higher than experience fit if you’re a first-time website owner, since those two areas cause the most pain after the contract is signed. Live sites and contactable references remain the strongest evidence you can gather, stronger than any polished process document, because they show what a designer actually delivered rather than what they promise to deliver.
Run this quick verification pass on your top two or three candidates: open a live URL on your phone, run a mobile usability check, and request two client references you can actually call. Here’s a simplified example of comparing two candidates’ written answers side-by-side:
| Question | Candidate A | Candidate B |
|---|---|---|
| Revision rounds included | 2 rounds, extra billed hourly | “Unlimited,” no written limit |
| Who owns source files | Client owns everything, in contract | Not addressed in quote |
| Maintenance plan | Optional retainer, response time stated | Not mentioned unless asked |
Candidate A’s answers are shorter, but every one of them is specific and verifiable. That pattern, specificity over promises, is exactly what you’re screening for across every category in this checklist.
Why Written Answers Beat Sales Pitches Every Time
At a creative studio, new potential collaborators and vendors are asked to put their process in writing before any contract discussions begin, holding every partner conversation to high standards. A confident answer said out loud on a call can evaporate under scrutiny once it’s written down, revision limits and ownership terms included. Writing forces specificity that a sales pitch can gloss over.
Two habits guide how I vet any partner or vendor: I ask for a live example of their actual work, not a description of it, and I ask what happens when something goes wrong, not just when things go right. The second question tells you more about a working relationship than the first ever will.
— Charles
A Web Design Partner Built Around Direct Ownership
If you’ve worked through this checklist and found yourself wishing more designers gave straight answers, that’s a gap some studios aim to close by offering bespoke projects with no recycled templates, providing direct collaboration with the creative lead through the entire process rather than through multiple account managers. Complete ownership of design files and assets upon project completion is a standard that some studios provide, without licensing restrictions or vendor-imposed access limitations later on.
That direct-access model matters most in the categories this checklist covers hardest: process clarity, ownership, and honest post-launch conversations. A strategy-led process ties design decisions back to the specific business needs of each client, rather than applying a generic solution to every project. If you’re weighing a redesign against a full rebuild, the Website Redesign service page walks through that distinction directly.
Ready to put these questions to work on a real project? Visit the Web Design & Development page to see the studio’s approach in detail, then reach out to schedule a discovery call and start comparing your notes against a written process of your own.
Where To Go For Deeper Standards Reading
For readers who want to go past this checklist into the underlying standards, a few sources are worth bookmarking directly.
- WCAG 2.1 lays out the technical accessibility criteria designers should be testing against.
- Section508 explains the U.S. federal policy context behind accessibility obligations.
- MarTech’s 100+ question checklist offers an even longer question bank for readers planning a large-scale build.
Sources
- Section508
- 100+ questions you must ask when developing a website — MarTech
- Toptal — Web designer interview questions
FAQ
What are some basic questions to ask a web designer?
Start with discovery (how they’ll research your business and customers), portfolio proof (live URLs and their specific role), process and timeline, pricing and contract terms, and post-launch support. Those five categories cover the areas most likely to cause problems if left unasked.
What are the 7 principles of web design?
Definitions vary slightly by source, but common versions include balance, contrast, emphasis, consistency, unity, hierarchy, and whitespace. Ask any designer you’re considering to explain how they apply two or three of these to an actual project, not just define them in the abstract.
What are the 5 elements of a good website design?
Most practitioner guides point to clear navigation, mobile responsiveness, fast page speed, readable content hierarchy, and a strong call to action as the core elements. A designer worth hiring should be able to point to each element on a live site they’ve built, not just describe it in theory.
What should a website design questionnaire include?
A solid questionnaire covers your business goals and target customers, desired features and pages, content and image readiness, budget range, timeline expectations, and examples of sites you like or dislike. Charles-creative uses a similar discovery approach to make sure design decisions connect back to real business needs from the first conversation.
How much revision is typically included in a web design project?
Two to three rounds of revisions is standard for most small business website projects, with additional changes billed separately as out-of-scope work. Get this number in writing before the project starts so you know exactly where the line sits.