Web Application or Website? A Framework for Deciding

This question comes up in nearly every first conversation, usually phrased as "do we need a website or something bigger?" The honest answer depends on one thing: what is the person on the other end of the screen actually there to do?

A website is an information delivery tool

A website's job is to communicate. Visitors read, watch, and navigate to find information, then act on it elsewhere — call, email, walk into a shop, make a decision. The site itself doesn't hold their data, doesn't remember who they are between visits, and doesn't process anything on their behalf. That's not a limitation; for a huge number of businesses, it's exactly the right amount of technology.

A web application is a software product delivered through a browser

A web application's job is different: users don't just consume content, they interact with it to accomplish something. The system stores their state, processes their input, and returns something personalised — an order status, a dashboard, a booking, a calculation. If you can log in and see something different from what the next person sees, you're already in application territory, whatever the marketing page calls it.

Five questions that settle it

Does a visitor need to log in and see something specific to them? Does the system need to remember state between visits — a cart, a saved preference, a history? Does it need to process a transaction or a calculation, not just display information? Does more than one type of user (a customer and an admin, say) need a different view of the same data? Would the business break in a specific way if this stopped working for a day?

Two or more "yes" answers, and you're building an application, not a website — with everything that implies for cost, timeline, and the standards it needs to be held to. One or zero, and a well-built website is very often the right amount of technology, not a compromise on the way to something bigger.