Is It a Website or a Web App? (And Why It Changes the Price)
People use the words like they mean the same thing. They don't, and the difference is most of what a quote is made of. Here's how to tell which one you're actually asking for.
Someone asks me to build them "a simple website," and then describes something with logins, customer accounts, a booking system, and a dashboard where they can see their orders.
That's not a simple website. That's a web app wearing the word "website," and the gap between the two is most of the reason quotes come back at wildly different numbers. It isn't that one developer is greedy and the other is fair. It's that they heard two different projects, because the words we use don't draw the line where the work does.
So let me draw it for you. Once you can see the line, a lot of confusing quotes stop being confusing.
A website shows. A web app does.
Here's the whole distinction in one sentence: a website shows people things, and a web app lets people do things.
A website is pages. An about page, a services page, some photos, your hours, a contact form. The content sits there and looks the same to everyone who visits. You update it now and then. Think of a restaurant's site: the menu, the address, a nice photo of the room. It informs. That's the job, and for a lot of businesses it's the whole job.
A web app is different. It remembers who you are, it changes based on what you do, and different people see different things. The moment your site has accounts people log into, or a booking calendar, or a cart, or anything that saves what a user did and shows it back to them later, you've crossed from website into web app. Online banking is the far end of it. So is a booking system, a members area, a store that tracks your orders.
The restaurant site that just shows the menu is a website. The same restaurant, the day it lets you reserve a table and log in to see your reservation, is running a web app.
Why the line is where the money is
Showing is easy. Doing is hard. That's the short version of why the price jumps.
A page that displays the same thing to everyone is a fraction of the work of a system that has to handle every different person doing every different thing, correctly, at the same time, without showing your data to someone else. The instant you let people do things, a pile of invisible questions comes with it. What happens when two people book the last slot at once? Where do customer passwords live, and how safe are they? What shows up if someone types the wrong thing, or tries something they shouldn't? A website rarely has to answer those. A web app is mostly those answers.
None of that work is visible when you look at the finished thing. It just quietly changes what you're buying, which is why the same three sentences from you can turn into two very different numbers.
Why "just add logins later" isn't little
A pattern I see often: a site gets built as a website, and then a few months in comes "can we just add customer accounts?"
It's a fair thing to ask, and it rarely lands as small. Adding the "doing" layer to something built only to "show" often means reworking the foundation, because the two are built differently from the ground up. It's the difference between adding a bookshelf to a room and adding a second floor to a bungalow. Both are "just adding," and only one of them touches the foundation.
This isn't a reason to never start small. It's a reason to say out loud, early, if the doing part is coming, so whoever builds it can leave room for the second floor instead of finding out after the roof is on.
How to tell which one you're asking for
You don't need the vocabulary. You need one question, asked about your own idea: does anyone log in?
If nobody logs in and every visitor sees the same thing, you're almost certainly asking for a website, and you should be quoted like it. Anyone charging web-app money to show your hours and your menu owes you an explanation.
If people log in, or the screen changes depending on who's looking, or the thing remembers what someone did last time, you're asking for a web app. That's not a warning, it's just the reality of what you want, and it should be priced and planned as its own kind of thing.
And if you're not sure, write down what you picture a customer doing on it, verb by verb. Browse. Book. Pay. Log in. Save. Upload. The verbs tell you which side of the line you're on faster than any label. Mostly looking is a website. Mostly doing is an app.
You're not being sold two versions of the same thing at two prices. You're looking at two different things that happen to share a word. Once you can see which one you're asking for, every quote you get starts making a lot more sense.