How to Hire a Web Designer: A Practical Guide for Small Business Owners in 2026

Hire a web designer by defining what the site must do, who maintains it, and your real two-year budget first. Then check live portfolio sites on your phone and run them through PageSpeed Insights. Match scope to your actual needs, and get deliverables, timeline, and ownership in writing.
Part of the complete web design guide.
On this page
- Start with what you actually need, not with a designer
- Read the portfolio like a skeptic
- Questions that separate real designers from resellers
- Red flags worth taking seriously
- What a modern build should actually include
- How to compare quotes without getting fooled
- The honest version
- FAQ
- How much should I expect to pay for a small business website in 2026?
- Can I just use a website builder like Squarespace or Wix?
- How long should a website project take?
Most small business owners hire a web designer once every five or six years, which means you’re making a high-stakes decision with almost no practice. The agency sites all look polished, the quotes range from $800 to $40,000, and nobody will tell you plainly what you’re actually buying. This guide is the checklist I’d hand a friend before they signed anything.
Start with what you actually need, not with a designer
Before you talk to anyone, write down three things: what the site must do (take bookings, sell products, generate quote requests), who maintains it after launch, and your real budget including the second year. That last part matters because hosting, domain, email, and plugin renewals don’t stop when the project ends.
If you’re a plumber in Commack who needs a five-page site with a contact form, you don’t need an agency with a strategy department. If you’re running a 400-product store with inventory syncing to a warehouse, you do. Matching the scope to the shop is the single biggest factor in whether you overpay.
Read the portfolio like a skeptic
Every designer’s portfolio looks good. That’s the point of a portfolio. So do two extra steps:
- Open the live sites on your phone. Not screenshots. The actual sites. Load them on cellular data, not wifi. If they’re slow or broken on mobile, that’s what you’ll get.
- Run them through PageSpeed Insights. Google’s own tool, free, no account needed. A designer whose portfolio sites score in the 30s on mobile is telling you something.
- Check who built it. Some portfolios are template demos or theme showcases with the logo swapped. View source and look for page builders you recognize, or ask directly what platform each site runs on.
If you want a sense of how I approach this kind of work, my own Long Island web design projects are all live and you can poke at them the same way.
Questions that separate real designers from resellers
Ask these on the first call. The answers tell you more than any proposal document.
- “What platform will you build on, and why that one for my case?” WordPress, Shopify, Webflow, and hand-coded static sites are all valid. A designer who uses one for everything regardless of the project is selling a process, not a solution.
- “Who owns the code and the accounts when we’re done?” The correct answer is you. You should own the domain, the hosting, the Google Analytics, and the repo or admin login. If they insist on holding the domain, walk.
- “What happens if I need a change in eight months?” If the answer involves a monthly retainer you can’t cancel, understand the terms before you sign.
- “Can you show me a site you built that you’ve since handed off?” This tests whether they actually let go of control.
Red flags worth taking seriously
- No written scope. A verbal agreement on a $6,000 project is how disputes start. Get deliverables, page count, revision rounds, and timeline in writing.
- Full payment up front. Standard is a deposit (often 30 to 50 percent) with the balance on delivery. Anyone demanding 100 percent before work starts is a risk.
- Guaranteed Google rankings. Nobody can guarantee a #1 position. Anyone who does is either lying or planning to rank you for a phrase nobody searches.
- Vague answers about speed and accessibility. In 2026 these aren’t extras. Core Web Vitals affect rankings, and the European Accessibility Act has pushed accessibility from “nice to have” to a real legal concern for anyone selling into the EU.
What a modern build should actually include
Whatever platform you land on, a site delivered in 2026 should ship with these basics. If a quote doesn’t mention them, ask why.
- Responsive layout tested on real devices, not just a browser resize
- HTTPS with a valid certificate (automatic on most hosts now)
- Core Web Vitals in the green on mobile, or a clear plan to get there
- Basic on-page SEO: proper titles, meta descriptions, heading structure, an XML sitemap
- Analytics you own, plus a way to see form submissions and calls
- Some form of backup and update plan
If you’re technical enough to want specifics, this is roughly what “good” looks like in the page source. A proper document head for a local business page:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Emergency Plumber in Commack, NY | Same-Day Service</title>
<meta name="description" content="Licensed plumber serving Commack and Suffolk County. Same-day emergency service. Call for a free estimate.">
<link rel="canonical" href="https://example.com/commack-plumber/">
<meta property="og:title" content="Emergency Plumber in Commack, NY">
<meta property="og:image" content="https://example.com/img/commack-van.jpg">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Plumber",
"name": "Example Plumbing",
"telephone": "+1-631-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Commack",
"addressRegion": "NY",
"postalCode": "11725"
}
}
</script>
</head>
That structured data block is what feeds Google’s local results. Plenty of cheap builds skip it entirely, which means you’re invisible in the map pack no matter how nice the homepage looks.
How to compare quotes without getting fooled
Put every quote in the same format before you decide. Line up these columns and the cheapest option often stops looking cheap:
- Total first-year cost (build + hosting + domain + any licenses)
- Total second-year cost (this is where the surprises live)
- Number of pages and revision rounds included
- Who owns what after handoff
- Timeline with a real launch date, not “4 to 6 weeks”
- What happens if the project runs long
A $2,000 site that costs $150 a month forever and locks you into their platform can cost more over three years than a $6,000 site you own outright. Do the math on paper.
The honest version
There’s no secret to hiring well. You want someone who answers questions directly, shows live work you can inspect, puts the scope in writing, and hands you the keys at the end. Everything else is noise. Take an extra week to do the vetting. It’s cheaper than a rebuild.
FAQ
How much should I expect to pay for a small business website in 2026?
For a five to eight page brochure site with a contact form, most freelancers land between $2,500 and $8,000, and agencies run higher. E-commerce and custom web apps go well beyond that. Beware anything under $1,000 that isn’t a template you build yourself.
Can I just use a website builder like Squarespace or Wix?
Yes, and for some businesses that’s the right call. If your site is simple, you’re comfortable editing it yourself, and you don’t need custom functionality, a builder is fine. The tradeoffs are less control over performance and harder migrations if you outgrow it.
How long should a website project take?
A straightforward five-page site takes two to four weeks of actual work. Six to ten weeks is common once you factor in content, photos, and your own review time. If a designer promises a custom 20-page site in three days, ask what’s being cut.


