20 Questions to Ask When Designing a Website

Every website project we take on starts the same way: with questions, not mockups. The projects that go over budget, miss deadlines, or need a redesign within a year almost always skipped this step. The projects that succeed answered the hard questions before anyone opened a design tool.

This article is our discovery process, opened up. The first sixteen are the questions to ask when designing a website for your own business, whether you build it yourself or hire help. The last four are the questions to ask a web designer or agency before you sign anything. Answer the first set honestly and ask the second set directly, and you will avoid most of the expensive mistakes we get called in to fix.

These are the website discovery questions every good agency asks first, because every later decision depends on them. If you cannot answer these three, you are not ready to talk about colors or layouts yet.

1. What is the single most important action a visitor should take?

Every website has one action that matters more than the rest: request a quote, book a consultation, buy a product, sign up, donate. Naming it forces clarity, because a site designed to do everything usually does nothing well. Once you know the primary action, every page, button, and paragraph can be judged by one standard: does this move a visitor closer to it?

A good answer is specific and singular. "Get more customers" is not an answer; "generate qualified consultation requests from mid-sized healthcare organizations" is.

2. What does success look like in numbers?

Set targets before the project starts, not after launch. That might be monthly leads, online sales, demo bookings, or newsletter signups. Numbers turn design debates into business decisions: when two layout options compete, the one more likely to hit the target wins, regardless of personal taste.

If you have an existing site, pull its current numbers first. You cannot recognize an improvement you never measured a baseline for.

3. If this is a redesign, what exactly is wrong with the current site?

"It looks dated" is a symptom, not a diagnosis. Dig into specifics: is traffic arriving but not converting, is the site slow on mobile, is it impossible to update, is the messaging aimed at the wrong audience? The more precisely you name what is failing, the less likely the new site repeats it.

Just as important: what is working? A redesign that discards the pages quietly generating your leads and rankings does more damage than no redesign at all, which is why good website redesign services start by auditing what to protect, not just what to replace.

You are not designing the website for yourself. These website design questions force the shift from "what we like" to "what our visitors need."

4. Who exactly is the website for?

Not "everyone." Define your primary audience in concrete terms: their role, their industry, what they already know, and what they are trying to accomplish when they land on your site. A site for procurement managers at manufacturing firms reads and looks nothing like a site for engaged couples choosing a wedding venue.

If you have more than one audience, rank them. The homepage can only lead with one message, and that message belongs to the audience that matters most to your business.

5. What questions do visitors arrive with?

Visitors come to your website with questions: what do you do, is this for someone like me, what does it cost, why should I trust you, what happens next. List them, because your pages exist to answer them. The fastest way to build this list is to ask whoever talks to customers directly, since your sales calls and support inbox already contain it.

6. Where will visitors come from?

A site fed by search traffic needs deep, well-structured content pages. A site fed by paid ads needs focused landing pages. A site fed by referrals and word of mouth needs a homepage that instantly confirms credibility. Knowing your traffic sources before designing means the site is built for how people will actually arrive, not for an imaginary visitor who starts at the homepage and reads everything.

Content decisions sink more website projects than design decisions. Answer these before the design phase and your project timeline becomes dramatically more realistic.

7. What pages do you actually need?

List every page before anyone designs anything. Start from your audiences and their questions, then map the pages that answer them: services, industries, case studies, about, pricing, contact. We keep a full website design requirements checklist for this stage, because the page list defines the scope, and the scope defines the budget and timeline.

Be honest about what you will maintain. Ten strong pages beat forty neglected ones.

8. Who is writing the content, and when?

The single most common cause of website project delays is content arriving late, because "we will write it ourselves" collides with everyone's day jobs. Decide upfront: are you writing the copy, is the agency writing it, or is it a mix? Then put dates on it. Design without real content is guesswork, and pages designed around lorem ipsum always need rework once the actual words arrive.

9. What existing assets can you reuse?

Gather your logo files, brand guidelines, photography, testimonials, case studies, and any content worth keeping before the project starts. Also gather your logins: hosting, domain registrar, analytics, and your current CMS. Projects stall for weeks over a missing domain password more often than anyone would like to admit.

