Skip to main content
    Jacobs Counsel LLC logo
    All deal anatomies
    Tech, AI & SaaS · Deal Anatomy

    Anatomy of a SaaS MSA for an AI Startup

    What an AI-native enterprise MSA looks like in 2026 — model output ownership, training data rights, indemnity, and the clauses generic SaaS templates miss.

    What it is

    A Master Services Agreement (MSA) is the umbrella contract between a SaaS vendor and an enterprise customer, with deal-specific terms moved into separately signed order forms. For an AI startup, the standard MSA template needs AI-specific provisions that most off-the-shelf SaaS forms don't address: model output ownership, training-data rights, AI hallucination indemnity, and customer AI-use restrictions.

    Parties

    • Vendor
      Provides the AI/SaaS service.
    • Customer
      Licenses the service for internal use.
    • Sub-processors
      Foundation model providers, hosting, analytics.
    • End users
      Customer's employees or — sometimes — customer's customers.

    Clause by clause

    12 clauses · what it does, what's market in 2026, what to push back on.

    01

    License grant & scope

    Purpose

    What the customer can do with the service.

    Market term (2026)

    Non-exclusive, non-transferable license to use the service for the customer's internal business purposes for the term of the order form.

    Red flag

    License limited to a specific business unit or use case in a way that blocks future expansion. Or affiliate-use carve-outs that exclude subsidiaries.

    02

    Customer data definition

    Purpose

    Defines what counts as the customer's data versus the vendor's.

    Market term (2026)

    Customer data includes all inputs, prompts, outputs, and configuration. Vendor data is limited to anonymized telemetry and aggregated usage metrics.

    Red flag

    Vendor templates that classify prompts or outputs as 'service data' rather than 'customer data' — this matters because the vendor's training rights often run only against 'service data.'

    03

    Model output ownership

    Purpose

    Allocates IP in content generated by the AI system.

    Market term (2026)

    Customer owns outputs to the maximum extent permitted by law; vendor disclaims any claim to outputs. Vendor retains rights in the underlying model only.

    Red flag

    Silence on outputs (defaults to unresolved copyright law) or shared-ownership language that gives the vendor commercial reuse rights.

    04

    Training data rights

    Purpose

    Whether vendor can use customer data to train its models.

    Market term (2026)

    No training on customer data, prompts, or outputs without explicit opt-in. Tenant isolation guaranteed. Anonymized telemetry permitted.

    Red flag

    Default training rights, 'service improvement' language that quietly includes model training, or no commitment on cross-customer data isolation.

    05

    Indemnification (IP)

    Purpose

    Vendor protects customer from third-party IP claims based on the service.

    Market term (2026)

    Vendor indemnifies for IP infringement claims arising from the service, including model outputs when used within the documentation. Defense and settlement at vendor's cost.

    Red flag

    IP indemnity that excludes model outputs, or carves out 'AI-generated content' entirely — leaves the customer holding the bag on the most novel risk.

    06

    Indemnification (AI hallucination & errors)

    Purpose

    Allocates risk of inaccurate or harmful model output.

    Market term (2026)

    Customer responsible for verifying output before use. Vendor responsible for material defects in the service relative to documentation. No indemnity for output accuracy per se.

    Red flag

    Vendor indemnity that promises 'accurate' output — overstates what is technically achievable and creates trap-door liability. Customer indemnity for any output it uses is overreach.

    07

    Customer AI use & prohibited uses

    Purpose

    What the customer can and can't use the service for.

    Market term (2026)

    Prohibited uses limited to a defined list — illegal content, weapons, election manipulation, child safety. No catch-all 'as the vendor determines.'

    Red flag

    Open-ended prohibited-use clauses that let the vendor terminate at discretion, or use-restrictions that block the customer's actual business case.

    08

    Sub-processors & flow-down

    Purpose

    Foundation model providers and other vendors in the stack.

    Market term (2026)

    Vendor names its sub-processors (OpenAI, Anthropic, AWS, etc.), notifies on change, and flows down equivalent obligations.

    Red flag

    No sub-processor list, or sub-processor terms that conflict with the MSA (e.g., the foundation model provider's policy actually permits training when the vendor MSA says no).

    09

    Data processing addendum (DPA)

    Purpose

    GDPR, CCPA, and similar privacy obligations.

    Market term (2026)

    Standard contractual clauses for international transfers, defined roles (controller vs. processor), breach notice within 72 hours, sub-processor list.

    Red flag

    Missing DPA entirely, or a DPA attached only on request — a serious gap for any enterprise sale into a regulated industry.

    10

    Limitation of liability

    Purpose

    Caps damages for both sides.

    Market term (2026)

    12 months' fees cap with carve-outs for IP infringement, confidentiality breach, indemnification, and gross negligence/willful misconduct.

    Red flag

    Cap at 3 months' fees, or cap with no IP carve-out (collapses the value of the IP indemnity).

    11

    Term, renewal, and termination

    Purpose

    How long, how it renews, how to leave.

    Market term (2026)

    Initial term per order form. Auto-renewal with 30–60 day non-renewal notice. Termination for cause with 30-day cure. Termination for convenience by customer in regulated industries.

    Red flag

    Auto-renewal with no notice required, multi-year terms with no out, or termination-for-cause defined narrowly enough to be unusable.

    12

    Data deletion & portability

    Purpose

    What happens to customer data at termination.

    Market term (2026)

    Customer data exportable in a standard format for 30 days post-termination, then deleted within 60 days. Backup retention defined.

    Red flag

    No defined deletion window, or 'commercially reasonable efforts' language that creates indefinite retention.

    How to negotiate it

    The order to work through these clauses for max leverage.

    1. 1
      Get the customer-data definition right

      Make prompts, inputs, and outputs all 'customer data,' not 'service data.' This one definition controls the rest of the AI-specific terms.

    2. 2
      Lock down training

      Add explicit no-training language with tenant isolation. If the vendor wants opt-in training, set the opt-in default to off and require a separate signature to flip it.

    3. 3
      Fix the IP indemnity

      Confirm IP indemnity covers model outputs when used within the documentation. If the vendor refuses, get pricing concessions or walk away — this is the new market norm.

    4. 4
      Reset the LoL carve-outs

      Confirm the limitation of liability has carve-outs for IP infringement, confidentiality, DPA breach, and gross negligence. Without them the indemnities are paper.

    5. 5
      Confirm the DPA

      Attach a DPA on signature, not on request. Confirm sub-processors, breach notice timing, and international-transfer mechanism.

    6. 6
      Validate the sub-processor stack

      Read the foundation model provider's enterprise terms. Make sure the vendor's MSA promises are consistent with what the foundation model actually allows.

    Red flag checklist

    • Outputs classified as 'service data' instead of 'customer data.'
    • Training rights granted by default.
    • IP indemnity that excludes AI outputs.
    • Open-ended prohibited-use clauses.
    • Missing DPA or sub-processor list.
    • Limitation of liability with no IP carve-out.
    • Auto-renewal with no non-renewal notice.
    • No data-deletion window at termination.

    Frequently asked

    Does an AI startup need a different MSA than a normal SaaS company?+

    Yes. A standard SaaS MSA template is silent on model output ownership, training data, hallucination risk, and AI-specific indemnity. Selling into enterprise without those provisions slows or kills deals in legal review.

    Who owns AI outputs by default?+

    U.S. copyright law on purely AI-generated work is unresolved. Contract terms govern between the parties — and the market norm in 2026 is for customers to own outputs to the maximum extent permitted by law, with vendors disclaiming any claim.

    Can the vendor train on our prompts?+

    Only if the contract says so. Modern enterprise MSAs default to no training, with opt-in required. Consumer and prosumer SaaS terms often default the other way, which is why enterprise contract templates have diverged.

    What's the right limitation of liability cap?+

    The market default for SaaS in 2026 is 12 months' fees, with carve-outs for IP infringement, confidentiality breach, indemnification, and gross negligence. Lower caps without carve-outs are common in vendor templates and worth pushing back on.

    Related deep-dives

    Updated May 26, 2026. General information about contract terms — not legal advice on your specific deal.

    Have one of these on your desk right now?

    Fixed-fee review, scoped before any work begins.

    Book a contract review

    More deal anatomies