What does a business web app cost in Switzerland?

The cost of a custom business web app in Switzerland depends on the work it must support, the systems it must connect and its operating requirements. Roles, business rules and integrations weigh more than the number of screens, so a useful estimate starts from a defined work process. Separate scoping, the first release, subsequent improvements and recurring costs when comparing quotes.

Start with a working process

For an SME in Vaud or French-speaking Switzerland, replacing spreadsheets might mean centralising records, approving requests or giving clients access to a portal. These projects can have similar screens while requiring very different work.

Describe a real case, from creation to closure. Who takes part? Who can view, change or approve what? What happens when a request is rejected, corrected or reopened? User numbers matter for capacity and operation. Roles, exceptions and approvals also determine what needs building and testing.

If the need is still uncertain, our guide When should you replace Excel with a custom app? helps identify what warrants specific development.

What changes the quote

Two quotes are comparable only if they cover the same situations. The diagram shows scope choices to discuss, without assigning them the same weight in every project.

Focused scope

Additional work

One team with shared permissions

Several organisations with permissions per record

One workflow and its priority exceptions

Multiple approval paths and exceptions

A controlled import on an agreed date

Continuous exchanges with several tools

Data sorted before migration

A history to clean and reconcile

Shared interface components

Specific interactions to design and test

Connections to an ERP, CRM or accounting system require more than transferring fields. Specify which system is authoritative, the direction of exchanges and what should happen if a connection fails. Request documentation, a test environment and access to the supplier's contact before fixing the price. Their licences or services are a separate cost.

Migration deserves its own line. Who resolves duplicates, transfers attachments and checks totals? Define what to retain, a trial migration, approval by your team and a possible return to the previous tool.

Documents and exports are part of the product too. A downloadable list, a formatted document and an accounting export have different requirements. Provide anonymised examples and expected formats so they do not become discoveries at delivery.

Design costs depend on the workflows to study, user testing and interactions to adapt. A daily tool may justify substantial work on data entry, search and error handling. Reusing components helps concentrate that work on situations specific to your business.

Hosting, data and security

Ask where data and backups are located, and where the people with support access work. Specify whether hosting must be in Switzerland and have that requirement priced. Where the software is developed does not, on its own, describe where data is processed.

Request details of access controls, account deletion, records of sensitive actions, backups and restoration tests. Requirements for stronger authentication, audits or availability should appear in the scope. Decide who monitors the service and who responds to an incident.

A smaller first release means removing secondary uses. The safeguards needed for the data it handles still belong in the launch scope.

Commit the budget in stages

Scoping should support a decision before committing to implementation. Agree its budget in advance and, if deliverables are sufficiently defined, request a fixed-fee proposal. At Appik Studio, the first conversation is free; detailed scoping requires a separate agreement on deliverables, scope and budget.

1. Scoping

Workflows, data, dependencies and acceptance criteria. Decide which scope to fund.

2. First release

A usable workflow, its data migration and tests. Approve it before launch.

3. Improvements

Prioritise improvements based on use. Price each new phase before starting it.

From launch, then continuously: hosting, third-party services, monitoring, maintenance and support as agreed in the contract.

A first release might handle one type of case from start to finish and defer secondary dashboards. Document exclusions, client acceptance criteria and dependencies on your team. The next phase is priced on this basis, informed by actual use.

Budget separately for usage-based charges, fixes, security updates and user support. New features belong in an improvement budget. Specify agreed support hours and response times, along with included or excluded VAT and third-party costs.

Keep the option to change partners

Ask for the contract to specify ownership of custom code, rights to third-party components and handover conditions. Plan access to source code, exportable data, hosting accounts and deployment instructions. A handover to another team should have an identifiable scope and cost.

Resolve this before signing. Receiving code without the access or information needed to operate it leaves a dependency to address.

Which price references are useful?

The scenarios in How much does a mobile app cost in Switzerland in 2026? are indicative, dated and specific to mobile apps. They are neither a business web app price list nor a study of Swiss prices. Our calculator provides an initial complexity estimate to discuss with the team; it does not replace a quotation for an agreed scope.

Compare proposals using the same implementation and operating cost lines. Our guide How to compare mobile app development quotes in Switzerland provides a checklist whose questions about scope, exclusions and maintenance also apply to web apps.

To prepare a conversation about your internal tool or client portal, bring a sample case, the systems to connect and your main current difficulties. Our web development service describes our involvement.