Web App Development Cost in Switzerland: What to Budget

A web app in Switzerland costs anywhere from a few thousand francs for a very simple tool to six figures for a platform with roles, integrations and compliance work. Where you land depends less on the technology than on scope, on who builds it, and on how many times the requirements change along the way. This guide gives you the ranges we can source, compares the realistic ways to build, and shows you what to ask for in a quote.

TL;DR

• A very simple web app can start around CHF 3,000, and a mobile-friendly web application with real logic averaged about CHF 11,400 in one Swiss marketplace’s cost comparison. Anything with several user roles, payments or integrations costs a multiple of that.
• Swiss labor is the main cost driver. Freelancer rates of CHF 120 to 180 per hour are typical of the lower end of the local market, and agencies charge more for team, management and continuity.
• The cheapest quote is rarely the cheapest project. Rewrites, staff changes and unclear scope cost more than a higher day rate with a senior person who stays.
• Budget for running the app too: hosting, monitoring, security updates and small improvements after launch.
• Ask for a fixed scope in writing, with a defined first release, before you compare prices.

What a web app actually costs in Switzerland

Most English-language cost guides quote dollar figures from India, Eastern Europe or the US. They are a poor guide for a Swiss buyer, because the biggest line in any software budget is people, and Swiss people are expensive.

Two Swiss sources give a useful anchor. The quote marketplace Gryps lists a very simple web app with static information from CHF 3,000. The same page puts the average cost of a simple app delivered as a mobile-capable web application at CHF 11,400. Those figures describe small, simple tools: a calculator, a booking form, a basic internal dashboard.

Once an app has accounts, permissions, payments, reporting and connections to other systems, you leave that bracket quickly. We do not publish a fixed price list for those projects, and no honest provider can name a number before scope is clear. What you can do is understand what moves the price.

A practical way to think about tiers

These are working categories we use to frame a conversation, not published prices:

Tier	What it looks like	What drives cost
Simple tool	One workflow, one user type, little or no integration	Design, one data model, hosting setup
MVP	Core product for first real users: sign-in, one or two main workflows, an admin view	Scope discipline, authentication, data design
Business application	Several roles, reporting, connections to CRM, ERP or shop	Integrations, testing, migration of existing data
Platform	Multi-tenant or marketplace logic, APIs for third parties, high availability	Architecture, security, operations, compliance

The jump between tiers is not the screens. It is the number of rules the system must enforce and the number of other systems it must talk to.

What drives the price up or down

Scope and the number of workflows

Every distinct thing a user can do is a workflow with edge cases: what happens when payment fails, when someone is deleted, when two people edit the same record. Ten screens that all do the same thing cost much less than four screens with different rules behind each.

Integrations

Connecting an app to an ERP, a CRM, a payment provider or a legacy database is often the largest hidden item. The new code is quick to write. Understanding the other system’s quirks is not. If your app must read and write to existing systems, say so at the first conversation.

Data protection and compliance

Since 1 September 2023, the revised Swiss Data Protection Act applies, and the SME portal of the federal government explains that privacy by design and by default mean data protection has to be built into software and its configuration from the planning stage. In practice that means deciding early what personal data you collect, where it is stored, who can see it and how it is deleted. Doing this in planning is cheap. Retrofitting it after launch is not.

Who builds it, and where

Labor is scarce. A survey of the Swiss software industry from the University of Bern found that a shortage of skilled staff is a leading reason Swiss firms outsource. Trade press makes the same point: Netzwoche reports that the Swiss ICT industry suffers from a lack of IT specialists. When talent is scarce, rates stay high, and the real question becomes how to get value from every hour.

Salaries tell the same story from the employer side. The swissICT salary survey for 2025 found only a moderate rise of 0.4 percent in the median base salary, but from a high base.

Change during the project

Rewritten requirements and mid-project staff changes are the quiet budget killers. Every time a new person joins a project, someone has to explain it to them, and the client usually pays for that time. This is the main reason we staff every project with senior engineers from the first call to handover.

