When an operations director asks «how much does an internal web application cost?», the honest answer always starts with another question: what exactly does it need to do? A KPI dashboard built on top of existing data has nothing in common with an expedient management system featuring digital signatures, approval workflows and ERP connectivity. That said, indicative market ranges do exist that let you judge whether the budget on the table is reasonable or far off reality. In this article we break them down using data from real projects delivered in Spain in 2025-2026.
What is an internal web application and how does it differ from a SaaS?
An internal web application (also called a bespoke tool, backoffice or management portal) is browser-based software developed specifically for an organisation's processes and hosted on its own servers or in the cloud under its control. It is not a packaged product sold to thousands of customers: it is a made-to-measure suit.
The alternative is to subscribe to a generic SaaS (Software as a Service) — a Trello, a Monday.com, a Notion — and adapt your processes to its capabilities. Many SMEs rightly choose this route. But when processes are sufficiently unusual, the SaaS starts to cost more in licences and wasted time adapting it than it would cost to build something bespoke. That is the inflection point at which custom development becomes economically justified.
Indicative price ranges by project type (Spain, 2026)
The figures below are market ranges based on publications from the Spanish technology sector and public provider quotes in 2025-2026. They are not Summum's rates; they are a benchmark to check whether a quote you receive is in line with the market.
| Application type | Typical features | Indicative range (€, excl. VAT) | Estimated timeline |
|---|---|---|---|
| Basic dashboard / simple CRUD | Management of a single entity (customers, orders, incidents), listings, filters, Excel export, no external integrations | 6,000 – 18,000 € | 4 – 10 weeks |
| Mid-range management application | Several modules (users, roles, documents, notifications), moderate business logic, 1-2 integrations (ERP, email), reporting dashboard | 18,000 – 55,000 € | 3 – 6 months |
| Complex system / platform | Multi-stage approval workflows, digital signatures, third-party portals (customer/supplier), multiple integrations (ERP + CRM + public API), advanced business logic | 55,000 – 150,000 € | 6 – 12 months |
| Sector platform with AI | All of the above plus artificial-intelligence components (document classification, prediction, automatic report generation) | 80,000 – 250,000 € | 8 – 18 months |
Indicative sources: ICT Sector Report Spain 2025 (AMETIC), Club de Innovación publications and analysis of public procurement tenders from the Spanish Public Procurement Portal.
What drives the price? The 7 factors that move it most
1. Complexity of the business logic
A form that saves data is not the same as a system that calculates tariffs according to 40 different rules, generates digitally signed PDF documents and pushes them to the ERP. Business logic is the primary cost driver, ahead of design or technology choice. The more specific and intricate the edge cases, the more hours of analysis and development.
2. Number of integrations with existing systems
Connecting the application to an ERP (Odoo, Sage, Dynamics 365), a CRM, an e-invoicing service or a public API can multiply the budget. Each integration requires analysing the external system's API, handling authentication, mapping fields and dealing with cases where the external system does not respond. A single well-built integration can add between 3,000 and 15,000 € depending on its complexity.
3. User roles and permission management
An application with a single user profile is straightforward. When there are multiple roles (administrator, supervisor, operator, external customer, read-only auditor) with granular permissions over each module, complexity scales non-linearly. The access-control system typically accounts for between 10% and 20% of total effort in mid-range applications.
4. Performance requirements and data volume
An application used by 10 people with 5,000 records does not need the same architecture as one used by 500 people processing millions of daily transactions. Scaling correctly from the outset — or planning for it in later phases — is a decision that affects both the initial cost and the ongoing running cost.
5. Interface design (UX/UI)
Internal applications tend to prioritise functionality over aesthetics, which is reasonable. However, a poorly designed interface costs money in training and in usage errors. The Spanish market distinguishes three levels: basic functional design (included in most standard quotes), design with a custom component system (+15-25% on the base budget) and user-experience auditing with usability testing (+5-10%).
6. Legal and security requirements
If the application handles personal data, the General Data Protection Regulation (GDPR) applies and certain controls may be mandatory: processing activity records, erasure mechanisms, export in a readable format and auditable access logs. In regulated sectors (healthcare, insurance, public sector), security requirements are even stricter. Adapting an application to meet the National Security Framework (ENS) at medium category can add between 8,000 and 30,000 € to the budget.
7. Team and provider location
In Spain in 2026, the hourly rate for a senior developer ranges from 60-90 €/h at mid-sized consultancies and can exceed 120 €/h at boutique agencies in major cities or with very niche specialisations. Nearshore models (Eastern Europe, Latin America) come in at 30-50 €/h but add coordination costs and cultural misalignment risk. A 500-hour project at 75 €/h amounts to 37,500 € in development labour alone.
Budget line items you must not forget
Many SMEs receive a development quote and are later surprised by costs they had not anticipated. Here are the most common ones:
- Functional analysis: defining exactly what the application needs to do before writing a single line of code. This can account for 10-15% of the total budget, but it is pure investment — it prevents costly rework.
- Cloud infrastructure: servers, databases, storage, CDN, backups. A medium-sized application on Azure or AWS costs between 150 and 800 €/month depending on load.
- Third-party licences: commercial libraries, interface components, e-signature services, payment gateways or data APIs.
- Testing and quality assurance: automated tests (unit, integration, end-to-end) are not optional if the application will be in production for years. They add between 15% and 25% to the development effort.
- Training and documentation: user manual, training videos, onboarding sessions for the team. Frequently overlooked and frequently responsible for failed adoption.
- Evolutionary maintenance: bug fixes, dependency updates, minor improvements. Budget between 15% and 20% of the initial development cost per year.
When does custom development make sense and when is a SaaS better?
The answer depends on three variables: process uniqueness, number of users and time horizon.
If the process you want to digitalise is generic (task management, project tracking, basic customer database), a standard SaaS is almost always more economical in the short term. The total cost of ownership of a SaaS — monthly licences, training, native integrations — is typically lower than custom development during the first 3-4 years.
Custom development starts to make sense when:
- The process contains highly specific business logic that no SaaS implements natively.
- User volume would mean SaaS licences exceed the cost of development within 3-5 years.
- You need full control over the data (for GDPR compliance, regulated sector requirements or competitive reasons).
- Integration with existing internal systems is complex and the SaaS's native connectors are insufficient.
- The application is part of the product you sell (not just an internal tool).
In bespoke web application development, the first step we always recommend is a feasibility study: comparing the TCO (Total Cost of Ownership) of in-house development against the available SaaS alternatives over a five-year horizon. That comparison tends to resolve the question better than any gut feeling.
Typical phases of an internal web development project
Regardless of project size, well-managed projects follow predictable phases. Understanding them helps you control the budget and know at which point you can still influence the outcome:
- Discovery and functional analysis (2-4 weeks): interviews with end users, mapping of current processes, requirements definition, detailed estimation and budget validation.
- Architecture design and prototype (1-3 weeks): technology decisions (stack, database, infrastructure), navigable prototype of the main screens. This is where you validate that what will be built is what the user actually needs.
- Development in sprints (the bulk of the project): two-week iterations with a functional delivery at the end of each one. This allows course corrections without paying the price of redoing months of work.
- Testing and bug fixing (2-4 weeks): functional tests, load testing, basic security review, bug fixes.
- Go-live and training (1-2 weeks): data migration if required, deployment to the production environment, training sessions with users.
- Post-launch support (first 4-8 weeks): resolving incidents that emerge in real-world use. Essential to prevent adoption failure.
If a provider proposes skipping the functional analysis to «get started sooner», treat it as a warning sign: requirement changes in advanced phases are the leading cause of budget overruns.
Most common technologies for internal web applications in Spanish SMEs (2026)
The technology choice affects cost (through developer availability in the market), performance and future maintenance cost. These are the most common combinations in Spanish SME projects in 2025-2026:
| Layer | Most common options | Notes |
|---|---|---|
| Frontend | React, Vue.js, Angular | React leads in developer availability in Spain |
| Backend / API | Node.js, Laravel (PHP), Django (Python), .NET | Laravel and .NET have strong penetration in the Spanish SME market |
| Database | PostgreSQL, MySQL/MariaDB, SQL Server | PostgreSQL is gaining ground in new projects for its extensibility |
| Infrastructure | Azure, AWS, Google Cloud; also VPS at Arsys, Raiola or Ionos for smaller SMEs | Azure is preferred when Microsoft licences are already in place |
| Authentication | Azure AD / Entra ID, Auth0, Keycloak | SSO with the corporate directory is standard in companies with 20+ employees |
For projects with Microsoft 365 or Dynamics 365 integrations, the Power Platform ecosystem (Power Apps, Power Automate) is a low-code alternative that can reduce development time by 30-50% for moderately complex processes. However, it has limits on advanced logic and can become more expensive in licences at scale. You can find out more about this route in our process automation with Power Platform service.
How to request quotes and what to really compare
When you ask several providers to quote for the same project, it is common to receive figures that differ by 200-300%. This does not necessarily mean one is more expensive and another cheaper: in many cases it means they are quoting for different projects. To compare rigorously:
- Always demand a breakdown by phase and by developer profile. A fixed quote of 30,000 € with no breakdown does not tell you whether it includes functional analysis, testing and post-launch support.
- Ask what happens if requirements change. Fixed price or time-and-materials? Each model has its advantages depending on how mature the specification is.
- Request references from similar projects. A developer who has worked in your sector knows the typical pitfalls and avoids them; one who has never done anything similar will discover them at your expense.
- Evaluate the project management methodology. Well-managed projects with short sprints and frequent demos carry far less risk of overrun than waterfall projects where you see nothing until the end.
Frequently asked questions
Can I ask for just a prototype to validate the idea before committing the full budget?
Yes, and it is usually a smart decision. A basic functional prototype (also called an MVP or Minimum Viable Product) for a management application can cost between 8,000 and 25,000 €. It allows you to validate with real users that the tool solves the problem before committing the full budget, and it produces far more mature requirements for the final development. The risk is building an MVP that is not scalable afterwards: make sure the provider plans the architecture with growth in mind, not just the initial version.
How much does annual maintenance typically cost for an internal web application?
The Spanish market standard places evolutionary maintenance cost at between 15% and 20% of the initial development cost per year. For an application that cost 40,000 €, budget between 6,000 and 8,000 € annually for security updates, minor bug fixes and small improvements. If the application needs to evolve significantly (new modules, additional integrations), that cost is added on top of the base maintenance.
Is it necessary to hire an external consultant to manage the project if we already have an in-house IT person?
It depends on the in-house IT person's profile and the complexity of the project. A systems technician with infrastructure experience may not have the software project management skills needed to coordinate an external development team, manage scope and ensure the outcome meets business needs. On projects above 30,000 €, having someone on the client side who understands both the business and the technology — or bringing in an external project manager — typically pays for itself in results that are much closer to what was actually needed.
What guarantees should I request regarding code ownership?
The source code of an application developed to measure for your company should belong to you. Require in the contract the full assignment of intellectual property rights over the code developed specifically for your project (distinguishing it from third-party libraries under open-source licences, which retain their own conditions). Also request access to the code repository during development — not just at the end — and that the technical documentation (architecture, data model, deployment guide) is delivered together with the code.