A test that settles most arguments
If anonymous visitors are the main users, you are in website territory. If signed-in users with different permissions are the main users, you are in application territory. A brochure site with a blog is a website. A client portal, a booking back-office, a dealer dashboard, an internal ops tool — those are applications that happen to use a browser.
Calling an application a “website” to make it sound cheaper is how you get a WordPress build that cannot do roles, audit trails or reporting, and then a second project to replace it.
What changes in the build
| Website | Web application | |
|---|---|---|
| Primary job | Explain, persuade, convert | Let people complete work correctly |
| SEO | Central | Usually irrelevant behind login |
| Performance target | Core Web Vitals, public pages | Snappy UI under real data volumes |
| Typical stack here | Modern site on a CMS or a small custom front | ASP.NET Core, SQL Server, proper auth |
| Failure mode | Nobody finds you | Staff invent a spreadsheet beside it |
Cost follows the job
A marketing site is a web development job. A system people work in is .NET development, and it should be estimated like custom software, not like a five-page brochure. If you need both — a public site and a logged-in product — they can share a brand and still be two builds with two definitions of done.