Your first SaaS contract: clauses that matter at seed stage

Your first paid customer will send you their paper or wait for yours. Send yours. A short, fair SaaS contract drafted for your business reduces every later negotiation to a redline conversation instead of starting from a Word document built for a different company. Plan to invest CHF 4'000 to 8'000 of Swiss commercial-lawyer time on the first template; you will reuse it for the next fifty customers.

The contract sits on top of the Swiss Code of Obligations: OR Art. 184 et seq. (sale and services), OR Art. 100 (liability waivers limited by gross negligence), and OR Art. 199 (warranty disclaimers). The FADP overlays it whenever personal data flows, which is almost always. Plant the contract in that frame and the rest reads itself.

Liability cap

The cap is the number your customer will negotiate hardest. Market for a seed SaaS in Switzerland is twelve months of fees paid in the twelve months preceding the claim, with carve-outs for confidentiality breaches, IP infringement and the gross-negligence floor that OR Art. 100 forbids you to waive anyway. Anything uncapped is a bet you cannot insure against (Swiss tech-E&O policies cap out at CHF 5 million for sub-CHF 10 million ARR companies, and the premium triples the moment uncapped IP indemnities appear in your stack).

An enterprise customer is asking for uncapped liability on IP infringement and confidentiality. Can I sign it?

Probably yes, with conditions. Uncapped for IP infringement is market-standard for enterprise SaaS once you have IP hygiene in place: a written third-party-licence inventory, no copyleft code in the shipped product, contributor-license-agreements for outside committers, and no training data of unclear provenance for any AI component. If you have all four, uncapped IP indemnity is signable. Uncapped for confidentiality is also signable if your breach-notification SLA is tight and you carry cyber insurance with a confidentiality endorsement. Anything else (uncapped for security, uncapped for SLA, uncapped for everything) means walk away or scope down.

Data and IP ownership

Be explicit. The customer owns its data, including personal data and the analytics derived from their tenant. You own the product, including any improvements you make to the platform while serving them. You receive a licence to use the customer data only to run and improve the service. Avoid clauses that hand the customer rights to derived data unless you have thought through what that means for your model, especially if you train AI on cross-tenant signals. A 'no use of customer data for training' clause should be either a hard yes or a paid upgrade tier, not a quiet concession.

Term, renewal, termination

An annual term with automatic renewal and a thirty-day notice window is the Swiss B2B SaaS default. Make termination for material breach mutual under OR Art. 107, with a cure period of thirty days. Termination for convenience is rare in B2B SaaS but customers ask for it; if you grant it, attach a pro-rata refund clause so cash flow is predictable and time it to a notice of at least ninety days so your forecast does not snap.

What is the difference between OR Art. 107 (material breach) and OR Art. 337 in my contract template?

OR Art. 107 governs commercial-contract termination for material breach after a cure period and is the right anchor for your SaaS termination clause. OR Art. 337 governs immediate termination of employment contracts for cause and has no place in a SaaS contract. If your template mentions OR Art. 337, it was copy-pasted from an HR document and you should rebuild from a Swiss commercial template.

Governing law and forum

Swiss law and an ordinary court at your registered seat (the Handelsgericht of your canton, Zurich and Aargau both run dedicated commercial courts that process disputes faster than ordinary courts) are sensible defaults. They are cheap to litigate (filing fees scale with claim value, typically CHF 5'000 to 25'000 for a CHF 500'000 dispute) and familiar to local counsel. Reject arbitration clauses pointing at expensive forums for early-stage deals; ICC or Swiss Arbitration adds CHF 50'000 to 150'000 of administrative cost before the first hearing, which makes sense only when contract value is above CHF 2 million.

Data residency without lying about it

Swiss enterprise customers in regulated industries (banks under FINMA, healthcare under HFG, public sector under FADP) will ask where the data sits. Name the AWS region (eu-central-2 Zurich, eu-central-1 Frankfurt are the common answers), name the sub-processor, and put it in the schedule. Do not promise 'Swiss-only' if Cloudflare or Postmark route through US edges; revise the architecture or revise the promise, but do not write a clause you will breach the next time you ship a feature.

Should I add a Most-Favoured-Nation clause for the first customer who asks?

No. MFN clauses (the promise that no other customer will get better terms) sound like a small concession at deal close and turn into a strategic straightjacket six months later when you want to do a discounted pilot or a strategic logo deal. If the customer truly needs price protection, give a fixed-percentage discount with a sunset, not an MFN. Once an MFN is in any contract, you must check every new deal against it for years.

Things to skip in version one

Service credits, SLA penalties and complex governance committees belong in enterprise contracts, not seed paper. Keep your first contract under twelve pages. If it is longer, you are negotiating against yourself.

Treat the first contract as a public artefact: every customer will see the same paper. Stand behind every clause, because the day you cannot explain a clause to a prospect is the day the trust in the rest of the contract evaporates.