How to choose a web designer without getting burned.

Hiring a web designer is one of the highest-leverage decisions a local business owner makes, and one of the least discussed. A bad hire costs you a year. A good one gets you booked. The difference between them is rarely talent. It is almost always process, clarity, and incentives, and you can assess all three in a 30-minute call if you know what to listen for.

This guide is written for owners of salons, clinics, gyms, studios, and other local service businesses who are about to spend somewhere between $300 and $10,000 on a website. The advice is the same whether you are hiring a freelancer on Upwork, a local agency, or a studio like ours. The goal is to stop you from paying for something that looks fine in screenshots and fails in practice.

Why most local businesses hire the wrong designer.

The pattern is almost always the same. Owner wants a new site. Owner collects three quotes. Owner picks the middle quote because it is the safe choice. Six weeks later, the site launches, nothing happens, and the owner quietly goes back to doing what they did before.

The quote was not the problem. The problem was that the owner was choosing between three deliverables and never asked what the designer's process looked like. A website is the output. A process is what you actually pay for.

Red flags to spot in the first call.

Most of the signal is in the first 30 minutes. These are the things that should make you pause before signing anything:

• They show you templates instead of asking questions about your business.
• They cannot name a single local business they have built for in the last 12 months.
• They quote a price before they have seen your current site, your Google Business Profile, or your booking flow.
• They promise a specific ranking position on Google ("we will get you to #1").
• They send you a PDF proposal written in the third person within 10 minutes of the call.
• They will not tell you, in writing, who owns the site after it launches.
• They describe their package as "custom" but every screenshot in their portfolio looks identical.

Any one of these is a yellow flag. Two or more and the call is over. The amount of money at stake is not the issue. The year you will spend unwinding a bad build is.

What a good portfolio actually shows.

Portfolios are scannable because they are meant to be. The work of reading one properly takes 20 minutes, and most people give it 20 seconds. Here is what you are actually looking for when you open a designer's portfolio:

1. Live sites, not mockups. Click through to the real URL. A mockup tells you the designer can arrange rectangles. A live site tells you they can ship.
2. Sites in your industry, or one close to it. A designer who has built for five salons understands the booking flow, the review funnel, and the way customers compare stylists. A designer who has only built for SaaS startups is going to treat your salon like a SaaS startup.
3. Sites older than a year. Anyone can make a site look sharp on launch day. Look for work that has been in the wild for 12 or 24 months and still holds up. That is how you know the designer builds for longevity, not for the launch screenshot.
4. Working forms and CTAs. Try to book, fill the contact form, click the phone number on mobile. If any of these feel broken on their reference sites, yours will feel broken too.
5. Outcome language on case studies. "Increased bookings 40% in three months" is a different claim than "beautiful redesign for a salon in Tampa." The first one requires the designer to have cared about the business, not just the pixels.

The seven questions to ask before you pay.

Pretty much every bad engagement can be prevented by asking these seven questions out loud before any money changes hands. Write them down and read them off a list. The designer's reaction to the list is itself useful data.

1. "What exactly is included in the price, and what is extra?" A clear answer names the pages, the revisions, the content handling, and the launch tasks. A vague answer is a future invoice.
2. "Who writes the copy?" Copy is half the project. If the designer does not write it and you do not either, nobody is writing it, and the site will launch with placeholder text that never gets replaced.
3. "What happens after launch?" Hosting, SSL, updates, small content changes, plugin updates, backups. Get a line-by-line breakdown. "Support is included" is not an answer.
4. "Who owns the domain, the hosting account, and the site files?" You. The correct answer is always you. If the designer wants to keep the domain in their account, walk.
5. "Can I see a test environment before we go live?" Staging is standard. A designer who does not use a staging environment is shipping directly to production, which is how sites launch broken.
6. "What is your revision policy?" Two rounds of revisions is standard. Unlimited revisions is a red flag, because it usually means the designer has no process and will resent you by round six.
7. "What does the contract say about cancellation?" Before you pay, read the exit clause. If there is no exit clause, there is no contract worth signing.

What a real proposal looks like.

A proposal is not a price list. A good one is a short document that proves the designer understood your business and has a specific plan to move it forward. Here is what should be in it:

• A one-paragraph restatement of your business, your customers, and the problem the site is solving. If this paragraph is wrong, nothing else in the document is worth reading.
• A page-by-page breakdown with word counts or content slots. "Home, About, Services, Contact" is not a breakdown. "Home (4 sections, 600 words, 2 CTAs, embedded booking widget)" is.
• A timeline with milestones, not a single "4-6 weeks" line. Kickoff, design concept, revision rounds, build, review, launch, post-launch. Each with a date.
• A total investment figure broken into one-time and ongoing costs. Hosting, domain, third-party tools, support, anything you will pay past launch.
• A short section on what is explicitly out of scope. This is the single most valuable part of any proposal, because it prevents the two worst conversations in the business: "I thought that was included" and "Oh, that is extra."

How to price the project fairly.

There is no correct price, but there are ranges that are defensible. A real one-person freelancer in a Western market, building a clean 5- to 7-page site for a local business, is typically in the $1,500 to $4,000 range for a one-off, or $50 to $150 per month on a subscription model. Below that, the designer is either new, offshore, or cutting corners somewhere. Above that, you are paying for brand, office overhead, or a strategy layer you may not need.

What matters more than the number is the structure. One-time builds save money upfront and cost you later in hosting, updates, and emergency fixes. Subscription builds cost a little every month and include the boring but necessary work that keeps a site alive. Pick the model that matches how much of this you want to think about after launch. Most local owners want to think about it never, and that is a reasonable reason to pay monthly.

The contract clauses most people forget.

Designers ship the contract and you sign it. That is normal. What is not normal is signing without reading the last third of the document, which is where the interesting clauses live. Before you sign, make sure these four are in your copy:

• Ownership transfer. On final payment, all files, code, designs, and accounts become yours. In writing.
• Kill fee. If you cancel mid-project, what do you pay. A 50% kill fee on work completed is standard. 100% of the contract is not.
• Timeline liability. What happens if the designer misses the deadline by more than two weeks. Refund of the month, free month of support, whatever it is, it needs to be defined.
• Termination for convenience. Either party can end the engagement with a fixed notice period, typically 30 days. A contract with no exit clause is a contract that benefits only the designer.

None of these are unreasonable to ask for, and any designer who pushes back on all four is telling you something about how the engagement will go.

A quick word on "free mockups" and "free audits".

A free mockup from a designer who already has a body of work is a marketing expense for them. They are showing you what a relationship with them would feel like. This is fine, and a good sign. What is not fine is a free audit from a designer who uses it to scare you about your current site ("your SEO is broken, your security is broken, you are losing customers") so they can sell you the fix. If the audit is longer than the website they are proposing, it is a sales document, not an audit.

The correct use of a free mockup is as a compatibility test. Does this designer understand the vibe of your business. Does the mockup look like something your customer would trust. If yes, proceed. If not, thank them and move on, no harm done.

The one shortcut that actually works.

If none of the above is useful to you, here is the single most effective shortcut: ask a local business you admire who built their site. Not who designed it, who built and maintains it today. If they hesitate, the answer is "nobody, really," and the site is quietly rotting. If they name someone and recommend them, that recommendation is worth more than any portfolio you will ever scroll through. Local services are a referral economy. Hiring a designer is no different.