Skip to main content

The Warranty Problem: Who Pays When Your AI Feature Is Wrong?

· 9 min read
Tian Pan
Software Engineer

Every software warranty ever written assumed deterministic behavior. You ship a function, it returns the same output for the same input, and your warranty covers the gap between documented behavior and actual behavior. AI features shatter that assumption entirely.

When your LLM-powered feature tells a customer something wrong — and that wrong thing costs them money — traditional warranty language leaves everyone pointing fingers at everyone else.

This is not hypothetical. Cumulative generative AI lawsuits in the U.S. passed 700 between 2020 and 2025, with year-over-year filings accelerating by 137%. The legal infrastructure governing software liability was built for a deterministic world, and the mismatch is already causing real damage.

The Air Canada Precedent: You Own Your Chatbot's Promises

The case that made every product team pay attention landed in February 2024. Jake Moffatt asked Air Canada's chatbot about bereavement fares. The chatbot said he could book a full-price ticket and apply for a bereavement discount retroactively. That was wrong — Air Canada's actual policy explicitly excluded retroactive applications.

When Moffatt requested his partial refund, Air Canada refused. Then they made an argument that should concern every company shipping AI features: they claimed the chatbot was a "separate legal entity" responsible for its own actions. The British Columbia Civil Resolution Tribunal rejected this completely — Air Canada is responsible for all information on its website, whether from a static page or a chatbot. The airline paid $812 in damages, a small amount that established an enormous principle.

If you deploy an AI system that makes claims to your customers, those claims are your claims. The model's non-deterministic nature is not a defense. The fact that you didn't write the specific words is not a defense. You chose to put the system in front of customers, and you own what it says.

Why "AI-Generated — Verify Independently" Doesn't Protect You

The most common risk mitigation strategy for AI features is a disclaimer: "This content was AI-generated. Please verify independently." In unregulated consumer contexts, this might reduce some exposure. In regulated industries, it is legally insufficient — and increasingly insufficient everywhere else too.

Consider the regulatory landscape:

  • Healthcare: California's AB 3030 requires health care providers using generative AI for patient communications to include specific disclaimers and instructions for contacting a human provider. But the disclaimer is a floor, not a ceiling — only physicians, not AI systems, can make final decisions regarding medical necessity.
  • Financial services: AI models used for credit scoring or risk assessment must comply with the Fair Credit Reporting Act. A disclaimer doesn't exempt you from substantive compliance obligations.
  • Sales and marketing: The FTC requires that all claims — including AI-generated ones — be truthful and not misleading. Slapping a disclaimer on a product recommendation that your AI fabricated doesn't satisfy this requirement.

The pattern is clear: regulators treat disclaimers as a minimum disclosure obligation, not a liability shield. The substantive duty of care remains with the deployer. You cannot outsource professional judgment to a language model and then disclaim the consequences.

This matters practically because many teams treat the disclaimer as the end of their liability analysis. It should be the beginning.

The Insurance Gap Nobody Talks About

Here is a fact that should alarm any engineering leader shipping AI features: your company's existing insurance policies probably do not cover AI-specific liabilities.

Traditional errors and omissions (E&O) and general liability policies were written for deterministic software failures — bugs, outages, data breaches. They typically do not cover:

  • AI hallucinations leading to financial losses
  • Intellectual property infringement by generated content
  • Defamation or misinformation from AI outputs
  • Professional malpractice claims arising from AI-generated advice

This problem is getting worse, not better. In January 2026, Verisk released new general liability exclusion forms specifically for generative AI. Policies renewing in Q1 and Q2 of 2026 are the first to incorporate these exclusions. If your company renewed its general liability policy recently, check whether it now explicitly excludes AI-related claims.

The insurance industry calls this "silent AI" — AI exposures that are neither explicitly included nor excluded in existing policies. When a claim lands, both sides argue about whether coverage applies, and the policyholder usually loses.

Some specialized AI insurance products are emerging. Armilla, backed by Chaucer and Axis Capital, launched coverage in 2025 that requires ongoing model quality assessments. Testudo launched in January 2026 with a claims-made product for enterprises deploying generative AI. But these are early-stage products with limited track records, and they require the kind of model monitoring and evaluation infrastructure that most teams haven't built yet.

The practical takeaway: before you ship an AI feature that makes claims, recommendations, or decisions affecting your customers, ask your legal team whether your current insurance covers the failure modes. The answer will likely change your risk calculus.

Loading…
References:Let's stay in touch and Follow me for more thoughts and updates