Filter by Category

How to Draft and Enforce a Non-Compete Agreement in Austin, Texas for a SaaS Company After the FTC Non-Compete Rule

Texas law (Tex. Bus. & Com. Code § 15.50) allows non-compete agreements when they are ancillary to an enforceable agreement and reasonable in time, geography, and scope. For Austin SaaS companies, the FTC’s 2024 non-compete rule—and the ongoing litigation around it—requires careful drafting and a fallback strategy focused on trade secrets and customer relationships. This article explains how to draft, implement, and enforce a Texas-compliant non-compete in Austin after the FTC rule.

Non-Compete Agreements in Austin After the FTC Rule: What Changed (and What Didn’t)

The Federal Trade Commission issued a final rule in 2024 that would broadly ban most worker non-competes nationwide and require notices to affected workers. That rule immediately triggered extensive court challenges, and its ultimate enforceability has been uncertain while litigation proceeds. For Austin SaaS companies, the practical takeaway is not “non-competes are dead,” but rather: you should draft as if (1) Texas law still controls enforceability in state court and (2) federal restrictions could tighten with limited notice.

Texas remains one of the states that enforces non-competes when they meet specific statutory requirements under Tex. Bus. & Com. Code § 15.50. Most Austin-based enforcement actions are filed in Texas state courts (often Travis County or Williamson County), where judges analyze the covenant’s reasonableness, the employer’s protectable interest, and the agreement’s structure. Post-FTC-rule uncertainty makes it even more important to (a) ground the covenant in strong confidentiality/trade secret protections and (b) build alternative restrictive covenants (non-solicitation, confidentiality, invention assignment) that are more durable even if a non-compete is later limited.

Texas Enforceability Checklist: The Statutory Requirements Under § 15.50

In Texas, a non-compete is enforceable only if it satisfies two core requirements:

1) The non-compete must be “ancillary to or part of” an otherwise enforceable agreement

This usually means the non-compete is tied to a valid agreement where the company provides something of value beyond at-will employment—most commonly access to confidential information, trade secrets, specialized training, or stock/option compensation paired with confidentiality obligations. The “ancillary” element is where many SaaS companies stumble: a stand-alone non-compete with weak or vague confidentiality promises is more vulnerable.

2) The restrictions must be reasonable in time, geographic area, and scope of activity

Texas courts look for a reasonable fit between the restriction and the company’s legitimate business interests—such as protecting trade secrets (source code, product roadmap, pricing models), goodwill with customers, and investments in employee training. Overbroad “no work in tech anywhere” clauses are enforcement magnets for disputes and judicial narrowing.

Identify Your Protectable Interests for a SaaS Company in Austin

Before drafting, define what you are actually protecting. For SaaS companies, courts and litigators commonly focus on these categories:

Trade secrets and confidential information: source code, proprietary algorithms, API keys, security architecture, customer usage data, pricing strategy, churn analysis, pipeline forecasts, and roadmap details.
Customer goodwill: relationships with enterprise buyers, channel partners, and key accounts—especially where the employee was the “face” of the relationship.
Competitive positioning: go-to-market strategy, vertical-specific playbooks (e.g., fintech compliance workflows), and product differentiation.
Specialized training: meaningful, employer-funded training that creates competitive advantage (not generic onboarding).

In Austin’s tight SaaS talent market, the best agreements do not attempt to “own the employee.” They narrowly protect what the company invested in and what the employee could unfairly exploit after departure.

How to Draft a Texas-Compliant Austin SaaS Non-Compete (Step-by-Step)

Step 1: Pair the non-compete with robust confidentiality and trade secret obligations

Because Texas requires the non-compete to be ancillary to an enforceable agreement, a well-drafted confidentiality clause is often the foundation. For SaaS businesses, your agreement should:

