Website vs. web app: which does your business need?

People use “website” and “web app” interchangeably, and it doesn't matter until you're paying for one. Then the difference is the difference between a few weeks and a few months, and between a marketing tool and an operating tool. Here's the distinction I use with clients.

A website tells; a web app does

A website's job is to explain and persuade: who you are, what you offer, why someone should get in touch. Visitors read it. A marketing site, a landing page, a portfolio, a restaurant's menu-and-hours page — those are websites.

A web app's job is to get work done. Users log in, create and change data, and rely on it as part of their day: a customer portal, a booking system, a dashboard, an internal tool that replaced a spreadsheet. If people would be upset when it's down, it's an app.

Signs you need a website

• You want more inquiries. More calls, bookings, or messages from people who don't know you yet.
• Your current site is holding you back. It's slow, dated, hard to update, or embarrassing to send to a prospect.
• You're launching something. You need a place to point ads, social posts, and word of mouth.
• Customers keep asking the same questions. The site should already answer them.

Signs you need a web app

• A spreadsheet has become critical. The business runs on it, and more than one person edits it.
• You're copying data between tools by hand. Several subscriptions, none of which talk to each other, and a person in the middle.
• People need to log in. Customers or staff need to see something specific to them.
• The software is the business. You have a product idea, and the product is the thing you're building.

The gray area

Plenty of projects are a website with one app-like feature: a quote calculator, a client login for documents, an appointment booker. That's normal, and it's usually best built as a website with that feature added — unless the feature is the reason people come to you, in which case it's an app with a marketing page in front of it. The distinction matters because it changes how the project is scoped and what it costs.

Can one grow into the other?

Yes, if it's built with that in mind. I build sites and apps on the same stack — Next.js, TypeScript, Postgres — so a marketing site can grow a logged-in area later without starting over, and an app can get a proper public front door. What doesn't work well is starting on a page builder or template and trying to grow an application out of it. That path usually ends in a rebuild.

Not sure which you need?

That's a fine place to start. Discovery is free and usually settles this in the first conversation. Tell me what you're trying to accomplish — not what you think you need to build — and I'll tell you honestly which one fits.