LESSON 4
Negotiating AI Clauses in Employment Contracts
Your next job offer may include clauses that claim ownership of your AI workflows, prompt libraries, and personal projects. This lesson teaches you what to watch for — and how to push back.

THE OWN IT FRAMEWORK
The "OWN IT" AI Clause Review
When reviewing any employment contract, check these four areas to protect your AI-related intellectual property.
- 1. Outputs: Company keeps deliverables, but your general methodology and prompt PATTERNS are yours
- 2. Work Scope: Narrow IP assignment to "work within scope using company resources"
- 3. No-Go Areas: Push back on clauses covering personal projects, pre-existing IP, and off-hours work
- 4. Time Bounds: Limit non-compete/IP tails to 6 months max — negotiate 12-24 months down

CASE STUDY
Alex: The Side Project Clause
Alex's new contract tried to claim ownership of ALL AI workflows created during employment — including personal GPTs and Zapier automations.

The Red Flag
- Clause: "Any AI models, prompts, or workflows created during employment..."
- Scope: "...whether or not using Company resources"
- Risk: Would have lost ownership of 18 months of personal tools

The Negotiation
- Fix: Added: "Excluding pre-existing IP per attached schedule"
- Action: Listed all personal projects on the IP schedule
- Result: Company agreed — Alex kept his tools
KEY INSIGHT
Your Prompt Library Is IP — Treat It That Way
The legal landscape is evolving fast. Standard IP clauses now include post-employment assignment for AI inventions. Protect yourself proactively.
IP
Standard clauses now cover AI outputs, models, and workflow improvements
Source: LinkedIn Legal
New
Legal guidance recommends explicit AI IP ownership in all new employment agreements
Source: Deloitte