Your options compared

There are six realistic ways to get a web app built in Switzerland. None is wrong for everyone.

Option	Best for	Cost profile	Main risk
No-code or low-code tools	Validating an idea, internal tools	Low upfront, monthly platform fees	Limits on logic, data portability and scale
Freelancer	Well-defined, small projects	Hourly, often CHF 120 to 180 per the Swiss freelancer guide	Single point of failure: illness, availability, no second pair of eyes
Large agency	Big organizations needing process and capacity	Highest day rates, layers of management	Junior staff doing the work, staff rotation
Offshore team	Cost-driven projects with strong in-house product management	Lower rates, high communication overhead	Time zones, quality control, rework
In-house hire	Long-term product with continuous development	Salary plus social contributions and recruiting time	Hiring takes months, and one person is rarely enough
Small senior-led studio	Startups and SMEs needing a reliable build with one accountable team	Fixed scope per project, monthly for advisory and support	Capacity is limited by design

No-code and low-code

For a first test with real users, a no-code tool can be the right choice. You can often get a prototype running in days. The trade-offs show up later: complex permissions, performance, and getting your data and logic out if you outgrow the tool. A good rule is to use no-code to learn, and to plan the move to custom code before you depend on it commercially.

Freelancers

A strong freelancer is excellent value for a contained project. Be clear about who owns the code, who maintains it, and what happens if they become unavailable. If your app becomes critical to the business, you will want documentation and a second person who knows the system.

Large agencies

Large agencies bring capacity, process and brand comfort. You pay for that in rates and, often, in the layering between the person who sells the project and the person who builds it. For enterprise procurement that may be what is needed. For a startup or an SME it is frequently more structure than the project requires.

Offshore development

Lower hourly rates are real. So are the costs that do not appear on the invoice: more time spent writing specifications, review cycles across time zones, and rework when intent is lost in translation. The Bern survey of Swiss software companies cited above is a reminder that even firms that outsource do so mainly for access to skills, not just price. Offshore works best when you have a strong technical product owner on your side.

Hiring in-house

One senior developer in Zurich is an annual commitment well above the cost of many first projects, before you add the second person you will need for reviews, holidays and resilience. In-house makes sense once you have a product that needs continuous development. It is a poor way to build a first version when you are still learning what the product is.

A small senior-led studio

This is the model we run at Ampersand, a small studio in Zurich. Senior engineers are involved from the first consultation to handover, so the person who understands your problem is the person who builds the solution. That continuity is what prevents rewritten requirements, mid-project staff changes and dependency traps. We also aim to hand the project over in a state where you can work with it independently, rather than locking you in. Our work includes projects for UBS and the City of Lugano.

How we price web app work at Ampersand

We do not publish prices for most of our services, because a fair price depends on scope. Here is how our offers are structured.

• Build: Website, web or mobile app / MVP, and platform projects are scoped as fixed-scope projects, so you know what the first release contains before work starts.
• Advisory and technical leadership: Advisory, Embedded and Full embed levels cover senior technical guidance, up to part-time CTO involvement, billed monthly.
• Run and support: Our Run & monitor plan costs 750 CHF per month. It covers ongoing monitoring and support after launch, which many buyers forget to budget for.
• Coaching: Guidance is 799 CHF per month for product coaching.
• Integrations, automation and migration: Single connection and Integration suite for linking shops, CRM and ERP, workflow automation with AI, and website, system or full replatform migrations.

All plans and services are listed on our pricing page. If you are not sure which tier your project falls into, an initial consultation is the quickest way to find out.

The costs people forget

A quote for the build is not the total cost of ownership. Plan for these lines from the beginning:

