10 Questions to Ask Before Hiring a Web Designer
Most people research web designers the same way they research everything else: they Google, they scroll portfolios, they check prices. What they rarely do is ask the right questions before signing. That's where projects go sideways.
A good web designer should be able to answer every one of these without hesitation. If they get vague, defensive, or pivot to a sales pitch instead of an actual answer, pay attention to that.
Table of Contents
1. How do you price your projects?
2. Do you specialize in any platforms?
3. Can I see examples of similar work?
4. What's included in your price?
5. Will I be able to edit my site myself?
6. How long will my project take?
7. How do revisions work?
8. Do you offer support after launch?
9. What do I need to provide?
10. Have you worked with businesses in my industry?
More Frequently Asked Questions
1. How do you price your projects?
You're not just looking for a number here. You're looking for how they think about scope. Do they charge a flat project fee? Hourly? A retainer? Each model has tradeoffs, and a designer who can explain their pricing logic clearly is one who has thought carefully about how they work.
What a good answer looks like: They explain their pricing model, what drives the cost up or down, and what's included at each level. They're not evasive about ranges.
What to watch for: Vague answers like "it depends on a lot of factors" with no further detail. That's either inexperience or a setup for scope creep.
Currently planning your squarespace website? Grab the free guide on how to plan and launch your website effortlessly with tips and tricks to guide you up to launch day!
2. Do you specialize in any platforms?
WordPress, Squarespace, Webflow, Shopify, each platform has a different learning curve, different ongoing costs, and different strengths. A designer who works in one platform exclusively isn't necessarily a problem, but they should be able to explain why they're recommending it for your specific project.
What a good answer looks like: They name the platforms they work in, explain the differences in plain language, and make a recommendation based on what your business actually needs, not just what they prefer to build.
3. Can I see examples of similar work?
Portfolio reviews matter, but asking for work similar to yours is more useful than scrolling a general gallery. A designer who has built sites for service businesses, local shops, or your specific industry will hit the ground faster and make fewer assumptions about how your audience thinks.
What a good answer looks like: They can point to two or three relevant examples and talk about the goals behind each project, not just how it looks.
What to watch for: A portfolio full of work they can't speak to in detail. Pretty screenshots with no context often mean the designer executed someone else's vision and isn't fluent in strategy.
4. What's included in your price?
This is where projects most often go off the rails. Some designers include copywriting. Some don't. Some include stock photography, logo prep, mobile testing, or SEO setup. Many don't. A detailed scope conversation before you sign protects both of you.
Ask specifically about: copywriting, image sourcing, on-page SEO setup, mobile and browser testing, revisions, and what happens if the project grows.
What a good answer looks like: A clear, written scope of what's covered and what would be billed as an add-on. If they don't have this in writing, ask for it before moving forward.
5. Will I be able to edit my site myself?
This matters more than most people realize until six months after launch, when they need to update their hours, add a team member, or swap out a photo. Some platforms make this easy. Some setups make it nearly impossible without calling your designer every time.
What a good answer looks like: Yes, with a clear explanation of how and optional training to make sure you're comfortable. A good designer wants you to feel capable of managing your own site.
A designer who makes you dependent on them for every small update isn't doing you any favors.
6. How long will my project take?
Four weeks. Eight weeks. Six months. Timelines vary widely and for legitimate reasons. What you're listening for is whether they can give you a realistic estimate with a clear explanation of what affects it.
What a good answer looks like: A timeline with milestones: discovery, design approval, development, content, revisions, launch. They should also tell you what from your side (feedback, content, approvals) keeps the project on track.
What to watch for: "It depends" with no range, or an unrealistically fast promise. A two-week turnaround for a custom ten-page site is either inexperienced or a red flag.
7. How do revisions work?
Every project involves changes. The question is whether those changes are budgeted in, and what happens when you ask for more than what's included. Some designers include unlimited revisions within reason. Others bill by the hour after a set number of rounds. Neither is wrong. You just need to know upfront.
What a good answer looks like: A defined revision policy in their contract, with clear language about what counts as a revision versus a new scope item.
8. Do you offer support after launch?
The week after a site goes live is often when questions pile up. Something looks wrong on mobile. You're not sure how to add a blog post. A plugin needs updating. Having a designer who offers post-launch support, even for a short window, makes the transition much smoother.
What a good answer looks like: A defined post-launch support window (30 days is common), and an explanation of ongoing maintenance options if you want continued help.
9. What do I need to provide?
A website project moves at the speed of the slowest collaborator. If you don't know what you're responsible for supplying, and when, the timeline slips. Logo files, brand colors, photography, written content, login credentials, and feedback turnaround are all on the client's side of the equation.
What a good answer looks like: A clear client checklist shared early in the process, and a conversation about what happens if content is delayed.
10. Have you worked with businesses in my industry?
Industry experience isn't required, but it's a legitimate thing to ask about. A designer who has built sites for restaurants, law firms, or contractors will understand your audience's expectations and your conversion goals faster than someone starting from scratch.
What a good answer looks like: Either relevant experience with context, or an honest acknowledgment that your industry is new to them alongside a clear explanation of how they'd approach learning it.
One More Thing Worth Asking
Beyond the ten questions above, pay attention to how the designer communicates during your initial conversation. Do they listen before they pitch? Do they ask about your goals or jump straight to their process? The way someone shows up before they have your business is usually how they show up during the project.
Trust your read on this. A technically skilled designer who doesn't communicate well will make your project harder than it needs to be.
The questions above are exactly what I walk through with every prospective client before a project starts.
More Frequently Asked Questions
How do I know if a web designer is legit?
Look for a real portfolio with work they can speak to in detail, a clear contract, and transparent pricing. Legitimate designers will have a defined process, references available on request, and no hesitation answering questions about how they work. If someone is evasive about scope, timeline, or what's included, that's a signal worth taking seriously.Should I hire a local web designer or does location not matter?
Location matters more for some businesses than others. If local SEO is a priority and you want someone who understands your market, a local designer has a real advantage. Working with someone in the Buffalo area, for example, means they know the competitive landscape, can meet in person, and have a stake in your local reputation. That said, a skilled remote designer can also do excellent work if communication is solid.What's a reasonable timeline for a small business website?
For a professionally built five to ten page site, four to eight weeks is a reasonable range. Projects move faster when clients provide content and feedback promptly. Rushing a website to meet an arbitrary deadline almost always creates problems that take longer to fix than the time saved at launch.What should be in a web design contract?
At minimum: scope of work, deliverables, timeline with milestones, payment schedule, revision policy, who owns the files and accounts at the end, and what happens if the project is cancelled. A designer who doesn't use a contract is a risk. A detailed contract protects both parties and is a sign of a professional operation.How much input will I have in the design?
That depends on the designer's process, and it's worth asking directly. Most professional designers run a discovery or strategy phase where they gather your goals, preferences, and brand direction before building anything. You should expect at least one round of design review before development begins, and a defined revision process after that. If a designer builds and presents without gathering any input first, that's a process worth questioning.
Meet The Author
Jamie Stott is a web designer based in Buffalo, NY, specializing in custom Squarespace and WordPress websites for small businesses. She's a Squarespace Circle Member and has helped dozens of WNY businesses build a stronger online presence.
Learn More About Jamie →