Negotiation
Signing on the customer’s paper in the EU: what to accept, what to change
A large European customer will usually insist on its own template, and send it with several attachments. Refusing can lose the deal; accepting blindly costs more. The skill is knowing which clauses are theirs to keep and which you must change.
3.1 Vendor shall deliver and install the Software at Customer’s designated site. Customer shall have thirty (30) days to conduct acceptance testing against the Specifications; payment is due upon written acceptance.Vendor shall make the Service available to Customer via the internet from the Subscription Start Date. The Service is provided in accordance with the Documentation.
- Working from a customer's paper is often the right commercial call. Accepting it unchanged almost never is.
- The form was written for buying services or hardware from large vendors, and much of it does not fit a SaaS product.
- Fix the structural mismatches and the four or five money clauses. Leave the rest and close.
- In EU deals the template is a package: check the order of precedence first, because the buyer’s purchasing terms often sit on top.
Why they insist
An enterprise procurement team works from a template its legal department approved, its insurers reviewed and its systems are built around. Insisting on it is not hostility; it is how the company buys everything. A vendor that refuses to engage asks the customer to run an exception process, and many customers will choose a competitor who does not.
So the starting position is usually yes, we will work from your paper. The question is what to change.
First: does the form fit the product?
Most customer templates were written to buy services or on-premise software. Read the whole form once with a single question: does it describe what we sell? The usual mismatches:
- Delivery and acceptance clauses that assume software is delivered and installed, with acceptance testing before payment. A SaaS product is accessed, not delivered. Replace them with provisioning and access terms.
- Source code escrow. Meaningless for multi-tenant SaaS. Remove it, or replace it with data export and transition terms that meet the real continuity concern.
- Ownership of deliverables clauses under which the customer owns everything created. Fine for bespoke development; disastrous for a product you sell to everyone. Carve out the platform and anything not created uniquely for them.
- A warranty of conformance to specifications where none exist. Replace it with a warranty that the service performs materially in line with the documentation.
- Site access, personnel and background check clauses that assume staff on the customer’s premises.
These changes are structural, not adversarial, and a reasonable customer accepts them quickly once the mismatch is explained. Lead with them.
Second: the money clauses
With the structure fixed, turn to the few clauses where the form puts risk on the vendor in ways the price does not reflect.
- Liability cap. Customer forms often leave vendor liability uncapped, or cap the customer’s liability only. Propose a mutual cap at a defensible multiple of fees. Under German law check the standard-terms limits first: see the liability guide.
- Indemnities. Narrow a general indemnity to third-party IP claims and, if needed, breach of confidentiality and data obligations.
- Data terms. Make sure your DPA governs the processing, and not an old confidentiality clause that does not meet regulatory requirements.
- Termination for convenience. Customer forms often let the customer terminate at any time on short notice, with a refund. In a committed-term subscription that destroys the economics: negotiate it out or price for it.
- Most-favoured-customer and audit clauses. Resist the first, and limit the second to what a third-party report can satisfy.
Third: leave the rest alone, but read the package
Their notice clause, their boilerplate, their formatting. Every change costs a round, and every round costs a week. A redline with sixty changes tells the other lawyer you have not prioritised, and invites a fight over everything. A redline with twelve changes, each explained in a line, gets accepted. Their governing law is the exception: check it before you leave it alone.
In an EU deal the “contract” is usually a set: a master agreement, a data processing agreement, a security addendum and, often attached without comment, the buyer’s general purchasing terms. The purchasing terms frequently hold the worst clause in the package and apply unless the master agreement says they do not. Ask for an order of precedence that puts the order or statement of work first and the purchasing terms last, expressly excluded where they conflict. The detail is in the German enterprise MSA guide.
Send the redline with a short note: three structural changes because the form assumes on-premise delivery, four risk changes with a one-sentence reason each, everything else accepted. Counterparty lawyers are busy, and a note that lets them approve in ten minutes gets approved in ten minutes.
Next step
Have a contract like this on your desk?
Send it over. We will mark it up and walk you through it in twenty minutes — no cost, and you will know whether the desk is worth it.