What separates a website from a web application, how to tell which one your project needs, and why the answer affects budget and timeline.
By Kuzikode Intelligent Technologies5 November 20263 min read
"We need a website" can mean very different things. Some projects need a clear public website; others need a web application that people sign in to and use to get work done. Knowing which one you need makes it easier to plan the budget and timeline, and to compare quotations fairly.
A website informs
A website mainly presents information to visitors: who you are, what you offer and how to get in touch. Most visitors do not sign in. Content changes occasionally and is managed by your team through a content editor. Typical examples are company sites, service pages, portfolios and news sections. A contact form, a booking request or a small online store can all sit comfortably on a website.
A web app does work
A web application lets signed-in users create, update and manage their own data, often with different permissions for different roles. Think of a client portal, a loan management system, a school fees system, a dispatch board or an internal dashboard. It runs in the browser like a website, but behaves more like software.
Questions that tell you which you need
Do people need to sign in to see information that belongs to them?
Will users create or change records, such as orders, applications, jobs or invoices?
Are there different roles that see and do different things?
Does it need to follow a process, with approvals, statuses or notifications?
Does it need to connect to other systems, such as accounting software, payment gateways or an existing database?
If you answered yes to most of these, you are describing a web application. If not, a website is probably the right start.
Why it matters for budget and time
A website's scope is mostly content and design, so it can often be priced as a fixed package. A web app's scope depends on its rules, roles, data and integrations, so it needs a short discovery phase to agree what will be built before it can be quoted with confidence. Web apps also need ongoing care: security updates, backups and support for users.
Often the answer is both
Many organisations have a public website for marketing and a separate web app (or portal) for customers or staff. They can share the same branding and domain, and you can start with the website and add the application later.
Start with the problem
Describe the problem you want to solve and who will use the solution, rather than the technology. A good partner will recommend the simplest thing that works, and tell you when a package will do and when a custom build is worth it.