Every month brings a fresh round of headlines about engineers and researchers leaving established companies to launch their own ventures, often within months of a major model release or funding round. Venture firms are competing hard for these founding teams, and the pace of departures shows no sign of slowing. But before any of that excitement, there is a document almost every one of these founders signed on their first day of work — and most never read closely again.
If you are an engineer, product manager, or researcher thinking about leaving your current employer to build a software or AI startup, the employment paperwork you signed years ago may matter more than you think. Here is what actually controls whether you can build your idea, and what does not.
The Non-Compete Question Is Usually Not the Real Problem
Most people assume a “non-compete” is the single biggest obstacle to leaving and starting a competing business. In practice, it is often the least of your worries — for two reasons.
First, the legal landscape has shifted hard against broad non-competes. The Federal Trade Commission spent 2024 and 2025 trying to ban them nationwide, and although that federal rule was ultimately withdrawn from the books in early 2026, the effect has been to push enforcement back to the states — and a growing number of states have moved to restrict or void non-competes on their own. California voids them almost entirely. Texas, Colorado, Illinois, and others allow them only if they are reasonable in time, geography, and scope, and courts increasingly narrow or strike down anything broader than necessary to protect a legitimate business interest.
Second, many employment agreements — particularly at larger tech and AI employers — restrict competitive activity only during employment, not after you leave. If that is your situation, once you have lawfully resigned, a non-compete clause may not stop you from building a competing company at all.
None of this means you are automatically in the clear. It means the non-compete clause is rarely the clause that ends up mattering most.
The Clauses in Employment Contracts That Actually Create Risk
Employment contracts usually clarify roles and responsibilities for employees, but three other provisions, usually buried deeper in the same agreement, tend to create far more real exposure for a departing founder:
- Confidentiality obligations. These almost never expire. They typically cover far more than “secrets” — internal roadmaps, architectures, pricing, customer data, and even general know-how gained on the job can be swept in. Building your new product using anything learned from proprietary internal systems, rather than public information, is where founders get into trouble.
- Invention assignment clauses. Depending on how they are drafted, these can claim ownership of work “related to” your employer’s business — sometimes even work done on your own time and equipment. If your new startup is adjacent to your old employer’s field, this clause deserves careful review before you write a line of code.
- Non-solicitation of employees. Even where non-competes are unenforceable, courts routinely uphold clauses barring you from recruiting former colleagues for a period after you leave — commonly one year. Hiring your old teammates to join the new venture is one of the most common ways founders unintentionally breach their prior agreement. Non-compete agreements generally must provide valid consideration to be enforceable.
Watch for a Choice-of-Law Trap
Many employment and confidentiality agreements at multi-state or multi-national employers specify that one state’s law governs the agreement, while an offer letter or handbook points to another. This is not an accident — employers often select the law most favorable to enforcement under state law and applicable laws. Which law actually applies can turn on where you live, where you work, and where the harm would occur, and courts do not always defer to the clause the employer wrote. In most states, enforceability still depends on whether the restrictions comply with employment law and whether any provisions violate local rules, though other states apply materially different standards, including for independent contractors. This is a fact-specific, often outcome-determinative question, and it is worth resolving before you assume either state’s rules protect you; the nature of the analysis is to respect jurisdiction-specific limits.
A Practical Starting Point
If you are contemplating a departure to build your own software or AI company, three steps go a long way before you take any public step toward the new venture, because your agreement may be governed by state law and other laws that vary across other states:
- Pull every document you signed at hire — offer letter, confidentiality/invention agreement, employee handbook, and any written agreement — and read them together, not in isolation. Check the contract for compensation, pay, stock options, any probation period, whether you were employed on an at-will basis, what notice is required to terminate, and whether non-disclosure agreements or other service terms affect IP, intellectual property, creative works, company time, proprietary information, confidential information, trade secrets, or any claimed connection to the employer’s goods or services.
- Build your new product from publicly available information and your own general skills and experience, not from internal tools, data, or code. That helps you retain a cleaner record and protect any competitive advantage without using employer material.
- Hold off on recruiting former colleagues, and on operating the new business in any real way, until after you have formally resigned and had the agreement reviewed. Employers often select the law most favorable to enforcement. In most states, courts will generally ask whether the provisions comply with employment law and do not violate local restrictions. That review can also surface legal challenges early, with results that may differ based on the worker relationship, including independent-contractor edge cases.
The AI hiring boom has made this a live issue for thousands of engineers and founders right now. A short review of your existing agreement before you leap is almost always cheaper — and faster — than untangling a dispute after the fact, so respect the governing jurisdiction’s rules before relying on any one clause.
This article is provided for general informational purposes and does not constitute legal advice. Every fundraising situation is different, and founders should consult with an attorney before finalizing any fundraising instruments.
