Web Design Questions to Ask Clients (Local Biz Guide)

Why local business clients need a different question set

Most web design questionnaires assume two things that are false for a roofer, a hairdresser, or a small architecture firm: that the client already has a website to critique, and that they can articulate brand goals in marketing language. They usually can't. A plumber who's run a solid business for 15 years off word of mouth has never had to define a "target audience" or pick a "brand personality." Ask him that and you'll get a blank stare, not a brief.

The standard listicle, the one built for SaaS startups and marketing teams, front-loads questions like "what's wrong with your current site" and "what's your brand voice." For a client with no current site and no brand voice, those questions waste the call. Worse, they signal that you don't understand their business, which is the opposite of what gets you hired.

This guide reorders and rewrites the questions for that reality: no existing site, no marketing vocabulary, often a decision made in five minutes between customers. It also covers the part other guides skip entirely, what to do when the client genuinely doesn't know, and how to use a draft instead of a questionnaire to get there faster. If you're still figuring out where to find these clients in the first place, finding businesses without a website is the logical step before any of this applies.

*Related: Guaranteed Web Design Leads: Myth vs. Reality*

*Related: Website Design Templates: A 2026 Guide for Freelancers*

Business & goals questions to ask first

Start with what the business does and what a website visit should end in, not with abstract goals. Local clients think in jobs done and customers served, not in "conversion funnels."

What does your business actually do day to day?

This question replaces the generic "what are your business goals" and gets a concrete answer instead. A painter will tell you about residential repaints versus commercial jobs, about which one pays better, about the slow season in January. That's content strategy material you can't invent. It also tells you whether the site needs a quote form, a gallery, or a booking calendar, long before you've asked a single "feature" question.

What should a visitor do after landing on the site?

One answer only, not a list. Most local businesses default to "get a phone call," which simplifies the whole build: a big, visible phone number and a single call-to-action beat five competing buttons every time. If the honest answer is "I don't know," that's useful too. It tells you the owner has never thought about the site as a sales tool, which should change how you price and scope the project. For a deeper breakdown of what local businesses actually need functionally, see what local businesses need from a website.

Audience, branding and style questions

Skip "what's your brand personality" and ask about the customer instead, because that's the question they can actually answer. A hairdresser can describe her regulars. She cannot describe a "brand archetype."

Who is your typical customer?

Ask for a real person, not a demographic. "Women 35 to 55, mostly local, booking color and cut every six to eight weeks" is usable. "Everyone who needs a haircut" is not, so push once: "Who's your best customer, the one you'd clone ten times?" That usually produces something specific.

Which websites (competitors or not) do you like and why?

Show, don't ask abstractly. Pull up two or three competitor sites during the call and watch the reaction. Most owners can't describe style preferences cold, but they can point and say "I like how clean that looks" or "that's too busy." That reaction is worth more than any adjective they'd offer unprompted. If they have a logo or brand colors already, confirm file formats now, not during production. If they don't, don't force the issue. Plenty of local sites launch with a clean type treatment and no formal logo at all.

Content, features and technical questions

Figure out what raw material already exists before you plan pages, because most local clients have more than they think, scattered across a phone and a Facebook page.

Do you have photos, texts or a logo already?

Usually some photos, rarely usable text, almost never a logo file. Pull existing photos from their Google Business Profile and Instagram before the call if you can. It saves a step and lets you ask "can I use these photos from your Google listing" instead of "do you have photos," which gets a faster yes.

Which languages do your customers speak?

This gets skipped constantly and it shouldn't, especially in cities with large immigrant or tourist populations. A Berlin electrician who gets half his calls from Turkish-speaking customers needs a Turkish page, not a Google Translate afterthought. Ask directly: which language do walk-ins or callers actually use. Then confirm whether local SEO terms should be bilingual too, since "Elektriker Berlin" and its Turkish equivalent are different search queries with different competition. A multilingual website isn't a premium add-on for these businesses; for some, it's the main reason the site exists at all.

Budget, timeline and logistics questions

Ask about timeline before budget, because deadlines are concrete and budgets are not. "When do you want this live" gets a real answer: before the busy season, before a grand opening, before a competitor's new site goes up. "What's your budget" gets silence or a lowball guess.

For the money question, offer ranges tied to outcomes instead of asking "what's your budget" cold. Something like "a simple 5-page site with hosting runs in one range, a booking system and multilingual pages push it into a higher one" gives the client something to react to rather than a number to defend. The guide to what a Handwerker website actually costs is useful to have open during that part of the call, so you're quoting ranges you can back up on the spot.

When clients can't answer: fallback questions and research shortcuts

When a client says "whatever you think is best," stop asking open questions and start researching instead. Open-ended questions assume the client has already formed an opinion. Many haven't, and forcing one out of them on the spot just produces a vague, noncommittal answer you'll have to walk back later.

Do this instead:

• Pull their Google Business Profile. Category, hours, photos, and especially the Q&A and review sections tell you what customers actually ask and care about.
• Read the last 10 reviews. Customers mention exactly what they value: fast response, fair pricing, a particular staff member. That's your homepage copy, written by someone else.
• Check two competitors in the same city. Not for style theft, but to see what's standard in their market, what services get listed first, what they charge if it's public.
• Ask yes/no reaction questions instead of open ones. "Should the phone number be at the top of every page?" beats "how should navigation work?" every time, because it has a right-feeling answer the client can recognize immediately.

