Budget and pricing
How much does a web application cost in 2026?
Features, integrations, PWA or mobile: what drives the budget for a web application, with CUB3’s public prices and the costs to plan for after launch.
The short answer
At CUB3, a web application starts at €6,000 excluding VAT for a clearly scoped first version. The final budget depends mainly on the number and complexity of features, the integrations and the target platform. Hosting, third-party services and maintenance should be budgeted separately.
- A CUB3 web application starts at €6,000 excluding VAT: this price covers a scope defined in the quote, not an unlimited number of features.
- Features, their complexity and integrations weigh more heavily than the number of screens.
- Plan separately for hosting, third-party services and maintenance, which starts at €300 excluding VAT per month at CUB3.
- WebAccess through a browser
- PWAAn installable application
- MobilePhone-based usage
The short answer: from €6,000 excluding VAT, depending on scope
A custom web application has no single price: two projects with the same number of screens can require very different amounts of work. To provide a verifiable benchmark, CUB3 publishes its starting prices. A first version of a web application starts at €6,000 excluding VAT. This amount covers a scope defined in the quote: user profiles, request management and administration, with scoping, testing and production deployment.
This price is a floor, not a package. It does not cover an unlimited number of features or integrations. The final budget depends on what the application must make possible, the tools to connect and the target platforms. The following sections detail these factors, then the costs that come on top after launch.
| Project | Starting price excluding VAT | What this starting point includes |
|---|---|---|
| Business website | €2,000 to €4,000 | Five pages in one language, with text and visuals supplied by you. |
| Web application | From €6,000 | A clearly scoped first version, with features and integrations specified in the quote. |
| Web application and PWA | From €7,200 | The web application, plus installation, icons, static caching and an offline screen. |
| Hybrid mobile application | €10,000 | Scoped recovery of an existing application. |
| Native mobile application | From €15,000 | An iOS or Android MVP, with a usable existing API. |
What drives the budget
The first factor is the number of features and their complexity. A feature brings together everything needed for an action to succeed: the screens, data, rules and checks. A simple form and a journey with several profiles, approvals and dependencies do not require the same work, even if they take up the same number of screens.
Next come exchanges with other tools: payment, CRM, ERP, a booking tool or a business API. Each integration adds scoping, data mapping and testing. Finally, the platform matters: an installable version or a mobile app adds capabilities and checks that a web application alone does not require.
Features
Accounts and login, roles, back-office, search, payment, files or notifications: each one adds rules and cases to test.
Integrations
A documented tool with test access connects more reliably than a poorly understood API. At CUB3, integrating one tool starts at €3,000 excluding VAT.
The platform
The standard PWA option adds €1,200 excluding VAT to the web application. Hybrid and native mobile have their own scopes.
What a serious quote should include
Building the screens is only part of the work. A comparable budget includes scoping the journeys and permissions, interface design, testing and validation of use cases, then production deployment. A proposal that leaves out one of these stages looks cheaper without covering the same result.
Also ask what production deployment covers. At CUB3, the deployment included in a web application does not automatically mean a full staging and production infrastructure, with Terraform and continuous deployment. That setup is a separate DevOps offer, at €6,000 excluding VAT. The quote should state clearly what is included.
- The selected features are listed, with what they make possible.
- Scoping, UX/UI design, testing and production deployment are planned.
- Integrations are named, with the access and documentation required.
- Exclusions are stated in writing: hosting, third-party services and maintenance.
- Acceptance criteria for delivery are defined.
The costs that continue after launch
An application in use has recurring costs. Hosting, the domain name, licences and third-party services, such as email sending, payment or storage, are billed by their providers according to your usage. They remain separate from the delivery budget and should be estimated from the scoping stage.
You also need to plan for ongoing support: fixes, technical updates and small improvements. At CUB3, application maintenance offers three monthly plans. Work outside the plan is billed at the hourly rate, by agreement, and larger developments require a new scope.
| Plan | Price | Allowance and coverage |
|---|---|---|
| Essential | €300 per month | Two hours per month: diagnosis and minor fixes. |
| Comfort | €690 per month | Six hours per month: fixes and technical updates. |
| Growth | €1,090 per month | Ten hours per month: maintenance and small improvements. |
| Out of plan | €90 per hour | Additional work, by agreement. |
Promo.dev: what reduced the custom work
For Promo.dev, two CUB3 people built a white-label e-commerce platform from a ready-made Figma design. Shopify handled the catalogue, payments and inventory; an API layer covered business logic and integrations. The web application was ready for production on day twenty-eight.
For your budget, the lesson comes down to two choices: designs available from the start, and an existing service for standard functions. These reduce the share that has to be custom-built. This case sets neither a price nor a timeline applicable to every project; it shows what drives the effort.
Get an initial estimate
For an initial reference, the CUB3 simulator asks you to choose the type of project, then the features you need: accounts, roles, back-office, search, payment, files, notifications or connection to an external tool. You then receive a detailed PDF estimate by email, with its assumptions and exclusions.
This estimate prepares the conversation; it does not replace the quote, which confirms the scope after discussion. To make it useful, start from the actions your users must complete rather than a number of screens. If a choice remains uncertain, such as the PWA or an integration, estimate both versions.
In the field
A real project
Ready-made designs, an existing commerce engine and two CUB3 people: a web app ready for production in twenty-eight days.
The Promo.dev case