# How SaaS advertising claims get regulated when the product keeps changing
A SaaS company ships a pricing page claim in January: "99.9% uptime, guaranteed." By March, a database migration causes two outages. The claim is still live. Nobody updated it, and nobody can produce the logs to prove it was ever true. That gap between what marketing publishes and what engineering can substantiate is where regulators, and plaintiffs' lawyers, go looking.
This lesson covers how advertising law treats fast-moving software products, and what you need on file before a performance claim goes live.
Traditional advertising law was built for products that don't change after they ship: a car, a mattress, a shampoo. SaaS products change weekly. A "save 10 hours a week" claim made in Q1 might rest on a feature set that's been refactored by Q3.
Regulators don't grant an exception for this. In the US, the Federal Trade Commission (FTC), the main consumer protection regulator, enforces Section 5 of the FTC Act, which bans "unfair or deceptive acts or practices." The standard is simple: a claim must be truthful, not misleading, and backed by evidence *at the time you make it and for as long as you keep making it*. If the product changes, the substantiation has to keep up, or the claim has to come down.
In the EU, the relevant framework is the Unfair Commercial Practices Directive (UCPD), enforced by national consumer authorities, plus the Digital Services Act (DSA) for online platform obligations and the Digital Markets Act (DMA) for large "gatekeeper" platforms. The UK runs a parallel system through the Advertising Standards Authority (ASA) and the
The common thread across all these regimes: claims need contemporaneous evidence, not evidence you assemble after a complaint arrives.
1. Quantitative performance claims. "99.9% uptime." "Save 10 hours a week." "50% faster than [competitor]." These are treated as objective, testable claims. Regulators expect a specific methodology behind the number: how was it measured, over what period, on what sample, under what conditions.
2. Comparative and superiority claims. "The #1 CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.Voir la définition complète → for small business." "More secure than Salesforce." These invite scrutiny from regulators and from competitors, who can sue directly. In the US, the Lanham Act lets companies sue rivals for false advertising, separate from any FTC action. Slack, HubSpot, and Zoom have all faced or threatened this kind of dispute over comparative marketing claims.
Uptime claims deserve special mention because they're near-universal in SaaS marketing and easy to get wrong. "99.9% uptime" (informally called "three nines") allows roughly 8.7 hours of downtime per year. If your actual logged downtime exceeds that, the claim is false the moment you publish an updated figure, or the moment a regulator subpoenas your status page history.
The FTC's standard, drawn from decades of case law, is that you need a "reasonable basis" for a claim *before* you make it. For SaaS, a reasonable basis file typically includes:
A useful reference is the FTC's own guidance on substantiating advertising claims, which lays out the "reasonable basis" test in plain language.
For time-saving claims specifically ("save 10 hours a week"), the FTC has pursued companies for relying on cherry-picked user testimonials or small unrepresentative samples rather than controlled studies. A single enthusiastic case study is not substantiation. A claim based on 12 beta users is thin. Regulators look for methodology that resembles a real study: defined baseline, defined comparison, adequate sample size.
Mature SaaS marketing teams run every performance claim through a pre-launch check before publication. A workable version looks like this:
1. Claim inventory: list every quantitative or comparative claim in the asset (landing pagelanding pageA standalone web page built for a single campaign goal, designed to maximise conversions by removing distractions and focusing visitors on one action.Voir la définition complète →, ad, deck, press release).
2. Substantiation match: for each claim, attach the specific data file or study that supports it. No file, no claim.
3. Currency check: confirm the underlying data reflects the *current* product, not a version from two releases ago.
4. Legal/compliance sign-off: someone outside the marketing team, often legal or a dedicated compliance function, reviews and signs off.
5. Review trigger: a rule that says "if uptime architecture changes, or if the feature behind this time-saving claim is deprecated, this claim gets re-reviewed within 30 days."
That fifth step is the one most companies skip, and the one that matters most for SaaS, because the product underneath the claim is a moving target in a way a mattress never is.
Performance claims aren't the only exposure. Regulators are increasingly focused on subscription mechanics: free-trial-to-paid conversion, cancellation friction, and auto-renewal disclosure. The FTC's "click-to-cancel" rule push and the CMA's subscription-contract provisions under the DMCCA both target the same pattern: making it easy to sign up and hard to leave.
This matters for the same reason as claims substantiation: it's a fair-treatment issue that gets tested at launch, not after the fact. A pricing page promising "cancel anytime" needs a cancellation flow that actually delivers that in one or two clicks, not a support ticket queue.
🎬 [VIDEO: "FTC Explains Deceptive Advertising Rules" - youtube.com/@FTCvideos - the FTC's own consumer-facing explainer on what counts as a deceptive claim, useful as a plain-language baseline before reading formal guidance]
Vérification des acquis
1. Why does the FTC's Section 5 standard create a distinct compliance burden for SaaS companies compared to physical product makers?
2. A SaaS company's 'save 10 hours a week' claim was true in Q1 based on a specific feature set. By Q3, that feature has been significantly changed. What is the regulatory implication?
3. What is the core reason the uptime guarantee scenario (claim still live after outages, no logs to prove the original claim) is legally risky?
4. Select ALL correct answers about the regulatory bodies/frameworks relevant to SaaS advertising claims described in the lesson.
Sélectionnez toutes les réponses correctes.
5. Select ALL correct answers about why traditional advertising law's assumptions don't map cleanly onto SaaS products.
Sélectionnez toutes les réponses correctes.
Enforcement isn't hypothetical. In 2023, the FTC settled with several tech and software companies over unsubstantiated efficacy and security claims, and continues to pursue "AI-washing," where companies overstate AI capabilities in marketing (a growing SaaS-specific risk as of 2026, given how many vendors now lead with AI-feature claims). The FTC has warned it will treat inflated AI claims the same way it treats any other unsubstantiated performance claim: as a Section 5 violation if you can't back it up.
In the EU, national consumer authorities coordinated through the Consumer Protection Cooperation (CPC) Network have opened cross-border investigations into subscription and cancellation practices at consumer-facing digital services, showing that enforcement now regularly crosses borders rather than staying within one country's regulator.
The practical cost isn't just the fine (which for FTC consent orders can run into millions for larger companies, though amounts vary widely and shouldn't be treated as a fixed benchmark). It's the corrective advertising, the multi-year compliance monitoring, and the reputational drag among B2B buyers who now diligence vendor claims as part of procurement.