Questions to ask before you hire a web designer
The questions that separate a designer who will deliver from one who will not, covering ownership, process, cost, and what happens after launch.
Before hiring a web designer, ask who will own the site and its accounts, what the total cost includes and excludes, who writes the content, how long it will take, what happens if it runs late, whether they measure results, and what support exists after launch. The answers tell you far more than a portfolio does, because a portfolio shows you the best work under ideal conditions, while these questions reveal how someone actually operates when a project gets difficult.
Most people choosing a web designer look at the portfolio and the price, decide on those two things, and are surprised later by everything the price did not cover. The portfolio matters, but it is the easy part. The questions below are the ones that prevent the expensive surprises, and a good designer will welcome all of them, because clarity protects them as much as it protects you.
Who owns the finished website?
This is the first question and the one most people never think to ask. When the project ends, do you own the site, the domain, the hosting account, and the code, or does the designer keep them and effectively rent the site back to you?
Some arrangements leave you unable to move, unable to edit, and unable to get your own site if the relationship ends. That is not always wrong, some platforms work that way by design, but you must know it going in. Ask specifically: if we part ways, do I walk away with the domain, the content, and a working site, or do I start again? Get the answer before you sign, not after.
What does the price actually include?
A single number means very little until you know what sits inside it. Ask what the quote covers and, more usefully, what it does not.
The common exclusions that become invoices later: copywriting, photography, stock imagery licences, ongoing hosting, domain registration, revisions beyond a set number, SEO setup, and any maintenance after launch. A quote that looks cheap next to another is often cheap because it excludes things the other one included. Ask for the exclusions in writing, because that is where the real cost of the project hides.
Who writes the words?
Most people assume the designer writes the content. Most designers assume the client provides it. This single misunderstanding delays more projects than any technical problem.
Ask directly whether copywriting is included, and if it is not, who is expected to produce it and by when. Content is usually the thing that holds a project up, because design can be finished in days while the words sit unwritten for weeks. Settle this at the start and you remove the most common cause of a launch slipping.
How long will it take, and what happens if it runs late?
Get a realistic timeline, not a hopeful one, and ask what the timeline depends on. Most delays are caused by content arriving late or feedback being slow, so a good designer will tell you what they need from you and when.
Then ask the harder question: what happens if it overruns? Is there a penalty, a revised schedule, a point at which the scope is frozen? You are not trying to catch anyone out. You are finding out whether they have run projects before and know where they go wrong.
How many rounds of revisions are included?
Revisions are where budgets quietly overflow. Ask how many rounds are included and what counts as a round, because "unlimited revisions" is rarely as generous as it sounds and a fixed number is only fair if you know what fills it.
The useful follow-up is what happens when you have used them up. A clear answer, an hourly rate, a new quote, a defined change process, is a sign of someone who has done this before. A vague answer is a sign of a difficult conversation waiting to happen.
Do you measure whether it works?
A website is not a piece of art, it is a tool that is supposed to produce enquiries, bookings, or sales. Ask whether analytics will be set up, whether conversion points will be tracked, and whether the designer takes any interest in how the site performs after it goes live.
Many designers hand over a beautiful site and never look at whether it does anything. The ones who ask about your goals at the start, and set up a way to measure them, are the ones treating your site as a business tool rather than a deliverable. That difference tends to show up in the results.
What happens after launch?
The launch is the middle of the story, not the end. Ask what support exists afterward. Who fixes it if something breaks, how updates are handled, whether there is a maintenance option, and what it costs.
A site with no plan for maintenance is a site that slowly decays: plugins go out of date, security holes open, small breakages accumulate until a minor fix becomes a rebuild. You do not necessarily need a full retainer, but you need to know what the options are before you are stuck with an emergency and no one to call.
The questions behind the questions
Notice what these have in common. None of them is about design taste, and all of them are about how someone works. That is deliberate. Taste you can judge from the portfolio. Reliability, honesty about cost, and what happens when things go wrong, you can only judge by asking. The designer who answers all of these clearly and without defensiveness is usually the one worth hiring, almost regardless of whose portfolio you liked most.
See also: How to write a website brief, How to review a web design proposal, Agency vs freelancer vs builder.