Swiss companies entering nearshore arrangements for the first time tend to focus on the commercial terms — day rate, team size, start date. The legal scaffolding gets less attention, often because it feels like boilerplate. It isn't.

The five areas below are where contracts most commonly fail — not dramatically, but in ways that create real problems 12 or 24 months in, when the relationship is established and unwinding anything is expensive.

1. IP ownership: "work for hire" doesn't automatically apply across borders

In Switzerland, the assumption is straightforward: if you pay for it, you own it. But nearshore arrangements often involve engineers who are not your employees — they're employees of a nearshore entity, local freelancers, or contractors engaged through a staffing intermediary. The IP rules are different.

What goes wrong: Companies assume that because they're paying the invoice, they own the code. In many nearshore jurisdictions — Spain, Poland, Ukraine, and others — IP created by a contractor does not automatically transfer to the client. Ownership stays with the creator unless explicitly assigned in writing.

What to look for:

  • An explicit IP assignment clause: all work product is assigned to the client upon creation — not upon payment, not upon completion
  • Coverage of moral rights waiver where applicable
  • Clarity on pre-existing IP: any tools or frameworks the engineer brings must be listed, with a licence granted to you for their use

The red flag: Any contract that says IP transfers "upon final payment" rather than continuously as work is produced.

2. Notice periods: 30 days looks reasonable until you actually need it

Most nearshore contracts include a 30-day notice period. That sounds reasonable. In practice, it's often the wrong structure — and it can leave you exposed in two directions.

What goes wrong: A funding round falls through, a pivot changes your technical needs — 30 days means 30 days of billing for engineers you no longer need. Or an engineer exits and your notice period doesn't include any obligation to provide a qualified replacement within that window.

What to look for:

  • A replacement SLA: if an engineer exits for any reason, what is the partner's obligation to provide a replacement, and within what timeframe?
  • Graduated notice periods tied to team size or engagement length
  • A distinction between notice for convenience and notice for cause
  • A knowledge transfer obligation: the exiting engineer must spend their notice period on documentation and handover

The red flag: A contract that gives the nearshoring partner the right to reassign engineers with short notice and no replacement obligation.

3. GDPR and data processing agreements: the Swiss–EU boundary is more complicated than it looks

Switzerland's revised data protection law (nDSG, in force since September 2023) aligns closely with GDPR. Engineers working on Swiss client systems frequently access personal data — user records, customer data, internal HR systems. This creates a cross-border data processing relationship that needs to be documented correctly.

What goes wrong: Companies either skip the Data Processing Agreement entirely, or use a generic EU DPA template that doesn't account for Switzerland-specific nDSG requirements.

What to look for:

  • A DPA as a standalone exhibit, not buried in general terms
  • Clear designation of roles: you are typically the data controller; the nearshoring partner is the data processor
  • Specification of what data categories may be accessed, for what purpose, and for how long
  • Sub-processor obligations: tools and infrastructure used by the partner must be listed and approved
  • A 72-hour data breach notification clause, mirroring GDPR

The red flag: No DPA at all, or one covering only EU-to-EU processing without addressing the Switzerland dimension.

4. Governing law and jurisdiction: the wrong choice creates a problem you won't see until you have a dispute

Every contract needs to specify which country's law governs it and which courts have jurisdiction. In nearshore contracts between Swiss companies and providers abroad, this clause is often negotiated casually or defaulted to the provider's standard template.

What goes wrong: Swiss companies sometimes accept the provider's home jurisdiction without considering what that means. If a dispute arises over IP, invoices, or a data incident, you are litigating abroad, in a foreign language, under a system your lawyers may not know.

What to look for:

  • Swiss governing law (Code of Obligations) — the system your legal team knows
  • Jurisdiction in a Swiss court (Lucerne, Zurich, or your canton of registration)
  • An arbitration clause as an alternative — ICC or Swiss Rules arbitration is often faster for cross-border disputes

The red flag: A contract defaulting to the provider's home jurisdiction with no negotiation, or silent on governing law entirely.

5. The entire agreement clause and verbal commitments

During the sales process, nearshoring partners make commitments — about team composition, seniority, response times, replacement guarantees. Some make it into the contract. Many don't.

What goes wrong: The signed contract contains an "entire agreement" clause stating the written contract supersedes all prior representations. Everything said in the sales process but not written in is now unenforceable. If your account manager promised a 48-hour replacement SLA and monthly steering calls, and none of that is in the contract, you have no legal basis to demand it.

What to look for:

  • Any commitment that matters operationally should be in the contract or a signed exhibit — SLAs, team composition, escalation procedures, reporting obligations
  • If the provider resists putting specific commitments in writing, that tells you something about how seriously they take them
  • Review the entire agreement clause and ensure nothing meaningful has been left out

The red flag: A long sales process full of specific commitments followed by a short, generic contract with few operational obligations on the provider side.

A note on what this post is not: This is not legal advice. The specifics of any nearshore contract depend on the structure of the engagement, the jurisdictions involved, and the nature of the work. If you are entering a significant nearshoring arrangement, have a lawyer review the contract — ideally one with cross-border commercial experience.

What this post is: a checklist of the areas where we most commonly see contracts fail, drawn from five years of operating nearshore arrangements between Switzerland and engineering teams across Southern and Eastern Europe. Most of these issues are fixable before signing. Almost none are easy to fix after a dispute has started.

Frequently asked questions

Who owns the IP in a nearshore software development contract?

Not automatically the company paying for it. In many nearshore jurisdictions — Spain, Poland, Ukraine and others — intellectual property created by a contractor stays with the creator unless it is explicitly assigned in writing. A Swiss company only secures ownership with an IP assignment clause that transfers all work product to the client upon creation, plus a moral-rights waiver where applicable. A clause that transfers IP "upon final payment" is a red flag.

What notice period should a nearshore contract have?

A flat 30-day notice period is the most common structure and often the wrong one. It should be paired with a replacement SLA (how fast the partner must supply a qualified replacement if an engineer exits), a knowledge-transfer obligation during the notice window, and a clear distinction between notice for convenience and notice for cause. Watch for contracts that let the partner reassign engineers at short notice with no replacement obligation.

Do Swiss companies need a Data Processing Agreement (DPA) for nearshore developers?

Usually yes. Engineers working on Swiss systems routinely access personal data, which creates a cross-border processing relationship under Switzerland's revised data protection law (nDSG, in force since September 2023). You need a standalone DPA that names you as data controller and the partner as processor, specifies which data categories may be accessed and for how long, lists approved sub-processors, and includes a 72-hour breach-notification clause. A generic EU-only template that ignores the Swiss dimension is not enough.

Which governing law should a Swiss nearshore contract use?

Where possible, Swiss governing law (the Code of Obligations) with jurisdiction in a Swiss court — the system your legal team already knows. An ICC or Swiss Rules arbitration clause is a reasonable alternative and is often faster for cross-border disputes. Defaulting to the provider's home jurisdiction means litigating abroad, in a foreign language, under a system your lawyers may not know.

Is nearshore staffing safe for Swiss companies?

Yes, when the contract is structured correctly. The risk in nearshoring is rarely the engineering — it is the legal scaffolding: IP assignment, notice and replacement terms, a Swiss-specific DPA, governing law, and getting verbal sales commitments written into the contract or a signed exhibit. Address those five areas before signing and nearshoring is a low-risk way for Swiss companies to add senior capacity.