Article:

"We need a website" is one of the most elastic sentences in business. It can mean a five-page brochure, a searchable knowledge base, a customer portal with logins or a booking system. Each is technically a website, and each calls for different planning, budgets and people. Getting the category wrong is one of the quieter reasons projects overrun.

What a website is for
A website's core job is to publish content to the public and guide visitors towards an action: reading, enquiring or buying. Its complexity lies in structure, writing, page speed and search visibility. Editors change the content regularly, so a content management system sits at the centre. A small brochure site and a large editorial one belong in the same category, because the underlying job is the same: publish, organise and be found.

What a web application is for
An application's core job is to let people do something with data: log in, submit records, see views based on their permissions, trigger workflows. Its complexity lies in business rules, security, integrations and testing. The public-facing pages are often a minor part of the whole.

A quick test
Ask three questions. Does the main value depend on users logging in? Does the system need to apply business rules, such as approvals or calculations? Would a change to the underlying data alter what different users see? Yes to most means you are commissioning an application, and the team and budget should be scoped accordingly. No to most points to a website, where the priorities are content, design and search visibility.

Projects that need both
Plenty of organisations need a public site and a small portal. Split them in the brief. The public site suits website development services focused on content, CMS and technical SEO, while the application belongs with engineers who specialise in product logic and data. Separating the two stops a marketing site inheriting application-level complexity, and stops an application being budgeted like a brochure.

Clear categories make for clearer briefs and fairer quotes. Before requesting proposals, write one paragraph describing what visitors will do on the finished project. The right kind of build usually becomes obvious from that paragraph alone.