Landing page, website, or web app — what does your business actually need?
The three things people call 'a website' are really three different products with different costs and timelines. Here's how to tell which one you need before anyone quotes you.
When someone says "I need a website," they usually mean one of three very different things — and the gap between them is the difference between a weekend and a quarter, between a few hundred dollars and a real budget. Pick the wrong one and you either overpay for capability you'll never use, or you build a brochure when you actually needed a product. So before you ask anyone how much, get clear on which one.
The three things people mean
| What you're building | What it does | Relative cost |
|---|---|---|
| Landing page | One page, one goal: capture a lead or a signup | $ |
| Website | Several pages, multilingual, built to rank and convert | $$ |
| Web application | Logins, dashboards, real data, real logic | $$$ |
| SaaS product | Multi-tenant, billing, accounts — software you sell | $$$$ |
The line that matters most is between the top two and the bottom two. A landing page and a website are content — they present, they persuade, they rank. A web app and a SaaS are software — they do work, hold state, and have to be correct. Crossing that line is where cost and timeline jump, because you're no longer paying for pages, you're paying for behavior.
When a landing page is the right call
A landing page is one page with exactly one job: get the visitor to do one thing. Book a call, join a waitlist, download the thing, buy the one product. No menu of distractions, no "about us" detour — just a clear pitch and a single action.
It's the right choice when you're testing an idea, running ads to a specific offer, or validating demand before you build anything bigger. It's the wrong choice the moment you have several things to say to several kinds of visitor — that's a website pretending to be a landing page, and it converts worse at both jobs.
When you actually need a website
A website is what most businesses mean and what most businesses need: a handful of pages that explain what you do, prove you can do it, and turn a stranger into an enquiry. The work that makes it worth paying for isn't the pages you see — it's the invisible 60%: responsive layout, speed, SEO, multilingual routing, forms that actually deliver, analytics, and the security and infrastructure that keep it fast and online.
This is the tier where "it's just a few pages" quotes go wrong. A marketing site that's meant to rank and convert is a different product from a template you fill in yourself — and the difference shows up months later in the enquiries you never got because Google never surfaced you.
When it's really a web application
The moment users log in, see data that's theirs, or the system has to enforce rules — pricing, permissions, workflows, state that has to stay correct — you've crossed from a website into a web app. Dashboards, booking systems, internal tools, customer portals, anything with accounts: that's software.
The cost jumps here for a real reason. A page either renders or it doesn't; an app can be subtly wrong — a permission leak, a double-charge on a retry, a race condition under load. That's why a web app is built with tests, a real database, and an architecture that won't collapse the third time you change it. Skipping that doesn't make it cheaper, it makes it cheaper now and far more expensive the first time it breaks in front of a customer.
And when it's a SaaS product
A SaaS is a web app you sell — many customers, isolated from each other, each on their own plan, billed automatically. Multi-tenancy, subscriptions, and the fact that a bug now hits every customer at once put it in its own tier. If that's what you're building, the architecture decisions made in week one decide whether you can grow — I wrote about doing multi-tenancy from day one precisely because retrofitting it later is the expensive path.
How to decide in three questions
- Does anyone log in? If yes, you're in web-app territory, not website territory — price and plan accordingly.
- How many things are you trying to say, to how many kinds of visitor? One thing to one audience is a landing page. Several is a website.
- Are you selling access to the software itself, to many customers? That's a SaaS, and it's a product decision long before it's a coding one.
Get those three right and the quote stops being a mystery — because you're finally comparing offers for the same thing.
If you're not sure which of these your idea actually is, that's the most useful conversation to have before any code gets written. Take a look at what I build, or just tell me what you're working on — I usually reply within a few hours.
Building something similar?
Tell me what you're working on. I take on a small number of projects at a time.