Define “Confidential Information” with specificity (code, architecture, customer lists, pricing, security controls, internal metrics).
State permissible uses (only for company business) and require return/destruction of materials on exit.
Include security obligations (device controls, MFA, no personal cloud storage, reporting of suspected breaches).

If you plan to enforce the non-compete, the record that the employee had access to protectable information matters. Maintain role-based access controls and logs showing access to repositories and sensitive systems.

Step 2: Choose a defensible duration (often 6–12 months, sometimes 18)

Texas law does not set a hard maximum, but in practice the longer the term, the more scrutiny it draws. For many SaaS roles:

Sales/CS leadership: 9–12 months may be defensible if tied to sales cycles and renewal periods.
Engineers with deep code access: 6–12 months is common; longer terms require strong justification (e.g., long-lived roadmap, sensitive security tooling).
Executives with strategy access: 12–18 months may be argued with strong evidence.

Draft the duration to match your competitive risk window: sales cycle length, product release cadence, and the half-life of roadmap information.

Step 3: Limit the geography in a way that fits SaaS reality

Austin SaaS companies often sell nationally or globally, making geography tricky. Overly broad “worldwide” restrictions can look punitive unless tied to the employee’s actual territory and role. Options that tend to be more defensible include:

Territory-based limits tied to where the employee actually sold or serviced customers.
Customer-based limits (e.g., restricted as to named accounts or categories of accounts) instead of pure geographic boundaries.
Hybrid limits: Travis/Williams on County plus any territory where the employee had material customer contact in the last 12 months.

For remote employees in Austin, courts focus on the business reality—not the employee’s home address. Draft to reflect the employee’s market footprint.

Step 4: Narrow the restricted activities to competitive work that creates unfair risk

A well-drafted Texas non-compete should restrict specific competitive activities, not employment in an entire industry. For example:

Prohibit working on products that compete with your named product category (e.g., “SOC 2 automation platforms,” “expense management SaaS for mid-market,” “observability tooling”).
Limit the restriction to roles similar to the employee’s former role (e.g., “product management, engineering, security architecture, enterprise sales within X vertical”).

Example (more defensible): “Employee will not, for 12 months, perform enterprise sales to healthcare SaaS customers for a direct competitor offering HIPAA compliance workflow automation, within the territory Employee covered in the last 12 months.”

Example (riskier): “Employee will not work for any technology company anywhere in the United States for two years.”

Step 5: Consider separate (and often stronger) non-solicitation provisions

If FTC limits expand or a court narrows your non-compete, non-solicitation and confidentiality provisions may still provide meaningful protection. SaaS companies often use:

Customer non-solicitation: no solicitation of customers/prospects the employee worked with (often 12–18 months).
Employee/contractor non-solicitation: no raiding key team members.
Vendor/partner non-solicitation: for channel-heavy SaaS businesses.

Draft with precision: define “solicit,” define the covered customers, and align the term with sales cycles and renewal windows.

Step 6: Include “blue pencil”/reformation language and attorney’s fees strategy

Texas courts can reform overbroad covenants in certain circumstances. Drafting for reformation does not excuse overreach, but it can reduce catastrophic risk if a judge narrows the covenant instead of voiding it. Also address:

Venue and forum selection (to the extent enforceable for your workforce).
Injunctive relief language acknowledging irreparable harm (while recognizing courts still require proof).
Attorney’s fees provisions (balanced to avoid unconscionability arguments).

Implementation in Austin: The Process Matters as Much as the Paper

Many enforcement problems arise from onboarding and offboarding failures, not clause wording. Best practices include:

Offer-stage disclosure: provide the agreement before acceptance when possible; avoid surprises on day one.
Consideration clarity: document what the employee receives—equity grants, access to sensitive systems, specialized training—so the “ancillary” requirement is supported.
Role-based access controls: limit access to “need to know” and keep logs; this becomes evidence later.
Exit protocol: confirm return of devices, revoke credentials immediately, and obtain written acknowledgment of continuing obligations.