Cost of a web application in 2026: what to budget for?

Scroll's custom software projects start at €10,000. Your application's budget then depends on its features, data, and integrations. A subscription to a building tool is only one part of the total cost. Here is how to scope a SaaS, marketplace, internal tool, or AI prototype takeover, and compare quotes.

What is a web application?

To understand where costs come from, you first need to know what a web application is.

Definition of a web application

A web application is software accessed through a browser, usually at a web address. It can work on desktop, tablet, or phone without mandatory installation. You still need to test the intended devices and browsers: one URL does not guarantee every feature works everywhere.

A web application often avoids distribution through native app stores and lets you deploy changes on the server. Websites and applications can both have forms, accounts, or transactions. The useful distinction is what users need to do, which data the service handles, and how it will be used.

The difference between a web application and a website

Websites and web applications can overlap. To estimate a project, start by describing what users need to do.

A web application lets users complete specific tasks, such as searching, booking, calculating, or managing a record. Depending on the project, these require accounts, access permissions, data, and connections to other services. That specific scope is what needs pricing.

A brochure or editorial website mainly presents a business or publishes content. It may also offer search, a store, or a customer area: interaction alone does not make it a separate application.

For more on the distinction, see our article on the differences between a web application and a website. And for the complete construction guide, read Build a web application.

Web app costs: how to estimate by project type

For estimates of brochure sites or standard stores, see our guide Website cost in 2026. A store can already handle a catalogue, cart, and checkout without a separate app. Here we consider the specific features of a SaaS, marketplace, internal tool, or AI-assisted prototype.

A project category or technology alone cannot determine its price. To obtain comparable quotes, share the same use case, essential features, integrations, data migration needs, security requirements, and launch conditions with each provider.

SaaS application (software-as-a-service)

- Initial SaaS: specify accounts and roles, stored data, any subscription or payment flow, administration, and key user journeys. A testable mock-up, private pilot, and service open to customers do not involve the same work.

- Custom version: ask what will be built, reused, or supplied by existing services: interface, authentication, database, billing, tests, and deployment. The choice of technology alone does not determine the price.

- SaaS with multiple roles and integrations: describe each journey, billing rule, and expected volume. Separate the build cost from operating costs and future enhancements.

Marketplace or online store

- Standard store or marketplace: for a catalogue sold by one business, first check whether an existing e-commerce solution is enough. A marketplace adds sellers, commissions, disputes, and sometimes identity checks: document these rules for the quote.

- Marketplace-specific functions: specify who manages sellers, payments, refunds, inventory, and support. Price separately what the platform already covers and what needs custom development or integration.

Internal tools / back-office

- Internal tool built from existing services: start with tasks to simplify, user roles, and data already held by the business. Check access, automation, and limits before choosing this approach.

- Custom internal tool: describe business rules, data flows between systems, exceptions, and each role's permissions. The quote should cover data migration, testing with the team, and training where needed.

AI-generated applications (Lovable, Bolt, v0)

Lovable, Bolt, and v0 can speed up an initial interface or prototype. Their subscriptions and any usage credits are separate from scoping, development, testing, and operating costs. Compare them for your expected use without treating the tool's price as the cost of the application.

An AI-generated prototype can sometimes evolve within its original tool. Before planning a rebuild, review its features, dependencies, access permissions, data, tests, and deployment. Human review and security checks still matter; only a project assessment can establish which fixes to price.

If a prototype needs an audit or further work, see the AI project recovery offer. The scope is defined after reviewing the project, without assuming a complete rewrite is required.

Marketing application (advanced campaign page)

Between a campaign page and a full application, a product configurator, simulator, or calculator can have very different scopes. To estimate one, describe its calculation rules, data, outputs, forms, and any integrations.

The components that make up development costs

A web application quote typically includes these items. Understanding what you're paying for helps avoid surprises.

Scoping: define users, tasks, priority features, data, and constraints. Ask whether this phase is included in the quote, what it delivers, and what remains to be decided before development.

