The Suniworks journal

Custom software or SaaS: choosing for a Swiss SME

Compare an existing SaaS product, a dedicated business application and a hybrid approach. Assess workflow fit, costs over three years, maintenance, data access and the practical conditions for changing supplier.

Updated on .

A workstation exchanges folders with a remote service and a dedicated server connected through a gateway.

Choose between custom software and SaaS by testing how each option handles a complete piece of work in your business. Give an existing product priority when it meets essential requirements without unacceptable workarounds; investigate a dedicated application or a targeted addition when important business rules remain unsupported. For your Swiss SME, compare costs over three years and the arrangements for continuing with another supplier alongside functional fit.

The essentials before comparing suppliers

  • Try standard software first when its current capabilities cover the work and your team accepts the remaining differences.
  • Consider a custom component when the existing product works well apart from a clearly defined gap.
  • Assess the whole arrangement: users, connections, maintenance, data recovery and the practicalities of leaving.

Define the work before choosing the software

Write down the required outcome before discussing screens. SaaS describes a software delivery model in which customers use the provider’s applications on cloud infrastructure. Custom software can also be delivered as SaaS. This guide compares an existing SaaS product with an application commissioned for your business; a hybrid approach keeps the existing product and adds a dedicated component.

Focus on what each offer lets you use immediately, configure or commission, and on the responsibilities included in the agreement. Evaluate specific offers rather than assuming that either category guarantees control or business fit.

Choose a completed job and reconstruct its journey. Identify who received the request, which information they needed, where approval occurred and what reached the next person. Use that same case to assess every candidate.

Separate essential rules from inherited habits

An unusual way of working deserves examination before it becomes a development requirement. Ask what each step protects: a pricing rule, a customer commitment or an approval that matters. If its purpose remains unclear, settle that question before commissioning software to reproduce it.

Consider a hypothetical Swiss joinery business preparing quotations from dimensions, materials and production constraints. Its evaluation should establish whether the software can represent those rules and pass approved information to production. The presence of a quotation screen would only be the starting point.

Describe each essential requirement as something your team can check. For example: an approval must retain the manager’s decision and pass the approved details to preparation. That statement gives a product supplier and a developer the same outcome to address.

Compare SaaS, custom software and a hybrid approach

Use the table to structure supplier questions. Its entries are checks to carry out, not guaranteed characteristics of every product or development contract. Ask candidates to distinguish an existing capability, configuration work and a function that still needs building.

CriterionExisting SaaS productDedicated applicationHybrid approach
Business fitDemonstrate essential rules using available features and settings.Specify the rules to build and how your team will accept them.Define what stays standard and what the addition must handle.
UsersCheck billable accounts, access profiles and the required subscription plan.Request costs for access, expected capacity and any third-party licences.Count users in each component and specify individual accounts with access according to their roles.
IntegrationsConfirm which connections are available in the selected offer.Include required exchanges with other systems in the development scope.Assign responsibility for every connection between components.
MaintenanceIdentify the supplier’s services and configuration work left to your team.Budget for corrections, operation and future changes.Include upkeep of the addition and its connections to the standard product.
DataRequest storage locations, participating organisations and access arrangements.Specify hosting and operational responsibilities.Describe where information is held and how it moves between systems.
ExportInspect an export actually produced by the product.Define the information and formats that must be recoverable.Check recovery of information distributed across the components.
Exit and handoverExamine departure conditions and available assistance.Specify rights, source code, documentation and transfer arrangements.Check whether each component can be taken over or replaced separately.

Request evidence appropriate to each commitment. Ask to see a function that already exists. Ask for a description of configuration work. For a proposed development, agree what will count as acceptance. Keep these distinctions visible in your comparison rather than treating every positive answer as equivalent.

When should an existing SaaS product win?

Start with standard software when the need is common and adequately covered by the market. Examine existing products for email, routine administration or electronic signatures, then check them against your particular constraints.

SaaS is a reasonable choice when your team accepts its workflow, the necessary subscription fits the budget and you are comfortable with the supplier directing the product’s development. A preference for a different screen or an old working habit should be weighed against the effort of a dedicated project.

If requirements are still changing, use a trial to clarify them. Assess internal availability too: someone must explain the business rules, resolve conflicting requests and accept deliveries during development.

Test your cases rather than following the sales demonstration

Prepare an ordinary case and a representative exception. Ask the supplier to demonstrate a correction, a rejected approval and the transfer of information to an application you already use. Record the manual operations that remain and ask your team whether they are acceptable.

An existing product can be the better choice without reproducing your current organisation exactly. Prefer it when essential requirements are met and the differences are understood and accepted. Do not add custom scope simply because a developer could build it.

When is a dedicated application or addition worth studying?

Investigate custom development when an essential rule cannot be handled adequately in the products evaluated. Duplicate entry and work performed outside the main application are signals to examine. They do not, by themselves, establish that replacing everything is the right response.

For each difficulty, ask whether configuration, a connection or a limited module could resolve it. Compare that answer with the scope of a complete application. Keep the required outcome unchanged so that a smaller proposal does not appear cheaper merely because it leaves important work uncovered.

