A website informs and converts; a web app lets users log in and do something repeatedly. If your visitors mostly read, compare, and contact you, you need a website. If they need to track, manage, book, or process something behind a login, that is a web app. Most businesses start with a site and add an app only when a real workflow — not a wish — demands it.
What's the actual difference?
A website is mostly pages: content you publish for visitors to read and act on. A web app is mostly state: data that changes per user, behind authentication — dashboards, portals, tools. The tell is simple. If the value is in reading something, it's a site. If the value is in doing something repeatedly, it's an app. Many products need both: a marketing site out front, an app behind the login. The clearest test is the login itself. If users never need an account, you almost certainly need a website. The moment each user has their own private data and state, you've crossed into app territory. Plenty of businesses run for years on a great website alone and never need an app — and that's a feature, not a gap.
When does a website do the job?
A website is the right call when your goal is to be found, explain what you offer, and convert visitors into leads or sales. Brochure sites, landing pages, marketing sites, and most small-business presences live here. It's faster and cheaper to build, and for most first steps it's all you need. It's also the front door an app will eventually sit behind, so it's rarely wasted work. If what you need is to be found and to sell, a site does the whole job. See my websites service.
When do you actually need a web app?
You need a web app when users repeatedly do something pages can't handle: a client portal, a dashboard, a booking system, an internal tool. The signal is per-user state and logged-in workflows. It's a bigger, more expensive build than a site — auth, a real data model, per-user views, more testing — so it should earn its place. Build it when a real, repeated task justifies it, not on a hunch. A good gut check: could a spreadsheet or an off-the-shelf tool do this for now? If yes, you're not ready for a custom app; if you've already outgrown those, you probably are. That's my web-apps service.
Can a website grow into a web app?
Yes, and that's usually the right sequence. Start with the website that gets you found and selling, then add app functionality behind a login once a repeated workflow clearly justifies it. Built sensibly, the two live together — the marketing site out front, the app behind the login — sharing a domain and a look. You don't have to choose forever on day one; you choose what to build first. The mistake is paying for the app before the website has even proven there's demand to serve.
What does each cost, roughly?
Very different numbers, which is why the choice matters. With me, a website is $1,800 (the 2026 rate), fixed; a custom web app is quoted from your roadmap and climbs with roles and integrations. Either way, the first step is the $399 assessment, credited in full. The gap is the point: a site is cheap enough to launch on a hunch, while an app should wait for evidence that the workflow is real. When budget is tight, that difference alone often answers the question — prove demand with a site first, then invest in the app once it's clearly earning its place.
How do I decide with a client?
I look at what the user must do, not what sounds impressive. If the job is acquisition and information, I build a site. If it's a repeated logged-in workflow, I scope an app — usually starting with the single core flow. The smallest thing that proves the need comes first. If both are genuinely needed, I sequence them — site first to start earning, app next — so you're never paying for capability ahead of demand.
Related web app guides
Next, read what a client portal should do, signs you've outgrown spreadsheets, and how much a web app costs.
