Here is a pattern we see constantly. A business owner hires a web designer. The portfolio looked great. The proposal sounded professional. The sales call went well.
Six weeks later, the site launches late, loads in five seconds, and the owner cannot log in to change a phone number without emailing the designer and waiting three days.
This is not bad luck. It is the predictable result of hiring on gut feeling instead of measurable criteria.
The problem is not a shortage of web designers -- there are thousands. The problem is a shortage of objective ways to evaluate them. Most advice tells you to "ask about their process" and "check their portfolio." Fine, but that gives you no baseline for judging the answers. How fast should their sites load? What should a contract include? What performance numbers are acceptable? What should you actually own when the project is over?
This guide gives you a scored evaluation framework you can apply to any designer or agency. You will learn the specific performance benchmarks to demand, concrete red flags to watch for before signing anything, what fair pricing looks like at each tier, and what a complete post-launch handoff includes. If you have already decided you need professional help -- maybe after reading our breakdown of DIY websites vs. professional web design -- this is how you choose the right person.
Why Most "How to Choose a Web Designer" Advice Falls Short
Search for how to choose a web designer for small business and you will find dozens of articles saying the same things: ask about their process, look at their portfolio, check references, make sure they are responsive. That advice is not wrong. It is just incomplete.
None of these tips give you a standard to measure against. "Ask about their process" is useful only if you know what a good process looks like. "Check their portfolio" helps only if you know how to evaluate those sites beyond whether they look nice.
There is also a bias problem. Many top-ranking articles on this topic are written by designers who recommend the exact platform they build on. Squarespace designers recommend Squarespace. WordPress shops recommend WordPress. The advice reads as objective, but the conclusion was predetermined. When someone tells you which platform to use before asking what your business needs -- that is a sales pitch dressed as guidance.
Then there is the gut-feeling trap. Most hiring decisions default to "they seemed knowledgeable and their portfolio looked nice." That is a terrible proxy for whether the finished site will load fast enough to rank on Google, convert visitors into customers, or let you update your own content six months from now.
The rest of this article replaces that guesswork with specific criteria, measurable benchmarks, and a scoring system you can use to compare any two designers side by side.
What Are Red Flags When Hiring a Web Designer?
Red flags when hiring a web designer include vague or verbal-only contracts, inability to share performance data for past work, ownership clauses that keep you locked into the designer's hosting, and a discovery process that skips asking about your business goals. Any designer who cannot show you a Lighthouse score for a site they built, or who cannot explain who owns the domain and code after launch, should raise serious concerns.
Here is what to watch for, organized by category.
Contract Red Flags
- • No written scope of work. If the deliverables, timeline, and revision policy are not documented before you sign, expect disagreements later. "We'll figure it out as we go" is not a process -- it is a recipe for scope creep on both sides.
- • Ownership clauses that favor the designer. Some contracts state the designer retains ownership of the code, design files, or both. This means you are licensing your own website. Read the intellectual property section carefully -- everything should transfer to you upon final payment.
- • Auto-renewing hosting lock-in. If the only way to host your site is through the designer's own hosting plan, and canceling means losing access to your site, you are locked in. Your hosting account should be in your name, or transferable at any time.
- • Vague revision policies. "Includes revisions" without a number is meaningless. How many rounds? What counts as a revision versus a change in scope? Get this in writing.
Process Red Flags
- • No discovery phase. A designer who starts showing you mockups before asking about your business goals, target customers, and competitors is designing blind. Strategy comes before aesthetics.
- • No mention of SEO or performance. If search visibility and page speed never come up during the sales process, they will not be priorities during the build. Ask directly: what Lighthouse scores do your sites typically achieve?
- • Cannot explain the platform choice. "I build on WordPress because that is what I know" is honest, but it is not strategic. The platform should match your needs -- content update frequency, integrations, performance expectations -- not the designer's comfort zone.
Portfolio Red Flags
- • Portfolio sites are slow. Open two or three of their portfolio sites on your phone. If they take more than three seconds to load, that tells you more about the designer's technical standards than any sales call. Run a free Lighthouse test -- anything scoring below 90 on Performance falls in Google's "Needs Improvement" range, and scores below 50 indicate serious problems.
- • Every site looks the same. If the portfolio is clearly one template reskinned five times, you are buying a template application, not a custom design. That is fine if you know it and the price reflects it. It is a problem if you are paying custom prices.
- • No sites similar to your business type. This is less about industry expertise and more about whether they have solved problems like yours -- lead generation, appointment booking, local SEO, e-commerce.
Communication Red Flags
- • Slow responses during the sales process. If they take a week to reply when they are trying to win your business, expect worse once they have your deposit.
- • No project management structure. No shared timeline, no task tracker, no regular check-ins. You should not have to chase your designer for status updates.
If you are seeing several of these patterns, check whether your current site has problems a new designer should fix -- or whether you are already showing signs you need a new website entirely.
How Much Should I Pay for a Web Designer for a Small Business?
A small business website typically costs between $1,500 and $15,000 depending on scope, platform, and provider type. The $1,500 end of that range gets you template-based work with minimal customization -- not custom design. True custom work from an experienced designer starts closer to $3,000. Above $10,000 is appropriate for complex functionality like e-commerce, booking systems, or multi-language support.
Those ranges are useless without context, though. Here is what to expect at each tier.
Under $1,500: Template Application
At this price, you are getting a pre-built theme customized with your logo, colors, and content. Expect limited design revisions (one to two rounds), no performance optimization, no copywriting, and no ongoing support. The designer may use a page builder like Elementor on WordPress or customize a Squarespace template.
This tier makes sense if you need a basic web presence quickly, your content is already written, and you do not depend on organic search traffic for leads.
$2,500 to $6,000: Custom Design with Strategy
This is where you should start expecting real deliverables: a discovery process that examines your goals and audience, custom design (not a modified template), professional copywriting or copy guidance, performance optimization targeting Lighthouse scores above 90, a CMS so you can update content yourself, mobile-responsive design tested across devices, and basic SEO setup.
At Designly, our fixed-price projects start at $2,500 and include all of the above plus a free Skora audit, WCAG 2.1 AA accessibility compliance, and full ownership of all files and code. We mention this not as a pitch but as a concrete example of what transparent pricing at this tier looks like -- so you have a benchmark when evaluating other proposals.
$6,000 to $15,000+: Complex Functionality
This tier is appropriate when the project involves e-commerce with product catalogs and payment processing, custom booking or scheduling integrations, membership areas, multi-language support, complex third-party API integrations, or large content sites with hundreds of pages.
If a designer quotes $10,000+ for a five-page informational site with no special functionality, ask why. The scope does not justify that price.
Fixed vs. Hourly Pricing
Hourly billing with no cap transfers risk from the designer to you. If the project runs over schedule -- and most do -- you pay more. Fixed pricing aligns incentives: the designer scopes the work upfront, quotes a price, and delivers within it. If they underestimate, that is their problem.
Look for fixed pricing with a clearly defined scope, a stated number of revision rounds, and a written list of what is and is not included.
What "Cheap" Actually Costs
A $500 website that scores 40 on Lighthouse, ranks on page four of Google, and needs replacing in 18 months costs more than a $3,000 site that performs well for five years. Factor in lost leads during months of poor performance, and the "savings" disappear fast. A free website audit can show you exactly where a cheap build cuts corners.
Should I Hire a Freelancer or an Agency for Web Design?
For most small businesses, a small agency or a freelancer with a defined process produces equivalent results. What matters more than the label is whether they have a repeatable system, can show performance data for past work, and offer clear ownership terms. Freelancers are often more affordable and flexible; agencies typically offer more continuity and broader skill coverage.
When a Freelancer Makes Sense
Freelancers typically charge less because they have lower overhead. A senior freelancer with 8-10 years of experience often delivers better work than a junior team at a mid-size agency -- you are paying for their expertise directly rather than funding an office and support staff.
The risks are real, though. A solo freelancer is a single point of failure. If they get sick, take on too many projects, or disappear mid-build, you have no backup. Freelancers also tend to specialize -- a strong designer may not handle SEO, copywriting, or accessibility well. Ask what they handle themselves versus what they outsource.
When a Small Agency Makes Sense
A small agency (two to ten people) gives you team coverage. If one person is unavailable, someone else can step in. Agencies are also more likely to have defined processes -- project management tools, regular check-ins, documented timelines -- because they have to coordinate across team members.
The trade-off is cost. Agencies carry overhead that freelancers do not, and that shows up in the quote. For a simple five-page small business website, an agency will typically charge more than a comparable freelancer for equivalent work -- sometimes significantly more.
When a Large Agency Does Not Make Sense
For most small businesses with budgets under $15,000, a large agency is rarely the right fit. You will likely be their smallest client. Your project gets staffed by junior team members. Your timeline flexes around their larger accounts. And the budget mismatch means you get a fraction of the attention their bigger clients receive.
The Decision Comes Down to Three Questions
- Do you need ongoing support after launch? If yes, an agency with a maintenance plan is easier to work with long-term than a freelancer who may not offer ongoing services.
- Does your project require multiple disciplines at once? Strategy, copywriting, design, development, SEO -- if you need all of these from one provider, a small agency is better equipped.
- Is your budget under $3,000? A senior freelancer will often deliver more value at this price point than an agency, where overhead eats into what goes toward the actual work.
The Evaluation Framework: How to Score and Compare Web Designers
This is the part most guides skip. Here is a structured scoring system you can apply to every designer or agency on your shortlist. Rate each candidate across five dimensions on a 0-1-2 scale:
- • 0 = Not addressed at all
- • 1 = Partially addressed or vague
- • 2 = Clearly addressed with specifics
Total possible score: 10. Any designer scoring below 6 should give you pause.
Dimension 1: Discovery Process Quality
Does the designer ask about your business before showing you designs? A strong discovery process covers your target customers, business goals, competitors, and how you define success. If they skip straight to "what colors do you like?" -- that is a 0.
Score 2 if: They have a structured intake form or discovery call covering business goals, target audience, competitors, and success metrics before any design work begins.
Score 1 if: They ask some business questions but have no formal process.
Score 0 if: They jump to design concepts or platform recommendations before understanding your business.
Dimension 2: Portfolio Performance
Do not just look at the portfolio -- test it. Open two or three of their sites on your phone. Then run them through Google's PageSpeed Insights. You are looking at four scores: Performance, Accessibility, Best Practices, and SEO.
Score 2 if: Portfolio sites consistently score 90+ across all four Lighthouse categories, load in under 3 seconds on mobile, and pass Core Web Vitals.
Score 1 if: Scores are mixed -- some above 80, some below. Inconsistent quality across their portfolio.
Score 0 if: Sites score below 50 on Performance (Google's official "Poor" threshold), take more than 4 seconds to load, or fail Core Web Vitals.
Lighthouse is Google's open-source tool for measuring website quality. The four categories each run from 0 to 100: 90-100 is Good (green), 50-89 is Needs Improvement (orange), and 0-49 is Poor (red). Any designer serious about technical quality should know these numbers for sites they have built. If you have already audited your own site using our small business website audit checklist, you know what these scores mean.
Dimension 3: Ownership and Contract Terms
Who owns what after the project is over? This covers four things: the domain name, the hosting account, the code, and the design files. All four should transfer to you.
Score 2 if: The contract explicitly states all assets transfer to the client upon final payment, and the domain and hosting are registered in the client's name.
Score 1 if: Some assets transfer, but hosting or domain is controlled by the designer.
Score 0 if: Ownership is not addressed in the contract, or the designer retains rights to code and design files.
Dimension 4: Pricing Transparency
Can you understand exactly what you are paying for before you sign?
Score 2 if: The quote is fixed-price with a detailed scope, defined revision rounds, and a clear list of inclusions and exclusions.
Score 1 if: The estimate is vague on scope, or hourly with a rough estimate and no cap.
Score 0 if: No written estimate, "we'll figure it out as we go," or hidden fees discovered mid-project.
Dimension 5: Post-Launch Support
What happens after the site goes live?
Score 2 if: The proposal includes a defined handoff process (credentials, files, training), a launch-day checklist, and an optional ongoing support plan with clear terms.
Score 1 if: Some post-launch support is mentioned but not defined.
Score 0 if: The engagement ends at launch with no handoff documentation, training, or support options.
Using the Scores
Get quotes from two to four designers. Score each one across these five dimensions. The numbers will not make the decision for you, but they surface differences that are often invisible during a sales call.
What Questions Should I Ask a Web Designer Before Hiring?
The most important questions to ask a web designer before hiring cover five areas: discovery and strategy, technical performance, contract and ownership, timeline, and post-launch support. Focus less on "what is your design style?" and more on "what measurable outcomes do your sites produce?"
Here are the questions organized by the five evaluation dimensions above.
Discovery and Strategy
- • How will you learn about my business and customers before starting?
- • Who handles the copy -- me or you? If me, what guidance do you provide?
- • How do you define success for a project like mine?
- • What research do you do on competitors before designing?
Technical Performance
- • What Lighthouse scores do your sites typically achieve?
- • How do you handle accessibility? Do you target WCAG 2.1 AA compliance?
- • What platform will you build on, and why is it right for my needs?
- • What are your Core Web Vitals targets?
Contract and Ownership
- • Who owns the domain, hosting account, code, and design files after launch?
- • What happens to my site if I stop paying your maintenance fee?
- • Can I move my site to a different host at any time?
- • How are revisions defined and capped in the contract?
Timeline and Process
- • What does the project timeline look like, phase by phase?
- • What do you need from me, and when?
- • What happens if the project runs past the deadline -- on your side or mine?
- • How will we communicate during the project? How often?
Post-Launch
- • What is included in the handoff when the project is done?
- • Do you offer ongoing support? What does it cover, and what does it cost?
- • Who do I contact if something breaks after launch?
- • Will I receive training on how to update the site myself?
You do not need to ask every question here. But any designer who cannot answer the ones about performance data, ownership terms, and post-launch handoff should not make your shortlist.
Do I Own My Website After a Designer Builds It?
You should own your website after a designer builds it, but this is not automatic. It depends on your contract. Ownership covers four separate things: the domain name, the hosting account, the code, and the design files. Each can be controlled by the designer if the contract does not explicitly assign ownership to you.
Domain Name
Your domain (yourcompany.com) should be registered in your name through a registrar like Namecheap, Cloudflare, or Porkbun. If the designer registered it under their own account, you may need their cooperation to transfer it. Confirm that the registrar account login belongs to you.
Hosting Account
The server where your site lives should be an account you control. Some designers host all client sites on their own server and charge a monthly fee. If you stop paying, your site goes offline. That is not hosting -- it is leverage.
Your hosting account should be in your name, or at minimum, fully transferable without the designer's involvement.
Code and Files
The HTML, CSS, JavaScript, and any CMS database that make up your site should belong to you after final payment. Some contracts include "work-for-hire" language that makes this explicit. Others are silent on code ownership, which creates disputes later. Ask directly and get it in writing.
Design Source Files
The Figma, Sketch, or Adobe files used to design your site are separate from the finished code. Some designers deliver these at project completion; others consider them internal working files. If you might work with a different designer in the future, getting the source files matters -- they make redesigns and updates far easier.
The "Proprietary CMS" Trap
Some designers build on proprietary systems where your content lives inside their platform. If you leave, you cannot export your pages, blog posts, or media. Before signing, ask: can I export all of my content and move to a different platform if I choose to? If the answer is no or unclear, that is a lock-in mechanism.
What Should a Web Designer Provide After the Project Is Done?
After a website project is complete, your designer should deliver login credentials and full access to your domain, hosting, and CMS; all source and design files; a walkthrough of how to use the CMS; documentation covering site structure and integrations; and a baseline performance report. Anything less is an incomplete handoff.
Here is the full post-launch checklist.
Access and Credentials
- • Domain registrar login (you should already have this, but confirm)
- • Hosting control panel login
- • CMS admin login with full permissions
- • Google Analytics access (your own account, not the designer's)
- • Google Search Console access
- • Any third-party service logins (email marketing, forms, chat widgets)
Files and Documentation
- • All design source files (Figma, Sketch, or equivalent)
- • Complete codebase if applicable (for custom-built sites)
- • Documentation covering site structure, page templates, and any custom functionality
- • A list of all third-party services and integrations, with account details
Training
- • A live or recorded walkthrough of the CMS: how to edit pages, add blog posts, update images, and manage navigation
- • Written documentation for common tasks your team will perform regularly
- • A clear point of contact for questions during the first 30 days
Performance Baseline
- • Lighthouse scores at launch (screenshot or report for all four categories)
- • Core Web Vitals baseline from Google Search Console
- • Number of indexed pages confirmed in Search Console
- • Analytics tracking confirmed as functional
This baseline matters because it gives you a reference point. If performance drops three months later, you know when it started and can diagnose what changed. It also establishes accountability -- if the designer promised 90+ Lighthouse scores and the launch baseline shows 65, that is a conversation to have immediately.
Ongoing Support
A good ongoing maintenance relationship includes uptime monitoring, security updates, regular performance checks, and content update support. At Designly, our monthly plans start at $50/month and include hosting, monitoring, and monthly Skora re-audits -- but whatever provider you choose, make sure the terms are written down. What is included? What costs extra? What are the response times?
How Long Does It Take a Web Designer to Build a Website?
A standard small business website typically takes 4 to 8 weeks from kickoff to launch. Accelerated timelines of 1 to 2 weeks are achievable with a defined production process, ready content, and limited revision cycles. The single biggest variable is how quickly you provide content and feedback.
Discovery and Strategy: 3-5 Days
The designer learns your business, reviews competitors, defines the site structure, and aligns on goals. Your job during this phase: provide brand assets, answer questions about your audience, and share existing content.
Design: 5-10 Days
Visual concepts are created based on the strategy work. You review, provide feedback, and approve. Most projects include two to three revision rounds here. Delays at this stage almost always come from slow client feedback -- if you take two weeks to review a mockup, the timeline extends by two weeks.
Development: 5-10 Days
The approved design becomes a functional website. CMS gets configured. Forms, integrations, and analytics are set up. Performance optimization happens here -- image compression, code minification, caching.
Review and Revisions: 3-5 Days
You test the site, flag issues, and request final changes. The designer fixes bugs, adjusts content, and runs final performance checks.
Launch: 1-2 Days
DNS is pointed, SSL is configured, redirects are set up (if migrating from an old site), analytics tracking is verified, and the site goes live.
What Drives Delays
Content is the number one delay on every web project. If the designer is waiting on your copy, photos, or brand materials, the build stalls. The second most common delay is decision-making -- multiple stakeholders reviewing designs with no single decision-maker.
A timeline with no client milestones is a red flag. It means the designer has no mechanism to keep the project on track when your deliverables are late.
At Designly, our 1-2 week delivery is possible because we handle strategy and copywriting in-house and build on a standardized tech stack. That model is not the only way, but if speed matters to you, ask prospective designers what their typical timeline looks like and what it depends on.
How to Prepare Before Hiring a Web Designer
Before hiring a web designer, gather your brand assets (logo, fonts, colors), define your primary business goals for the website, identify three to five competitor or inspiration sites, prepare a basic content outline, and set a realistic budget range. Clients who arrive prepared get better results and shorter timelines.
Gather Your Brand Assets
- • Logo files (vector format if possible -- SVG or AI)
- • Brand colors (hex codes if you have them)
- • Fonts you currently use
- • Any brand guidelines or style documentation
- • High-resolution photos of your team, location, or products
Define Your Goals
What does success look like in six months? Be specific. "More traffic" is not a goal. "20 contact form submissions per month" is. "More phone calls" is vague. "15 phone calls per month from the website" is measurable. Your designer needs concrete targets to design toward, or they will optimize for aesthetics instead of outcomes.
Identify Competitor and Inspiration Sites
Pick three to five websites you admire -- some from competitors, some from unrelated businesses. For each one, note what you like and why. This gives your designer a visual shorthand that prevents misaligned expectations.
"I want something modern and clean" means something different to every designer. "I like the layout structure of this site and the typography of that one" is specific and useful.
Outline Your Content
List the pages you need and the key messages for each. You do not need finished copy -- a rough outline is enough. But knowing that you need a homepage, about page, services page, FAQ, and contact form is essential for scoping and pricing.
Set a Budget Range
Knowing your range prevents wasted conversations. If your budget is $3,000, say so upfront. A good designer will tell you honestly what is achievable at that price. A bad one will agree to anything and cut corners later.
Run an Audit on Your Current Site
If you have an existing website, run a free audit before your first call with any designer. Arriving with data about what is broken -- specific Lighthouse scores, accessibility failures, SEO gaps -- puts you in a stronger negotiating position and helps the designer scope the project accurately.
Frequently Asked Questions
How do I find a good web designer for my small business?
Start with referrals from other small business owners in your industry -- ask specifically about their experience with the handoff, not just the design. Supplement with Google searches for local web designers and review platforms like Clutch and Google Business Profile. Once you have three to four candidates, run each one through the five-dimension scoring framework in this guide. A referral gets someone on the list. The framework decides who stays.
What is the difference between a web designer and a web developer?
A web designer focuses on the visual and experience layer: layout, typography, color, and how the site feels to use. A web developer builds the technical layer: code, database, and integrations that make the site function. Many professionals handle both. For a small business website, the distinction matters less than whether the person or team can deliver a site that looks good, loads fast, and works correctly.
How do I know if a web designer is good?
Test their work, not their pitch. Run Lighthouse on two or three of their portfolio sites and check whether scores consistently hit 90 or above. Review their contract for clear ownership terms. Ask whether their discovery process covers your business goals before jumping into design. A good designer produces sites that perform well on measurable criteria -- not just sites that look nice in a portfolio screenshot.
Choose With Evidence, Not Gut Feeling
Choosing a web designer is a business decision, not an aesthetic one. The right framework evaluates performance data, ownership terms, cost transparency, and post-launch support -- not just whether the portfolio looks nice during a 15-minute scroll.
Here are the five evaluation dimensions one more time:
- Discovery process quality -- do they understand your business before designing?
- Portfolio performance -- do their sites score 90+ on Lighthouse?
- Ownership and contract terms -- do you own the domain, code, hosting, and files?
- Pricing transparency -- is the scope, price, and revision policy written down?
- Post-launch support -- is the handoff defined, and is ongoing help available?
Score every candidate. Compare the numbers. The designer who scores highest may not be the cheapest, but they will be the one least likely to leave you with a site you cannot maintain, measure, or control.
If you want to start with data before talking to designers, run a free Skora audit on your current site. It scores your site across 10 dimensions and gives you a concrete picture of what needs fixing -- so your first conversation with any designer starts with evidence, not guesses. And if you are ready to talk about a project, we are here.
Photo credits: [Featured] by Vitaly Gariev on Unsplash, [Analytics Dashboard] by Luke Chesser on Unsplash, [Reviewing Notes] by Vitaly Gariev on Unsplash, [Colleagues Reviewing Documents] by Vitaly Gariev on Unsplash, [Document Handoff] by Van Tay Media on Unsplash