What the FTC's non-compete ruling means for service businesses
The FTC's non-compete restrictions changed how service businesses can structure technician agreements. Here's the practical impact for owners — and what to put in employment contracts instead.
The FTC's restrictions on non-compete agreements, first proposed in 2023 and refined through ongoing litigation and state-level adoption, are now broadly applicable to service businesses. The legal landscape will keep evolving, but the practical implications for residential service operators are clear enough to plan around.
This post is not legal advice. Talk to an employment attorney before drafting or revising contracts. What we can offer is the operator-level read.
What the rule does
In broad strokes:
- Most non-compete agreements between employers and employees are unenforceable
- The rule applies to existing non-competes, not just new ones
- Some narrow exceptions exist (senior executives at the time the rule went into effect; sale-of-business non-competes)
- State-level rules vary — California has long banned them; Texas and Florida had broader enforceability historically; the FTC framework provides a federal baseline
What it means for service businesses
Most residential service businesses had non-competes for technicians that prohibited them from working for competitors within a geographic radius (typically 25-50 miles) for a period (typically 1-2 years) after leaving.
Under the new framework, those agreements are largely unenforceable. A tech who leaves can go straight to a competitor, even if the original contract said otherwise.
Practically, this means:
Tech mobility increased. Techs you train can leave for competitors more easily. Conversely, you can hire from competitors more easily.
Recruiting changed. "Come work for us, we won't enforce your non-compete" is no longer a sales pitch — the legal background already supports the move.
Customer relationships need protection through other means. Non-competes were partially about preventing techs from poaching your customers. That protection now has to come from other contract clauses (see below).
Investment in tech development became higher-stakes. Training a tech for two years and watching them leave for a competitor is a real cost. Operators have to invest in retention, not just legal protection.
What to put in agreements instead
The standard alternatives, all of which remain enforceable in most contexts:
Non-solicitation agreements. A tech can leave and join a competitor, but they can't solicit your customers (or your other employees) for a defined period. These are generally enforceable as long as they're reasonable in scope and time (12-18 months is typical).
Confidentiality agreements (NDAs). Customer lists, pricing data, supplier relationships, and proprietary processes are protectable as confidential information regardless of the non-compete framework. NDAs cover this.
Trade-secret protections. Some operational data (your service-call routing algorithm, your pricing tiers, your supplier discount structure) may qualify as trade secrets, which carry strong legal protection independent of contractual provisions.
Notice requirements. Requiring 2-4 weeks of notice before termination is enforceable in most states and gives you time to manage the customer-relationship transition.
Customer-list ownership clauses. Explicitly stating in employment agreements that customer relationships and customer-data ownership belongs to the company (not the tech) supports your position if a tech tries to take customers when they leave.
Repayment of training costs. Some states allow contractual provisions where employees must repay training costs (apprentice wages, certification fees) if they leave within a defined period. Enforceability varies by state and by how the program is structured.
Operational responses
The legal side is one piece. The operational side matters at least as much:
Make leaving harder by making staying better. Compensation, benefits, growth paths, ownership stakes, autonomy. Techs who feel ownership are less likely to leave.
Distribute customer relationships across the team. If a single tech holds the relationship with 50 customers, their departure is catastrophic. If five techs share that load, less so.
Invest in customer relationships at the company level. Branded service, customer portal, recurring service plans, satisfaction surveys, referral programs — all build customer attachment to the company, not just to a particular tech.
Build the kind of brand that makes customers stick. Customers stay with brands they trust, even when their preferred tech leaves. Generic, undifferentiated service businesses lose customers more easily.
What this means going forward
The shift from non-competes to non-solicitations + confidentiality + retention investment is, on net, healthier for the industry. It puts pressure on owners to actually be good employers rather than relying on legal cages. It moves the equilibrium toward higher tech compensation, better training, and stronger customer relationships at the company level.
If you're updating employee agreements in 2026, work with an employment attorney to align with both the FTC framework and your state-specific rules. The cost of doing this right ($1k-$5k for solid template revisions for a typical SMB operator) is small compared to the cost of relying on agreements a court will throw out.
For more on building the operational foundations that reduce dependency on legal protections, our playbook on hiring your first technician covers the comp structures, training programs, and retention practices that actually work.