“We need a website” can mean anything from a five-page brochure to a platform that hundreds of companies log into every day. These are very different projects, with different teams, timelines and running costs. Picking the wrong one is expensive in both directions: over-build and you spend months on features nobody uses; under-build and you end up stretching a website plugin into something it was never designed to do.
Here is how to tell which one you actually need.
Three things that all get called “a website”
A website is mostly content, and it looks the same for every visitor. Its job is to inform, build trust and generate enquiries or sales. It can still include a lot: a content management system so you can edit pages, a blog, contact and booking forms, a product catalogue, multiple languages and solid SEO. But visitors mostly read, they don't log in and work.
A web application is software that runs in the browser. Users sign in, create and change data, and move through workflows: a customer portal, a booking system with your own scheduling rules, a dispatch dashboard, an inventory tool, a partner ordering system. It is built around your business and the people who use it, whether that's your staff, your customers or both.
SaaS (software as a service) is a web application that you sell to many other organisations, usually on a subscription. On top of everything a web app needs, it needs multi-tenancy (each customer's data kept separate), self-service sign-up and onboarding, subscription billing, plan limits, roles and permissions per customer, usage reporting, and the operational maturity to keep many paying customers happy at once.
Five questions that settle it
- 01Do people need to log in? If not, you almost certainly need a website.
- 02Do users create data that must be saved and shown back to them? Orders, bookings, records, files. If yes, you are in web app territory.
- 03Who are the users? The public (website), your own staff or customers (web app), or other businesses who will pay to use it (SaaS).
- 04Will more than one organisation use it with their data kept separate? That's the defining feature of SaaS.
- 05Is the software itself what you sell? If yes, it's SaaS. If it supports a business that sells something else, it's a website or web app.
A quick decision guide
- You want to be found, explain your services and get enquiries → a website, possibly with a CMS and blog.
- You sell physical or digital products to consumers → an e-commerce website. A well-configured platform often beats custom code here.
- Your team runs on spreadsheets, WhatsApp groups and manual follow-ups → an internal web app that turns those workflows into software.
- Your customers need to check status, upload documents or reorder → a customer portal (web app), often alongside your existing website.
- You've solved a problem that other businesses in your industry also have, and they'd pay for it → SaaS, but validate demand before you build it.
Most real businesses end up with a combination. A marketing website that sends sign-ups into a web app is the norm. Many successful SaaS products started as an internal tool that one business built for itself and later opened to others.
What actually drives cost and timeline
We won't quote numbers here, because without a scope any number is a guess. What we can tell you is which factors move the estimate the most, so you can make informed trade-offs:
- Number of user roles. Admin, staff, customer and partner each need their own screens and permissions.
- Number of distinct workflows. Each one (booking, approval, invoicing, refunds) needs design, logic, edge cases and testing.
- Integrations. Payment gateways, WhatsApp, accounting or ERP systems, GST e-invoicing, shipping, maps, SMS. Each external system brings its own quirks.
- Data migration. Moving years of records out of spreadsheets or an old system is frequently underestimated.
- Custom design vs. an adapted template. Both are valid; they are different amounts of work.
- Platforms. Web only, or web plus iOS and Android apps.
- Admin and reporting. The back office your team uses every day is often as big as the customer-facing side.
- Security and compliance. Handling payments, health or financial data, or personal data at scale raises the bar.
- Content. Who writes the copy and produces the images, and how much of it there is.
Do you also need a mobile app?
Often, not at first. A responsive web app works well on phones and can be installed to the home screen as a progressive web app. A native or cross-platform app earns its place when you need reliable push notifications, offline use, device hardware such as the camera, GPS or Bluetooth used heavily, or when your customers expect to find you in the App Store and Play Store. If you're unsure, start on the web and add apps once usage proves the need.
Common mistakes to avoid
- Building SaaS before validating demand. A website, a waitlist and a manual service behind it can prove whether people will pay, long before you write billing code.
- Forcing a website builder to behave like an app. Ten plugins held together with workarounds become fragile and slow. If users log in and manage data, plan for a proper application.
- Underestimating the admin panel. Your team will spend more hours in it than customers spend in the front end.
- Bolting on multi-tenancy later. If there's a real chance the product will serve several organisations, design for separated data from the start. Retrofitting it is painful.
- Specifying features instead of outcomes. “We need a dashboard” is vague. “Managers need to see overdue orders each morning” is buildable and testable.
- Putting everything in version one. Launch the smallest version that solves the core problem, then let real usage decide what comes next.
- Not owning your accounts and code. Whatever you build, the domain, hosting, repository and app store accounts should be in your company's name.
How to brief a developer
You don't need a technical specification to get a useful estimate. A good brief fits on one page:
- The problem in one paragraph, and who has it.
- The types of users and what each one needs to do.
- The three to five workflows that matter most.
- Systems it must connect to, and what you use today.
- Any hard deadline and the reason behind it.
- What success looks like six months after launch.
A good development partner will turn that into a written scope and tell you honestly whether you need a website, a web app or SaaS, even if the answer is the smaller project.
If you'd like help working out which one fits, tell us what you're planning, or run through our project estimator to get your requirements down in a structured way.
Planning something similar?
Tell us what you're building — you'll get a written scope and a fixed quote within 24 hours.