In a move that could reshape how software-as-a-service (SaaS) vendors package and distribute add‑ons, the U.S. Federal Trade Commission (FTC) has opened an enforcement inquiry into bundling and preinstalled third‑party integrations on major SaaS platforms.
What the inquiry covers
The inquiry, announced in regulatory filings and confirmed by company notices this week, asks a cross‑section of SaaS companies for information about preinstalled integrations, default settings that promote in‑house extensions, revenue‑sharing arrangements, and the contractual terms used with marketplace partners and independent software vendors (ISVs).
According to document requests seen by SaaS Review Hub, the FTC seeks:
- Lists of preinstalled or default integrations included in standard product tiers
- Revenue‑share and placement agreements with ISVs and marketplace partners
- Internal analyses of customer switching costs and the costs of removing bundled features
- Communications and policies relating to API access, API throttling, and app review processes
Officials told reporters the agency is focused on whether dominant SaaS platforms are using bundling and default placement to unfairly advantage their own add‑ons and to raise barriers for competing vendors. The FTC’s interest mirrors global scrutiny of platform behaviors in other technology segments but applies the lens to business software where subscription lock‑in and ecosystem control are increasingly important.
Why SaaS bundling matters now
SaaS ecosystems have matured rapidly in the past five years. Vendors once focused solely on single applications now compete on the strength of their ecosystems: marketplaces, partner integrations, embedded analytics, and low‑code extension runtimes. For enterprise buyers, that richness can mean faster deployments and fewer integration headaches. For ISVs and smaller partners, it can mean limited discoverability and uneven commercial terms.
Regulators are taking note for three practical reasons:
- Market concentration: Several large vendors now dominate critical categories such as CRM, collaboration, and customer service, increasing the economic stakes of default placements.
- Switching friction: Preinstalled integrations and proprietary extension points can add technical and contractual friction that makes moving to a competitor expensive.
- Commercial dependence: Many ISVs rely on platform marketplaces for distribution and revenue, creating asymmetric power dynamics susceptible to unfair conduct.
Industry reaction and immediate effects
Public statements from several large SaaS vendors emphasized cooperation with regulators and a desire to preserve healthy ecosystems. Vendors told customers they will comply with information requests and review policies.
ISVs that resell or integrate with large platforms are watching closely. Executives at small and mid‑sized SaaS companies told SaaS Review Hub they hope the inquiry will prompt clearer rules around default placements and marketplace fairness; others worry that increased regulation could slow partner programs and marketplace innovation.
Marketplace dynamics may shift
In the short term, SaaS marketplaces and ecosystem teams are likely to accelerate documentation and audit readiness: codifying placement policies, publishing clearer marketplace ranking criteria, and revising revenue‑share disclosures. Platform operators may also pause aggressive placement experiments (for example, surfacing in‑house features more prominently by default) while counsel reviews legal risk.
What vendors should do now
SaaS product and legal teams should take immediate, practical steps to reduce regulatory risk and preserve customer trust:
- Inventory integrations and defaults. Maintain a clear, exportable list of preinstalled components and default settings that affect customer choices.
- Document partner agreements. Centralize contracts, placement eligibility rules, and revenue‑share terms for marketplace partners and ISVs.
- Assess switching costs. Quantify the technical and commercial costs customers face when removing bundled features or migrating data and integrations.
- Review marketplace policies. Publish transparent criteria for app discoverability, review processes and any paid placement programs.
- Communicate with customers. Proactive explanations of why defaults exist and how to change them can reduce complaints and show good faith.
Broader implications for SaaS ecosystems
The FTC’s inquiry signals a turning point: regulators are no longer content to treat SaaS ecosystems as purely technical or commercial choices that fall outside antitrust and consumer protection scrutiny. For platform builders, the enforcement risk adds costs and governance obligations. For ISVs and customers, the probe raises the possibility of clearer operational rules and remedies if anti‑competitive bundling is found.
Legal experts note that the outcome could take many forms—from guidance and consent decrees to new scrutiny of contracts and developer platform rules. Even absent a formal enforcement action, the reputational and compliance costs of an FTC inquiry tend to encourage policy changes that favor greater transparency and parity for partners.
What to watch next
Key next steps to monitor:
- Which companies received document requests and whether any acknowledge targeted allegations publicly
- Whether the FTC moves beyond document collection to subpoenas, civil investigations, or structured enforcement
- Industry responses—consortium formation, voluntary marketplace rulebooks, or platform policy revisions
- Potential parallel actions by state attorneys general or international regulators
For SaaS operators and ISVs, the inquiry is a practical reminder that ecosystem design is now squarely in the regulatory spotlight. How platform owners balance convenience for customers with fair access for partners could define competitive dynamics for years to come.