Website or web app: which does your business need?

A website mainly presents information: who you are, what you offer and how to get in touch. A web app lets people do things: log in, manage data, complete tasks and work together.

The line between the two is not always sharp, and many businesses end up needing both. But knowing which one you are really asking for makes the brief, the budget and the timeline far clearer.

Getting this right early matters because the two are built differently. A website is mostly about content, design and speed; a web app adds accounts, data and business logic, which means more design, more development and more testing.

A website’s job is to attract, inform and convert. It should load quickly, look good on every device, be easy for search engines to understand and make the next step obvious — a call, an enquiry or a purchase.

Most of its content is the same for every visitor, and the people who update it are usually your own team, through a content management system or simple edits.

Because most of the content is public, your website also carries most of your search visibility. Clear structure, fast loading and genuinely useful content help people find you in the first place.

• Company and service pages
• Portfolios, case studies and galleries
• Landing pages for campaigns
• Blogs and news
• Contact and enquiry forms

For an independent photographer, we built a creative portfolio website with smooth animations, a lightbox gallery and optimised image delivery. The challenge was keeping it fast while showing large, high-resolution images across a visually rich layout.

We built it with HTML, CSS, JavaScript and GSAP in three weeks. It delivered a 95+ Lighthouse performance score and helped the client secure three new commissions within the first month of launch. That is a website doing exactly its job: presenting the work well and turning visitors into enquiries.

Notice what it did not need: no user accounts, no customer records and no complex permissions. Keeping the build to what the site actually had to do kept it short and fast.

A web app is software that runs in the browser. Users usually log in, see information specific to them and take actions that change data. It needs a back end, a database, user accounts and often permissions that control who can see and do what.

• Client portals and dashboards
• Booking, ordering and management systems
• Internal tools for teams
• SaaS products
• Anything with user accounts and roles

Because a web app holds your data and processes, security, permissions and reliability become central to the design rather than extras.

For an enterprise client, we built a bespoke portal where users manage projects, review deliverables and communicate with teams in one place. The key challenge was a role-based permission system flexible enough for complex organisational hierarchies, without making the product hard to use.

It was built with React, Node.js and MongoDB over five months. It reduced client communication overhead by 50% and became the primary project management tool for three enterprise accounts. That is a web app doing its job: replacing scattered emails and files with one place to get work done.

Here the opposite was true. Accounts, roles, permissions and a database were the product, and most of the design effort went into making a complex structure feel simple to use.

Plenty of businesses run a website and a web app side by side. The website explains what you do and wins new customers; the web app serves people who are already customers or staff. They can share one design system, so moving from one to the other feels seamless.

• A marketing website with a client login to a portal
• An online store backed by an order management system
• A company website alongside internal tools for staff

If you are planning both, it often makes sense to launch the website first and build the web app in a second phase, once the processes it must support are clear.

If you answer "yes" to most of these, you are probably looking at a web app rather than a website:

• Will users need to log in?
• Will different users see different information?
• Will users create, edit or approve things?
• Do you need roles and permissions?
• Will it replace spreadsheets, email threads or manual processes?

If most answers are "no", a well-built website is likely the right — and faster — choice. Many businesses start with a website and add a web app later as their processes grow.

Not sure which side your idea falls on? Tell us what you want people to be able to do and we will recommend the simplest route that works. You can also try the project estimator at /pricing/ for a first view of timeline.