Keep the standard foundation when the gap is limited

In a hypothetical retail business, the existing application could retain sales and invoices while a dedicated module prepares orders according to particular rules. The decision would concern that preparation task, rather than rebuilding every function already working satisfactorily.

An application programming interface, usually shortened to API, defines how software can exchange information. Before selecting a hybrid arrangement, ask the suppliers to confirm the exchanges their offers support. Specify which application holds the authoritative record for each item and who handles a failed transfer.

Include connection maintenance in the proposal. Ask for a demonstration of the full workflow, including an unsuccessful exchange, and agree who handles failures and how staff should respond.

Calculate the total cost over three years

Compare the same functional scope over the same period. Total cost of ownership brings together the expenditure needed to implement and operate a solution, beyond its initial purchase or subscription. Include internal work and manual operations that will remain, whether you choose SaaS, custom software or both.

A formula to populate with your own figures

Total cost over three years = implementation + subscriptions and licences during the period + hosting and maintenance during the period + planned integrations and changes + internal work and remaining manual operations + an exit allowance.

This formula is a budgeting framework, not a price estimate. Three years is the comparison period chosen here; adapt it to your decision. Retain the quotation, invoice or stated assumption behind every entry. Count each item once: hosting or an integration already included in a plan must not be added again.

  • For SaaS, use the plan you actually need, its add-ons, paid connections and expected users throughout the period.
  • For custom software, separate scoping, construction, testing, deployment, operation and anticipated changes.
  • For a hybrid approach, add the retained products and the new component, counting each service only once.
  • For every option, distinguish supplier invoices, valued internal time and allowances that remain uncertain.

The exit allowance is a comparison provision for recovering information and continuing elsewhere. It does not assume that you will leave at the end of the period. Ask what can be estimated and keep unknown items visible rather than entering them as zero.

Keep assumed savings separate from observed work

To value a manual operation, record its frequency and observed duration, then apply an internally approved hourly cost. Separate potentially removable work from approvals that will still be necessary. Do not count all current effort as a saving if the proposal addresses only part of the workflow.

Prepare a scenario using current staffing and another using your own staffing assumption. Keep quotations in their original currency and explain any conversion used in your Swiss budget. A universal user threshold or subscription amount should not replace this calculation.

Check exclusions before comparing totals. If an offer includes training, support or historical records while another excludes them, request the missing scope or show the difference separately. A lower total is useful only alongside a clear account of the work it covers.

Examine data arrangements and the ability to leave

Ask the same operational questions of every candidate: where will information be held, which organisations can access it and how can you recover it? Assess the specific offer. Do not equate SaaS with foreign hosting or assume that commissioning an application automatically gives you control.

Request a written description of processing locations, participating organisations and access arrangements. Switzerland’s data protection authority explains that outsourcing personal-data processing does not remove the controller’s responsibilities. Have commitments assessed for your situation; server location alone does not establish compliance. The linked official guidance is in French.

Our page on data control and handover explains the questions to settle when commissioning an application. Confirm the actual terms in the proposal for your project.

Inspect an export and a practical handover

Exit arrangements describe how you can leave a solution and continue elsewhere. An export is part of that preparation. Its contents must still be assessed for use in the replacement application; retrieving files does not complete the transition.

Request an example export and check the information essential to your work. For a dedicated application, specify the intended rights to use and modify it, access to source code and the documentation to be delivered. Source code is the set of instructions that developers can read and change.

Ask what another provider would receive to take over operation. Keep rights, access and practical handover as separate questions. Do not infer ownership simply from having financed development, or treat a foreign guide’s legal explanation as a ready-made clause for your Swiss agreement.

Use a short decision grid

Record a conditional recommendation for each workflow. The following grid is a decision method, not a financial score or a guarantee that a category will outperform another.

  • If a product meets essential requirements and your team accepts the differences, make SaaS the priority candidate.
  • If the standard foundation works and the gap is bounded, compare a targeted addition with full replacement.
  • If essential business rules remain unsupported, request a development study for the affected scope.
  • If the intended workflow remains unsettled, resolve the business decisions before commissioning its construction.

A cheaper proposal must still meet the agreed requirements. An extra function needs a reason to justify its cost. Keep unresolved disagreements visible in the decision note instead of hiding them inside an overall rating.

Where to start this week

Prepare a common brief so suppliers answer the same need. Use anonymised documents and name the person who will accept the result.

  • Choose a workflow and describe its intended outcome, essential rules and representative exceptions.
  • Collect contracts, expenditure and observations of manual work for the three-year comparison.
  • Have candidates demonstrate the same cases and answer separately on gaps, connections and departure arrangements.
  • Compare commitments, then make the next stage conditional on acceptance criteria and an explicit maintenance budget.

For development, request a limited initial scope and progressive acceptance. Suniworks explains its approach to custom application development. For an existing SaaS product, test the complete workflow before extending use and obtain a detailed proposal for the remaining gaps.

A software decision to prepare? Tell us about the context and the work your application needs to support.

Discuss your project