Two clients came to me in the same week. Both said they needed a "website."

Client A needed a company website — who they are, what they do, how to contact them. 8 pages. Brochure. Static content. A website.

Client B needed a platform where their customers could log in, upload documents, track application status, and receive automated notifications. 15 user roles. Complex workflows. A web application.

Both called it a "website." The difference in what they needed was S$8,000 vs S$60,000. Getting this wrong — in either direction — is an expensive mistake.

The Simple Distinction

A website presents information. Visitors read it. They might fill a contact form. But the core function is: display content to people.

A web application does something. Users log in, create things, process data, trigger actions. The content is dynamic — it changes based on who is logged in and what they've done. The core function is: help users accomplish a task.

Examples to calibrate:

Website: your company homepage, a portfolio, a blog, an informational resource, an event registration page (basic)
Web application: an e-commerce store, a customer portal, a booking system, a project management tool, a CRM, any system where users log in and manage their own data

The grey areas: an e-commerce product catalogue (website) vs an e-commerce checkout (web application). A public blog (website) vs a content management system for editors (web application).

Why It Matters for Your Budget

Websites are primarily a design and content exercise. The technical complexity is relatively low. Cost drivers: number of pages, design quality, whether it's template-based or custom.

Web applications are primarily an engineering exercise. Every user-facing feature requires backend logic, database design, security architecture, and testing. Cost drivers: number of user workflows, data complexity, integration requirements, security requirements.

A well-designed website: S$5,000–S$20,000
A simple web application (single workflow, basic auth): S$20,000–S$45,000
A complex web application (multiple roles, integrations, real-time): S$60,000–S$150,000+

Paying web application rates for a website is waste. Building a website when you need a web application is a project that will be thrown away and rebuilt.

Different web interfaces showing complexity levels
The diagnostic question: does a user "do something" in your product, or do they just read it? The answer determines whether you need a website or a web application.

The Diagnostic Questions

To classify what you actually need:

  1. Do users log in? If yes: web application. If no: almost certainly a website.
  2. Is there user-generated data? Things users create, submit, or modify that persist and affect other users' experiences. If yes: web application.
  3. Does the content change based on who's looking at it? If the same page shows different content to different users: web application.
  4. Are there automated processes? Notifications, calculations, state changes triggered by user actions or time. If yes: web application.

If your honest answers are all "no" — you need a website. If any answers are "yes" — you need (at least part of) a web application.

The Hybrid Reality

Most mature digital presences have both.

A Singapore B2B company might have:

  • A marketing website (who we are, services, blog, contact form) — website
  • A client portal (project status, document access, invoices) — web application

These can be different products on different domains (website on nicktung.com, portal on portal.nicktung.com) or integrated under the same domain (website for unauthenticated visitors, web app revealed after login).

The important thing is to know which part is which, so you scope and budget them separately.

Technology Stack Differences

This is where the cost difference comes from.

Website: HTML/CSS/JavaScript, possibly a CMS (WordPress, Webflow, Contentful) for content management. Hosting on a CDN (Vercel, Netlify, Cloudflare Pages). No database required. No authentication required.

Web application: Frontend framework (React, Next.js), backend API or serverless functions, database (Postgres/Supabase, MySQL), authentication system, hosting with server compute (Vercel + Supabase, AWS, GCP). Each component adds cost and complexity.

When to Build vs When to Use a Platform

Before building a custom website or web application, check whether existing platforms cover your needs:

For websites: WordPress (most flexible, needs maintenance), Webflow (best design control, no development required), Framer (design-focused, fast to launch), Squarespace (easiest for non-technical users)

For web applications: Bubble (no-code application builder), Retool (internal tools), Softr (apps built on Airtable), Glide (apps built on Google Sheets)

No-code platforms have real limitations. They're appropriate for early-stage validation and simple use cases. For complex workflows, performance requirements, or integration-heavy systems, custom development wins on long-term cost and capability.

Not sure which category your project falls into? Describe what you need to accomplish — we'll tell you whether it's a website, a web application, or something in between, and what the honest cost range looks like.