A web application or MVP costs from €2,900 with us, and a SaaS platform from €4,800. A marketplace is quoted individually. We deliver a web application in 6-10 weeks, and maintenance after launch starts at CZK 5,000 a month. We are not VAT registered, so these prices are final. How far above the floor your project lands comes down to roles, integrations, the admin panel, payments and multi-tenancy. We go through each one below, along with the cases where you shouldn't build an app at all.
Web application pricing for 2026
We quote web application development as a fixed price up front, so the figures below are floors rather than hourly estimates. You get the exact price after a consultation, and the rest of our services are on the pricing page.
| Project type | Starting price | What it usually includes |
|---|---|---|
| Web application or MVP | €2,900 | User authentication and management, admin panel, API, responsive frontend, cloud deployment. Delivered in 6-10 weeks. |
| SaaS platform | €4,800 | Separated customer data (multi-tenancy), subscriptions and payments, advanced roles, third-party integrations. |
| Marketplace | On request | Two types of user, listings and search, transactions between sellers and buyers. |
| Maintenance after launch | CZK 5,000 a month | Updates, backups, monitoring and security checks. |
A web application includes initial analysis, design, user authentication, the database, API integrations, testing and launch, plus 1 year of free hosting and 90 days of support. The technology we use and how the work runs are covered on our web application development page.
What determines the cost of a web application
Screen count tells you very little. Two applications with the same number of pages can differ several times over in price, because one only displays data while the other tracks who may change it, what happens on an error and how the change reaches the next system. These five things make the biggest difference.
Roles and permissions
One role is simple: a logged-in user sees their own data. Add a colleague from the same company, an approver and an administrator, and every screen and API endpoint has to answer who may see this and who may change it. That check belongs on the server, because a hidden button protects nothing. Each extra role adds combinations to test, so before asking for a quote, list the roles in a table and write down what each may do.
Integrations
Calling someone else's API takes very little time. Everything around the call is what costs money: what happens when the other system doesn't respond, when a webhook arrives twice, or when part of the data fails to transfer and someone has to find it. A modern service with documentation and a sandbox is a cheap integration. An older accounting or warehouse system that can only export a file costs far more. Find out whether your system has an API, and who can give you access, before you ask for a quote.
Admin panel
The admin panel is the easiest thing to forget during planning, yet it's where your staff will spend most of their time. Someone has to look up a customer, fix a wrong entry, issue a refund or block an account. A basic panel is included in the price. Reports, bulk edits and exports for the accountant are separate work and belong in the brief. Leave them out and you end up editing the database by hand, which is both expensive and dangerous.
Payments
A one-off payment through a gateway is a solved problem, and we have a separate comparison of Czech payment gateways. Subscriptions are a different category. You have to handle trial periods, plan changes mid-month, cards that fail on renewal, invoices and credit notes. A marketplace also has to split payments between sellers and the operator, and deal with commissions and payouts, which is why it sits above a standard application.
Multi-tenancy
Multi-tenancy means one application serves several companies and each sees only its own data. It's decided in the data model at the start, because it touches every database query. Retrofitting it into a finished application is one of the most expensive changes you can order, and a bug in it means one customer sees another's data. That's the main reason SaaS starts at €4,800 rather than €2,900. An internal system for a single company doesn't need it. For a look at a SaaS from idea to operation, here is the story of Consentio, our own product.
Smaller items add up too: importing data from an old system, email and SMS notifications, multiple languages, live updates over WebSocket. None of them will sink a project alone, but they belong in the brief before you get a quote.
MVP or full build
An MVP is the smallest version that takes a user through one journey from start to finish and shows whether anyone wants it. You can postpone the second role, reports, settings, and automating anything a person can handle in the admin panel for the first few months. You can't postpone security, backups or a sensible data model, because those are the hardest to add later.
Go straight to a full build only when you're replacing a working process and people can't run half in the old system and half in the new one. An internal system for a whole team is the typical case. An idea without paying users is the opposite: every extra feature is money spent on a guess about what people want. The route from idea to launch is on our MVP development page. If you already have a prototype from an AI tool, read when an AI-built app needs rescuing before you extend it.
Running costs after launch
You pay for development once and for operation indefinitely. These items belong in the budget:
- Our maintenance starts at CZK 5,000 a month. It covers updates, backups, monitoring and security checks, with details on the maintenance page.
- Hosting is included for the first year. After that you pay according to how heavily the application is used.
- Third-party services such as a payment gateway, email and SMS delivery, maps or AI models are mostly billed by volume, so they grow with your user base.
- Further development is its own line. A new feature is new work and gets quoted separately.
There is a wider breakdown in what website maintenance costs. Ask your supplier about these items up front, so the first invoice after launch holds no surprises.
How to get a fixed price instead of an estimate
Only someone who knows what they're building can give you a fixed quote. The more precise your brief, the less contingency the supplier has to add. A few pages will do:
- Who uses the application: a list of roles and what each may do.
- Three to five main scenarios in your own words, such as "a customer files a request, an approver confirms it, the accountant gets an invoice".
- The systems the application should connect to, and whether they have an API.
- What the first version must do and what can wait.
- How many users you expect and whether anything is moving over from an old system.
After a free consultation we send a fixed-price quote within 48 hours. We don't bill hourly. Standard projects are paid 50% up front and 50% on completion, larger ones in three parts. The code and design are yours after the final payment. Whoever you choose, ask how changes to the brief are handled during development and who owns the code. We collected more questions in how to choose a web agency.
When an off-the-shelf tool is the better choice
We build custom applications, and they're still often the wrong answer. Invoicing, CRM, helpdesk and booking are solved problems. A ready-made tool works today and someone else looks after it. If your process looks like most companies' processes, buy the tool.
Ready-made also wins early on, while you're still finding out whether anyone wants the service. A form, a spreadsheet and manual handling will test demand sooner and for less than a €2,900 build. And if you only need to connect two systems you already have, process automation often does the job without a new application.
Custom development makes sense when the process is the reason customers choose you, or when you keep working around a ready-made tool in spreadsheets. It also makes sense if you plan to sell the application yourself. One question helps: what would change if your competitors used the same tool as you? If the answer is nothing, save the money.
What to do next
Write down the roles, scenarios and integrations from the list above and send them to us. Within 48 hours of the consultation you'll have a fixed price, or we'll tell you a ready-made tool is enough. If you're planning a shop rather than an app, read what an online store costs.