"I need a website for my startup" is one of the most common first sentences in a discovery call, and it's often wrong — not because the founder is confused, but because the three categories genuinely overlap in casual language. Getting this right before you ask for a quote saves you from being scoped (and priced) for the wrong thing.
Website: informs, doesn't authenticate
A website's job is to present information and convert a visitor into a lead or a sale. Nobody logs in. There's no persistent per-user state. A marketing site, a portfolio, a restaurant's online menu, most SaaS companies' own homepage — all websites, even if the company behind them is a SaaS business. If your product idea has no concept of "my account" or "my data," it's a website.
Web app: logged in, does work
A web app has users who log in and the interface does something with their data — a dashboard, an internal tool, a customer portal that shows order status or account history. The defining trait is state: what one user sees and does is different from what another user sees, and that difference persists between visits. If you're picturing a login screen and then a personalized view behind it, you're picturing a web app.
SaaS: a web app you sell as a subscription
SaaS is a web app plus a business model — recurring billing, plan tiers, an onboarding flow designed to convert a trial into a paying account, and usually multi-tenancy (many separate customers' data living in the same system, kept apart). Every SaaS product is technically a web app; not every web app is SaaS. The extra scope in a SaaS build is billing integration, plan/permission logic, and the onboarding and retention UX that a purely internal tool doesn't need.
Why the distinction changes your quote
These aren't just labels — they map directly to real scope differences. A website quote assumes no auth, no per-user data, and a smaller, more predictable build. A web app quote has to account for state management, an API layer, and access control. A SaaS quote adds billing, plan logic, and onboarding on top of the web app scope. Asking for "a website" when you actually need SaaS is how founders end up underscoped and surprised later — see our note on what actually drives SaaS MVP cost.
The quick self-test
- No login, no personalization? Website.
- Login, personalized data, no billing? Web app.
- Login, personalized data, plans and billing? SaaS.
If you're still not sure, that's normal — plenty of real products are a website with one small logged-in feature bolted on, which is its own scope conversation. See our services breakdown for how we split these three, or go straight to pricing once you know which one you're building.