Web design vs web development: which do you actually need?

Design is what your site says and how it feels. Development is what your site does. Most small-business projects need a lot of the first and a little of the second, and knowing which is which keeps you from hiring the wrong person or paying for machinery you'll never switch on.

The reason this gets confusing is that both roles are sold under the same label. Search 'web designer' in Wichita and you'll get people who only push pixels around in Figma, people who only write code, and people who do both. All three call themselves the same thing. Here's how to tell them apart and figure out which you need.

What design actually covers

Design is not decoration. That's the misunderstanding that costs owners the most, because it leads them to treat design as the optional pretty layer on top of the real work.

Design is the decision-making about what a visitor sees first, second, and third. What goes above the fold. Whether the eye lands on your phone number or your logo. Which of your six services get named on the homepage and which get buried. How much text a stranger will actually read before deciding to call. What your colors and type say about whether you're the cheap option or the careful one. It's the layout, hierarchy, typography, spacing, and flow, and every one of those is a business decision wearing a visual costume.

This is the part I came in through. I took two years of formal art classes in California, drawing and painting through storyboarding, plus Illustrator work as part of 3D animation coursework, and learned color theory properly rather than by picking swatches that felt nice. It's a different foundation than most people building websites have, and it shows up in whether a site looks like it belongs to your business or looks like a template with your logo dropped in.

What development actually covers

Development is the engineering. It's what makes a booking system actually hold a slot, a payment actually clear, a login actually keep the wrong people out, a calculator actually calculate.

The rule of thumb: if the page just shows information, that's mostly design. The moment the page has to remember something, check something, charge something, or talk to another system, you're in development. That's why development costs more. Showing the wrong font is embarrassing; charging the wrong card is a real problem, so the work has to be right every time rather than most of the time.

For 3 Keys & Co the development piece was buyer tools, a mortgage calculator and guides, sitting inside what is otherwise an informational real estate site. For a Wichita wrap shop it was a full measuring and markup tool where they upload a vehicle photo, draw measurements and labels to scale, and export a clean PNG quote. They use it daily. That's not a website feature, that's software that happens to live in a browser.

The overlap nobody explains: the front-end

Here's the part that trips up owners comparing quotes. Between design and development sits a third thing: turning the design into actual working code in a browser. That's the front-end, and it's where most of the quality difference in small-business websites is decided.

A design can be beautiful in Figma and fall apart in real life. It can reflow badly on a phone, load slowly, be unusable for someone tapping with a thumb, or ignore anyone using a screen reader. None of that is visible in the mockup, and none of it is what most people mean by development either. It's the seam between the two, and it's where sites quietly fail.

This is exactly why Cloud 9 Slime's site could look completely fine to its owners while scoring 35 on performance and 52 on accessibility. Nothing was wrong with the design idea. The translation into code was the problem, because it was a heavy off-the-shelf theme doing the translating.

Which one your project needs

Sort yourself honestly with this.

• You need customers to find you, understand what you do, trust you, and call: that's design and front-end, with almost no development. This is most local service businesses, and it's the majority of what I build.
• You need customers to book a time, pay a deposit, or log into something: that's real development on top of the design.
• You sell products online: that's both, and the amount of development depends on how far your needs sit from what an off-the-shelf store does.
• You need a tool your industry doesn't have: that's mostly development, and it's a software project, not a website project. Budget and plan for it as one.
• Your site looks fine but nobody finds it: that's neither. That's SEO and structure, and paying a designer to redecorate won't fix it.

That last one matters more than it looks. A lot of owners ask for a redesign when the actual problem is that Google doesn't know what they do or where they do it. Myers AFP is the example. Their single-page GoDaddy site wasn't primarily a design failure, it was invisible. If you're not sure which camp you're in, check the five signs first before you spend anything.

Where the money actually goes

On a typical local-business build starting at $2,500, the budget doesn't split the way owners expect. Very little of it is spent making things look nice. The bulk goes to deciding what each page has to accomplish, writing or shaping the words, and building it so it loads fast and works on a phone.

Design cost scales with how many genuinely different page types you need. A site with a homepage, a services template, and a contact page is three design problems no matter how many services you sell, because the rest are the same template with different content. That's why page count alone is a bad way to estimate a quote.

Development cost scales with edge cases, not features. 'Let customers book a time' sounds like one feature. Then come the real questions: what happens if two people book the same slot, what if someone cancels, does it sync to your calendar, do you take a deposit, what happens when a card declines, what does the customer get by email. That's six decisions hiding inside one sentence, and it's why development quotes feel unpredictable when the request seemed simple. If you want a custom feature, describe what should happen when it goes wrong, not just when it goes right. You'll get a far more accurate number.

The trap of hiring one and needing the other

The expensive version of this mistake goes one of two ways.

You hire a pure designer, get beautiful mockups, and then discover the build is a separate project with a separate budget, and the person building it makes a hundred small decisions the designer never specified. Or you hire a pure developer, get something that works perfectly and looks like a tax form, and then find that visitors don't trust it enough to call.

For a small business, the person doing the work should be able to carry a decision from 'what should this page make someone feel' all the way to 'here's the code that does it, and it scores 100 on Google's test.' Not because one person is inherently better, but because every handoff between people is a place where intent leaks out.

What to ask whoever you're hiring

Four questions sort this out fast.

• Are you designing this, building it, or both? If both, ask to see something they took start to finish.
• What performance score does your work typically hit on Google PageSpeed, and can I go run the test on a site you built?
• Who handles the mobile version, and is it designed for the phone first or shrunk down afterward?
• If I need something custom later, a calculator, booking, a portal, can you build it or does that go to someone else?

That second question is the one that separates talk from work. Rush Fire Protection, 3 Keys & Co, and F3 Wichita all score a perfect 100, and Myers AFP scores 98. Those are public sites and you can test them yourself in thirty seconds, which is exactly the point.

The short answer

Most local businesses need excellent design, excellent front-end, and very little development. What they're usually sold is mediocre design, invisible front-end problems, and development they'll never use. If you're not sure which you need, that's a normal place to be, and it's a five-minute conversation rather than something you should have to figure out before calling.

Tell me what you want the site to do, in your own words, and I'll tell you honestly whether it's a design job, a development job, or both, and roughly what each version would cost. Builds start at $2,500, and I'd rather scope you into the right one than the big one.

Frequently asked questions