Website Design Questionnaire: 40 Questions to Ask Clients
Last updated: November 18, 2026
A website design questionnaire is the set of questions you ask a client before design starts, so the brief, scope, and timeline rest on their answers instead of guesses. Below are 40 questions in eight groups: the business, goals, audience, content, brand, features, budget and decisions, and feedback and launch.
This guide is for agency owners, designers, and project leads starting a new website. NN/g recommends running stakeholder interviews from a discussion guide rather than a script, covering success metrics, priorities, history and expertise, and how people want to be kept in the loop. The questions below follow the same idea: send them before the kickoff call, then use the call to go deeper on the answers.
The Business
- 1. What does your business do, in one sentence? The answer often becomes the first line of the homepage.
- 2. Who are your best customers? Design for the customers they want more of, not everyone.
- 3. What makes you different from your competitors? This is what the site has to make obvious.
- 4. Which competitors do customers compare you with? Look at those sites before the first design review.
- 5. What is changing in your business this year? New services, prices, or locations change what the site needs on day one.
Goals and Success
- 6. Why are you redesigning now? The trigger tells you what the client will judge the project by.
- 7. What should the new site do that the current one does not? Concrete answers become requirements; vague ones need a follow-up.
- 8. What is the one action you most want visitors to take? Calls, bookings, sign-ups, or purchases set the page hierarchy.
- 9. How will you know the site is working six months after launch? Agree the measure now, so success is not decided after the fact.
- 10. What would make this project a failure in your eyes? Fears surface risks that a goals question misses.
Audience
- 11. Who visits the site today, and who do you want to reach? The gap between the two is often the real brief.
- 12. What do visitors come to do? Top tasks decide the navigation.
- 13. What do customers ask before they buy? Those questions are your page sections and FAQs.
- 14. Which devices do your visitors use? If you have analytics, ask for access rather than a guess.
- 15. Do any of your visitors have accessibility needs, or do you have a legal requirement to meet? Agree a target such as WCAG 2.2 level AA now, not at launch.
Content
- 16. Which pages do you need? A page list is the start of a scope you can price and check.
- 17. Who writes the copy, and by when? Late content holds up every step after it, so agree the date now.
- 18. Which photos, videos, and logos do you have, and who owns the rights? Stock or a shoot changes both budget and timeline.
- 19. What existing content must stay, and which old pages need redirects? Old pages that rank in search need a plan before they disappear.
- 20. Do you need legal pages, such as a privacy policy, terms, or cookie notice? Someone on the client side has to supply or approve them.
Brand and Design
- 21. Do you have brand guidelines, fonts, and colors we must use? Ask for the files, not a description.
- 22. Which websites do you like, and what specifically about them? The “what” matters more than the link.
- 23. Which websites do you dislike, and why? Dislikes are often clearer than likes.
- 24. Which three words should people use to describe the site? Use them later to settle design debates.
- 25. Is anything off-limits? Colors, imagery, or phrases the client will reject save a round of revisions.
Features and Technical
- 26. Who will update the site after launch, and how often? This decides the content management system and the training you plan.
- 27. Which tools must the site connect to? CRM, booking, payments, email, and analytics each add work and testing.
- 28. Which forms do you need, and where should each one send its data? Every form needs a destination someone checks.
- 29. Who controls the domain, hosting, and current site logins? Access problems are a classic constraint to find in discovery, not on launch day.
- 30. Do you need more than one language or region? A second language adds translation, review, and testing for every page.
Budget, Timeline, and Decisions
- 31. What budget range have you set? A range lets you shape the scope instead of guessing it.
- 32. When do you need to launch, and what is driving that date? An event or campaign date is fixed; a preference is not.
- 33. Who has the final say on design and content? Name one approver, so conflicting feedback has someone to settle it.
- 34. Who else will review the work? A reviewer who joins late can reopen work the client already approved.
- 35. How many revision rounds do you expect? Agree the number now. Our guide on scope creep covers what happens after the last one.
Feedback and Launch
- 36. How do you prefer to give feedback? Ask early; NN/g treats communication preferences as part of stakeholder planning. Comments pinned on the page beat long email threads.
- 37. How quickly can you return feedback in each round? Days per round belong in the project plan.
- 38. Who will test the site before launch? Client testers need time in the schedule for user acceptance testing.
- 39. What does “done” look like for you? This becomes the sign-off condition.
- 40. Who looks after the site after launch? Maintenance, fixes, and updates need an owner and, often, a separate agreement.
How to Send the Questionnaire
- Send it before the kickoff call. Written answers give you time to prepare follow-up questions.
- Trim it to the project. A small refresh does not need all 40 questions. Keep the goals, content, and decisions groups for every project.
- Use a form, not an attachment. A shared form is easier to answer than a document clients have to save and send back.
- Talk through the answers. Treat the call as the semistructured interview NN/g describes: follow the answers, not the list.
What to Do With the Answers
Turn the answers into three documents the client signs: a short brief (goals, audience, the one action, what success means), a scope written as a list (pages, templates, integrations, rounds, exclusions), and a website project plan with dates and owners. Then follow the website design process step by step. When feedback starts arriving, our guide on how to manage client feedback covers the rounds.
When the design is live on a staging site, clients can open an OverlayQA review link and comment on the page itself, with no account or extension. Each comment arrives as an issue with a screenshot, the page address, browser, and screen size, so question 36 has an answer before the first round.
Frequently Asked Questions
What questions should I ask a client before designing a website?
Ask about the business, goals and success, audience, content, brand, features, budget and timeline, who decides, and how they will give feedback. Start with what the site must achieve and who approves the work.
How long should a website design questionnaire be?
Long enough to cover goals, content, and decisions, and short enough that the client finishes it. For a small project, 15 to 20 questions is often enough; use the full 40 for a new site or a redesign.
Should I send the questionnaire or ask it on a call?
Both. Send it first so the client has time to think and gather files, then use the kickoff call to follow up on the answers that matter most.
What is the difference between a questionnaire and a design brief?
The questionnaire collects the client’s answers. The brief is the summary you write from them and ask the client to approve, so the whole team works from the same goals.
What if the client does not know the answers?
That is a finding, not a failure. Unknown goals or content owners are risks to plan for, and some answers, such as who visits the site, can come from analytics instead.
Which questions matter most?
The one action you want visitors to take, how success will be measured, who writes the content and by when, who has the final say, and how many revision rounds are included.
Collect client feedback on the live page instead of in email threads. With OverlayQA, clients comment with no account, and each comment becomes a tracked issue with the screenshot attached.