You need a website if visitors mainly read information and contact you. You need a web app if people log in and do something with their own data, such as managing bookings, orders or documents. Many small businesses need a website first and, at most, one small app-like feature. This guide helps you decide.
The difference in plain words
Both open in a browser, so they look similar from outside. The difference is what the visitor does there.
- A website informs. Every visitor sees the same pages: services, prices, opening hours, contact. The visitor reads and then calls, writes or books.
- A web app lets people work. Each user sees their own data after logging in. They create, change and save things. Online banking, a webmail inbox and a booking system are web apps.
| Point | Website | Web app |
|---|---|---|
| Main purpose | Inform and win enquiries | Let users complete tasks |
| Content | The same for everyone | Different for each user |
| Login | Usually none | Usually required |
| Data stored per user | Little, for example a form entry | A lot: accounts, orders, files |
| Effort to build | Lower, often weeks | Higher, often months |
| Effort to run | Low | Ongoing: security, backups, support |
The line is not sharp. A website with a booking tool is a website with one app-like part. That middle ground is where many small businesses end up.
Examples from small businesses
A website is enough for:
- A painter who shows services, photos of past work and a quote request form.
- A restaurant with menu, opening hours, location and a phone number.
- A tax adviser who presents the team, the services and a contact form.
A website plus a ready-made tool fits:
- A hair salon that embeds an existing online booking service.
- A bakery that takes pre-orders through a standard shop system.
- A trainer who sells course places through a ticketing service.
A web app makes sense for:
- A cleaning company where customers log in to see their schedule, change dates and download invoices.
- A workshop where staff record jobs, parts and hours on a tablet and the office sees it live.
- A wholesaler whose business customers log in to see their own prices and reorder with two clicks.
Note that two of the three app examples solve an internal problem. Many useful web apps are never seen by the public. They replace a spreadsheet that has grown too big.
Five questions that decide it
- Do users need to log in? If nobody needs an account, you almost certainly need a website.
- Does each user see different data? Their own orders, appointments or documents point to a web app.
- Do users create or change data that must be saved? A contact form does not count. A customer who edits a recurring order does.
- Is there a process with several steps and rules? For example: request, approval, scheduling, invoice. Rules mean logic, and logic means an app.
- Does a ready-made product already do this? If yes, use it first. Building your own is only worth it when the standard tools really do not fit.
How to read your answers:
- All no: a website.
- Yes only to question 5, or one or two yes answers that a standard tool covers: a website with an embedded tool.
- Yes to questions 1 to 4 and no fitting product: a web app.
Cost, time and upkeep
A web app is not a bigger website. It is a different kind of project.
- Planning takes longer. For a website you list pages. For a web app you describe who may do what, in which order, and what happens when something goes wrong.
- Testing takes longer. Every role and every path through the app must be tried.
- Security matters more. As soon as you store customer accounts and personal data, you are responsible for protecting them. Data protection rules differ by country.
- It is never fully finished. Users ask for changes, browsers change, and software needs updates. Plan a budget for the time after launch.
As a rough picture, a simple website is often done in a few weeks, while a web app often takes a few months, depending on scope. These are not fixed numbers. For price ranges and cost drivers, see the guide on what a small business website costs.
Start small: a sensible path
If you are unsure, do not start with the largest version. This order keeps the risk low:
- Build a clear website. It brings enquiries and shows what customers really ask for.
- Add ready-made tools. Booking, shop, payments and newsletters exist as products with a monthly fee. Test them for a few months.
- Write down where the tools fail. Collect concrete cases: "Customers cannot move a recurring appointment themselves."
- Build only that missing part. A small web app for one clear task is cheaper and safer than a big one for everything.
Before you ask for quotes, describe the task in one sentence per user group:
[Who] should be able to [do what] so that [result]. Today this happens by [phone, email, spreadsheet] and takes about [time] per week.
If you cannot fill in this sentence, it is too early for a web app. If you can, you have the start of a good brief. Astranode builds both websites and web apps, custom, with a fixed quote in writing before work starts.
A website informs, a web app lets users work with their own data. Start with a website and ready-made tools, and build a custom web app only for the part that no standard product covers.