--- title: "What Happens in a Website Design Consultation?" description: "Learn what a website design consultation should cover, how to prepare, which questions to ask, and what decisions you should have afterward." date: 2026-09-08 updated: 2026-09-08 author: SimpleLaunch category: Website Strategy industry: All industries primaryKeyword: website design consultation keywords: web design discovery call, website consultation questions, prepare for website redesign question: "What happens during a website design consultation?" answer: "A useful website design consultation clarifies the business goal, intended audience, priority actions, existing content and systems, project constraints, and the most sensible next step. You should leave with a clearer problem and decision—not pressure to buy a preset package." translation: consulta-diseno-sitio-web --- A website design consultation should clarify what the website needs to accomplish, who it must serve, what is getting in the way now, and whether a new build is the right next step. Expect questions about customers, services, content, search visibility, contact or booking paths, integrations, ownership, timing, and budget boundaries. You should not need technical vocabulary or a finished brief. The useful outcome is a decision: improve the current site, redesign it, build something new, or solve a narrower problem first. A consultation that ends only with “we will make it look modern” has not defined the job. ## What happens during a website design consultation? Most consultations begin with the business rather than the color palette. The designer needs enough context to understand why the website exists and what a successful visit should produce. The conversation should usually cover six areas: 1. **Business goal.** Is the site meant to generate qualified calls, appointment requests, estimates, applications, property enquiries, or something else? 2. **Audience.** Who is making the decision, what problem brings them to the site, and what do they need to trust before contacting the business? 3. **Current website.** Which pages attract useful traffic, where do prospects get confused, and what already works well enough to preserve? 4. **Content and proof.** Which services, locations, team details, photos, credentials, reviews, policies, or project facts are verified and available? 5. **Required systems.** Does the site need to connect with a form, calendar, CRM, phone workflow, payment tool, inventory source, or another approved platform? 6. **Constraints.** Who approves the work, who owns the content, what timing matters, and which budget or compliance limits affect the scope? This is discovery, not a live design session. A designer may discuss possible page structure or show relevant examples, but choosing a font or sketching a homepage before the underlying decisions are clear can lock the project around an assumption. ## What should you prepare before the call? Bring what already exists. Do not delay the consultation while trying to create a polished strategy document. A short preparation list is enough: - The current website URL and any other domains the business controls. - The two or three services or offers the new site must explain best. - The customer action that matters most after a visit. - Examples of enquiries the business wants more—and fewer—of. - Existing brand files, photos, copy, analytics, and search data, if available. - Websites you find clear or confusing, with a sentence explaining why. - Known integrations, such as scheduling, forms, a CRM, listings, or a client portal. - A realistic decision-maker list and any launch date that has a real business reason. If this is a redesign, preserve access to the current hosting, domain registrar, analytics, Search Console, forms, and content system. You do not need to hand over passwords on the first call, but the team should identify who controls each account. Ownership problems discovered during launch are far more disruptive than the same questions asked during discovery. ## Which questions should the designer ask you? The strongest questions expose decisions and tradeoffs. They are not a questionnaire performed for its own sake. Useful questions include: - What changed in the business that made this project necessary now? - Which customer should recognize immediately that this company is for them? - What do qualified prospects ask before they are willing to call or book? - Which services, markets, or audiences are priorities—and which are not? - What happens after someone submits a form or schedules a conversation? - Which claims, credentials, prices, service areas, and results can the business verify? - Which pages or search traffic must survive a redesign? - Who supplies and approves copy, images, legal language, and account access? - What will the business own when the project ends? - How will the site be tested before launch? Google's [people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) asks whether a visitor leaves feeling they learned enough to achieve their goal. That is a useful consultation test too. The call should uncover what customers actually need to learn, not create pages merely because every competitor has them. ## What should you ask the web designer? Use the consultation to understand how decisions will be made and what is included. Ask plain questions and expect plain answers. ### How will you decide what pages the site needs? The answer should connect pages to distinct services, audiences, search intent, or customer tasks. A larger page count is not automatically a better strategy. ### Who writes the copy and supplies the images? Confirm whether strategy, research, writing, editing, photography selection, image preparation, and approvals are included. “Content provided by client” can shift most of the difficult work back to the business. ### What happens to our existing search visibility? A redesign should inventory valuable URLs and decide what stays, changes, or redirects. Google's current [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) recommends preparing a URL map, testing the new site, using server-side permanent redirects when URLs change, updating internal links, and monitoring the move in Search Console. Ask who owns those tasks. ### How will accessibility be handled? Accessibility belongs in planning, content, design, development, and testing. The W3C's updated [planning and managing accessibility guidance](https://www.w3.org/WAI/planning-and-managing/) recommends setting objectives, assigning responsibilities, reviewing the current environment, and evaluating early and regularly. Ask for a working standard and testing approach rather than a vague promise or an overlay added at the end. ### What will we own and control after launch? Confirm ownership of the domain, source files, content, media, analytics, accounts, and any paid themes or subscriptions. Ask which recurring services are required, who can export the content, and what happens if the working relationship ends. ### What does launch verification include? The answer should cover real pages on desktop and mobile, forms or booking, links, analytics, metadata, redirects, structured data where appropriate, sitemap, robots controls, and error handling. For accessibility evaluation, the W3C's [WCAG Evaluation Methodology](https://www.w3.org/TR/WCAG-EM/) provides a structured way to define scope, explore the site, select representative pages, audit them, and report findings. ## Is a free website consultation just a sales call? It is partly a fit conversation: the provider is deciding whether the project matches its services, and the business is deciding whether to trust the provider. That does not make the call useless. The distinction is whether discovery changes the recommendation. Watch for these warning signs: - A package is recommended before the business problem is understood. - The conversation stays on colors, animations, and page count. - Nobody asks who follows up with a new enquiry. - Existing high-value pages, analytics, or redirects are ignored during a redesign. - Ownership, recurring costs, exclusions, and approval responsibilities remain vague. - The designer promises rankings, AI citations, leads, or revenue. - Every question is answered with a feature instead of a tradeoff. A credible consultation can conclude that the current site needs a focused repair, clearer service pages, or a better intake path—not necessarily a full rebuild. If your site already gets traffic but not enquiries, the related [website lead diagnosis](/blog/professional-services-website-not-generating-leads) shows why separating traffic, page clarity, trust, and post-submit handling matters before redesigning everything. ## What should you have after the consultation? You may not receive a complete strategy or specification from an introductory call. You should still understand: - The problem the project is intended to solve. - The primary audience and action. - Whether the current site can be improved or should be replaced. - The likely content, integration, migration, and approval work. - The major unknowns that affect scope or timing. - The provider's recommended next step and why. - What would need to be confirmed in a written proposal or agreement. Do not treat a verbal estimate as a complete scope. Before work begins, put deliverables, responsibilities, exclusions, payment terms, ownership, launch requirements, and ongoing costs in writing. ## Website design consultation checklist Before the call: - Choose one primary business outcome for the website. - List priority services, audiences, and customer questions. - Gather current URLs, useful data, content, and brand assets. - Identify account owners and final decision-makers. - Note required systems and genuine timing constraints. During the call: - Explain the business problem before discussing visual preferences. - Ask how scope, content, SEO, accessibility, migration, and testing are handled. - Confirm who owns decisions, accounts, assets, and ongoing costs. - Write down assumptions that still need evidence. After the call: - Confirm the recommended next step in plain language. - Compare the written scope with the problem you described. - Do not proceed until responsibilities, ownership, exclusions, and launch checks are clear. SimpleLaunch starts with a free 20-minute conversation about what the business does, who the website needs to reach, and what should happen after a visitor lands. If a new site is not the right next move, you will hear that plainly. [Book a website design consultation](/#contact) to clarify the problem and the smallest sensible next step. ## Authoritative sources - [W3C Web Accessibility Initiative: Planning and Managing Web Accessibility](https://www.w3.org/WAI/planning-and-managing/) - [W3C: Website Accessibility Conformance Evaluation Methodology](https://www.w3.org/TR/WCAG-EM/) - [Google Search Central: Creating Helpful, Reliable, People-First Content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) - [Google Search Central: Site Moves and Migrations](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)