How much does a web application cost – what the quote depends on
“How much does a web application cost?” is usually the first question. That is natural: before a company enters a project, it wants to know whether the budget has any chance of coming together.
An honest answer does not start with a single amount. It starts with scope: which problem the system should solve, who will use it, what it must connect to, and what has to work from day one. Only then does an application quote stop being a guess.
I do not publish a price list or ranges here. I quote every project individually. In this article I describe how I think about a quote, what a budget conversation looks like, and what is worth preparing before you ask for a proposal. I wrote the detailed complexity factors separately in the piece on what affects project cost.
Why there is no single price
“Web application” is a label that covers very different work. A panel in which one team handles requests is a different project from a system with customer accounts, payments and several integrations. In a brief both can sound similar: “an application with sign-in and a few screens.”
The number of screens says the least. A mockup with five views can be more expensive to build than fifteen simple lists and forms — if those five screens sit on roles, exceptions and connections to other systems.
That is why a quote “right away, based on the number of views” usually compares different things. A sensible quote describes the scope, not only the interface.
A practical example: two briefs can share the title “a panel for the company.” In the first, an internal team takes in requests, changes statuses and exports a list to a spreadsheet. In the second, customers create accounts, place orders or bookings, and payments plus a CRM connection sit in the background. That is not “a slightly bigger panel.” It is a different product responsibility, a different number of paths and a different quote.
A website is a different budget conversation
Before we talk about an application, it is worth making sure you actually need one.
A website shows the offer, builds trust and collects contact. An application runs a process: accounts, panels, statuses, sometimes payments. If the goal is more enquiries and a clear offer, we usually start with a company website — including when a product may appear later. A comparison of both paths is in web application or website.
Companies in Wrocław and the surrounding area often arrive with exactly this dilemma: a marketing site, or a system straight away. On the websites in Wrocław page I describe how we set that boundary.
This matters for the budget as well. A website quote and an application quote are two different conversations. Mixing them in one brief (“we want a website, but with panels, roles and an integration”) ends in proposals that cannot be compared honestly.
What an application quote depends on
In short: on the process, the data, the roles, the integrations, and the expectations for the first version and for care after launch. I expand that in the article on cost factors. Here I leave the short version that is usually enough to start the conversation:
- process — how many paths and exceptions the system has to handle;
- roles — who sees what, and what they must not be able to do;
- integrations — CRM, payments, a calendar or a partner API;
- data — whether we move history, and what quality it is in;
- product class — an internal tool, an MVP, or a product with customer accounts;
- life after launch — care, fixes, further development.
If a quote is missing one of these points, it is hard to say what you are actually paying for.
What the quote conversation looks like
You do not need a finished specification of dozens of pages. You need an organised outline.
I usually start with a few questions:
- Which problem should disappear after launch? (a spreadsheet, email, retyping data by hand, a request queue)
- Who will use the system, and what roles do they have?
- What does the process look like today, step by step — even as a list?
- Which systems should the application connect to, and is there test access or documentation?
- Are we moving historical data?
- What must work in the first version, and what can wait?
- How will we know after 30–90 days that the first version succeeded?
On that basis I come back with a proposed scope, written assumptions and a quote. If something is left unsaid, I prefer to name it outright (“I assume the import is from one spreadsheet, without cleaning the history”) rather than hide it inside a low figure.
An individual quote does not mean a vague answer. It means the amount comes from a described scope. When the scope changes, the quote changes too — that is normal, not a trick.
How the whole collaboration runs from the first meeting to launch is in what building a web application looks like from idea to launch.
How to think about budget: the first version and what comes later
The most expensive budget mistake is trying to fit “everything” into the first version. The cheapest sensible start is usually a narrow process that can be launched and checked in everyday work.
That is why I like to split the budget conversation into two parts:
- the first version (MVP) — the smallest scope on which someone actually works;
- development after launch — features that come from use, not from the full wish list in the brief.
Care sits on top of that: fixes, updates, looking after integrations. It is not an extra “if there is money left.” It is part of the cost of the first year.
If you have a budget range in mind, it is worth saying it outright. Not so the proposal can be “fitted to a number,” but so we can decide together what goes into the first version and what stays for later. An open budget makes the scope easier to choose. A hidden budget often leads to a proposal that is complete on paper and hard to sustain in practice.
That does not mean you must know the exact amount immediately. An order of magnitude and a priority are enough: whether a faster launch of a narrow process matters more, or a wider scope over a longer time. On that basis it is possible to shape a first version that makes business sense, not only one that “fits in a spreadsheet.”
How to compare proposals when the amounts differ a lot
When three application quotes differ several times over, the assumed scope usually differs, not only the rate. Before you compare the numbers, check:
- whether the proposal includes analysis, interface design, testing, launch and documentation, or only the build;
- which integrations and which data migration are inside, and which are options;
- what happens after launch: fixes, care, further development;
- who owns the code and the access after handover.
A cheaper proposal that skips an integration critical to the process is not cheaper — it is incomplete relative to your need. A wider list of questions is in the articles on comparing proposals and cost factors and on how to choose a company to build a web application.
What to prepare before you ask for a quote
The more concrete the description, the faster you get a proposal you can compare with another one.
A short note is enough:
- the goal in one or two sentences and a success criterion after 30–90 days;
- user roles;
- the process “as it is today” and “as it should be”;
- a list of systems to connect;
- whether we migrate data, and what quality it is in;
- a list of “must be in the first version” / “can wait.”
You do not have to know every answer. Gaps are information too — we write them down as assumptions and refine them in discovery.
If you would rather organise the idea first and only then talk about numbers, that is also a good start. Some companies arrive with a feature list, others with one pain (“every day we retype the same thing from email”). Both paths are fine, as long as we name clearly what is in the first version.
FAQ
How much does a web application cost?
There is no single amount. The quote depends on processes, roles, integrations, data migration, and whether the first version is a narrow MVP or a fuller product. A range is set after a conversation about scope.
What does an application quote depend on?
Above all on scope: which process we handle, who uses it, what the system connects to, whether we move history, and what care after launch should look like. The number of screens is the weakest reference point.
Can I get a quote immediately, without the details?
I can say, roughly, which league the project is in, but a concrete proposal without a description of the process and the assumptions will be a guess. A short outline is enough to start.
How much does an application cost compared with a website?
These are two different budgets. A website presents the offer and collects contact. An application carries out a process. If you are unsure which form you need, it is worth settling that first, and only then talking about the quote.
What is in the first quote, and what appears later?
The first quote should describe the scope of the first version: analysis, design, build, testing and launch, plus the assumptions. Development of further features and ongoing care are usually a separate part of the conversation — worth planning, not “quietly added later.”
Summary and next step
What a web application costs depends on the scope — not on the number of screens and not on one universal rate. The best quote appears when the process, the roles, the integrations and the boundary of the first version are visible.
If you have an idea for an application, or you want to organise the scope before a budget conversation, write. I will come back with questions, a proposed scope and an individual quote. I build web applications for companies in the development services offer.
Related materials
- Web applications & SaaS
- Web application pricing — what drives project cost?
- What building a web application looks like from idea to launch
- How to choose a company to build a web application? Software house, freelancer or no-code
- Web application or website — how to choose
- Website development
- Strony internetowe Wrocław