Web designer vs web developer: which do you need?

A web designer decides how your site looks and reads: the layout, the colors, the type, the words and images that carry your story. A web developer decides how it is built and performs: the code, the speed, the security, and what Google and AI tools can read about you. Many solo practitioners, me included, do both. For a small business, the title matters less than two questions: who owns the result, and is anyone measuring it?

Which one do I actually need?

Start from the symptom, not the job title.

• The site looks dated, or the story is muddled. That is design work: layout, words, photography, and a clear path for the visitor to follow. The code underneath might be fine.
• The site is slow, breaks on phones, got hacked, or never shows up in search. That is developer work. No visual refresh fixes a six-second load time or a site that Google and AI tools cannot read.
• You are starting fresh, or replacing the whole thing. You need both, and for a typical small-business site you do not need two separate hires. One capable person or a small team covers it. What you should confirm is that both halves are actually being done: a site that is beautiful but slow fails, and so does a fast site that says nothing.

The two crafts are real and both take years to get good at. A dedicated designer will usually produce a more distinctive look than a developer who designs. A dedicated developer will usually produce a faster, sounder build than a designer who codes. For most local businesses, though, the gap that hurts is not craft, it is follow-through: nobody measured anything, and nobody wrote down who owns what.

What about "web design agencies"?

The label tells you almost nothing. Most firms that call themselves web design agencies also do development, and plenty of "developers" ship a designer's work. These titles are marketing, not job descriptions, and there is nothing dishonest about that.

The useful question to ask any agency is: who, specifically, will do the design, and who will write the code? Sometimes it is a strong in-house team. Sometimes your project is subcontracted out and marked up, which can still be fine, if the accountability and the measurements stay in your contract. You are not buying the label on the door. You are buying the people who touch your site and the numbers they are willing to show you.

What should you ask whoever you hire?

Designer, developer, agency, or a person who is all three, these four questions sort the professionals from the rest in about five minutes.

• "Will the domain and the site be registered to me?" The domain is your address on the internet. If it sits in a vendor's account, they can hold it, lose it, or price your exit. The only right answer is yes, in your name, in an account you control.
• "What speed numbers will you show me, before and after?" Google's free PageSpeed test scores any site, and how long the main content takes to appear is the number that decides whether visitors stay. A professional expects this question. Vague reassurance instead of a number is your cue to leave.
• "What security grade will the site get?" Every site sends browsers a set of instructions that block common attacks, graded A through F by free public checkers. Configuring them costs nothing. Ask for the grade, then check it yourself after launch.
• "What happens if I leave?" The content, the files, and every account should go with you, with no exit fee and no contract holding the site hostage. Anyone who hesitates here is telling you something important.

Notice that none of these questions require you to judge design taste or read code. They test ownership and measurement, which is where small businesses actually get burned. I hold my own work to the same four answers, and publish the measurements.

If you are weighing options in the North Bay, the companion piece covers what a website costs in Sonoma County, and this page explains how I work as a web developer in Petaluma.