A polished portfolio can tell you whether a designer makes attractive websites. It cannot tell you whether the project will stay on budget, who will own the finished site, or what happens when you need help six months after launch.
These projects often go wrong through assumptions: writing was included, photos were ready, monthly fees were understood, and the business could access its domain.
The right questions expose those assumptions before a contract or deposit. You do not need to understand code. You need to know what is being built, who is responsible, and what happens after launch.
Here are 12 questions to ask a web designer before hiring them, along with what a useful answer should cover.
1. What Business Result Should This Website Produce?
Start with the reason for the project, not colors or page count. A useful website should help the right people call, request an estimate, schedule, visit, or buy.
A good designer should ask about your customers, service area, and sales process. They should explain how the proposed pages and calls to action support those goals.
Be cautious if the conversation stays entirely focused on appearance. Design matters, but a beautiful site with no clear next step is still hard for customers to use. Before the project begins, you and the designer should be able to finish this sentence: “The website succeeds when the right visitor can easily ____.”
That shared goal makes later decisions easier. If the goal is qualified quote requests, the contact experience deserves more attention than decorative animation.
2. Who Will Actually Do the Work?
The person selling the project may not design, write, or build it. Teams and subcontractors can do excellent work, but you need to know who is responsible.
Ask whether the work is completed in-house, outsourced, or divided among specialists. Find out who manages the project and answers questions when something stalls.
You should also know how communication works, how often you will receive updates, and who can approve changes.
This question is especially helpful when comparing a solo professional with a larger company. My guide to choosing a freelance web designer versus an agency explains the practical tradeoffs. The important part is not the team’s size. It is whether responsibility is clear.
3. What Exactly Is Included in the Price?
“A five-page website” can mean very different things. One quote may include strategy, copy editing, mobile layouts, forms, analytics, basic search setup, and launch support. Another may include only visual design and page assembly.
Ask for a written scope that names the deliverables. It should address items such as:
- Page planning and navigation
- Design and development
- Written content and editing
- Photo preparation or stock images
- Contact forms and integrations
- Mobile and browser testing
- Basic on-page SEO
- Analytics and Search Console setup
- Hosting, domain, and launch work
- Training and post-launch support
Also ask what is excluded. Clear exclusions prevent surprises. A vague promise that “everything is included” is less useful than a precise list.
Compare proposals by deliverables and responsibilities, not just the total. If you need context for the numbers, read what a small-business website costs and the more local Kentucky website cost guide.
4. What Do You Need From Me, and When?
Website timelines often depend more on missing content and delayed decisions than on coding. Ask the designer to list what your business must provide and the dates those items are needed.
Common client responsibilities include approving the sitemap, supplying service details, choosing photos, providing account access, and reviewing drafts. If you do not have finished copy or professional photography, say so early so it can be included in the plan.
A dependable answer should explain how feedback is collected and who gives final approval. Choose one decision-maker, even if that person gathers comments from the team.
This conversation reveals whether the proposed schedule is based on real dependencies or just an optimistic launch date.
5. What Is Your Process and Realistic Timeline?
Ask the designer to walk through the project from kickoff to launch. A clear process might include discovery, content planning, an initial design direction, page development, review, testing, and deployment. The names may differ, but there should be an understandable sequence.
Then ask what could change the timeline. Delayed content, approvals, new features, integrations, and major revisions all affect delivery. A useful schedule identifies milestones for both sides.
Ask whether you will see the site in stages or only near the end. Early checkpoints make it easier to correct the direction before every page is built. A simple informational site and a custom booking system should not follow the same schedule.
6. How Many Revisions Are Included?
“Unlimited revisions” sounds reassuring, but it can hide an undefined process. Ask how a revision round works, how many are included, and what counts as a change in scope.
Adjusting a headline is different from adding online ordering after the site has been designed. The contract should explain how out-of-scope work is approved before extra charges appear.
Find out when you will review work and how feedback should be submitted. One organized list per round is more efficient than scattered texts and emails.
The goal is not to eliminate changes. It is to create a fair method for handling them without turning every request into a disagreement.
7. Is the Site Custom, Template-Based, or Built on a Platform?
These approaches can all be appropriate. What matters is understanding what you are buying and why it fits your needs.
A custom static site may be lightweight but require a developer for structural updates. A content management system lets staff publish changes but adds maintenance responsibilities. A hosted builder may simplify editing while limiting portability or customization.
Ask what platform they plan to use, what you can edit, and what happens if you move to another provider. If a template is involved, ask what will be customized and whether licenses renew.
The answer should connect the technical choice to your business. You do not need the newest tool. You need an approach that supports the site’s purpose without creating unnecessary complexity.
8. How Will You Handle Mobile Use, Accessibility, and Performance?
“Responsive” should mean more than squeezing a desktop layout onto a phone. Ask how the designer tests navigation, forms, tap targets, images, and readable text across screen sizes and common browsers.
Accessibility should be considered during planning, design, development, and testing. The W3C’s evaluation guidance says it should be integrated from the beginning. Ask about keyboard navigation, headings, form labels, color contrast, alternative text, and error messages. An automated scan alone does not prove complete accessibility.
Performance deserves a concrete answer too. Google’s Web Vitals guidance identifies Core Web Vitals as metrics that help measure the experience a site delivers. Ask how images, fonts, scripts, and third-party embeds will be managed, and how performance will be tested before launch.
Look for a testing process, not a blanket promise that the site will be “fast and compliant.”
9. What SEO Work Is Included?
SEO can mean anything from installing a plugin to months of research and content work. Ask the designer to define exactly what the proposal includes.
For a small business site, a reasonable build may cover crawlable navigation, descriptive page titles, meta descriptions, heading structure, image text alternatives, redirects, a sitemap, local business information, and connections to Search Console. Keyword research, location strategy, ongoing articles, link building, and Google Business Profile management may be separate services.
Ask how the designer handles changed URLs and decides which search phrases belong on which pages. Be wary of guaranteed number-one rankings. Search results depend on factors outside any designer’s control.
A strong answer separates technical foundations from ongoing marketing and explains what your business must continue doing after launch.
10. Who Owns and Controls Every Account?
Your business should know where the domain is registered and have access to the accounts that keep the website running. Ask who will control the domain, hosting, website platform, source files, written content, images, analytics, Search Console, and business email settings.
Whenever practical, core accounts should be in the business owner’s name with the designer added as a user. Google explains that a verified Search Console owner has the highest permission, while its permissions guidance shows how owners manage other users.
Ask what the contract says about ownership after final payment and whether themes, fonts, photos, or software carry separate licenses. Request a handoff document listing accounts and renewal dates. Passwords should be shared securely.
If the answer is “we handle all of that,” follow with: “How do I regain control if we stop working together?”
11. What Recurring Costs Should I Expect?
The project price is only part of the total cost. Ask for every expected renewal and who pays it.
Possible recurring items include the domain registration, hosting, platform subscription, premium plugins, form tools, email delivery, stock media licenses, maintenance, backups, security monitoring, analytics tools, and ongoing content or SEO work.
Ask which charges are required, which are optional, and whether pricing is controlled by the designer or a third party. Find out what happens if you cancel a maintenance plan. Does the website stay online? Do you retain access? Which updates become your responsibility?
Outside vendors can change prices, but the designer can identify current services, billing cycles, renewal owners, and the consequences of cancellation. That lets you compare the real long-term commitment.
12. What Happens After Launch or If We Part Ways?
Launching is a milestone, not the end. Ask what support is included, how later requests are billed, and who monitors forms, updates software, and restores backups.
If you want to make routine edits yourself, ask what training and documentation you will receive. If you prefer to send changes to the designer, ask about response times, minimum charges, and maintenance options.
Then discuss an orderly exit. Will you receive source files, content exports, account access, and instructions for moving the site? Is there a transfer fee? How much notice is required?
A professional should be comfortable explaining the handoff before you hire them. Clear exit terms protect both sides and are a better sign of confidence than making departure difficult.
Compare the Answers, Not Just the Sales Pitch
After each conversation, review the answers while they are fresh. You are looking for clarity and fit, not a perfect script.
Give more weight to a designer who:
- Connects recommendations to your customers and goals
- Defines the scope, exclusions, responsibilities, and revision process
- Explains technology in plain language
- Gives you appropriate ownership and account access
- Discusses accessibility, performance, SEO, and testing with specifics
- Lists recurring costs and post-launch expectations
- Puts important promises in writing
Pay attention to how it feels to ask questions. A website project requires decisions, feedback, and occasional problem-solving. If basic questions produce vague or defensive responses during the sales process, communication is unlikely to improve after the deposit.
Hire With Fewer Assumptions
The best questions to ask a web designer before hiring are the ones that reveal how the project will actually work. A portfolio shows the finished surface. These conversations uncover the process, responsibilities, ownership, and long-term costs underneath it.
You do not need every provider to use the same tools or process. You need answers you understand, terms that match your business, and a written scope that reflects the conversation.
If you are planning a website for a small business in Grayson, Breckinridge, Meade, Bullitt, Hardin, Larue, or Jefferson County, I build straightforward custom websites and explain the decisions without mystery tech talk. Tell me what you need and request a quote.