1. Hosting and infrastructure. Small apps are cheap to run, but production setups with backups, staging environments and monitoring add up. If your team needs heavy compute during development, such as GPU workloads, it can be cheaper to rent capacity by the minute: cloud-based Windows desktops with GPUs are one example of that approach.
2. Third-party services. Email delivery, payments, maps, authentication and AI APIs usually charge per use or per month.
3. Maintenance. Dependencies need security updates, browsers change, and bugs appear with real use. A monthly support plan is far cheaper than an emergency fix.
4. Data protection work. Privacy notices, consent flows, deletion processes and records of processing are part of a compliant launch under the revised Swiss law.
5. Content and data migration. Moving existing data from spreadsheets or a legacy system can take longer than building the screens that display it.
6. Your own time. Someone on your side needs to make decisions quickly. Slow feedback stretches schedules, and schedules are money.

A worked example

Imagine a Zurich logistics startup that wants a customer portal: sign-in, order overview, document downloads, and a link to its existing ERP.

The visible part, three or four screens, is the smaller share of the work. The larger share is the ERP connection, permissions so customers see only their own orders, and data protection decisions about stored documents. A sensible approach is to split it:

1. A short paid discovery or audit to define scope and surface risks in the ERP.
2. A first release with sign-in, order list and one integration, built as a fixed-scope project.
3. A support plan once real customers are using it.
4. Further releases only after you see what users actually do.

This keeps the first commitment small and keeps decisions grounded in evidence instead of guesses. It is also the most reliable way to avoid paying twice.

How to get a quote you can compare

Prices from different providers are only comparable if they describe the same thing. Before you request quotes:

• Write a one-page brief. Who the users are, the three most important things they must be able to do, and the systems you must connect to.
• Separate must-have from nice-to-have. Ask for the first release to include only the must-haves.
• Ask who will do the work. Names and seniority, and whether they will stay on the project until handover.
• Ask about ownership. You should own the code, the data and the accounts, with documentation to match.
• Ask what is not included. Hosting, testing, data migration, training and support are common gaps.
• Ask how changes are handled. A fixed scope needs a clear process for what happens when you add to it.
• Compare at least two different types of provider. For example a freelancer and a studio, not three near-identical offers.

A marketplace like Gryps lets you request free, non-binding offers from several development firms, which can be a useful way to calibrate expectations before you choose.

Work with us

If you are planning a web app, MVP or platform and want a senior engineer on the first call, not a salesperson, see our services and plans. Tell us what you want to build and what systems it must connect to, and we will tell you honestly what it involves and whether we are the right fit.

FAQ

How much does a web app cost in Switzerland?

A very simple web app can start around CHF 3,000, and a simple mobile-capable web application averaged CHF 11,400 in the same comparison. Apps with several roles, integrations and compliance requirements cost considerably more, and the figure depends on scope. A scoped quote is the only reliable number.

Is a web app cheaper than a native mobile app?

Often yes, because you build one product that runs in the browser on every device. In the Gryps comparison, a simple native app is listed from CHF 5,000 for iOS or Android, and the mobile-friendly web version of a simple app averaged CHF 11,400 against about CHF 10,600 for iOS. So the difference depends on the app. Choose by what users need, such as push notifications or device features, not only by price.

Why is software development so expensive in Switzerland?

The main reason is labor. Skilled developers are scarce, as Netzwoche reports, and salaries and living costs are high. Senior-led teams cost more per hour but can spend fewer hours on rework.

Do I need to budget for data protection?

Yes. Under the revised Data Protection Act, in force since 1 September 2023, privacy by design and by default must be considered from the planning phase. If your app handles sensitive data or you are unsure what applies, speak to a Swiss data protection lawyer.

What does it cost to run a web app after launch?

Expect hosting, third-party services and maintenance. At Ampersand, our Run & monitor plan is 750 CHF per month. Your actual running cost depends on traffic, integrations and how much you keep improving the product.

Sources

• App-Entwicklung für KMU: Kosten (Gryps)
• Kosten für eine Softwareentwicklung (Gryps)
• Selbständig als Programmierer in der Schweiz
• E-Commerce-Sites und Datenschutz (KMU-Portal)
• Swiss Software Industry Survey 2022 (University of Bern)
• Vom IT-Systemintegrator zum Digital-Transformation-Partner (Netzwoche)
• Saläre der ICT 2025 (swissICT)