Now, and only now, the design questions. Notice how much is already decided before taste enters the conversation.

10. What should the site communicate before anyone reads a word?

Visitors form a first impression of your website in a fraction of a second, and that impression comes almost entirely from design. So decide what it should say: established or scrappy, premium or affordable, warm or precise. Three to five adjectives, agreed on by every decision-maker, will settle a hundred later debates about fonts and colors.

11. Which websites do you love, and which do you hate?

Collect five to ten examples of each, and write down why. The "why" is the valuable part: it turns vague taste into usable direction. Competitor sites belong on the list too, not to copy, but to define what you need to do differently to stand out in the exact company visitors will compare you against.

12. Which features are must-haves, and which are nice-to-haves?

Booking systems, calculators, member areas, live chat, multilingual support: every feature adds cost, build time, and maintenance. Sort every request into two lists: must have at launch, and nice to have later. Most successful projects launch lean and add features once real visitor behavior shows what is actually needed. For the design fundamentals that apply to every site regardless of features, our data-backed web design tips guide covers what moves results.

The unglamorous questions that determine whether your website is still serving you well in three years.

13. What platform should the site be built on?

WordPress, Webflow, Shopify, or something custom: the right answer depends on who updates the site, what it needs to do, and how it will grow. The wrong answer is whatever platform a designer happens to prefer when it does not fit your needs. Ask how easily your team can edit content, what ongoing costs the platform carries, and how hard it would be to leave.

14. What systems does the site need to connect to?

CRM, email marketing, booking tools, payment processing, inventory, analytics: list every integration before the project is scoped. Integrations discovered mid-project are the classic source of budget overruns, because retrofitting a connection is always more expensive than planning for it.

15. What is your realistic budget?

Budget shapes every decision above, so it cannot stay vague. Professional websites range from a few thousand dollars to six figures depending on scope, and knowing where you sit narrows your options fast. Our full breakdown of website development cost covers what different project types cost and what drives the price up or down. Whatever the number, hold back part of it for content, photography, and post-launch fixes, because the build is never the whole cost.

16. Who will own and update the site after launch?

A website is not finished at launch; it is started. Decide who on your team updates content, who handles maintenance and security, and what happens when something breaks. If the answer is "nobody internally," that is fine, but then a maintenance arrangement belongs in the project scope from day one.

The questions above are for you. These four are the questions to ask a web designer or agency before you commit, and the answers reveal more than any portfolio.

17. Have you built sites for businesses like mine, and what happened after launch?

Look past how the portfolio looks and ask what it did. Strong designers can point to outcomes: more leads, better rankings, higher conversion rates. Ask for an example from your industry or a similar business model, and if possible, talk to a past client about what working together was actually like.

18. What does your process look like, and who will I actually work with?

A professional will walk you through a documented process: discovery, structure, design, build, testing, launch. Ask who your point of contact is, how often you will communicate, how feedback and revisions work, and who is really doing the work, especially if parts of the project are subcontracted. Vague answers here predict a chaotic project.

19. What exactly is included, and what costs extra?

Get specific: is copywriting included, is SEO setup included, how many revision rounds, what does support cost after launch? The cheapest quote is often the least complete one, and the gaps surface as invoices later. A detailed proposal that spells out inclusions is worth more than a low number on a one-line estimate.

20. Who owns the website, domain, and accounts when we are done?

The answer should be simple: you do. Confirm in writing that you will own or have full admin access to the domain, hosting, CMS, analytics, and every account created for the project. Businesses that skip this question sometimes discover their own website is being held hostage the day they try to switch providers.

Good websites start with good questions

Design skill matters, but no amount of it can rescue a project that never defined its goal, audience, or scope. Work through the sixteen questions above before your project starts, and use the last four to choose who you build with.

And if you want a partner who asks these questions before showing you a single mockup, that is how we run the discovery process behind our responsive web design services. Get in touch and bring your answers, or let's find them together.