5,0/5 Google · 167 reviewsWe do not check reviews of us on other platforms that we do not quote verbatim for authenticity. They may therefore also come from people who are not our clients. The rules of the respective platform apply. Reviews that we quote verbatim on our website, by contrast, have been checked for authenticity within the meaning of Section 5b(3) UWG (German Act against Unfair Competition): we compared the reviewers’ names with our client register. We also asked the respective platform to check the reviews for authenticity.Period: October 2016 to date · As of: 17 November 2026
Enterprise ready check for SaaS start-ups
Procurement-ready, not just demo-ready
Is your first larger customer asking to review the contract, the service description, customer service, data processing and the chain of title? We classify what must be in place before the pilot and procurement, which points block the deal and what can be caught up later.
Enquire without this information
Please enter a short description first.
The first contact is free of charge. Before any costs arise, we will tell you explicitly.
Response within 24 hours on working days
As of: 23.10.2026
Before the deal3 of 5
- Terms and service descriptionIn place
- DPA and sub-processorsIn place
- The SLA fits customer serviceReview
- Chain of title in the codeIn place
- Vertragsverhandlungseparates MandatMissing
Checkpoint: Does the sales promise hold up in the contract?
- 1Stand schildernProduct and customer
- 2Blocker trennenDeal-Risiken priorisieren
- 3Keep the lineWhat must be in place now
Schematische Darstellung. Beispiel vereinfacht.
We support start-ups with
- SaaS-Produkten
- AI functions
- API-Diensten
- Plattformen
- B2B-Software
Key points at a glance
- With the first larger customer, procurement, the pilot contract, the DPA, security questions, sub-processors, customer service and exit all land on the table at once.
- ITMR separates genuine closing and pilot blockers from points that can be caught up later.
- You then know what must be in place before the deal and when IT contract, data protection, open source, AI or trademark should be taken further.
- We conduct the negotiation of a specific contract on request as a separate mandate.
- Your contact is Jean Paul Bohne and his team. He is a certified specialist lawyer for IT law and for copyright and media law (Fachanwalt). Response within 24 hours on working days.
- SaaS
- Software as a Service. Software used over the internet rather than installed.
- SLA
- Service level agreement. It sets out availability, response times and customer service.
- Open source
- Software with open source code. Its use is governed by the respective licence.
- GDPR
- The EU General Data Protection Regulation (GDPR). It governs how companies may process personal data.
Starting position
When does the first customer become a matter for review?
When an interested customer asks more than expected and requests its own documents.
An enterprise deal fails because of an unclear or contradictory structure, not because of missing paper.
The pilot customer wants to see terms, the DPA and the service description. Anyone who has to give internal approval needs clear statements on the service, customer service, roles, data processing and sub-processors.
A larger customer sends its own contract documents. It must now become visible what is negotiable, where the risks lie and what you can actually promise.
Sales promises more than the contract and customer service cover. That leads to expensive follow-on problems because sales, product and the legal structure are at different stages of maturity.
External developers, tools, AI models or open-source components become relevant to the review. It must then be clear what is documented and what needs a deeper review.
- For whom
- SaaS start-ups in B2B sales
- Trigger
- Pilot, Procurement, erster Enterprise-Deal
- Core
- Terms, DPA, SLA, Rechtekette
- Hearing
- separately, on request
It becomes particularly risky when the customer sends its own DPA, security or procurement documents, or when sales has already made promises. Early prioritisation then saves weeks.
This page is the right fit when several points that matter for the deal have to be sorted at the same time. If the data-protection approval before go-live is the focus, the data protection set-up is a better fit.
Describe the product and the state of the deal via the form. We will get back to you within 24 hours on working days.
Process
How does the start-up conversation run?
From the state of the deal to a clear line in three steps.
01
Stand schildern You state the product, the target customers, the deal status, the documents you have and the places where the contract, DPA, SLA or rights do not fit together.
02
Blocker trennen We separate genuine closing or pilot blockers from points you can catch up later without putting the customer relationship at risk.
03
Keep the line You know what must be in place before the deal, where a deeper review is needed and how product, sales and the law come together.
What should be in place before the first larger customer
- 1
Vertragsstruktur
The MSA, terms of use, pilot contract, service description, termination, exit, liability, customer service and change rules must fit the product.
- 2
DPA and data processing We clarify the points that become relevant to approval in the deal immediately, namely roles, sub-processors, transfers, categories of data, erasure and access.
- 3
Customer service and SLA Response times, escalations, maintenance windows, service limits and security questions quickly move into the closing. Promises must be operationally sustainable.
- 4
Chain of title and third-party components We classify external developers, agencies, open source, AI components, data sources, APIs and hosting so that the customer does not get stuck on an avoidable uncertainty.
Service
What does the enterprise ready check cover?
Service package: enterprise ready check
Deal-Unterlagen sichten Review terms, DPA, SLA, service description and customer documents for contradictions.
Prioritise blockers Separate genuine closing obstacles from points that can be caught up later.
Zusagen abgleichen Match sales statements with the contract, customer service and the reality of the product.
Rechtekette einordnen
Review the documentation of rights in code, content and third-party components.
Vertiefung empfehlen Say when IT contract, data protection, open source, AI or trademark should be taken further.
- For whom
- SaaS start-ups in B2B sales
- First response
- within 24 hours on working days
- Costs
- We tell you the costs transparently before you instruct us.
- Not included
- Drafting the contract, negotiating with the customer and a complete data-protection set-up. We take these on, on request, as a separate mandate.
- Product description and target customer
- Terms, DPA, SLA so far as they exist
- The customer's documents
- Contracts with developers and service providers
- Review and matching
- Prioritised list of blockers
- Recommendation for a deeper review
- Conversation with your team
- You, on promises and the sequence
- The customer, on approval and closing
- 1
First assessment You describe the product and the state of the deal via the form. We assess which scope is appropriate.
- 2
Offer Before we start, we tell you the scope and costs transparently.
- 3
Court steps separately We agree court proceedings and representation separately.
Failure patterns
Which mistakes slow down the first deal?
Four patterns we see in young SaaS providers.
T&Cs, DPA and service description were created separately. Sales then promises something different from what the terms or customer service can deliver.
The product convinces, but questions on the contract, roles, sub-processors, SLA or evidence lead nowhere.
Some teams turn the deal into a GDPR construction site. Others ignore DPA and role questions that matter for the deal for too long.
If customers, investors or procurement follow up, oral assurances and scattered documents are no longer enough.
Specialist pages
When is another page a better fit?
If the emphasis lies elsewhere, a deeper page leads to the goal more quickly.
When consent, tracking, tools, privacy notices or go-live approvals form the emphasis.
Start-up advice
When the early legal phase as a whole has to be sorted.
When the specific draft contract or the negotiation is at the centre.
Open source law
When licence chains or copyleft risks become the main question.
AI Law
When AI functions, roles or regulatory requirements shape the deal.
When the name and market presence themselves become the bottleneck.
Legal framework
Which rules does an enterprise customer review?
If you process personal data on the customer's behalf, Article 28 GDPR requires a data processing agreement. You may engage further sub-processors, under Article 28(2) GDPR, only with the customer's authorisation.
Transfers to third countries are permitted only under the conditions of Articles 44 et seq. GDPR.
Standard terms are also, as between companies, subject to content review under section 307 BGB in conjunction with section 310(1) BGB.
Rights in software created by employees sit, under section 69b UrhG, with the employer. That does not apply to external developers; a contractual grant of rights is needed here.
Since 12 September 2025 the Data Act rules on switching between data processing services have applied, under Articles 23 et seq. of Regulation (EU) 2023/2854.
- Art. 28 GDPR Data processing on behalf.
- Section 307 BGB Review of content.
- Section 310 BGB Scope of application in business dealings.
- § 69b UrhG Software created by employees.
- Data Act (EU) 2023/2854 Switching between data processing services.
Limits
What is not part of the check?
Clear boundaries keep prioritisation and a deeper review apart.
- 1
No negotiation in the package We conduct negotiation and contract drafting as a separate mandate.
- 2
No data-protection set-up We clarify DPA questions that matter for the deal, not data protection in the company as a whole.
- 3
No promise of outcome Whether the customer gives approval is for the customer to decide.
- 4
The decision remains yours We prioritise. You decide on promises and the sequence.
- A list of genuine blockers and of points that can be caught up later.
- Clarity about which promises the contract and customer service cover.
- A recommendation as to which deeper review is useful before the deal.
Lawyer and mediator · Partner · Specialist lawyer for IT law · Specialist lawyer for copyright and media law
View profile: Jean Paul Bohne Düsseldorf, Schirmerstraße 80 · Hamburg, Palmaille 124
TOP lawyer 2027 · Business lawyers · Intellectual property
F.A.Z.-Institut and QuantiQuest. Based on recommendations by fellow professionals and assessments by in-house counsel. Quelle (opens in a new tab)
5,0 out of 5 · 71 reviews on anwalt.dePeriod: October 2018 to date · As of: 17 November 2026
“After a first meeting with Mr Bohne I received competent advice and useful tips. He clearly explained how I should proceed. …” (translated from German)
“After a very informative first discussion on the contract, Mr Bohne was able to answer all my questions and also draw attention to further issues. … I was spoken to plainly, which has certainly saved me a great deal of trouble.”
“Quick response from Mr J-P Bohne. In an initial consultation I received comprehensive advice on the problem. That enabled me to act on my own. Excellent!” (translated from German)
FAQ
What do SaaS start-ups ask before the first deal?
Does this still fit if the customer already sends its own documents?
Yes. It then quickly becomes visible whether the deal structure must be prioritised first, or whether the matter leads directly into a deeper review of the IT contract.
Are T&Cs and a privacy notice enough for larger customers?
We hardly ever see that. Larger customers ask about the service description, the DPA, sub-processors, roles, customer service, security and the actual reality of the product.
What if the DPA, SLA and service description do not fit together?
Then an approval backlog arises. The check shows what must be brought into line before the deal and what can be caught up in a controlled way.
Is this also the right fit for websites, shops or tracking?
Not as a first starting point. If consent, tracking, tools or go-live approvals are the focus, the data protection set-up is a better fit.
What applies if open source or AI is in the product?
Then an early classification is worthwhile. We prioritise risks that matter for the deal, instead of fully expanding every specialist topic at once.
When should we branch directly into the IT contract?
When an isolated draft contract or a concrete negotiation is the focus and no further deal prioritisation is needed.
Next step
Is your first enterprise deal coming up?
We usually do not see the damage in the first call. It arises in the procurement process, in the delay or in the customer's first hard follow-up question.
Helpful for the enquiry
- Product description and target customer
- Terms, DPA and SLA
- The customer's documents or questionnaire
- Contracts with external developers
A short description of the state of the deal is enough to get started.
Ersten Enterprise-Fall besprechen
For SaaS start-ups before a pilot, procurement or the first larger B2B deal.
Describe the product, the customer type and the state of the deal.
Related services
IT contract and software contract The specific contract and the negotiation.data protection set-up Approval before go-live.Service packages All packages.
