Author

Magdalena Vakulova
Senior Associate (Prague)
The deal is $180,000 a year, your largest by a factor of four. Their procurement team sent a 40 page master services agreement, a security addendum, an insurance schedule and a data processing addendum, and asked for redlines by Friday. Your entire contract stack until now has been a four page order form you wrote yourself.
You have two bad instincts here and both are common. The first is to sign it, because the revenue matters more than the paperwork. The second is to send it to a lawyer and redline all 40 pages, which takes three weeks, costs more than the first quarter of the contract, and makes you look like a company that cannot close.
Neither is right. In a first enterprise agreement, four clauses carry almost all of the risk. Read those properly, accept most of the rest, and you can turn a document around in two days without signing something that can end the company.
1. Limitation of liability, and what sits outside it
Find the liability cap. It is usually expressed as fees paid in the preceding 12 months, which on this deal means $180,000. That number is not the risk. The risk is the list of things carved out of the cap, because anything in that list is uncapped.
Typical carve outs are indemnity obligations, breach of confidentiality, data protection breaches, and gross negligence. If your indemnity is uncapped and broad, your true exposure on a $180,000 contract is unlimited, which is a different business decision from the one you thought you were making.
What to ask for: a mutual cap, carve outs limited to a defined multiple of fees rather than uncapped, and an explicit exclusion of indirect and consequential loss on both sides.
2. The IP indemnity
You are being asked to defend and indemnify the customer if your product infringes someone’s intellectual property. That is standard and you will not remove it. What you can do is make it survivable.
Three things matter. First, the indemnity should cover claims about your technology, not claims arising from the customer’s own data, their instructions, or your product combined with something you have never seen. Second, you want control of the defence, because otherwise the customer settles with someone else’s money. Third, you want the standard escape routes: if a claim lands, you can modify the product, procure a licence, or terminate and refund, rather than being on the hook indefinitely.
If you have a model or an open source component at the core of the product, read this clause twice. An AI product with a broad IP indemnity and no cap is one of the few ways an early stage company signs away more than it is worth.
3. Data protection, security, and the promises in the addendum
The security addendum is where European sellers get caught, because it is written as a list of things you already do. Encryption at rest and in transit, annual penetration testing, SOC 2, a named security officer, breach notification within 24 hours, sub processor approval rights.
Every line is a promise. If you do not have SOC 2, do not sign a document that says you do, and do not sign one that says you will have it by a date you have not planned for. Ask for the obligations you can actually meet and add a commitment to a roadmap date where you need one.
Watch the breach notification window in particular. A 24 hour notification obligation to the customer, running alongside your own regulatory obligations, is operationally hard for a team of nine people. 72 hours is a normal ask.
4. Term, renewal and how you get out
Read the term clause and the termination clause together, in that order.
An evergreen renewal with a 90 day notice window means the practical decision date is not the anniversary, it is three months before it, and nobody in your company has that in a calendar. Check whether termination for convenience is mutual or one sided. A contract the customer can exit in 30 days and you cannot exit at all is a commitment you should price differently.
Also check what happens on termination: data return and deletion obligations, transition assistance you may be required to provide for months afterwards, and whether fees are refundable.
What to accept without a fight
Spend your credibility on the four above. Most of the rest is boilerplate that a large customer will not move on and that will not hurt you: governing law and venue in their state, notice provisions, assignment on change of control, publicity restrictions, force majeure, the entire agreement clause.
One exception. If governing law lands in a US state and you have no US entity, ask yourself which company is signing. Selling into US enterprises through a foreign parent creates tax and enforcement questions that a US subsidiary avoids. This is one of the more common reasons founders flip earlier than planned.
Before your next enterprise deal
The reason this document took a week is that you were reacting. The fix is to have your own paper ready, so the next deal starts from your MSA and their redlines instead of the other way around. Our list of the seven legal documents to have in place before you raise or sell is a good place to check what you are missing.
This week, do one thing: open the last contract you signed, find the liability cap, and read the carve outs underneath it. If you cannot tell from the page what your maximum exposure is, that is the answer.
Get the next one first
One email a month on the US legal decisions that catch founders late: contracts, employment, equity, and the deadlines nobody invoices you for. Subscribe to the Fellow newsletter.
If recurring SaaS contracts like this one are becoming a pattern, a dedicated SaaS lawyer can handle the paper so legal stops being the bottleneck on every deal.



