SaaSInsightBrowse reviews
Product design

Product design agency or web design agency: which do you actually need?

Look at where you lose people. If visitors leave before signing up, the problem is the website and a web design agency is the hire. If they sign up and then stop using the product, no homepage fixes it: hire a product design agency. If both leak, run two projects on one shared design system.

By Rajat Kapoor

Updated October 2026

Key takeaways

  • The login screen is the clearest line between the two: a web design agency designs everything before it, and a product design agency designs everything after it.

  • Where people drop off tells you which you need: visitors who never sign up point to the website, and users who sign up and stop point to the product.

  • Signup and onboarding sit on the line and belong to nobody unless you assign them in both briefs.

  • Customer portals, configurators, booking flows and mobile apps are product design projects, even when they live on your website's domain.

  • When both need work, give the two firms one shared set of design tokens so the site and the app stay recognisably the same company.

  • If you cannot tell where people drop off, measuring the funnel is a cheaper first step than hiring either kind of agency.

You run a software company, and something in the numbers is wrong. Maybe the new homepage gets traffic and nobody books a demo. Maybe people sign up, poke around for ten minutes and never come back. Either way, two kinds of firm answer the enquiry, both call what they do design, and both will happily quote.

Picking the wrong one is expensive in a specific way. A web design studio asked to redesign an application tends to draw handsome screens that break on the first real workflow. A product design studio asked for a marketing site can spend months on research for pages a visitor reads once. This page sorts out which problem you have and which kind of firm it needs, and what to do where the two meet. It does not rank firms; the rankings it links to do the naming.

The login screen is the line

The cleanest way to split the two is the moment someone signs in.

Everything before it is the website: the homepage, pricing, feature and comparison pages, the blog, the signup page itself. Its job is to persuade a stranger, and it is judged on first impressions and on how many visitors take the next step. A web design agency is built for this. It thinks in pages, messaging, a content system your marketers can edit, and conversion.

Everything after it is the product: onboarding, the dashboard, settings, the workflows people come back for, and any mobile app. Its job is to let someone who already said yes get a task done on their fortieth visit without thinking about it. A product design agency works on flows, states, error handling and a design system that holds together as features pile up. The practice looks a lot like the UK government's Service Standard describes for digital services: understand users and their needs, then iterate and improve frequently. That is a different rhythm from a site that launches and gets refreshed every few years.

Plenty of firms offer both. The label on their homepage tells you where they started, not where they are strong, so look at which side of the login screen their portfolio actually shows.

Find where people drop off

Before you brief anyone, look at where you lose people, because that tells you which side of the line the problem lives on.

If visitors arrive and do not sign up, request a demo or start a trial, the problem is in front of the login screen. That is website work: messaging, page structure, the path to the form.

If people sign up and then fail to set up the account, never reach the moment the product proves its worth, or quietly stop using it after a month, the problem is behind the login screen. No homepage redesign fixes that. It is product work.

If support tickets cluster on one flow, that is product work too, and usually a smaller project than a full redesign.

If you cannot tell where people drop, that is the first job, and it is cheaper than either agency. Instrument the funnel from visit to signup to first real use, wait a few weeks, and the answer usually names itself.

The seam: signup and onboarding

One stretch sits on the line and belongs to nobody unless you assign it: the signup form, account creation and the first session inside the app. It is where the promise on the website meets the reality of the product, and it is where most handovers go wrong, because each firm assumes the other owns it.

A workable rule is that whoever ships the code that renders a screen owns its design. The signup page on the marketing site is usually the web team's. The steps after the account exists are the product team's. Write that split into both briefs, and ask each firm to review the other's half before launch, so the words a visitor reads on the pricing page are the words they see on the first screen of the app.

Things that look like a website but are product

Some projects arrive labelled as website work and are really applications. A customer portal, a logged-in dashboard, a quote builder or configurator, a booking flow, a patient or member area: if people sign in and come back to do something, treat it as product design, even if it lives on your domain and looks like part of the site.

A mobile app is product work without exception. Apple runs a curated App Store where every app is reviewed by experts before it reaches users, against platform rules that marketing sites never meet. A studio that has not shipped through that process will learn on your project.