Take a client who answers every question with "I trust you." Rather than pushing harder, pull their Google Business Profile, note that 80% of their reviews mention same-day response time, and build that into the homepage as the lead line. Then show it to them and ask one question: "does this sound like your business?" That's a question they can actually answer.

The 'show, then ask' method: using an AI draft to skip blank-page discovery

Build a working draft first, then ask the client to react to it instead of describe it. This flips the whole discovery process. Instead of "what should the homepage say," you ask "is this close?" Instead of "what colors represent your brand," you ask "does this feel right or too corporate?" Reaction questions are easier for anyone to answer, and they're dramatically easier for a client with no design vocabulary.

This is the core idea behind LumaSite: generate a real preview, with a live link, based on the business's existing Google Business Profile data and photos, before the discovery call even finishes. You're not asking the client to imagine a website. You're asking them to look at one and say what's wrong with it. That's a faster conversation and it closes more deals, because an abstract pitch is easy to postpone and a concrete preview link is not. The broader sales process around this approach, including how discovery fits into actually closing local business clients, is covered in selling websites to local businesses.

Practically, this doesn't replace every question above. It replaces the ones that ask clients to generate something from nothing: tone, structure, page layout, visual style. The budget, timeline, and decision-maker questions still need to happen the old-fashioned way, because no draft answers those.

Honest limits: what these questions won't fix

Good questions don't fix a bad client fit, and no questionnaire guarantees a smooth project. A well-run discovery call narrows ambiguity. It doesn't eliminate indecision, inflate a real budget, or force an owner to make a fast decision if that's not how they operate. Some clients will still say "surprise me" after three rounds of specific questions, and some will still change their mind after seeing the finished site, no matter how clear the brief was.

Scope creep is the realistic failure mode here, not bad questions. A client who asked for five pages during discovery will ask for an online store three weeks into the build. Good discovery questions reduce how often this happens, but a written scope and a change-order policy prevent it. Treat the questionnaire as a starting contract, not a finished one.

Self-reported budgets are also unreliable by nature. A client might say "$500" because that's what a friend paid for something unrelated, not because it reflects what their project needs. Ranges tied to outcomes, as covered above, help more than asking the number directly, but they don't guarantee accuracy either.

Red flags in client answers that predict a difficult project

Some answers during discovery are worth weighing heavily before you commit to the project.

• "My nephew/cousin can also do this" signals price sensitivity and a comparison mindset that usually ends in haggling.
• Can't name a single competitor often means they haven't thought about the market their site needs to compete in, which means more revisions later.
• Wants to approve every single word before it goes live predicts a slow project with heavy back-and-forth, budget for that in your timeline.
• Vague on who actually decides (a spouse or business partner not on the call) is the single biggest predictor of late-stage scope changes.
• No clear answer on what success looks like, beyond "a nice website," means you'll be the one defining success after launch, which is a harder position to defend if they're unhappy.

FAQ

What are the 7 C's of website design?

The 7 C's are a planning checklist, not a question script. The 7 C's of effective website design, introduced by Rayport and Jaworski, include Context, Content, Community, Customization, Communication, Connection, and Commerce. They're useful for structuring your own thinking about a project, but they don't replace direct questions to the client. A local business owner has never heard of "customization" as a design principle, so translate it: ask about photos and logo (customization), ask about contact method (communication), ask about reviews and social proof (community).

What are some good questions to ask clients?

The core set covers five areas: what the business does and what success looks like, who the typical customer is, what content and photos already exist, what the budget range and deadline are, and how the client prefers to communicate during the project. Each area has its own section above with specific wording that works better than the generic versions found in most questionnaires.

What are the five golden rules of web design?

Simplicity, consistency, clear navigation, speed and mobile-friendliness, and obvious calls-to-action are among the most commonly cited rules, though different sources frame the "five golden rules" somewhat differently. Discovery questions should map directly onto these: ask what one action a visitor should take (maps to clear CTAs), ask what pages are truly necessary (maps to simplicity), and ask how customers currently find the business, phone or mobile search, mostly (maps to mobile-friendliness).

What are 5 good questions to ask?

For a time-pressed call with a local business owner: What does your business do day to day? Who's your typical customer? What should a visitor do after landing on your site: call, book, or visit? Do you have photos or a logo already? When do you need the site live? Five questions, ten minutes, enough to start a draft.

What if the client doesn't have a website at all yet?

This changes the whole approach. Skip every "what's wrong with your current site" question entirely and instead focus on business basics, competitor research, and showing a draft early so they can react to something concrete rather than imagine it from scratch. Clients with no existing site also tend to have no brand guidelines, so expect to build those as part of the project, not gather them beforehand.

How do I ask about budget without scaring off a local business client?

Offer two or three price ranges tied to outcomes rather than asking "what's your budget" directly. Say something like a basic 5-page site with hosting falls in one range, while a booking system or multilingual pages push it into the next, and let the client place themselves. The pricing breakdown for Handwerker websites gives concrete numbers to quote confidently during that conversation.

Keep reading

Guides

How to Sell Websites to Local Businesses in 2026: The Honest 5-Step Guide

Guides

Businesses Without Websites: How to Find, Verify and Pitch Them (2026)

Guides

Average Cost of Website Design for Small Business (2026)

Guides

Best Free Website Builder 2026: Full Comparison + Agency Use