You need a website if people visit to learn about your business and then contact you, book, or buy. You need a web app if they log in and come back to do a job inside it, like managing orders or tracking data. A website typically costs $8,000–22,000 with a freelancer. A web app people pay for, $30,000–70,000.
The words get used loosely, and that causes real problems: a "website" quote for something that's actually software will be wrong by tens of thousands of dollars, and an "app" built for what should be a five-page site wastes money the other way. Below: how to tell which you need, what each costs, four real projects, the common mix-ups, and when you need both.
Website or web app: the short answer
You need a website when
People visit, then act
- Visitors need to understand what you do, then contact or buy
- Nobody needs an account to get what they came for
- Success means enquiries, bookings, sales, or being found on Google
- Most visitors come once, or a few times
You need a web app when
People log in and come back
- People log in and come back to their own data
- They do a job inside it: book, order, manage, track
- Your staff or customers use it daily, like a tool
- Success means active users, repeat use, or subscriptions
The cut
A contact form, a booking widget, or a blog doesn't make a site a web app. Those are features of a website. The line is crossed when people have their own data inside it that they return to, or when your team does its daily work through it.
The difference between a website and a web app
| Website | Web app | |
|---|---|---|
| Main job | Inform and convert visitors | Let users do a task, repeatedly |
| Accounts | Rarely | Almost always |
| What matters most | Speed, clarity, Google rankings | Reliability, data safety, ease of use |
| After launch | Occasional updates | Ongoing fixes and features |
| Examples | Clinic site, service business, store | Booking platform, SaaS, customer portal |
The difference shows up most after launch. A website can run for months with small updates. A web app is a product people depend on, so it needs someone looking after it: support for web apps starts at $2,000 a month with me, against $600–1,500 for a business website.
Website vs web app cost and timeline
My prices in US dollars. The ranges overlap in the middle, because a complex store can cost as much as a simple internal tool.
| Type | Typical range | Real projects |
|---|---|---|
| Marketing website (4–8 weeks) | $8,000–22,000 | — |
| Store or booking website (10–16 weeks) | $18,000–45,000 | — |
| Internal tool (4–10 weeks) | $15,000–35,000 | — |
| Web app people pay for (6–14 weeks) | $30,000–70,000 | — |
| Five real projects | — | Vet clinic website: $14,000; IoT website and dashboard: $20,000; Digital business card app: $25,000; Food brand store: $30,000; School platform and website: $32,000 |
Full breakdowns are in what a custom website costs and what a web product costs.
Four real projects: website, web app, or both
A website: Easy Pawsy
Easy Pawsy, a vet clinic, needed people nearby to find it on Google and book a visit. No accounts, no dashboard. A fast website with online booking, built in six weeks for $14,000, took bookings from about 20 to 120 a week.
A web app: a digital business card platform
Owners build a profile, share it by tapping an NFC card, and update it any time. That's a product: accounts, a profile editor, analytics, and paid plans. It took eight weeks and $25,000, and has 30K+ users. A brochure site couldn't have done that job, because every owner needs their own editable profile behind a login.
Both: Life9sys and Hongirana
Life9sys needed a website explaining three technical products, and software connecting their devices to a live dashboard: $20,000 over eight weeks. Hongirana, a school, needed a public website for parents and a platform for attendance, fees, and messages: $32,000 over ten weeks.
Mix-ups that lead to the wrong quote
Most wrong quotes come from one of three mix-ups. Spot yours before you ask for prices:
- "Website, plus a customer area". The customer area is a web app, and usually the bigger half of the job. Quoting it as a website add-on is how prices triple mid-build.
- "An app" for a five-page business. If nobody logs in, you need a website. Building it as an app costs more, and can make it harder to rank on Google.
- Both, without saying so. A public site and a logged-in product in one vague brief. Either the marketing pages eat the budget, or the product ships and nobody can find it.
Naming the right thing is the single cheapest way to get an accurate quote. It costs nothing, and it changes every number that follows. If you're not sure which one you have, describe what a typical user does on their third visit. If the answer is "nothing new", it's a website.
Signs your website is turning into a web app
Many businesses start with a website and slowly bolt things onto it until it's doing a web app's job badly. Watch for these:
- Customers email you for information they could look up themselves
- Staff copy details from website forms into spreadsheets every day
- You've added a members area with plugins that keep breaking
- Customers ask to see their past orders, bookings, or documents
- You pay for several tools that each hold part of the same data
Two or more of these usually mean part of your business now runs on software you haven't built yet. Keep the website for being found, and move the logged-in part into a proper web app, starting with the one job that eats the most staff time. That's often a customer portal or a booking and scheduling tool, and it can usually connect to the tools you already use rather than replacing them all at once. Whether to build that piece or buy a tool for it is covered in build custom software or buy SaaS.
When you need both a website and a web app
Most businesses with a product eventually need both: a public website that explains it and ranks on Google, and the product behind a login. They do different jobs, so plan them as two parts:
- Separate goals. The website wins visitors; the web app serves people who already said yes.
- Separate budgets and milestones.So one can't quietly eat the other.
- A clear link between them. Usually a login button on the site, and the app on its own subdomain.
- The right order. Often the website first, to be found and start conversations, then the app once you know what customers need.
One developer can build both if they're full-stack, as in the two examples above. What to put in the product's first release is covered in what to put in a first version. Keep the two visually consistent, with the same logo, colours, and fonts, so customers moving from the site into the app feel they're in the same place.
A brief that gets the right thing quoted
Answer these in a few lines each, and any developer can tell whether you need a website, a web app, or both, and quote the right one:
If questions two and four are both "no", you need a website, and it will cost less than you feared. If either is "yes", part of it is a web app, and it's worth knowing that before anyone quotes. Either way, send me your answers and I'll tell you which it is and what it would cost. If it's both, you'll get a price for each part, so you can decide what to build first.
