"I need a website" and "I need a web app" sound similar in a sales conversation. They're not. The first one might cost $1,500 and take three weeks. The second might cost $25,000 and take four months. Same client, same domain — completely different work.
Here's the framework I use to figure out which one a project actually needs.
The simple definition
A website mostly shows information. Visitors read, scroll, maybe submit a contact form, then leave. The site is the same for everyone.
A web app does work. Users log in, perform actions, see personalized data, and the app remembers state between sessions. The page is different for every user.
The five-question test
Ask these five questions about what you're building. Count the "yes" answers.
- Will users need to log in?
- Will users see different content based on who they are?
- Will users save, edit, or delete data that persists across sessions?
- Will the site need an admin dashboard?
- Will users perform repeated actions, not just one-time submissions?
If you said yes to 0–1: you need a website.
If you said yes to 2–3: you're in the middle (a CMS-driven site, an e-commerce store, or a basic SaaS).
If you said yes to 4–5: you need a real web app.
Examples
| Project | Type | Why |
|---|---|---|
| Restaurant homepage with menu | Website | Same content for everyone. |
| Restaurant QR-code ordering system | Web app | Each table has live order state. |
| Photographer's portfolio | Website | Showcase, contact form, that's it. |
| Photographer's client gallery with proofing | Web app | Login per client, comments, downloads. |
| Local clinic info site | Website | Hours, services, contact, blog. |
| Clinic appointment booking platform | Web app | Schedules, availability, notifications. |
| Single-product Shopify store | In-between | Light app, but mostly a buy-now flow. |
| Multi-vendor marketplace | Web app | Logins, dashboards, payments, escrow. |
The cost difference
A website is mostly content + presentation. A web app is content + presentation + auth + database + business logic + admin tools + ongoing maintenance.
- Website: $500 – $5,000 typical, 1–6 weeks.
- Web app MVP: $5,000 – $25,000 typical, 6–14 weeks.
- Production-ready SaaS: $20,000 – $100,000+, 3–9 months.
The cost gap isn't the developer being greedy. It's the work. Auth alone is a week. Building an admin dashboard is another week. Payment integration is a week. Email notifications, password reset, role-based permissions — each is multiple days. None of those exist on a website.
The middle ground
A lot of projects sit in between. Common examples:
- CMS-driven business site. 90% website, 10% admin app for content editing.
- Shopify or WooCommerce store. Pre-built web app, you customize the front.
- Booking embed. A booking app from Calendly or similar embedded into a website.
- Form-driven workflow. A website with one heavy form that triggers automation.
For these, you can often save 60% of the budget by using a hosted tool for the app part and a custom site for the public-facing part.
How to decide
If you're not sure which side of the line your project falls on, the cheapest answer is to start with the website. Ship it. See if real users want the app features before you build them. I've watched founders spend $40,000 on a custom dashboard for a product nobody uses, when a $3,000 landing page + Calendly + a Google Form would have validated the same idea in two weeks.
What I recommend
- If you're early: ship a website. Validate before you build dashboards nobody asked for.
- If you have real users with real workflows: build the app. Don't try to fake it with form embeds forever.
- If you're in the middle: use SaaS tools for the app parts (Notion, Airtable, Tally, Cal.com) and put your budget into the public-facing site.
Need help deciding?
Send me what you're building at m2hgamerz.prince@gmail.com. I'll tell you honestly which side of the line your project sits on. If you don't need a custom build, I'll tell you that too — usually with a list of cheaper hosted alternatives.