SaaS providers
Providers need terms that match product features, operational limits and support capability.
SaaS agreements in Germany · Berlin · advising across Germany
SaaS agreements in Germany
SaaS agreements need to connect product, operations and legal responsibility in language that supports scalable sales and durable customer relationships.
Who it is for
For providers and customers in the SaaS market.
Requirements change from early product stages to enterprise sales, particularly around scope, security and negotiation.
Business customers
Customers need clarity about availability, data handling, remedies and access after termination.
Product and management teams
Teams benefit when legal commitments and the actual technical architecture describe the same service.
Advice
A coordinated SaaS contract suite.
The main agreement, service description, SLA and supporting schedules are aligned with one another.
Service and availability
Scope, SLA and support should present one realistic account of the hosted service.
- Define features and exclusions
- Specify uptime and maintenance
- Address support, changes and deprecation
Data and security
Data processing roles, security promises and supplier involvement must reflect the real architecture.
- Map data flows and party roles
- Allocate security and cooperation duties
- Align schedules with the product team
Liability and exit
Liability, term and termination consequences affect how manageable outages or strategic changes will be.
- Assess realistic loss scenarios
- Set clear renewal and termination terms
- Plan data return and transition support
Contact
Making SaaS contracts scalable?
Outline the product, target customers and current documents. I can support a new suite or a focused upgrade.
How we work
Translate product knowledge into clear terms.
Technical and commercial workflows are captured first and then converted into understandable, durable provisions.
Request counselUnderstand the product and operations
We map the functions provided, data flows, suppliers and availability the operating model can realistically support.
Align the contract documents
The main agreement, service description, SLA and any processing agreement are checked for conflicting obligations.
Support negotiation and rollout
Material clauses are revised and the commercial, product and privacy teams are aligned for signing.
Practical perspective
What matters in practice
The following points explain typical decisions and dependencies in this area of advice.
Separate scope, uptime and support
The agreement should explain the contracted functions and how changes are communicated. Uptime and support commitments need measurable terms that reflect operations.
- Define the service and excluded features
- Specify measurement, maintenance windows and response times
- Align remedies and escalation for outages
Map data and responsibilities
Technical processing and contractual roles should match. Whether an Article 28 processing agreement is needed depends on the actual data flows and roles.
- Identify data categories, locations and subprocessors
- Allocate access, instructions and security responsibilities
- Plan export, return and deletion at exit
Plan for change and exit
Products evolve and customers depend on continuity. The agreement should provide workable rules for feature changes, price adjustments, termination and migration.
- Define a process for changing scope and price
- Align term and termination with investment
- Agree export format, deadlines and transition support
Read more
Reviewing a SaaS agreement: Five questions before signing →
Your contact: Dr. Philipp Lerch, attorney · Content last updated: 24 September 2026
Dr. Philipp LerchAttorney · Berlin
Profile
Legal precision meets commercial understanding.
As an attorney with experience at an international business law firm and an additional background in computer science, I combine corporate law expertise with a clear understanding of business models, processes, and technology.
- Former attorney at Hogan Lovells International LLP
- Two German honours examinations with a focus on commercial and corporate law
- Dr. jur. and LL.M. Corporate and Commercial Law, University of Sheffield
- B.Sc. Computer Science, Free University of Berlin
FAQ
Frequently asked questions
Which documents make up a SaaS agreement?
Depending on the offering, these may include the main terms, service description, SLA and a processing agreement where relevant. Defined terms, priorities and obligations should be consistent.
How should uptime be set out in an SLA?
An SLA should specify measurement, reporting period, maintenance windows, notification and consequences of a shortfall. The commitment should reflect the system actually operated and external dependencies.
When is a data processing agreement needed?
That depends on whether personal data is processed for a customer and on the parties’ actual roles. The processing activities should be assessed; a document title alone does not decide the issue.
What should happen to customer data at contract end?
Export, format, timing, assistance and deletion should be addressed before signing. The arrangement must work technically and align with the parties’ data protection duties.
Do you advise both SaaS providers and customers?
Yes. Providers need deliverable commitments and clear boundaries; customers need effective rights when services fail, change or end. The review reflects the client’s role and negotiating position.
Contact
Making SaaS contracts scalable?
Outline the product, target customers and current documents. I can support a new suite or a focused upgrade.