Two professions, one bad conflation
Web design decides how a site looks, communicates and flows, layout, typography, brand expression, the user's path from landing to action. Web development decides how it works, code, data, integrations, performance, security. Buyers conflate them constantly, and the conflation is expensive: hiring a developer for a problem that is really a design problem produces technically excellent pages nobody converts on; hiring a designer for a problem that is really an engineering problem produces beautiful mockups of software that cannot exist. The design services page and the development services page carry each side in full.
Where one ends and the other begins
Design's deliverables: brand application, page layouts, the user journey, content hierarchy, prototypes. Development's deliverables: the working system, code, databases, integrations, hosting, performance. The overlap zone is real and growing: design systems in code, designers who ship HTML/CSS, developers with strong visual judgment ("design engineers"). But the professions train different muscles: a designer asks "does this communicate and persuade"; a developer asks "does this work, scale, and stay safe." The working method here runs them in sequence, design approved first, then built, because redesigning pixels mid-build is the most expensive revision in the industry.
Which your project needs first
- Design-led problems: the site works but converts badly, the brand feels dated, users get lost, hire design first (or a design-led developer), then build.
- Development-led problems: the concept works but the site breaks, integrates poorly, or cannot do the thing the business needs, development is the lead.
- Both: most real projects. The efficient shape is design first (wireframes → approved design), development second, never both simultaneously on the same pages.
The decision test: write down the complaint in one sentence. "It looks like 2012 and customers don't get it" is design. "It breaks when customers pay" is development. "Both" is common, and now you know the order. The cost calculator prices each side separately so the tradeoffs are visible, and the brief starts whichever lane, or the sequence, your project needs.