How to choose the right web designer for your business

Start by defining what you are hiring for

When business owners say they need a web designer, they often mean someone who will deliver a complete, working website.

In practice, that can involve several different responsibilities:

• visual design
• user experience and information architecture
• content structure and messaging
• frontend and CMS development
• accessibility and performance
• technical SEO
• analytics, forms, and integrations
• maintenance after launch

Not every web designer provides all of these services. Some specialize in visual design and hand their files to a developer. Others manage the complete process from planning to launch.

Neither model is inherently wrong, but you need to know which one you are buying.

Before comparing portfolios, write down what the project actually requires:

• a new marketing website
• a redesign of an existing site
• an online store or booking system
• a multilingual website
• a technical rebuild with the existing design
• ongoing improvements rather than a one-time launch

The right partner for a five-page service-business website is rarely the same as the right team for a multilingual product platform.

Evaluate every candidate using the same criteria

An attractive portfolio is useful, but it is only one part of the decision. Use the same five areas to compare every candidate after the first conversation.

You can score each area from one to five. The number is not scientific, but it helps prevent a polished presentation from overshadowing weak answers about ownership, process, or technical quality.

A beautiful portfolio combined with vague delivery terms is a pattern that can become expensive after launch.

Ask how they understand the business

A useful website begins with a clear offer, audience, and desired action. The designer should therefore ask questions before proposing layouts.

Questions worth asking include:

• What would you need from me to understand the offer and audience?
• How would you identify the pages that matter most?
• How do you decide what belongs in the navigation?
• What should a visitor understand within the first few seconds?
• How would you determine the primary call to action?
• How will we know whether the website is working?

Listen for answers connected to actual users and business outcomes.

If the conversation moves immediately to colors, animations, and visual references without discussing the purpose of the website, the project may begin with decoration before the underlying problem is understood.

Clarify exactly what will be delivered

Two proposals can use the phrase “complete website” while including very different work.

Ask:

• What exactly is included in the quoted price?
• How many unique pages and templates are included?
• Who writes, edits, and uploads the content?
• Who handles development?
• Are any parts subcontracted?
• Is the design custom, adapted from a system, or based on a template?
• How many rounds of revisions are included?
• How is feedback collected and approved?
• What is explicitly excluded?
• What happens if the scope changes?

Templates and subcontractors are not automatically warning signs. Both can be sensible choices when disclosed clearly and managed properly.

The problem is discovering halfway through the project that “custom design” means an existing theme with new colors, or that development was never included in the original price.

Look beyond portfolio screenshots

Portfolio images show visual ability, but they do not tell you how the website behaves in real use.

Open live projects and check:

• mobile navigation
• loading speed
• readability and content hierarchy
• forms and calls to action
• keyboard navigation
• consistency between pages
• broken links or unfinished sections
• whether the live result matches the portfolio presentation

Ask the designer which parts of the project they personally handled. A portfolio may include work completed as part of a larger team, and their role could have been limited to one section.

A useful question is:

Can you show me a live website you worked on and explain one design decision and one technical decision behind it?

A strong answer reveals more than another gallery of polished mockups.

Ask specific questions about quality

You do not need to become a developer before hiring one. You do need answers that go beyond general claims such as “SEO-friendly,” “mobile-ready,” and “optimized.”

Ask:

• How do you approach responsive design across different screen sizes?
• How do you test the site on real devices and browsers?
• What do you do to protect loading performance?
• How is accessibility considered during design and development?
• Which SEO foundations are included?
• How are page titles, descriptions, heading structure, redirects, and indexability handled?
• How are forms tested?
• Will analytics and conversion events be configured?
• What happens if performance deteriorates after a plugin or third-party script is added?

Good answers do not need to be overly technical. They should be clear, concrete, and connected to the way the website will actually be built.

Confirm ownership before signing

Ownership problems often remain invisible until the client wants to move the website, change providers, or add another developer.

Clarify who controls:

• the domain
• hosting and DNS
• CMS administrator accounts
• analytics and Search Console
• third-party services
• design files
• source code
• website content and media

Where possible, important accounts should be registered in your name or the company’s name, with the provider receiving the access needed to do the work.

Also ask:

• If we stop working together, can another developer take over?
• Is there any proprietary system that prevents migration?
• Will I receive the final files and documentation?
• Is there a handover process?
• Are licenses tied to the designer’s account?

Some managed platforms legitimately limit access to their underlying infrastructure. That can be acceptable when explained before the contract is signed. Hidden lock-in is the problem.

Understand what happens after launch

A website is not finished simply because it is online. Software updates, security, content changes, backups, and performance still need ownership.

Ask:

• Is a post-launch support period included?
• What qualifies as a launch-related bug?
• How are later changes requested and billed?
• Who handles CMS and plugin updates?
• Who monitors backups and security?
• What response time applies to urgent problems?
• Is ongoing support required or optional?

“No maintenance included” can be a valid arrangement if your team will handle it. What matters is that responsibility is explicit.

A vague promise to “help if anything comes up” is not a support plan.

Warning signs worth taking seriously

Price is the only advantage discussed

A lower price can reflect a smaller scope or a more efficient process. It can also mean that planning, testing, performance, content support, or proper handover has been removed.

Compare what is included, not only the headline number.

They ask no questions about business goals

If someone proposes layouts before understanding the audience, offer, and desired action, they may be solving the wrong problem attractively.

The portfolio contains only screenshots

Screenshots cannot demonstrate loading performance, mobile behavior, accessibility, form reliability, or content quality.

They want to control your domain

The domain should normally be registered to you or your company. Losing control of it can create serious problems later.

A template is presented as fully custom work

Templates can be a practical and economical choice. Hiding their use undermines trust and makes the offer difficult to evaluate.

AI output is treated as finished work

AI can accelerate research, drafts, layout exploration, and development. It does not remove the need for judgment, review, testing, accessibility, and a clear business strategy.

There is no plan after launch

Without defined responsibility for updates, security, backups, and support, the website begins accumulating risk immediately.

What a solid process usually looks like

A reliable website project commonly moves through these stages:

1. Project brief, goals, audience, and success criteria
2. Site structure, content requirements, and primary user paths
3. Design and UX for the most important templates
4. Development with performance, accessibility, and maintainability in mind
5. Content implementation and integrations
6. Testing on relevant devices and browsers
7. Launch, documentation, handover, and an agreed support period

The exact names of the stages can differ. What matters is that planning, design, development, testing, and handover are all accounted for.

Skipping structure to “start designing faster” often creates more revisions later.

Accept the right trade-offs

You may not need a full branding agency for a focused marketing website. A capable freelancer may provide a more direct process with fewer communication layers.

You may need a larger team if the project requires brand strategy, copywriting, custom development, localization, and campaign work to happen simultaneously under a fixed deadline.

My guide to choosing between an agency and a freelancer explains that distinction in more detail.

The goal is not to choose the largest or cheapest provider. It is to choose the delivery model that fits the project.

Paying more for clear scope, documentation, technical quality, and ownership is often cheaper than rebuilding a rushed website later.

One decision before you commit

Choose the partner who can explain how the website will support your business goal, document what will be delivered, and leave you in control after launch, not simply the one whose portfolio impressed you in the first five minutes.

A good web designer does more than make the website attractive. They help make the business easier to understand, trust, and contact.

Want a website that works for your business?

If you need a website that is fast, clear, accessible, and built for a defined purpose, contact me. We can briefly review your existing website or project idea, without obligation, and determine what should be improved and whether working together makes sense.