SaaS and IT Contracts
SaaS, cloud, IT outsourcing and sourcing contracts for buyers and suppliers, from the request for information to the signed contract and the obligations that follow, with data, exit and AI clauses checked.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
The question
You are about to move a core process to a SaaS platform, outsource part of your IT, or replace a supplier who no longer delivers. Or you are the supplier, and a large customer sends a 60-page framework agreement with security annexes.
Either way, the contract decides what happens when the service is down, when data is lost, when the price goes up at renewal, and when you want to leave. Those are the clauses suppliers' standard terms tend to settle in their own favour, and the ones a buyer only reads when something has gone wrong.
Our approach
For a buyer, the contract starts before the contract. A structured sourcing process gives you comparable offers and a stronger negotiating position. We run it from the request for information to the signed agreement in our deal and tender environment. Suppliers get access only after accepting the confidentiality terms for the process. Each supplier sees only its own questions and answers, never a competitor's. Responses are collected against one set of questions so they can be compared like for like, offers can be submitted under seal and opened together at the deadline, and answers that contradict each other are flagged for the lawyer. The comparison ends in a documented award decision, which stays yours. Our article on running a request for information or proposal explains the steps.
Then the contract itself. For an ongoing relationship we usually recommend a framework with orders or statements of work underneath, as set out in master services agreements and SOWs. When the supplier's terms are the starting point, our contract review checks them clause by clause against our playbook, taking into account which side you are on, and ranks the issues by risk. Where we draft, we use our Document Studio and our clause library. Our technology is our own, and a lawyer reviews every finding and every draft before it reaches you.
The clauses we look at hardest:
- Service levels: what is measured, how, and what a missed level actually costs the supplier.
- Data: who may use your data and for what, where it is hosted, security commitments, and the data processing agreement where personal data is involved.
- Price: indexation, increases at renewal, and charges for extra users or storage.
- Liability: caps, exclusions and how they relate to the real exposure.
- AI: whether the supplier may train on your data, who owns outputs, and what happens when the supplier changes models. See AI clauses in vendor contracts.
- Exit: data return in a usable format, assistance during transition, and how long the service keeps running.
For cloud services, the Data Act (Regulation (EU) 2023/2854) has applied since 12 September 2025. Article 25 requires the switching rights to be set out in a written contract, with a notice period of at most two months to start the switch and a transitional period of in principle no more than 30 calendar days. Under Article 29, providers may charge no switching charges at all from 12 January 2027, and until then only reduced charges that do not exceed their direct costs. Our article on switching cloud providers covers the details. Our article on SaaS agreements covers the rest of a typical subscription.
After signature, the rights and obligations register follows service credits, renewal and notice dates, audit rights and exit windows, so that a contract does not roll over unnoticed.
What you get
- For buyers: a run sourcing process, with a question set, comparable responses, an award record and a negotiated contract.
- For suppliers: a contract set for your customers (framework, order form, service levels, data processing agreement), and support when a customer sends its own.
- A review note on the other side's draft, with ranked issues and proposed redlines.
- A short summary of the dates and duties after signature, with reminders.
- Contracts in Word, in English, Dutch, French or German.
There are limits. We advise on the legal terms and run the process; the technical evaluation of a platform, its security and its architecture stays with your IT team or advisers. A contract cannot make an unreliable supplier reliable. If you are a public authority, the procurement rules decide how you buy, see public procurement.
Next step
Send us the supplier's terms or the draft framework, or describe what you want to source and by when.
In short
- Sourcing run end to end: RFI, RFP, award and contract
- Supplier terms reviewed against our playbook
- Service levels, data and exit written so they work
- Cloud switching rights under the Data Act checked
- Obligations followed after signature