A question I hear constantly from AI SaaS founders: “We sell to businesses, not consumers — does FTC AI disclosure guidance even apply to us?” The honest answer is that the label on your sales contract doesn’t determine your FTC exposure. What matters is whether an actual consumer, somewhere downstream, ends up interacting with your AI. If the answer is yes, the FTC’s guidance reaches you — even if your invoice says “B2B.”
The FTC’s Standard Is About the Interaction, Not the Contract
The FTC built its current AI enforcement approach on Section 5 of the FTC Act, which prohibits unfair or deceptive practices in commerce generally — it was never limited to direct-to-consumer sellers. Following a 2025 executive order directing federal agencies to clarify how existing consumer protection law applies to AI, the FTC issued a policy statement confirming it will apply Section 5, along with statutes like the FCRA and ECOA, to AI systems using its existing enforcement authority rather than waiting on new AI-specific legislation. The core deception standard hasn’t changed: if a reasonable consumer could believe they’re interacting with a human, and the business knows otherwise, failing to disclose that is deceptive.
Nothing in that standard is limited to companies that sell directly to consumers. It’s about where the AI actually shows up — and for most AI SaaS products in the receptionist, service desk, and outreach space, that’s squarely in front of consumers, even though the paying customer is a business.
Where B2B AI SaaS Platforms Actually Create Consumer-Facing Exposure
Think about the typical path an AI SaaS product takes to reach an actual person:
- An AI receptionist platform is sold to a trades business (B2B), but it’s the trades business’s customers — homeowners, patients, insureds — who actually talk to the AI.
- An AI-driven customer service desk is licensed to a company (B2B), but it’s that company’s end users submitting tickets and chatting with the AI.
- An AI review-generation or outreach tool is sold to a business (B2B), but it’s that business’s customers who receive the automated text or are asked to leave a review.
In every one of these cases, the platform’s contractual relationship is B2B, but the AI’s actual point of contact is a consumer. That consumer-facing moment is exactly where the FTC’s disclosure standard lives — regardless of who’s on the subscription agreement, and it’s part of why these platforms carry compliance risk on two fronts at once.
“We’re Just the Platform” Is Not a Reliable Shield
It’s tempting to assume that because the platform’s customer is a business, disclosure obligations belong entirely to that business, not the platform provider. In practice, this doesn’t hold up well for two reasons:
- The platform builds the interaction. If your product’s default scripts, chat flows, or call handling never include an AI disclosure, that’s a product design choice the platform made — and regulators and plaintiffs’ attorneys increasingly look past the contractual label to the party that actually controls the consumer-facing behavior.
- Most end-clients won’t customize compliance in. Small and mid-sized businesses licensing an AI receptionist or service desk platform are unlikely to build their own disclosure language from scratch. If the platform doesn’t make disclosure part of the default experience, in practice it usually doesn’t happen at all.
This mirrors a pattern showing up across FTC enforcement more broadly: guidance increasingly treats compliance obligations as running with whoever controls the consumer-facing behavior, not just whoever signed the contract with the end business.
State Law Adds Another Layer That B2B Framing Doesn’t Avoid Either
State AI disclosure laws — including New York’s disclosure law taking effect in mid-2026 and Colorado’s AI Act slated for later in 2026 — generally apply based on where the consumer is located, not where the business licensing the platform is headquartered or how the deal is structured. A B2B AI SaaS platform whose product reaches consumers in multiple states can find itself subject to the strictest applicable state standard even though it never contracts directly with an individual consumer anywhere.
What This Means for Your Product and Your Contracts
For AI SaaS platforms in the receptionist, service desk, and outreach space, treating “we’re B2B” as a compliance exemption is a mistake worth correcting before it becomes a regulator’s or plaintiff’s argument instead of yours. The more durable approach:
- Build AI disclosure into the product’s default behavior, not as an optional setting an end-client has to turn on.
- Make sure your Subscription Agreement and Terms of Use accurately allocate this responsibility and reflect what the platform does by default regarding consumer-facing AI disclosure, and clearly allocate any remaining responsibility to the end-client.
- Treat consumer location, not your own contracting structure, as the trigger for state-level disclosure obligations.
Get This Addressed in Your Platform and Your Contracts
I work with AI SaaS clients on a flat-fee basis to review how their product actually interacts with end consumers, then build disclosure defaults and contract language — in the Subscription Agreement, Terms of Use, and Privacy Policy — that reflect the real compliance picture instead of relying on a B2B label to do work it can’t actually do.
Andrew S. Bosin, Esq. Andrew S. Bosin LLC, 36 Highland Road, Glen Rock, NJ www.njbusiness-attorney.com | 201-446-9643
This post is provided for general informational purposes and does not constitute legal advice. Contact our office to discuss how these requirements apply to your specific platform and use case.
#FTCCompliance #AIDisclosure #B2BSaaS #AISaaS #SaaSCompliance #TechLaw #StartupLaw #NJAttorney #LegalTech #ComplianceRisk