One analogy sorts it out
Think of building a website as fitting out a shop.
Design is the drawings and the look: where the door goes, where the counter sits, what colour the walls are, what a customer sees first. Development is actually building it: wiring, walls, equipment, and making sure the lights come on when someone hits the switch.
Both have to be done before the shop can open. Drawings alone open nothing; someone who can build walls but does not know what they should look like produces something nobody wants to walk into.
So the question is not which one matters more, it is which one you are currently missing.
What each side actually handles
Design handles "how it looks and how it feels to use"
Layout, type size, colour, how it folds on a phone, how many taps between arriving and calling you. It decides what visitors feel and do — the same content laid out differently can change how many people call by several times over.
Development handles "it actually runs, runs fast, and does not break"
Load time, whether it breaks on a phone, whether a submitted form genuinely sends the email, what a search engine reads when it crawls. It decides whether the site works at all and whether Google can understand it.
And a third piece both sides tend to drop
Structure. Which pages exist, how they link, how URLs are set, which page targets which search. It is neither purely visual nor purely technical, and it decides whether the site can ever be found. Plenty of sites underperform not because they look bad but because structure was never decided.
The thing to fear when hiring is not weak design or weak development. It is nobody owning structure. You end up with pages that each look fine and each run fine, and a site that cannot be found — and that only becomes visible six months after launch.
Which one are you missing
Find yourself in the list below and you will know roughly who to look for.
You have a site but it looks dated and is awkward on a phone
Probably design. But do not rush into a rebuild — if the site still ranks on Google, tearing it down is risky and every old address has to be redirected. See the rebuild section in what web design costs first.
The site looks good, but customers say it will not open, or forms go unanswered
That is development, and it is the kind to check immediately. Silently failing forms are especially common: the page says "thank you" while not a single email goes out, and the owner finds out months later.
The site looks good and works, but nobody finds it
Neither side is missing; structure and search work are. Rebuilding the site again usually achieves nothing here — the ranking work is what is needed.
You have nothing and are starting from zero
You need both, and you need someone setting structure from day one. Counter-intuitively, the cheapest route is usually one team that covers all of it rather than design from one company, development from another and search from a third.
What to ask when hiring
Whether the shop calls itself a design company or a development company, these questions all work. The answers tell you more than the label does.
"Do you do both in-house, or is one part subcontracted?"
Subcontracting is not bad, but you need to know who to call when something breaks. Two halves at two companies with nobody coordinating is the easiest situation for finger-pointing.
"Which devices do you actually test on before launch?"
Anyone who names specific devices and screen widths has usually tested. "Oh, we test everything" without specifics usually means launching and waiting for customers to report problems.
"What does the page show when a form fails to send?"
This one question reveals a lot. The right answer is "it shows a failure and gives an alternative way to reach you". Anyone answering "it will not fail" has not thought about it.
"Who decides which pages exist and how the URLs are set?"
This is asking who owns structure. If design says development decides and development says they follow the design, nobody owns it.
Questions this article gets
Can I get design only and handle development elsewhere?
You can, but you carry the join between them. Unless you already have developers, splitting it usually ends up slower and more expensive, because when something goes wrong each side points at the other.
Where does a drag-and-drop site builder fit?
The platform has done part of both for you, at the cost of limited room to change things and a structure the platform decided.
For a shop that only needs address, phone and menu to be findable, that is entirely sufficient. If you intend to take search seriously, the limits tend to show up about six months in — and migrating away then costs more than building properly would have.
Why do some quotes just say "website" as one line?
Because on a small project the two are done together anyway and splitting them is fussy. Not necessarily a problem, but you can ask for design, development, content and post-launch service to be listed separately — if they cannot be separated, no dispute about any of them can be settled later.
Which are you?
We do both in-house, and we set structure from the start — which is precisely the part that usually ends up unowned. See trilingual web design for how that works.
Free marketing review
Not sure how much growth your website is leaving on the table?
Send us your website and industry. We will review your site, search visibility, Google Maps presence and social footprint, and tell you the three things worth fixing first.