Web app costs: what Swiss SMEs should know
A company website with services, images and a contact form needs a different budget from a custom web app with user accounts, data management and business workflows. For website costs in Switzerland with price examples and a calculator, use the separate overview. This article helps you plan a custom web app.
This article covers custom web apps. The figures below are simplified planning examples with stated assumptions. They are neither Swiss market statistics nor a binding quote from eluma.ch.
Why "How much does an app cost?" needs more detail
An internal dashboard is a different project from a platform with user management, payment processing and real-time notifications. Scope is an important cost factor. Technology, existing data and operating requirements also affect the work involved.
The useful starting question is: what problem does your web app need to solve, and for whom?
Before requesting quotes, define these three things:
- Who uses the app? Internal team, customers, or both?
- What are the core workflows? List the tasks users must be able to complete.
- What systems must it connect to? Existing databases, payment providers, ERP systems?
These answers help define the scope used for a cost estimate.
Cost factors in detail
Include these factors in the estimate:
-
Scope and features: Features need design, development and testing. Role-based access involves more work than a simple contact form. Decide what is needed at launch and what can follow later.
-
Technical complexity: Real-time features, complex calculations and large data sets add requirements. Even creating, reading, updating and deleting records needs suitable access controls and validation.
-
Third-party integrations: Does the app need to connect to accounting software, a payment platform or another service? Allow for development, error handling and testing for each integration.
-
Design and UX: Reusing an existing design and creating a new one involve different work. Include user interviews, prototypes and usability checks where needed. They do not guarantee a higher adoption rate.
-
Testing and quality assurance: Automated tests, manual checks and security reviews should match the application's risks. They reduce risk but cannot rule out every defect or outage.
-
Devices and operation: Define the supported devices, expected usage, availability and backup requirements. Development and testing need to cover them.
Planning examples for SME projects
For an initial budget discussion, we assume the following ranges. They require a clearly defined scope, existing content and no extensive data migration. The examples include planning, design, development, testing and initial deployment. Running costs, new features and internal staff time are excluded. All figures exclude any applicable VAT.
Simple web app (dashboard, CRUD operations) CHF 8'000 to 15'000 as a planning assumption
Assumed scope: an internal dashboard for managing data, with one user role and no external integrations.
Medium complexity (multi-user, API integrations) CHF 15'000 to 35'000 as a planning assumption
Assumed scope: multiple user roles, one documented integration with an existing system, email notifications and simple reports.
Complex platform (e-commerce, booking system with payments) CHF 35'000 to 80'000 as a planning assumption
Assumed scope: a booking system with a defined set of features, payment processing and multiple user roles. A complete marketplace, extensive integrations or specific availability requirements may fall outside this example. These figures are not price ceilings.
Fictional model: restaurant booking app
Imagine a fictional restaurant with one location that wants a booking app. We assume 15 person-days at CHF 1'200 each. This is a calculation assumption, not a client project, a market rate or a quote. It assumes an existing design, one admin role and no integration with a POS system, calendar or payment service.
| Component | Effort | Cost |
|---|---|---|
| Planning and UX design | 3 days | CHF 3'600 |
| Online booking and table management | 5 days | CHF 6'000 |
| Admin dashboard for staff | 3 days | CHF 3'600 |
| Email and SMS confirmations | 2 days | CHF 2'400 |
| Responsive design and testing | 2 days | CHF 2'400 |
| Total | 15 days | CHF 18'000 |
The 15 person-days describe assumed effort, not a promised delivery date. For the comparison, we also assume CHF 600 to 2'200 per month to run the custom app, as detailed below. For a standard product with comparable features, we assume CHF 3'000 to 6'000 per year, including the required usage fees and excluding setup costs. This is not a verified provider price either.
| Period | Custom app, development and operation | Standard product, assumed subscription fees |
|---|---|---|
| 3 years | CHF 39'600 to 97'200 | CHF 9'000 to 18'000 |
| 5 years | CHF 54'000 to 150'000 | CHF 15'000 to 30'000 |
Under these assumptions, the custom app does not pay for itself through subscription savings. Its assumed running costs alone are at least CHF 7'200 per year. Custom development would need additional, measurable benefits to justify its extra cost. For an actual decision, add setup, migration, new features, price changes and internal staff time on both sides. A custom app also remains dependent on hosting, libraries and other services.
Template or custom: which should you consider?
Not every business needs a custom web app. Compare the required scope and total cost over the same period.
Use a template or SaaS product when:
- Your requirements are standard, such as a blog, simple online shop or portfolio
- You can use existing features without having them developed again
- Your processes can adapt to the software
Consider custom development when:
- Available products do not cover your specific business processes
- Usage rights, data export and a possible provider change need contractual arrangements
- The app will be a central tool for your core business
- You need integrations with existing systems
- Available products do not meet your data access or hosting requirements
None of these points proves that custom development will save money. First check which standard products meet your requirements and which gaps remain.
Ongoing costs after launch
Development is only part of the investment. The model above uses these monthly budget assumptions:
- Infrastructure and messaging: CHF 100 to 200 per month as a combined allowance for hosting, domain, TLS certificate, backups, email and SMS. This is not a provider tariff. Usage and the selected services determine the actual amount.
- Maintenance and updates: CHF 500 to 2'000 per month as assumed spending on security updates, monitoring and bug fixes. Scope, response times and responsibilities need a separate agreement.
Together, this is CHF 600 to 2'200 per month or CHF 7'200 to 26'400 per year. New features and additional support are excluded from this example. These costs cannot be set as a blanket percentage of the development price. They need a separate operating budget based on the agreed services.
What to clarify before commissioning
To compare quotes, get these points in writing:
- Which features, devices and integrations are included, and which are excluded?
- Is the price fixed or based on actual effort? How are changes agreed?
- What are the acceptance criteria and promised dates?
- Who handles operation, maintenance and support after launch, and at what cost?
Conclusion
Custom web app costs depend on scope, technology and operation. A company website needs a different calculation. The ranges in this article support an initial budget discussion but do not replace an assessment of your project.
Compare standard software and custom development against the same requirements, including running costs. To assess whether it pays for itself, calculate development, operation and measurable savings together.
Read more about custom web apps for SMEs from Schaffhausen. Describe your workflow and the systems involved to request a web app project discussion.
Sources and scope
The monetary amounts in this article are explicitly stated planning assumptions. They are not taken from a market study. These sources explain requirements to consider when defining scope.