The back-end (server-side processing and data): database, APIs (connections between software), authentication, and business rules. Specify volumes, permissions, external services, and error cases, as these affect the work to build and test.

The front-end (user interface): user journeys, design, and interface. Adapting an existing template and designing custom screens involve different work; ask which screens and states are included.

Device support: specify the devices and browsers people will actually use. The quote should cover their design and testing, especially for mobile or field work.

Testing and acceptance: check key journeys, error cases, permissions, and integrations. Clarify who tests, who accepts delivery, and how defects are fixed.

Security and data protection: access controls, backups, secret management, updates, and applicable obligations. AI-generated code also needs human review and testing before it is opened to users.

Security obligations depend on the project's data and use. The fines issued by the CNIL show why they matter, but provide neither a cost schedule nor a prediction of risk for your app. Check which measures the quote includes and who will maintain them.

More journeys, roles, and integrations mean more design and testing. List what the first release must include and what can wait; classify the features as essential / optional.

Recurring costs to plan for after launch

To compare costs over twelve months, add the build, subscriptions, estimated external service usage, maintenance, and planned changes. Distinguish prices before and after tax, and check what is already included to avoid double counting. Clarify what the provider charges and what you will pay suppliers directly.

- Hosting and infrastructure: check the chosen plan, included resources, backups, test environments, and usage thresholds. Hosting bundled with a platform is still subject to its plan conditions.

Example checked on 23 September 2026: Supabase lists its Pro plan from US$25 per month. Additional compute, optional features, and usage beyond included quotas can add costs. This covers a technical service, not your application's entire hosting or maintenance. To estimate costs for your volumes, see the Supabase pricing page.

- Platform subscriptions: if the project uses Bubble, Webflow, FlutterFlow, or other tools, identify who owns the account, what features are included, usage limits, and upgrade conditions.

- Maintenance and fixes: define the scope of support, updates, backups, response times, and defect handling. Ask for an estimate suited to the application instead of a fixed percentage of the initial build cost.

- Product enhancements: separate fixes from features built after the first release. Agree on how new work will be requested, approved, and priced.

- Third-party and AI services: APIs, AI models, messaging, and payment services may charge by usage. Ask which accounts are needed and what volume assumptions underpin the estimate.

Payment fee example using French prices checked on 23 September 2026: 200 payments of €50 using standard European Economic Area cards incur €200 in fees at Stripe Payments' rate of 1.5% + €0.25. This excludes extra services such as Billing, disputes, and other card types. Source: Stripe pricing in France.

How to manage your web app budget

These steps can reduce the initial scope or reuse existing features. Their effect on the quote must be assessed for each project.

Compare approaches: for no-code, AI-assisted tools, and custom development, ask what the first release includes, what depends on a platform, and what can evolve. A future migration is neither automatic nor free.

Prioritize features: define one useful end-to-end journey for the first release, then defer secondary features. Ask how that split affects the quote, data, and integrations.

Work in phases: set deliverables and acceptance criteria for each stage. Feedback from early users will help determine the next investment.

Reuse proven components to avoid custom work, for example for authentication or certain interface elements. Check their costs, maintenance, and fit for the project's constraints.

Compare providers against the same scope: ask for quotes that separate scoping, build, testing, launch, and support. Also check the team's experience with the selected tools and integrations.

What should you budget for your project?

Our custom software projects start at €10,000. The budget depends on scope and required integrations. Depending on your needs, we can start with a more limited scoping, audit, or automation assignment. To prepare an estimate, describe the users, the priority workflow, the software to connect, and any data to migrate.

To discuss the scope and obtain a tailored estimate, see our AI code development approach; if you already have an AI prototype, you can also explore our AI project recovery service.

Develop your web application with Scroll Agency

At Scroll, we provide no-code and AI code web application development. Tell us who will use the product, its essential features, and the tools already in place; we can define what needs pricing and possible delivery stages.