How to Defend a Texas Tech Company Against an FTC Non-Compete Ban Under Antitrust and Competition Law
Texas tech companies can challenge an FTC non-compete ban by showing the rule exceeds FTC authority, is arbitrary under the APA, and conflicts with Texas trade-secret and contract interests. Austin, Dallas, Houston, and San Antonio employers also have antitrust and competition-law defenses to reduce enforcement risk and preserve lawful protections. This article explains how to defend, restructure agreements, and litigate strategically in Texas.
Why an FTC Non-Compete Ban Creates Immediate Risk for Texas Tech Companies
Texas tech companies often rely on non-competes to protect proprietary software, customer relationships, pricing models, go-to-market plans, and hard-won engineering know-how. A sweeping federal ban (or near-ban) on employment non-competes changes that risk calculus overnight: talent mobility increases, competitors can recruit more aggressively, and companies may face regulatory scrutiny if they continue using restricted provisions.
From an antitrust and competition-law perspective, the key defense theme is this: even if non-competes are limited, companies still have legitimate, procompetitive interests—protecting trade secrets, ensuring return on training investment, preserving customer goodwill, and preventing free riding—that can be addressed through narrower tools. When the FTC attempts to ban non-competes broadly, employers can challenge the agency’s authority and the rule’s reasonableness, while also moving quickly to restructure contracts to reduce exposure.
Step One: Identify the Enforcement Posture and Your Company’s Exposure
Before litigating, counsel should map the company’s exposure across five practical questions:
1) Are you a “tech company” with high-velocity employee movement?
Software, SaaS, semiconductors, AI, cybersecurity, and platform businesses typically have higher employee churn and faster competitive cycles. That tends to increase both the business need for protections and the scrutiny of restrictive practices.
2) Which worker groups are covered?
Risk varies by role. A narrowly tailored restriction for a senior sales executive with access to pipeline, pricing, and strategy is easier to justify than a broad restriction imposed on junior developers or support staff. An internal audit should flag: (a) low-wage or entry-level roles, (b) remote employees working in multiple states, and (c) roles without real access to protectable information.
3) What does your agreement actually restrict?
Agreements often contain more than “non-compete” language: non-solicitation, non-disclosure, invention assignment, no-hire clauses, “forfeiture-for-competition,” garden leave, and liquidated damages. Some of these may be treated as “de facto” non-competes if they functionally prevent a worker from switching jobs.
4) What is your evidence of protectable interests?
In Texas, defensibility often turns on documentation: trade-secret classification, access logs, security controls, and clear descriptions of confidential information and goodwill. If a company cannot articulate what it is protecting, a broad restraint looks punitive rather than procompetitive.
5) Are competitors likely to complain?
FTC risk often starts with complaints. If your company is in a hot hiring market (Austin AI labs, Dallas cybersecurity, Houston energy-tech), assume competitor and employee counsel are watching.
Core Legal Defense #1: Challenge FTC Authority and Rulemaking Under the APA
A primary defense for a Texas tech company is to contest the FTC’s authority to impose a categorical ban through rulemaking, and to challenge the rule under the Administrative Procedure Act (APA). This is not “anti-worker” as a legal position; it is a separation-of-powers and administrative law argument grounded in how federal agencies may regulate competition.
Key APA and authority arguments
Ultra vires / lack of substantive rulemaking authority. A central challenge is whether Congress empowered the FTC to issue substantive competition rules that broadly prohibit non-competes, rather than proceeding through case-by-case enforcement. The defense argues that a sweeping labor-market rule exceeds statutory authority.
Major questions doctrine. Where an agency asserts broad power over a significant portion of the economy—especially an area traditionally governed by state contract law—courts may require clear congressional authorization. Employment covenants have long been regulated by states (including Texas), so a nationwide prohibition is vulnerable to “major questions” scrutiny.
Arbitrary and capricious rulemaking. Under the APA, the FTC must reasonably explain its policy choices and grapple with alternatives. A Texas tech company can argue that a broad ban fails to account for industry-specific realities (trade secret intensity, customer goodwill, rapid innovation cycles) and ignores less restrictive options.
Procedural defects. If the record is incomplete, economic assumptions are overstated, or the agency did not adequately consider comments, those gaps can support injunctive relief.
Litigation posture in Texas federal courts
Texas-based plaintiffs often seek declaratory and injunctive relief in federal court, emphasizing: (1) irreparable harm from loss of protectable assets, (2) likelihood of success on APA/statutory grounds, and (3) public interest in stable contract enforcement and trade secret protection. Counsel should prepare detailed declarations from executives and security leaders tying the company’s competitive edge to specific protectable information and customer relationships.
Core Legal Defense #2: Reframe the Case Using Antitrust’s “Rule of Reason” and Procompetitive Justifications
Even though the FTC frames non-competes as restraints on labor competition, antitrust doctrine commonly evaluates restraints under a structured analysis rather than per se condemnation—especially where restraints can increase investment, innovation, and output.
Procompetitive rationales that matter in tech
Protection of trade secrets and proprietary know-how. If engineers can immediately join a direct competitor with sensitive architecture knowledge, the incentive to invest in R&D decreases. The defense is strongest where the company demonstrates robust secrecy measures and genuine trade secret content.
Protection of customer goodwill and pricing strategy. For B2B SaaS and enterprise technology, customer relationships are often cultivated over long cycles. Narrow protections aimed at preventing immediate exploitation of those relationships can be justified as preserving goodwill rather than suppressing labor mobility.
Training and investment recoupment. When a company invests in specialized training—security clearances, proprietary stack onboarding, or regulated compliance training—limited restraints can prevent a competitor from free-riding on that investment.
Facilitation of collaboration. In some contexts (joint ventures, M&A integration, or strategic partnerships), limited non-competes can enable information sharing and integration that increases output and innovation.
Practical takeaway
A Texas tech company should not defend “any non-compete.” It should defend narrowly tailored protections tied to identifiable procompetitive benefits and paired with less restrictive alternatives.
Core Legal Defense #3: Use Texas Contract and Trade Secret Policy as a Counterweight
Texas has a strong policy of enforcing reasonable restraints that are ancillary to an otherwise enforceable agreement and designed to protect legitimate business interests. While federal law can preempt state law in certain contexts, Texas policy remains relevant in assessing harms, reliance interests, and the reasonableness of a federal rule that disrupts settled expectations.
How Texas policy supports a defense narrative
Reliance and stability. Texas employers and employees have long negotiated restrictive covenants with the expectation that reasonable limits could be enforced. Sudden invalidation can impair planning and investment.
Trade secret protection complements competition. Texas has adopted modern trade-secret protections. A defense can argue that a one-size-fits-all federal ban disregards state frameworks designed to allow mobility while protecting confidential information.
Judicial tailoring (“reformation”). Texas courts may reform overbroad restrictions rather than voiding them entirely in certain circumstances. That availability undermines the need for a categorical federal prohibition.
Immediate Compliance Strategy: Reduce Risk Without Surrendering Competitive Protections
Even while pursuing legal challenges, companies should reduce exposure by redesigning agreements. The goal is to avoid provisions that look like blunt labor restraints while strengthening enforceable protections.
1) Strengthen non-disclosure and trade secret controls
Replace broad “you can’t work for a competitor” language with enforceable confidentiality regimes:
Examples for Texas tech employers:
Code repository controls. Limit access by role; log exports and unusual cloning; enforce least-privilege permissions.
Trade secret schedules. Maintain internal lists of key trade secrets (build pipelines, model weights where applicable, security configurations, pricing algorithms) and update them quarterly.
Exit certification. Require departing employees to certify return/deletion of confidential information and to identify devices, accounts, and storage locations used.
2) Use targeted non-solicitation provisions (carefully)
Customer and employee non-solicitation clauses can protect goodwill and team stability. However, if drafted too broadly—covering all customers regardless of contact, or preventing hiring in a way that blocks mobility—they can be attacked as de facto non-competes. Narrow to customers the employee serviced or learned about during a defined period, and avoid “industry-wide” bans.
3) Consider garden leave or paid notice periods
In some circumstances, a paid notice period (where the employee remains employed and compensated while transitioning off sensitive systems) can reduce trade-secret leakage risk without a post-employment restraint. Draft carefully to avoid coercive features.
4) Use invention assignment and IP ownership clauses
Ensure IP developed using company resources is clearly assigned, and define “company time” and “company materials.” This is especially important for remote employees using mixed devices and accounts.
5) Revisit equity and bonus structures
Some companies use forfeiture-for-competition clauses tied to equity or bonuses. These can be scrutinized if they function as penalties that prevent switching. Consider redesigning them as time-based vesting or performance-based awards with clear, non-punitive triggers.
How to Build the Evidentiary Record That Wins Injunctions
If you seek to block FTC enforcement or defend against investigations, your record must be specific. General statements like “we’re a tech company and need non-competes” are not enough.
Evidence checklist
Market and competitor mapping. Identify direct competitors and the roles most likely to move. Show how rapid hiring cycles can lead





















