Website Design Discovery Questions to Ask Before You Build

Website design discovery is the conversation that turns “we need a new site” into a project people can actually estimate, build, test, and maintain. Good questions reveal the customer's decision, the business's real workflow, and the constraints that a visual mockup cannot show.

Use these questions with your team or a prospective developer. The answers do not need to be perfect; they need to make assumptions visible early.

Business and customer questions

• What does the business sell or deliver, in plain language?
• Who is the primary customer for the first release?
• What problem causes that customer to search or call?
• What makes the business a fit, and who is not a fit?
• Which questions delay a decision today?
• What should a visitor do after understanding the offer?

If everyone describes the business differently, write the shared version before designing a home page. The website copy checklist can help turn internal language into customer language.

Goals and measurement questions

Ask what should improve after launch: calls, qualified forms, bookings, purchases, applications, support deflection, recruiting, or trust. Define the event that proves progress and where the record lives.

Separate a design goal from a business outcome. “A cleaner layout” can support “more completed quote requests,” but the project should measure the latter.

Content and page questions

• Which pages exist today, and which still earn their place?
• Which services, products, locations, or audiences need distinct pages?
• Who supplies copy, photos, policies, prices, and proof?
• What content is outdated, duplicated, or legally sensitive?
• Which URLs and search pages must remain stable?
• Who approves content, and how quickly can they review it?

Page count should follow real customer questions, not a template package. Use the content audit checklist to inventory what already exists.

Workflow and integration questions

Ask what happens after every form, booking, purchase, download, or login. Which system receives the record? Who owns it? What fields are needed? What happens if an integration fails? Which tools are authoritative for customers, inventory, appointments, products, or payments?

A website can look complete while its business workflow is unfinished. Include CRM, calendar, email, payment, inventory, analytics, chat, search, and customer portal requirements in discovery when they affect the first release.

Ownership and maintenance questions

• Who owns the domain, code, hosting, accounts, and data?
• Who can edit content and manage users?
• How are backups, updates, security, and monitoring handled?
• What happens if the business changes provider?
• Which work is included after launch, and which is new development?

Ownership terms should appear in the scope or agreement, not rely on an informal promise. See how to choose a website support plan.

Constraints and risk questions

Identify launch dates, required vendors, security needs, accessibility requirements, content dependencies, data migration, approval bottlenecks, and budget boundaries. Name risks that could change the estimate.

Ask what the team can launch without. A smaller release with accurate content and reliable forms is usually easier to learn from than a large release blocked by one unfinished integration.

Acceptance questions

Define what “done” means for pages, responsive behavior, forms, integrations, redirects, analytics, accessibility, performance, content, training, and launch. Include test scenarios for the normal and failure paths.

The guide on website QA before launch turns these questions into a practical test list.

Good discovery does not make every decision in advance. It makes the decisions that affect scope, ownership, and risk visible enough to handle deliberately.