How much does a web application cost?

In our offer, a bespoke web application costs 15,000–35,000 PLN net for an MVP, 35,000–90,000 PLN net for a business application with integrations, or 90,000–250,000 PLN net for an extensive custom system. We price maintenance at 1,500–6,000 PLN net per month.

These are our indicative ranges as of August 2026, not market averages. The final price depends on the agreed scope and assumptions.

Ranges by project scale

Scope	What it means in practice	Indicative time	Net range
MVP / starter application	one primary flow, one user role, available data, and a limited number of integrations	4–6 weeks	15,000–35,000 PLN
Business application	several roles, an admin panel, 2–4 integrations, reporting	2–4 months	35,000–90,000 PLN
Custom system	many modules, permissions, data scale, migration from a legacy system	from 4 months	90,000–250,000 PLN
Maintenance and development	hosting, monitoring, fixes, incremental development	ongoing	1,500–6,000 PLN/month

If you are asking “can we afford this?”, the cheapest route to an answer is not a quote for the whole thing but a quote for the first stage. More on that below.

Nine factors that move the estimate

Their impact depends on the particular product, so this is a pricing checklist rather than a universal ranking:

1. The number and quality of integrations. Good documentation, a test environment, and predictable errors reduce work. No documentation, restrictive limits, and unusual error handling raise uncertainty, so an integration is worth checking technically before a fixed quote.
2. The permission model. An application with one role and one with five roles plus permissions at the level of individual records are two different projects, even when their mock-ups look similar.
3. Data migration from a legacy system. Format, completeness, duplicates, mapping, and the cutover method must be checked. Clean data with a documented export can be simple; inconsistent data needs separate cleansing and tests.
4. Security and compliance requirements. Personal data, auditability, and processing in a specified location add architecture work, not an “extra option”.
5. Scale and performance. It is not only the number of users that matters, but concurrency, data size, operation type, and required response time. Not every increase requires a different architecture immediately.
6. The AI layer. An agent, semantic retrieval, or content generation is a separate module with its own ongoing costs. We break this down in how much AI implementation costs in a company.
7. The scope of interface design. A custom visual language, accessibility, complex states, user research, and many screen variants expand the scope compared with a simple tool based on a ready component system.
8. Decision-maker availability on your side. Waiting for decisions about data, scope, and acceptance can extend the schedule and block dependent work.
9. The quality of the incoming specification. An estimate for a project described in one paragraph contains more assumptions. A provider should disclose them, price a discovery stage, or offer a range rather than pretend certainty.

The ninth point can be reduced through discovery and planning. Our workshop with a direction document costs 3,000–8,000 PLN net and turns a general description into assumptions, scope, and acceptance criteria. It can reduce an uncertainty buffer, but may also reveal a requirement that raises the price.

Post-launch costs that are not visible in the quote

• Server and infrastructure. A VPS or cloud, database, backups, transfer, monitoring, and environments. The cost depends on volume, availability, and security requirements.
• Dependency updates. Libraries, the operating system, and external services change. Regular small updates reduce the risk of an accumulated migration and security gaps.
• Observability and alerts. Their cost depends on criticality and response time. Without suitable signals and someone to receive alerts, the first information about an outage may be a user report.
• Development. An application people use generates ideas. That is a good problem, but it needs to be planned in the annual budget.

How to buy while limiting risk

Gates instead of one large decision:

Discovery and plan (3–8 thousand PLN net) → fixed-price MVP (15–35 thousand PLN net) → development by scope → maintenance.

Each stage has its own value and its own “continue or stop” decision. After discovery, you have a document you can implement anywhere. After an MVP, you have a working agreed scope and data from initial use; its strength depends on the number and fit of users and observation time.

Staging limits the size of a decision made before collecting implementation data. Our MVP in 4–6 weeks is sold at a fixed price for a defined scope; later stages can be priced after verifying assumptions.

Why quotes differ severalfold

Three common reasons worth checking before deciding:

• A different scope behind the same word. An “admin panel” can mean three screens or thirty.
• Production included or excluded. Deployment with monitoring, backups, and proven restore-from-backup is real work. A quote without it is cheaper because it covers something different.
• A different delivery model. An in-house team, partners, and subcontractors can work well or poorly. Check who will actually perform the work, who owns quality, and whether a staffing change affects price, continuity, or code rights.

Before choosing a provider, ask for the people assigned to the project, the review and testing method, production responsibility, subcontractor rules, code rights, and a handover plan.

When not to build an application

• When a ready-made tool covers the key requirements. Compare its licence and process fit with the cost of building and maintaining.
• When the product is content, not a function. A website is then the right choice — compare this in Next.js or WordPress.
• When there is no certainty that the problem is real yet. Validate it first, even manually.
• When the budget covers construction but not the required maintenance. Before starting, calculate hosting, monitoring, updates, support, and development for at least the first year.

Frequently asked questions

Can we get a fixed price?

Yes, for a defined scope — that is how we sell MVPs and entry products. With substantial uncertainty, a fixed price requires a larger buffer, explicit assumptions, and a change procedure; an alternative is time-based billing in short stages with a budget limit and outcome review.

How long does a quote itself take?

For a described idea, several days. For one paragraph, a conversation first, because otherwise we would provide a number neither side could take seriously.

Will we own the code?

We hand over the repository and rights to code produced for a client within the agreement’s scope. Open-source components and external services retain their own licences, which is why a dependency list should be part of the handover.

---

If you want to turn ranges into a specific number, describe your project — the first conversation and estimate cost nothing. See also what applications built from scratch include.