They Look Similar, But They're Different Things
Websites and web applications form a spectrum. One address can combine information pages, sign-in and an ordering process. For budgeting, naming tasks, data and responsibilities is more useful than drawing a hard boundary between two labels.
What Is a Website
A website presents information. A visitor comes, reads what you offer, and either contacts you or leaves.
Examples:
- Company website with portfolio and contact
- Restaurant page with menu
- Blog or media website
- Campaign landing page
The main task is finding and understanding information. Update frequency does not decide the category: a news site can change content every minute.
What Is a Web Application
A web application solves a specific task. Users actively work, with or without signing in, entering data, tracking metrics, managing orders, communicating with team members.
Examples:
- Internal dashboard for order tracking
- SaaS product (like Trello, Notion, Fakturoid)
- Customer portal with order history
- Booking system for reservations
- E-learning platform with courses and tests
- Custom CRM for a sales team
Key characteristic: users interact with the application, creating and modifying data.
When a Website Is Enough vs. When You Need an App
| Need | What to specify |
|---|---|
| Presentation and enquiries | Content, contact and reliable enquiry delivery |
| Sign-in and order history | Accounts, roles and data-access checks |
| Booking or calculation | Input validation, success and error states |
| CRM or ERP integration | Data interface, failure handling and integration owner |
| E-shop | Product content and a transaction flow in one solution |
What to check in the technical brief
An information site can be dynamic, and an application can perform some tasks entirely in the browser. Sign-in and a database are not mandatory features of every application. Describe the actual flow: where data comes from, who can change it, what is saved and how failures are handled. Security, accessibility and reliability belong in both kinds of delivery.
When Companies Move from Website to Application
Typical scenario: a company starts with a website, gets customers, and gradually discovers they need:
- Customer portal, customers want to see order history, invoices, project status
- Internal tool, the team wants to reduce repetitive work; a pilot on the actual process must establish any saving
- Automation, repetitive processes that consume time and generate errors
- SaaS product, the idea for their own software-as-a-service
Worked example: From information to a saved booking
illustrative example
| Step | Information page | Booking application |
|---|---|---|
| Request | Show opening hours | Book Tuesday at 10:00 |
| Server | Return page content | Validate slot and input |
| Data | No new booking | Save booking R-104 |
| Result | Workshop contact details | Confirmation of specific slot |
Illustrative flow; an informational website can also integrate booking functionality.
What It Costs
The prices are my entry levels; the exact amount follows from the scope:
| Type | Price | Time |
|---|---|---|
| Business website | from €800 | depends on scope |
| Web application (MVP) | from €3,200 | 5-8 weeks |
| Production application | from €7,200 | 8-14 weeks |
| Enterprise solution | from €16,000 | 14-30 weeks |
Can You Combine Both?
Yes, and I do it often. A company website that presents the business (SEO, marketing), alongside a customer portal or internal dashboard that handles specific processes. The two parts can share design and some services. Shared sign-in and infrastructure are separate architectural decisions, not automatic consequences of using React or Next.js. Why Next.js? I explain in Why Next.js for Business Websites.
How to Decide
Ask yourself three questions:
- Do users need to work with data, or just read information?
- Am I dealing with a repetitive process that takes hours of manual work?
- Do I need individual content for each logged-in user?
A yes identifies a needed capability. First investigate an existing service or integration with your current website. A custom application makes sense when available solutions cannot reasonably support the process and the benefit justifies development and maintenance.
Not sure? Get in touch. I'll review your case and tell you what makes sense, no commitments. Interested in pricing? Check out my web application development page.