A founder usually discovers a non-compete problem at the worst possible time. A key employee resigns, joins a competitor, contacts former customers, and leaves a signed agreement sitting in a personnel file that nobody has reviewed since the employee started. The founder wants an immediate cease-and-desist letter. That instinct can be understandable, but an aggressive threat built on an overbroad clause may expose weaknesses the departing employee can use.
For South Florida companies, non-compete agreement enforceability depends on more than a signature. Florida law, the employee's role and compensation, the company's protectable interests, the wording of the restriction, the circumstances of termination, and the latest judicial treatment can all change the result. The practical question isn't just whether an employee signed. It's whether the employer can prove that this particular restraint protects a legitimate business interest without blocking ordinary competition.
Table of Contents
- A Miami Founder Walks Into a Non-Compete Dispute
- What Enforceability Actually Means in 2026
- Florida's Statute and the Case Law Reshaping It
- Drafting an Enforceable Clause as an Employer
- Strategies for Employees Facing a Restrictive Covenant
- Sample Clauses and Red Flags You Can Compare
- Why One Size Fits All Advice Keeps Failing Founders
- FAQs and Next Steps for South Florida Businesses
A Miami Founder Walks Into a Non-Compete Dispute
A Wynwood-based SaaS founder discovers that her senior engineer has resigned and is preparing to launch a competing product in Brickell. The engineer signed a non-compete eighteen months earlier. Within days, two former accounts mention receiving texts from the engineer, and one customer asks whether the new company will replace the founder's platform. The founder's cease-and-desist letter is drafted, but it remains unanswered.
The obvious reaction is to threaten a lawsuit immediately. The smarter first step is to audit the agreement and the facts that would support it. What confidential information did the engineer access? Did the engineer maintain customer relationships, or merely write code? Does the clause identify a realistic market, or does it prohibit work throughout an entire industry? Did the company provide separate consideration, specialized training, equity, or another benefit connected to the restriction?
Florida has historically been more receptive to properly crafted restraints than states such as California, North Dakota, and Oklahoma, where employee non-competes are not enforced. Yet Florida's posture doesn't make every signed clause enforceable. Courts scrutinize whether the employer has identified a legitimate business interest and whether the restriction is reasonably connected to that interest.
Practical rule: A cease-and-desist letter should reflect the evidence supporting enforcement, not substitute for it.
A useful plain-language overview is the Paradigm International Inc. 2026 guide, especially for founders who need to understand the basic function of a restrictive covenant before reviewing a specific contract. For a Miami business, however, the agreement should be analyzed alongside customer records, access permissions, compensation history, termination documents, and the employee's actual duties. A founder looking for counsel on that broader review can start with a Miami business law attorney.
The analysis below focuses on the three enforceability tests, Florida's statutory framework, drafting moves that improve an employer's position, defenses available to employees, sample language, and questions that arise frequently for startups and small businesses in Miami-Dade, Broward, and Palm Beach.
What Enforceability Actually Means in 2026
Enforceability isn't a binary checkbox. A court may enforce a covenant, narrow it, or reject it depending on the contract language and the evidence surrounding the employment relationship. State law supplies the framework, but contract principles and the parties' conduct determine how that framework applies.
The first test is reasonable restraint
Florida judges typically examine time, geography, and scope together.
- Time asks how long the former employee is restricted. A short period may give the employer time to transition customer relationships or protect sensitive information. A lengthy period needs stronger justification.
- Geography asks where the restriction applies. A Miami company serving named accounts in Miami-Dade and Broward has a harder time justifying a nationwide ban unless its actual business and customer relationships are national.
- Scope asks what the employee may not do. A prohibition on servicing identified customers or competing product lines is easier to defend than a ban on working anywhere in an entire industry.
The second test is a legitimate business interest
The employer must identify something worth protecting, such as trade secrets, confidential information, substantial customer relationships, goodwill, or specialized training. The interest must be real and connected to the employee's work. A company can't create legitimacy by labeling every ordinary business relationship confidential.
A founder whose concern is source code and product architecture may need a carefully drafted confidentiality agreement and access controls. A company worried about customer diversion may need a targeted non-solicitation clause. Practical guidance on protecting confidential information appears in this resource on trade secret protection.
The third test is consideration
The employee must receive value for the restriction. That value may arise through the employment relationship or a later promotion, compensation arrangement, equity grant, specialized training program, or other exchange, depending on the facts and applicable law. The contract should make the connection clear instead of leaving the employer to reconstruct it after a resignation.
Florida courts may reform an overbroad covenant, but employers shouldn't assume a judge will rewrite a careless agreement. Courts have struck down, narrowed, and upheld employee covenants in different circumstances, which is why the best drafting starts with the business interest and works outward to the smallest reasonable restriction.
Florida's Statute and the Case Law Reshaping It
Florida Statute § 542.335 provides the principal framework for restrictive covenants. The statute focuses on legitimate business interests and reasonableness, and it creates a rebuttable presumption favoring enforceability when the employer makes the required initial showing. That presumption helps an employer, but it doesn't eliminate the need for precise language and credible proof.
The interests must be specific
Florida's statutory list includes several categories employers commonly rely on:
| Statutory Interest | What It Covers | Typical Employer Proof |
|---|---|---|
| Trade secrets | Protected technical, commercial, or operational information | Access records, security policies, source-code controls |
| Valuable confidential information | Information that gives the business a competitive advantage | Confidentiality policies, restricted files, employee acknowledgments |
| Substantial customer relationships | Relationships the employee developed or maintained for the company | Account assignments, communications, renewals, CRM records |
| Customer goodwill | The company's repeat business and reputation connected to customer contact | Branding, account history, relationship records |
| Extraordinary or specialized training | Training beyond ordinary onboarding that creates a protectable advantage | Training materials, costs, certifications, documented programs |
The phrase “legitimate business interest” doesn't rescue a restriction that protects only the employer's desire to prevent competition. Courts increasingly ask whether the employee received access to something specific and whether the restraint actually addresses that risk.
Hospitality Ventures changed the drafting conversation
The Florida Fourth District's Hospitality Ventures line is an important warning for employers relying on broad employment restraints. The decisions signal closer scrutiny of the exchange supporting a covenant, the employer's asserted interest, and whether the restriction is tied to the employee's actual role. Employers should be particularly cautious when presenting a non-compete as a routine form without explaining what value supports it.
The judicial direction is also unfavorable to vague geographic descriptions and sweeping occupational bans. A clause that says an employee can't work for any competitor, anywhere, for an extended period may invite a court to reject the restriction rather than repair it. The same concern applies when the employer has little evidence that a lower-paid or junior worker possessed sensitive information or meaningful customer influence.
A study of 514 state-court decisions found that courts struck down 53%, pared down 7%, and upheld 40% of employee covenants after substantive reasonableness review, as reported in this empirical legal analysis. The figures don't predict a Florida case, but they illustrate why enforceability often turns on drafting and proof rather than the existence of a signed document.
Drafting an Enforceable Clause as an Employer
A Florida founder should draft a non-compete as a risk-control instrument, not as a declaration that the company owns an employee's future career. The clause should answer three questions directly: what is protected, whose conduct creates the risk, and how much restraint is necessary to address it?
Start with the business interest
Identify the protected interest in the agreement and support it in the company's records. If the concern is a customer relationship, identify the type of relationship and the employee's role in developing it. If the concern is source code or product strategy, pair the covenant with confidentiality protections, access controls, return-of-property procedures, and documented security practices.
Geography should follow the company's actual footprint. A South Florida company serving customers only in Miami-Dade and Broward should think carefully before demanding a statewide or national restriction. Named accounts, defined product lines, and customer categories usually communicate more precision than a broad industry label.
Match duration to the risk
For many rank-and-file roles, a six-month period may be easier to justify than a longer restraint. A twelve-month period should be reserved for roles where the employer can explain why customer relationships, confidential information, or transition needs require additional time. The duration should reflect the useful life of the information or relationship, not the maximum period the template happens to contain.
Use a checklist before presenting the agreement:
- Role fit: Explain why this employee, rather than every employee, needs the restriction.
- Customer proof: Preserve account assignments, revenue responsibility, and relationship history.
- Training records: Document unusual training and the value it provides.
- Compensation connection: Tie the covenant to employment, promotion, equity, bonus arrangements, or other consideration.
- Exceptions: Consider passive investments, pre-existing relationships, and work that doesn't compete with the protected product or service.
- Exit mechanics: Include return-of-property, certification, notice, and transition provisions.
- Choice of law: Select a jurisdiction with a meaningful connection to the employment and business.
- Severability: State how the parties expect an overbroad provision to be handled, while recognizing that a court may refuse to rewrite an unreasonable clause.
Don't overlook narrower alternatives. A carefully drafted non-solicitation agreement may address customer or employee poaching without preventing the worker from accepting a job in the industry. Garden leave, paid transition periods, confidentiality obligations, and targeted non-dealing restrictions can also protect the business while reducing the burden of a total work prohibition.
Strategies for Employees Facing a Restrictive Covenant
Employees often assume that a signed agreement ends the discussion. It doesn't. The employer still has to connect the restriction to a legitimate interest and defend its time, geography, and scope.
Start by obtaining the exact signed version, including exhibits, amendments, compensation plans, and referenced policies. Then compare the language with the job actually performed. A junior designer who never handled customers or sensitive strategy may have a stronger challenge than the title alone suggests, particularly if the employer uses the same restriction for every worker.
Test the employer's weakest point
Look for practical defects:
- Overbroad geography: The clause reaches markets where the employer has no customers or goodwill.
- Excessive duration: The restriction lasts longer than the employer's information or relationship risk.
- Missing interest: The employer can't identify trade secrets, substantial customer relationships, or specialized training.
- Role mismatch: The employee had no meaningful access to the information the covenant supposedly protects.
- Compensation issue: The agreement lacks a clear exchange or ignores a relevant compensation threshold or termination rule.
- Functional overreach: A confidentiality or non-solicitation provision effectively prevents the employee from accepting other work.
The employee can request the employer's asserted protectable interests and ask for a written explanation of the restriction. Before signing a new agreement, negotiate the customer list, product definition, geography, duration, and carve-outs. A choice-of-law clause also deserves scrutiny, especially for a remote worker whose residence, work location, and employer headquarters are in different states.
The broader national picture makes location especially important. In the United States, state law governs non-compete enforceability through a patchwork rather than one controlling federal statute. The FTC's April 23, 2024 rule attempted to prohibit new worker non-competes and make most existing worker clauses unenforceable after an effective date set for September 4, 2024, but a federal district court stopped enforcement on August 20, 2024, and the FTC appealed on October 18, 2024, as documented in the FTC announcement.
If litigation is threatened, don't ignore the demand. An employee may seek declaratory or injunctive relief, challenge the employer's evidence, negotiate a narrowed release, and evaluate potential fee rights under the agreement and applicable Florida law. The immediate goal is often to preserve the ability to work while preventing misuse of confidential information.
Sample Clauses and Red Flags You Can Compare
Founders can spot drafting problems by comparing a clause's protection to its burden. The following examples are illustrations for discussion, not a substitute for adapting language to the company, employee, and transaction.
| Provision | Enforceable Version | Red-Flag Version |
|---|---|---|
| Scope | “For six months after employment ends, Employee won't provide substantially similar services for a competing product line to customers Employee serviced or solicited for Company during the prior twelve months.” | “Employee may not work in any competing industry in any capacity.” |
| Geography | “The restriction applies to Miami-Dade and Broward Counties and the named accounts listed in Exhibit A.” | “The restriction applies throughout Florida, the United States, and worldwide.” |
| Duration | “The restriction lasts six months for this role, based on the documented customer transition period.” | “The restriction lasts two or five years regardless of position or risk.” |
| Consideration | “The restriction is supported by the employment relationship and the compensation, access, and benefits described in this agreement.” | “Employee receives no new consideration, but agrees to the restriction after the existing arrangement has already been completed.” |
| Severability | “If a court finds a provision overbroad, the parties request enforcement to the extent permitted by law.” | “Any reduction automatically shifts all attorney's fees to the employee.” |
| Customer protection | “Employee won't solicit or knowingly divert the customers identified in Exhibit A for competing services.” | “Employee may not contact anyone who has ever heard of Company.” |
| Confidentiality | “Employee must protect source code, product plans, pricing, and nonpublic customer information, and return Company property at separation.” | “Everything learned during employment remains confidential forever, including general skills and public information.” |
The acceptable versions are narrower because they identify the conduct and relationships that create the genuine risk. The red-flag versions attempt to control an entire career, market, or category of information. A court may view that breadth as evidence that the employer is trying to suppress competition rather than protect a legitimate interest.
A confidentiality addendum can strengthen the overall protection when it identifies information specifically and requires sensible handling. It can't replace the employer's obligation to justify a non-compete, and it shouldn't operate as a de facto work prohibition. Likewise, a non-solicitation clause should address customers, employees, or vendors with whom the worker had a meaningful connection, rather than every person connected to the business.
Why One Size Fits All Advice Keeps Failing Founders
A template fails when it treats every employee, customer relationship, and termination the same. Florida's framework contains role and compensation distinctions that can matter before job title does. The federal environment also remains a poor reason to copy a national form, because the FTC's attempted nationwide rule was halted in litigation and state law continues to control most practical disputes.
Florida employers must account for the $15-per-hour wage threshold in Fla. Stat. § 542.335, the 2024 amendment's constructive-notice requirement after termination, and the status of the FTC rule when reviewing an agreement. Those mechanics don't produce the same result for every worker, and an employer should verify the current statutory text and judicial interpretation before relying on them.
Consider two South Florida businesses. A Wynwood SaaS founder pays a senior engineer above the statutory threshold, gives the engineer access to source code and product roadmaps, and restricts only work on a directly competing product for a defined customer market. A Brickell agency owner dismisses a junior designer during probation, uses the same form, and claims a statewide restriction even though the designer had no customer authority or confidential strategic access. The clauses may look similar on paper, but the enforcement analysis is materially different.
The case law makes templates riskier
Hospitality Ventures and White Pearl reflect a narrowing judicial approach to what counts as a legitimate business interest and how employers prove it. A 2019 form may omit current compensation language, termination mechanics, notice requirements, or role-specific limitations. A template borrowed from another state may use different assumptions about wage thresholds, severance triggers, reformation, or choice of law.
Some states have tightened restrictions based on compensation and termination circumstances. One 2026 update summarized Tennessee's treatment of employees discharged without cause, while another noted Virginia's threshold barring non-competes for employees earning less than $70,000 annually (Akin Gump's state-law update). These examples show why a remote employee's location and termination facts may matter more than the employer's preferred form.
FAQs and Next Steps for South Florida Businesses
Will Florida enforce a non-compete signed by a remote worker in another state?
Not automatically. The court may examine the worker's location, the employer's operations, the work performed, the selected law, and the state's public policy. A Florida choice-of-law clause doesn't guarantee enforcement if another state has a stronger connection or materially restricts the covenant.
How long is too long for a Miami geographic restriction?
There's no universal Miami radius. The restriction should track the company's actual customer footprint and the employee's relationship to that market. A named-account restriction may be easier to defend than a nationwide ban, particularly for a business operating primarily in Miami-Dade and Broward.
Can garden leave substitute for a post-employment bar?
It can help manage transition risk, but it doesn't automatically cure an overbroad covenant. The agreement should explain the payment, duties, duration, confidentiality obligations, and business reason for the leave. The court will still evaluate the restraint under Florida Statute § 542.335 and the relevant case law.
How are independent contractors treated?
The 2024 FTC rule's compliance materials addressed workers broadly, but the rule was stopped by a federal court. Florida analysis still depends on the contract, the relationship, the asserted business interest, and the worker's actual access to customers or confidential information. Don't assume labeling someone an independent contractor makes a restriction enforceable.
| Question Topic | Governing Authority | Quick Takeaway |
|---|---|---|
| Florida employee covenant | Fla. Stat. § 542.335 | Prove a legitimate interest and reasonable restraint. |
| Remote worker | Choice-of-law principles and applicable state law | Analyze the worker's location and relationship to Florida. |
| Federal rule | FTC rule and litigation history | Don't treat the attempted ban as settled enforcement law. |
| Sale transaction | Federal rule materials and transaction documents | Business-sale covenants may receive different treatment from employment restraints. |
| Confidentiality and solicitation | Contract language and Florida law | Draft them narrowly so they don't become a de facto non-compete. |
Founders should audit existing agreements before the next hire, promotion, acquisition, or termination. Businesses also need a process for preserving access records, customer assignments, confidentiality acknowledgments, and the consideration supporting each covenant. For firms building a broader digital presence while reviewing counsel options, a Local SEO tool for Lawyers can support discoverability, but it doesn't replace a Florida-specific contract review.
Coto & Waddington, Attorneys at Law advises South Florida founders and small businesses on restrictive covenants, employment contracts, confidentiality protections, and startup agreements. Visit Coto & Waddington, Attorneys at Law to schedule a practical review before you hire, promote, or terminate an employee and turn a contract question into a dispute.
