I keep getting the same brief with the wrong noun. "We need a website" that is actually login, payments, and an admin. "We need an app" that is actually five pages and a form. Should you build a website or a web product first? That question has to be answered before anyone quotes.
The words are not cosmetic. They decide the shape of the work, the cost, and whether one full-stack developer is enough. I build both — business websites and SaaS and web products, the split on the services page — and the mistake is almost always made in the first email, not in the code.
What a website is actually for
A website has a job: a stranger lands, understands what you do, and can act — call, book, buy, write. It has to be fast, readable on a phone, and possible for Google to understand. Done is when that loop works, not when you have an account system you don't need.
If nobody has to come back tomorrow for the thing to be useful, you probably need a website. The pages can be many. The content can be heavy. That still isn't a product. It is a site that has to perform.
What a web product is actually for
A web product — a SaaS tool, a portal, a system your team or your customers live in — is software people return to. There are accounts. There is data that belongs to them. There is a job they do inside it, not just a page they read. Done is when that job runs without you in the loop.
This is why "just a website with a login" is a product wearing a cheaper word. Auth, a database, payments, permissions, the part that has to stay up on a Tuesday — that is the product work, whether you call it SaaS or not. The test is the return visit, not the billing model.
Website
A stranger acts once
Explain, convert, rank. The useful thing can happen without an account.
Web product
Someone comes back
Login, data, a job inside the thing. The business runs through it.
How to tell which one you need
Ignore the word in the email. Look at the job. I write a brief before I quotefor this reason: if the thing isn't named, the range is fiction.
It's a website if
- A stranger has to understand what you do in ten seconds
- The main job is to look real, rank, and get a message or a sale
- Nobody needs an account to finish the useful thing
- You would still recognise it if you printed the pages
It's a web product if
- People come back. There is a next session, not just a first visit
- Someone logs in, pays, books, or runs a job through it
- There is data that has to stay theirs — orders, records, messages
- You said dashboard, portal, customers, or "like X, but for us"
The three mix-ups I see
- 01
You said website. You meant a product.
Login, a place for customers, payments, an admin panel. That is software people return to. Calling it a website does not make the backend go away. It just means the quote will be wrong until someone names it.
- 02
You said app. You meant a website.
Five pages, a contact form, maybe a blog. No accounts. No job that happens inside the thing. You need to look real on Google and on a phone. That is a website. Building it "as an app" is how you pay product money for brochure work.
- 03
You need both and haven't said so yet.
A public site that explains the business, and a product behind a login for the people who already said yes. Two jobs. One hire can own both if they fit in one head. They still have to be named as two jobs in the brief, or the marketing pages eat the product, or the other way around.
When you need a website and a web product
Plenty of businesses need both: a public site that does the explaining, and a product the customers actually use. That is still one line of ownership if it fits in one head — interface, systems, production — which is the filter I wrote down in hiring a developer. It is not one blob of work. Two jobs, one person, a cut line between them.
If you already have a site that grew a login and an admin behind nobody's back, that is usually a takeover, not a new brand with a blank repo. Name what it is now. Then decide what belongs in the first version.
Call it a website when a stranger can finish the useful thing without an account. Call it a product when the useful thing is coming back.
If you're staring at that split, don't send a feature list. Send which one you think it is, in a sentence. The rest of website or product is that sentence from different angles. Wrong noun, wrong quote. Right noun, and the build can start.