The opposite trap is smaller but real. A product tour page, a feature page with animated screenshots, or a landing page for a launch is website work, however much it talks about the product.

Accessibility applies on both sides. WCAG 2.2 addresses web content on any kind of device, including desktops, laptops, kiosks and mobile devices, so ask each firm how it tests its half rather than assuming the other one covers it.

When both need work

Often the honest answer is both: the site undersells the product, and the product feels dated next to a new site. That is two projects with one shared problem, which is keeping them looking and sounding like the same company.

The practical fix is a shared foundation that both teams build on. Colour, type, spacing and core components live in one set of design tokens, and both the site and the app read from it. The Design Tokens W3C Community Group published its first stable format version, 2025.10, so this no longer depends on one firm's private conventions. Ask both firms, in writing, to work from one token set, and decide who owns it. The product side usually should, because the application has more states and more constraints, and the site can borrow from it far more easily than the reverse.

On sequence, fix the side where you lose more people first. If the deeper problem is that nobody agrees what the company does, neither firm can solve that, and branding or web design covers that decision.

Route by where you are

Visitors do not sign up, and you sell software. A web design agency that builds marketing sites for software companies. Start with best web design agencies for SaaS.

Visitors do not convert, and you are not a software company. You probably do not need product design at all. Start with best web design agencies.

People sign up and do not stick. Product design. Start with best product design agencies, which also sorts firms by stage and budget.

You are building or rebuilding a mobile app. Product design, for the reasons above, on the same ranking.

You need a marketing site and an application from one firm. Look for a team that writes application code, not only marketing pages. Best web development agencies covers firms that ship both.

The new site makes the app look old. Product design, scoped as a design system rather than a redesign, with the site reading from the same tokens afterwards.

The marketing site is the job and the platform is still open. Web design or Webflow settles that first. For what the website side costs, see what a web design agency costs.

The question that sorts any shortlist

Ask every firm to open its portfolio, point at the login screen in a project it shipped, and tell you which side of it they designed and who designed the other side. A web studio will show you pages before the line. A product studio will show you screens after it, with the states and edge cases that only exist once real people use the thing. A firm that claims both should be able to show both halves of the same product, and explain how the two stayed consistent after launch.

Frequently asked questions

Can a web design agency design my app?

Some can, but most are built for the website in front of the login screen, not the application behind it. Marketing sites are judged on first impressions and conversion; applications are judged on whether someone can finish a task on their fortieth visit. Ask to see application screens the firm designed, including empty states, error messages and settings, not only homepages. If its portfolio stops at the signup button, it is a web design agency, whatever the services page says.

Can a product design agency design our marketing website?

Many can, and several offer it, but check that it treats the site as a marketing job rather than an extension of the app. A website needs messaging, page structure, a content system your marketers can edit without engineering, and attention to search. A product studio that brings months of user research to a ten page site is spending your budget on the wrong problem. Ask who writes the copy and who will maintain the site after launch.

Who should design our signup and onboarding flow?

Assign it explicitly, because it sits exactly on the line between the two and each firm tends to assume the other owns it. A workable rule is that whoever ships the code owns the design: the signup page on the marketing site goes to the web team, and the steps after the account exists go to the product team. Write the split into both briefs and have each firm review the other's half before launch.

If both the website and the product need work, which comes first?

Fix the side where you lose more people. If visitors leave before signing up, the website comes first. If people sign up and then stop using the product, product design comes first, because a better homepage only sends more people into the same leak. If you cannot tell where people drop, measure the funnel before hiring anyone. Running both at once works if both firms build from one shared set of design tokens.

Is a mobile app product design or web design?

Product design. A mobile app is something people sign into and come back to, and it has to pass platform rules: Apple, for example, reviews every app before it appears on the App Store. That calls for flows, states, accessibility and platform conventions, which is product design work. A studio that has only shipped websites will learn those rules on your project. The app's download page on your website is still web design.

How do we keep the website and the product looking like the same company?

Give both firms one shared foundation: colour, type, spacing and core components defined once as design tokens, with both the site and the application reading from them. There is now a stable open format for this from the Design Tokens W3C Community Group, so it does not depend on one firm's conventions. Decide who owns the token set, usually the product side, and put that in both contracts.

Where to go next