How much does a web app cost in 2026? A simple application with user accounts and an admin panel comes to roughly €4,150–10,400 net (excl. VAT), a platform or product MVP with several modules, integrations and payments — €9,200–23,000 net, and an extensive system with many roles and integrations with ERP or CRM starts from ca. €23,000 net.
Euro amounts converted at the NBP mid-market rate of 14 September 2026 (€1 = 4.3391 zł) and rounded. We invoice in PLN.
These are ranges, not a price list. A web app is not an off-the-shelf product — each one has a different number of screens, roles, exceptions and systems it has to talk to. The exact figure only emerges after a conversation about scope.
Where do these ranges come from? Hours times rate
Estimating a web app is simple arithmetic: the number of hours of work multiplied by the rate. At CodePort the rates are public — development €46/h net, design €35/h net. Everything else is a matter of estimating how many hours a specific scope will take.
That is why a conversation about budget always comes down to a conversation about features. Every additional account type, report or integration means more hours of work.
Example (illustration only, not an offer): a panel for managing orders — 120 hours of development × €46 = €5,550 net, plus 20 hours of interface design × €35 = €690 net. That is €6,200 net in total, an amount that fits within the range for a simple application.
Second example: a platform MVP with payments and two account types — 300 hours of development × €46 = €13,800 net plus 60 hours of design × €35 = €2,050 net, €15,900 net in total.
Your project may come in lower or higher. The point is that you understand the mechanics: you are not buying "an application", you are buying hours of work turned into specific features.
How much does a web app cost depending on its type?
| Type of application | What it usually includes | Indicative cost, net | Typical delivery time |
|---|---|---|---|
| Simple application / panel | User accounts, basic modules, admin panel | €4,150–10,400 | 6 – 10 weeks |
| Platform / product MVP | Several modules, integrations, payments, roles and permissions | €9,200–23,000 | 2 – 4 months |
| Extensive system | Many roles, complex logic, ERP/CRM integrations, high scale | from ca. €23,000 | built in stages, modules as they become ready |
The first row is the most common starting point for companies that want to move a process out of spreadsheets. The second — founders building a product to show the market and investors. The third covers systems where it makes no sense to talk about a single launch date, because they are created module by module over many months.
Examples from CodePort's web projects: for ZAC Group we built a product site with an admin panel (client and transaction lists, a team task module, login and roles), and for HunterValley IT a platform with IT job offers — two account types, a map of listings, a search engine with filters, a listing builder and Google sign-in.
What pushes web app development cost up the most?
Four things shift an estimate the most. It is worth knowing them before you start writing your feature list.
Roles and permissions
A single administrator account is straightforward. Five user types, each seeing different data, with different buttons and different notifications, means many times more screens to design, build and test. This is the most common reason why a "small application" turns out to be a medium-sized project.
Integrations with external systems
CRM, ERP, a payment gateway, Allegro (Poland's largest online marketplace), KSeF (Poland's National e-Invoicing System), a supplier's API. The cost depends on the number of systems being connected, the quality of the API documentation and the number of exceptions — because it is the exceptions that take time, not the "happy path". You will find more about what needs to be prepared before the start on the page about system and API integrations.
Recurring payments
A one-off payment means plugging in a gateway. Subscriptions already mean plans, trial periods, mid-month plan changes, failed charges, invoices and history. Each of these cases has to be handled and tested.
An extensive admin panel
The panel is sometimes bigger than the part visible to the user. Filters, exports, reports, change logs, bulk operations — all of these are hours you cannot see in the first screenshot, yet they decide whether the team will actually start using the application.
How much does a web app cost after launch?
The budget does not end on launch day. Three items are worth putting into your spreadsheet straight away.
- Server and infrastructure — from a few tens to a few hundred zloty per month, depending on the number of users and the volume of data.
- Technical support — monitoring, backups, library and system updates, minor fixes. Typically 5 – 15 hours a month billed at the hourly rate. In numbers: 5 hours × €46 = €230 net, 15 hours × €46 = €690 net per month.
- Further development — new features after the first weeks of real use. This is usually the best-spent money in the whole project, because it is based on user behaviour rather than assumptions.
An application nobody updates becomes a risk after a year: outdated libraries, security holes, problems with new browser versions. Maintenance is not an optional extra, it is part of the cost of ownership.
Web app or mobile app?
A web app runs in the browser on a computer, tablet and phone, without publication in the App Store and Google Play and without developer accounts (Apple 99 USD a year, Google 25 USD one-off). It works well for panels, systems for teams and platforms used mainly at a desk.
A mobile app has the advantage when users reach for it every day on their phone, and the product needs push notifications, offline working or camera access. We describe the ranges for iOS and Android, the difference between cross-platform and native apps, and maintenance costs in the article How much does a mobile app cost in 2026?
Custom application or an off-the-shelf subscription tool?
The honest answer: if your process looks the same as in thousands of other companies, an off-the-shelf subscription tool will do and will be cheaper. There is no point building from scratch something you can switch on tomorrow.
Custom software makes sense in four situations:
- You pay for several tools that have to be joined manually — someone re-types data from one into another.
- Your process is a competitive advantage and does not fit into someone else's template.
- You need integrations that an off-the-shelf tool does not allow.
- You want to sell your own product as SaaS.
On top of that there is the question of ownership. Once the project is settled, at CodePort you receive full intellectual property rights to the code and design, the code goes into your repository, and the services are registered to your company. With a subscription you pay every month for access, and if you cancel you are left with exported data at best.
How to reduce the cost of the first version
The cheapest feature is the one you did not build. Three approaches work regardless of the industry.
Start with an MVP. The first version should solve one problem for a specific group of users, not replace everything at once. We describe how to trim the scope without spoiling the product in the article MVP or full product.
Build a clickable prototype before the code. Changing a screen layout in Figma takes minutes. The same change in a finished application takes hours of development. A prototype also lets you show the solution to your team and clients before the first line of code is written.
Settle the project in stages. Instead of one big decision you make several smaller ones. After each stage you have a working version and can decide whether the next module is still needed in the planned form. In practice it looks like this: a conversation and an estimate (price range and schedule within 2 – 3 working days), a prototype, sprints with a working version every 1 – 2 weeks, launch and further development.
How to prepare for an estimate so the range is accurate
The difference between "around €7,000" and a specific figure lies in the information you provide. Prepare four things:
- The business goal — what should change after launch. "Orders stop being re-typed by hand" is better than "we want a system".
- A prioritised feature list — split it into "we will not launch without this" and "could come in the second stage". That split alone can cut several dozen hours from the cost of the first version.
- User types — who logs in and what each of them sees.
- Integrations — the names of the systems the application is to connect to, and whether they have API documentation.
With that in hand, you can check indicative ranges in the cost calculator or describe the project in the project brief builder — it produces an initial technical specification. We reply within one working day, and prepare a price range and schedule within 2 – 3 working days.
The more you know about the scope, the narrower the range you will get. The less you know, the more cautiously every supplier will price the work, because the risk has to be accounted for somewhere.
If you want to see a figure for your idea, start with the cost calculator — you will get an indicative range straight away, with no obligation.
Frequently asked questions
How much does the simplest web app cost?
The simplest projects — user accounts, one or two modules and an admin panel — start from ca. €4,150 net. Below that amount we are usually talking about a website with a form rather than an application.
How long does it take to build a web application?
A simple panel usually takes 6 – 10 weeks, a platform MVP 2 – 4 months, and extensive systems are built in stages and released module by module. You receive the schedule itself, together with the price range, within 2 – 3 working days of our conversation.
Is an estimate for a web app chargeable?
No. The cost calculator and the project brief builder are free, and you will see the indicative range from the calculator straight away, with no obligation.
What does the price of a web app depend on within the same category?
For the same type of application, the difference usually comes from the number of roles, the number of integrations and how many exceptions the system has to handle. Two applications with an identical feature list can differ by several dozen hours of work simply because of an unusual sales process or missing API documentation on the side of the system you need to connect to.
Can I spread the cost of the application across stages?
Yes, we settle projects in stages — after each one you have a working version and decide on the next step. That way you do not tie up the whole budget at the start, and you can change the scope of the following modules based on how users work with the first version.