UI/UX vs Web Design: Are You Buying the Same Thing?

These terms overlap enough that two agencies can quote for the same project under different labels. The distinction that actually matters is not vocabulary — it is whether the thing being designed is a website or a product.

What Web Design Usually Means

In practice, web design describes designing a website: marketing pages, service pages, a blog, a contact route. The visitor arrives, reads, and either acts or leaves. Sessions are short and the same person may never return.

The design problems are about clarity, hierarchy, persuasion and structure — helping someone unfamiliar understand quickly and find what they came for.

What UI/UX Usually Means

UI/UX design usually describes designing a product: something with state, accounts, repeated use and tasks that span sessions. A dashboard, an application, a booking system, a portal.

The design problems are different — what happens when a list is empty, how a task resumes after an interruption, what a task looks like on the hundredth repetition rather than the first.

Where the Overlap Is Real

A checkout is both. So is a booking flow, a multi-step form, a search interface, a member area. These are product problems living inside a website, and they need product thinking regardless of what the project is called.

This is why the labels cause confusion. A "web design" project containing a booking system needs UX work that a brochure site does not, and a quote that treats it as another page will be wrong.

Why the Distinction Matters Commercially

Because the two are scoped differently. Website work is scoped by templates: how many page types, how much content. Product work is scoped by states and flows, and a single screen may have six states that each need designing.

A booking system quoted as "one page" is quoted wrongly. It is a flow with availability display, selection, form, confirmation, failure handling and an empty state — see booking website design for the visitor side.

Which Should You Ask For?

Ask for web design if

• The site is pages people read and act on.
• The main outcomes are enquiries, calls or straightforward purchases.
• Nobody logs in.
• Sessions are short and largely self-contained.

Ask for UI/UX if

• People log in and return.
• There is state that persists between sessions.
• Tasks have several steps and can fail partway.
• The same person will use it hundreds of times — see B2B UX design.

The Decision Rule

If people log in, it is a product and needs UI/UX. If they read and act, it is a website and needs web design.

If it is a website with a product-shaped thing inside it — a booking flow, a configurator, a portal — scope that part separately. It is the part most commonly under-quoted and the part most likely to fail.