Website vs. web app vs. custom system: what do you actually need?
Website, web app, or custom system? A plain-English guide to telling them apart and choosing the smallest build that solves your problem.
Start with the job, not the label
The fastest way to overspend on software is to build a category instead of solving a problem. "We need an app" or "we need a portal" is a label — it skips the only question that matters: what job does this thing have to do? Once the job is clear, the right shape is usually obvious, and it's often smaller than you feared.
Here's how the three shapes differ in practice.
Website
A website's job is to be found and to be convincing. It tells people who you are, what you offer, and why to trust you — then nudges them to act (book a call, buy, sign up). The content changes occasionally; visitors mostly read, they don't do much.
- Best for: marketing, brand, lead generation, content and SEO.
- Signs it's enough: you need to look credible and capture interest, but nobody logs in to get work done.
Web app
The moment people log in and change data, you've crossed into web-app territory. A web app does work in the browser — a dashboard, an internal tool, a SaaS product. There's state, there are accounts, and the value is in what users can do, not just read.
- Best for: tools, dashboards, SaaS products, anything interactive behind a login.
- Signs you need one: you're tracking, calculating, or managing something that a static page (or a spreadsheet) can no longer handle.
Custom system
When several workflows, roles, and data sources have to live together — members and billing and scheduling and reporting, each feeding the others — you're looking at a custom system. It's a web app with more surface area: multiple user types, deeper data, and integrations with the tools you already run on.
- Best for: operations software, admin portals, internal platforms.
- Signs you need one: your team is stitching together spreadsheets, email, and disconnected apps to run the day, and the seams are starting to cost you.
At a glance
| Website | Web app | Custom system | |
|---|---|---|---|
| Main job | Inform & convert | Do work in-browser | Run an operation |
| Users log in? | Rarely | Yes | Yes — multiple roles |
| Data changes? | Occasionally | Yes | Constantly |
| Typical example | Marketing site | Dashboard, SaaS | Admin portal |
How to choose
Pick the smallest build that solves today's problem. A great website beats a half-built web app, and a focused web app beats a sprawling system nobody finishes. The shapes are a ladder, not a fork — plenty of products start as a marketing site, grow a web app behind a login, and only later become the system that runs the business.
Still unsure which one you need? That's exactly what our first call is for. See what we build, read MVP vs. full build to decide how much to ship first, or tell us what you're working on.