The three things I build overlap, and people often ask for one when they need another. The quickest way to tell them apart is to ask what the thing has to do.
A website: people find you and get in touch
If the main job is being found on Google, explaining what you do and getting enquiries, you need a website. Visitors don't log in. You update it through an admin panel, and nothing else has to connect to it.
Good for a trades business, a café, a consultant, or a new product that needs a page before launch.
A web app: people log in and do something
Once people need an account, it's a web app. Customers book and pay, staff update jobs, clients see their own documents. Underneath there's a database, logins with different permissions, and usually at least one connection to another service, such as payments or email.
Good for a booking system, a client portal, or an internal tool that replaces a shared spreadsheet.
Automation: a job nobody should be doing by hand
If the problem is a repetitive task rather than something customers see, automation is usually cheaper than either. A script reads the emails, fills in the spreadsheet or files the documents, and keeps a log of everything it did so you can check its work.
Good for copying order details between systems, sending invoice reminders, or renaming and filing PDFs.
Still not sure?
Start with the problem, not the product. Tell me what takes too long or what customers keep asking for, and I'll tell you which of the three solves it, including when the answer is none of them. The first call is free.