Concept card

Liability Cap

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Liability Cap?

Liability cap negotiation matters because the asymmetry is severe — a consultant earning thousands per engagement can be exposed to millions in client losses without one.

A liability cap is the contractual ceiling on the damages a consultant can be ordered to pay if delivered work causes the client a loss. It exists because the underlying risk is wildly asymmetric: a solo SAP analytics consultant earns perhaps eight hundred to fifteen hundred euros a day from an engagement, while a misconfigured data model or a botched migration can cost an enterprise client millions in remediation, lost revenue, or regulatory exposure. Without a cap, a single bad project can end a freelance practice; with an unreasonably generous cap for the client, the same is true in reverse. Article 1231-3 of the French Code civil gives a fallback — damages limited to what was foreseeable at signing — but almost every serious B2B contract overrides that default with an explicit number, so the negotiated figure, not the statute, usually governs.

The four cap structures, and when each is the right ask

Why it matters

The standard freelance ask is a multiple-of-fees cap (1-3x annual engagement fees, e.g. €100k engagement x2 = €200k cap) — the most common negotiable structure.
Gross negligence, death/personal injury, confidentiality breach, and IP infringement are typically carved OUT of the cap — the real exposure is often uncapped despite the negotiated number.
Without an explicit cap, French Art. 1231-3 defaults to foreseeable-damages-only — rarely the operative regime once client lawyers get involved.

Key points

Code civil Art. 1231-3 default: damages limited to foreseeable at signing (1-3× contract value).
Four cap structures: aggregate · per-claim · multiple-of-fees · insurance-backed.
Standard ask: aggregate cap = 2× annual fees, ≤ insurance limit.
Always exclude indirect/consequential damages (10-100× direct multiplier).
Sub-caps for confidentiality + IP infringement (1× annual fees each).
Mandatory carve-outs (uncappable): gross negligence · death · personal injury.
Cap > insurance = personal-bankruptcy risk; cap ≤ RCP €1-3M FR coverage.
Client refuses standard caps = walk away OR 30-50% day-rate uplift for risk.
Liability Cap is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

Liability cap: Contractual ceiling on damages owed by consultant if work causes loss to client.
Aggregate cap: Total liability across all claims under the contract is bounded. Most negotiator-friendly structure.
Multiple-of-fees cap: Cap = N × annual fees from the engagement (typically 1-3×). Standard freelance ask.
Carve-out: Liability category excluded from the cap (e.g., confidentiality breach, IP infringement, gross negligence).
Sub-cap: Lower-tier cap applied to specific carve-outs (e.g., 1× annual fees for confidentiality breach).
Indirect / consequential damages: Damages flowing from but not directly caused by the breach (lost profits, lost data, business interruption). 10-100× direct multiplier.
Faute lourde / dol: Gross negligence or wilful misconduct under French law. Caps on these are void by jurisprudence.
RCP (Responsabilité Civile Professionnelle): French professional indemnity insurance. Solo SAP analytics norm: €1-3M coverage.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →