SaaS Product Builds
Website, web app or SaaS: what does your idea need?
A website shows information, a web app lets people do things, SaaS is how you sell it. Work out which one your project really is.
If your project mainly tells people something, you need a website. If people log in to do something, you need a web app. If you sell that web app to many customers on a repeat basis, you are building SaaS (software as a service). Most ideas fall clearly into one of these once you answer a few plain questions.
The three terms overlap, and that causes much of the confusion. Every SaaS product is a web app, and a web app is built with the same basic parts as a website. Agencies also use the words loosely. So treat the labels as a guide to what you must build, not as strict categories.
This post gives you a short answer, then a questionnaire you can finish in five minutes, then a way to start small.
The short answer
| Website | Web app | SaaS | |
|---|---|---|---|
| Main job | Show information | Let people do tasks | Sell a web app to many customers |
| Visitors | Read, call, fill a form | Log in, enter data, get results | Sign up, pay, use it again and again |
| Data | Mostly the same for everyone | Different for each user | Each customer's data is kept apart |
| Example | A clinic's page with timings and a contact form | A booking system the clinic staff use every day | The same booking system sold to many clinics |
A website is something people read. A web app is something people use. SaaS is a web app plus a way of selling and running it for many customers.
When a website is enough
A website is enough when the content is the same for every visitor and the only action is contact. Think of a company profile, a portfolio, a restaurant menu, a coaching page or a landing page for one product.
A website can still have some moving parts. A contact form, a blog, a gallery, a map and a WhatsApp button are all normal on a website. A visitor who fills a form and waits for your reply does not make it a web app.
If you only need to be found, explain what you do and get enquiries, start with a website. You can add more later.
When you need a web app
You need a web app when people must log in and the screen shows them their own information or lets them change it. Common signs:
- Staff or customers need accounts with different permissions.
- The page shows a user's own orders, files, invoices or records.
- People enter data that the system must store, check and report on.
- Your team currently does this work in spreadsheets, paper or long WhatsApp threads.
A web app does not have to be sold to anyone. A booking tool that only your own team uses is a web app. Many such tools are really internal software built around how your business works, which is the work described under custom software.
What makes something SaaS
SaaS describes how a product is delivered and sold. The customer does not install anything or own a copy. They use your hosted software through a browser, and they usually pay on a repeat basis. You run it, fix it and update it for everyone at once.
The same booking tool shows the difference. Built for one clinic and run by that clinic, it is a web app. Offered to many clinics, each with its own login and its own patients, paying every month, it is SaaS.
Note that a product is not SaaS just because it has a login or a payment page. The test is whether many separate customers share one product that you operate.
What SaaS adds
Compared with a plain web app, SaaS needs extra pieces. Each one is real work, so know them before you plan.
Accounts and teams. A customer is usually a company with several users. You need sign-up, login, password reset, invitations and roles such as owner and member.
Billing. You need a way to take repeat payments, issue invoices, handle failed payments and let customers change or cancel a plan. Tax and invoice rules depend on your country, so confirm them with your accountant.
Separate customer data. One customer must never see another customer's records. This is a design decision made at the start. It is hard to fix later, and it is also a security matter. Weak separation is also a security risk.
Running it for many people. You need backups, monitoring, a plan for outages, support and a way to release updates without breaking customers' work.
An admin view for you. Your own team needs a place to see customers, plans and problems.
If you want this, the SaaS development page describes the service.
Three questions to ask before you build
Answer each question honestly and note where it points.
- Will people need to log in to see or change their own information?
- No: you lean towards a website.
- Yes: you lean towards a web app.
- Will more than one separate business or group use it, each with its own data and its own payment?
- No: a web app or custom software for your own team is likely enough.
- Yes: you are describing SaaS.
- Have you tested the idea with real people, even by hand?
- Yes, people want it: build the smallest working version.
- No: do not build yet. Test it first, as described below.
The one-page questionnaire
Answer yes or no to each line. Count where your answers land.
- Is the content the same for every visitor? Yes points to a website.
- Is the only action contact, call or a simple enquiry form? Yes points to a website.
- Do users need their own account? Yes points to a web app or SaaS.
- Does the system store records that users create or change? Yes points to a web app or SaaS.
- Will different people see different screens or have different permissions? Yes points to a web app or SaaS.
- Is this tool for your own team only? Yes points to a web app or custom software.
- Do you plan to sell access to other businesses? Yes points to SaaS.
- Will customers pay on a repeat basis? Yes points to SaaS.
- Must each customer's data stay fully separate from the others? Yes points to SaaS.
- Do you want to keep improving the product for all customers at once? Yes points to SaaS.
Your recommendation:
- Yes only on questions 1 and 2: build a website.
- Yes on any of 3 to 6, but no on 7 to 10: build a web app, or custom software if it is for your team only.
- Yes on 7, 8 or 9: you are planning SaaS. Read the next section before you start.
If your answers are mixed, that is normal. Many products begin as a website with a small tool added, and grow into a web app later.
How to start small
Do not build all the SaaS pieces on day one. Build the one thing that proves people want the product.
- Write one sentence. "This helps [type of customer] do [one task] without [current pain]." If you cannot write it, the idea needs more thought.
- Do the task by hand first. Run it with a spreadsheet, forms and messages for a few real customers. This shows what they actually need.
- Start with a website that explains it. A simple page with a sign-up or enquiry form tells you whether anyone is interested.
- Build the core task only. Leave out extra reports, many roles and fancy settings. One task that works well beats ten that half work.
- Add billing when people ask to pay. Early users can be invoiced by hand.
- Design for separate customer data from the start, even if you have one customer. It is easier than redoing it later.
- Add features from real requests, not from guesses.
This order lowers the risk. You spend money on the parts that customers have shown they want.
Where to go from here
If your answers point to SaaS, SaaS development covers how a first version can be planned. If you only need to be found online, website development is the place to start. For a tool used only by your own team, see custom software.
