If you have asked a developer for a quote recently and wondered why the numbers seemed so different depending on who you spoke to, part of the answer might be that different people interpreted your brief as describing different things. "We need a website" covers an enormous range — from a five-page brochure site to a fully interactive platform with user accounts, data processing, and real-time functionality.
Understanding the distinction between a website and a web application is practically useful, not just semantic.
What is a website?
A website is primarily an information delivery tool. It presents content to visitors — who you are, what you offer, how to contact you, articles you have written, products you sell. Most of the interaction is one-directional: the site presents information, the visitor reads it. The content is largely static or changes only when an administrator updates it.
A standard business website, a portfolio, a blog, a news publication, an e-commerce store with standard checkout functionality — these are all websites. They may be sophisticated and well-designed, but the fundamental model is about presenting content to a visitor.
Technologies commonly used for websites include WordPress, Webflow, Squarespace, and static site generators like Next.js in static export mode. These are well-suited to the task and considerably less expensive to build and maintain than custom applications.
What is a web application?
A web application is primarily a tool that users interact with to accomplish something. Rather than reading content, users input data, trigger processes, and receive dynamic outputs. The system responds to each user's actions individually and often stores and retrieves data specific to that user.
Examples of web applications include: online banking interfaces, project management tools like Trello or Asana, learning management systems, booking platforms, customer portals, inventory management systems, and custom CRMs.
The key characteristics of a web application are:
- User authentication (log in, log out, user-specific data)
- Dynamic data — content changes based on who is viewing it or what they have done
- User input that is processed and stored
- Business logic running on the server, not just the browser
Building a web application requires more complex architecture than a website: a back end server, a database, API design, authentication systems, and careful thinking about data security. The development timeline is longer and the cost is higher — often significantly so.
Why the distinction matters for your project
If you brief a website designer on a project that is actually a web application, you will get a quote that either does not cover what you actually need or is based on assumptions about functionality that the designer has made without realising the full scope. This is one of the most common sources of miscommunication in digital projects.
Conversely, if you approach a software development agency with a project that is fundamentally a website, you may get quoted for a level of technical complexity that your project does not require — and pay accordingly.
Being clear about which you need, and why, leads to better conversations and more accurate quotes.
The grey area: websites with application features
Most real projects sit somewhere on a spectrum rather than being purely one or the other. A standard WordPress website might have a booking system plugin added — that is a website with a web application feature. An e-commerce site with a customer account portal where people can view their order history has application characteristics. A membership site with protected content and a user dashboard is moving firmly into web application territory.
When you are planning a project, map out the user journeys you need to support. For each step, ask: is the user reading content, or doing something? Are they logged in? Does the content change based on who they are or what they have done? The more "doing" and personalisation involved, the further along the web application spectrum you are.
Practical implications for cost and timeline
A brochure website for a small business: four to eight pages, contact form, blog capability. Typical cost £1,500 to £4,000. Timeline four to eight weeks.
A website with a custom booking system or client portal added: cost typically £4,000 to £10,000 depending on complexity. Timeline eight to sixteen weeks.
A full custom web application — a learning management system, a custom CRM, a booking platform with business logic: cost typically £10,000 to £40,000+. Timeline four to twelve months depending on scope.
These are illustrative ranges, not fixed prices. The variables are the complexity of the business logic, the number of user roles, the integrations required, and the scale of the data model.
Choosing the right partner
For a straightforward website, a good web design agency is the right choice. For a custom web application, you need a team with software engineering capability — front end development, back end development, database design, and ideally experience in the domain your application operates in.
At Ramdex, we work across both. We have built straightforward websites for local businesses and custom applications for education providers. We are honest about which category a project falls into and what it will realistically cost and take.
If you are trying to figure out what your project actually is, start a conversation with us at info@ramdex.co.uk or on WhatsApp at +44 7931 272489. We are happy to help you think it through before any commitment.