Key answer: A website communicates information – it presents your company, offer and content. A web application lets the user act – log in, store data, manage processes; it is a program running in the browser. The boundary can blur (a site with a configurator is already part app), but the budget difference is real – a company website runs €2,500–18,000, a web application starts at around €10,000, and a SaaS product MVP costs €20,000–60,000.
Table of contents
The short answer
A website communicates information: who you are, what you offer, how to get in touch. A web application lets users act: log in, store data, manage processes – it's a program in the browser. The distinction has practical consequences: different technologies, a different build process and budgets that can differ by an order of magnitude. If you're planning a project and don't know which path is yours, this article will help you decide before you talk to any vendor.
What a website is
A website presents content: your offer, articles, contact details. The user reads, looks around, perhaps fills in a form. Websites are built for search visibility and fast loading, and their content is managed through a CMS. A typical company website costs €2,500–6,000; a larger site €6,000–18,000 – we break this down in detail in our website pricing guide.
What a web application is
A web application is a tool: the user has an account, works with data, completes tasks. A client panel, a booking system, an invoicing tool, an analytics dashboard – all of these are web applications. Underneath run business logic and a database, and besides the interface you design user roles, permissions and security. Smaller internal tools start at around €10,000, and an MVP of a commercial SaaS product typically costs €20,000–60,000.
Five questions that settle the choice
- Will users log in? Accounts, data and action history mean an application. Presenting an offer means a website.
- Does the product store and process user data? If so, it's an application, with consequences for security and GDPR.
- Where will users come from? From search engines, for content: a website. From a "log in" link in their daily work: an application.
- How often does the content change? Updated pages and a blog are CMS territory. Data changing in real time means an application.
- What's your starting budget? If it's under €10,000, start with a website that validates the idea before you invest in a product.
The middle ground: a website with app features
The boundary blurs. A site with a product configurator, a quote calculator or a client area is a hybrid – and a frequent, sensible first step. You start with a website plus one app-like feature, measure whether users touch it, and only then build the full product. We often recommend this path to clients who come "for an app" and discover at the workshop that something half the price will test their hypothesis.
What this means for your budget
The most common mistake is buying an application when you need a website (you overpay several times over), or a website when you need an application (you get a shell you'll throw away anyway). The second trap: quoting an application without a scoping workshop. "A web application" says as much as "a building" – without a feature list, any figure is fortune-telling. That's why we start product builds with a workshop and an MVP that leaves you with a concrete scope and budget.
Not sure which side of the line your idea is on? Describe it to us and we'll advise honestly – including when the answer is "a website is enough".