A professional services website
If visitors need to understand services, read credentials and make contact, focus on content, navigation and editing responsibilities.
Guide
Website or web application: how to scope the right project
A website mainly helps visitors find and understand information. A web application lets users carry out tasks with business data. Many organisations need both; the right scope depends on the work users must complete.
Compare the work users need to complete
| Consideration | Website | Web application |
|---|---|---|
| Main purpose | Explain the organisation, its services and how to make contact. | Let users create, update, approve or analyse business records. |
| Typical users | Customers, partners, applicants and content editors. | Staff, customers or partners carrying out a defined workflow. |
| Access | Often public, sometimes with restricted sections. | Often signed in, with permissions based on the work each user can do. |
| Data | Pages, media, enquiries and catalogue information. | Transactions, status changes, records and reports; often shared with other systems. |
| Testing | Content, navigation, accessibility, devices and enquiry routing. | Those checks plus business rules, permissions, data integrity and integration failures. |
| Ongoing work | Content updates, hosting, security maintenance and editor support. | Operational support, changes to business rules, integrations and user access. |
When does a website need application features?
A corporate site may include a quotation request, account area or booking process. The important question is what happens after submission: who checks it, which records change and which other systems need an update.
For example, a public product catalogue can be a website. Account-specific prices, purchase approvals and stock allocation add application requirements. These can share a site, but need a separate workflow and testing scope.
What determines the budget?
The label alone does not determine cost. Content volume, custom design, user roles, business rules, data migration and third-party connections all affect the work. Ask suppliers to identify assumptions, exclusions and ongoing costs in their proposals.
What should go into the brief?
- The tasks users need to complete and the teams responsible.
- The current forms, records and systems involved.
- Permissions, approvals and common exceptions.
- Content ownership, migration needs and acceptance criteria.
The first release should follow the business priority. There is no rule that a public website must be built before an internal system.
Three ways the scope can differ
Choose the scope from the task a user needs to complete. Some projects combine a public website with an application behind sign-in.
A customer service portal
If customers submit requests, upload information and track progress, define accounts, permissions, workflow states and the staff tools behind them.
A distributor website and portal
Public product information may sit beside account-specific prices and ordering. Scope the publishing and transaction journeys together, including their shared product data.
Website or web application FAQ
What is the main difference between a website and a web application?
A website mainly helps people read and find information. A web application lets them carry out tasks with records, permissions and business rules. The two can overlap: a corporate website may include a customer portal, booking flow or other application features.
Does a business need a website before building a web application?
No. The first project should address the business priority. A public website may help customers understand your services, while an internal application may solve a more urgent operations problem. Neither has to come first in every business.
Can we add application features to an existing website?
Sometimes. A login area, booking process or customer dashboard may fit the existing platform, or may need a separate backend. Review the code, hosting and data requirements first so the new feature does not depend on a platform that cannot support it.
Is a web application always more expensive than a website?
No. Cost follows the scope rather than the label. A large multilingual website with extensive content can require more work than a small internal tool. Compare design, workflows, integrations, migration and ongoing support when assessing proposals.
Does adding a login make a website a web application?
A login alone does not define the project. A site may simply restrict access to documents, or it may let users change records, submit requests and approve transactions. Scope the tasks, permissions and business rules behind the login rather than using the label to estimate the work.
How can we decide whether a website feature needs a separate application?
Look at the data it changes, the systems it connects to and the people who maintain it. A simple enquiry form may fit the CMS; a multi-step approval process may need its own application backend. Keeping a consistent user experience does not require every feature to share the same codebase.