How to Draft a California AB 5–Compliant Independent Contractor Agreement for a SaaS Startup in 2026
In California, a SaaS startup must satisfy the AB 5 “ABC test” (or a statutory exemption) to classify a worker as an independent contractor in 2026. Misclassification can trigger wage-and-hour liability, penalties, and PAGA exposure. This article explains how to draft an AB 5–compliant independent contractor agreement for common SaaS roles, including key clauses, exemption strategy, and onboarding documentation.
California’s AB 5 framework remains the central legal “gatekeeper” for independent contractor classification: if you cannot meet the statutory test (or cleanly fit an exemption), your “contractor” should generally be treated as an employee for California purposes. For SaaS startups—where talent is frequently engaged for engineering, product design, sales development, content marketing, implementation, and customer success—misclassification risk often arises not from bad intent, but from operational reality: contractors end up integrated into the team and managed like employees.
This guide focuses on drafting and structuring an independent contractor agreement that aligns with AB 5 and related California enforcement risks in 2026. It is not a substitute for role-by-role legal analysis; AB 5 compliance is as much about facts and day-to-day practice as it is about contract language.
1) Start With the AB 5 Framework: ABC Test or Exemption
AB 5 (codified primarily in Labor Code section 2775 and related provisions) uses the “ABC test” as the default for determining whether a worker is an employee. The hiring entity must generally establish all three prongs:
A. Freedom from control and direction
The worker must be free from the company’s control and direction in performing the work, both under the contract and in practice. “Control” includes how, when, and where the work is done, the tools used, and whether the worker is managed like staff (daily standups, required hours, internal performance plans, etc.).
B. Work outside the usual course of the hiring entity’s business
The worker’s services must be outside your usual course of business. This is the prong that trips up many SaaS startups. If your core business is developing, selling, or supporting a software platform, then core engineering, product management, customer support, and often sales work can be viewed as within your usual course.
C. Independently established trade or business
The worker must be customarily engaged in an independently established trade, occupation, or business of the same nature as the work performed—typically shown through a business entity, multiple clients, separate marketing, business insurance, business licensing (if applicable), and the ability to accept/refuse projects.
Exemptions: AB 5 contains multiple exemptions (with their own tests), including “business-to-business” contracting and certain professional services. Exemptions do not mean “anything goes.” They usually require a written contract plus factual elements (e.g., separate business location, autonomy, ability to contract with others). Your agreement should be drafted to match the exemption you are relying on—and your operations must also match.
2) Role Triage for SaaS Startups: Who Is Most (and Least) Defensible as a Contractor?
Before drafting, identify whether the role can plausibly meet prong B or an exemption. A practical triage approach:
Often higher risk under prong B (core business functions)
Software engineers, product designers, QA testers, implementation specialists, customer success/support, and sales development reps frequently look like the “usual course” of a SaaS business, especially if they use internal systems, represent the company to customers, or are scheduled like employees.
Often more defensible (ancillary, project-based, or specialized)
Brand designers for a discrete rebrand, PR firms, specialized security consultants performing a limited-scope assessment, tax/accounting firms, or a content studio producing a defined deliverable may be easier to structure as independent contractors—particularly via business-to-business contracting.
Drafting implication: If a role is structurally within your core business, a “perfect” contract will not cure misclassification. The safer legal move may be (1) hire as an employee, (2) use a staffing agency/employer-of-record model where appropriate, or (3) re-scope the engagement into a discrete, deliverable-based project performed by a true independent business.
3) Agreement Architecture: Draft for AB 5 Compliance and Audit Readiness
A California-facing independent contractor agreement for a SaaS startup should be built around: (i) classification strategy, (ii) deliverables and autonomy, (iii) payment structure, (iv) IP/data/security, and (v) dispute/risk allocation. Below are core sections and drafting objectives.
3.1 Parties, status, and classification statement (don’t overpromise)
Include a clear statement that the contractor is an independent business and not an employee, but avoid “magic words” that conflict with reality. State that contractor is responsible for taxes, workers’ comp (if applicable), licenses, and insurance. Add a compliance-forward qualifier, e.g., that both parties intend to comply with applicable law and will cooperate if reclassification is required by a government determination.
Drafting tip: Do not include provisions that look like employment, such as paid vacation, employee-style benefits, or mandatory attendance at daily internal meetings. If you need attendance, frame it around project coordination and milestone reviews, not “supervision.”
3.2 Scope of services: define deliverables, not job duties
AB 5 risk increases when the agreement reads like a job description. Structure the scope as:
- Statement of Work (SOW) with defined deliverables (e.g., “Security assessment report,” “Landing page design system,” “SOC 2 readiness gap analysis”).
- Milestones tied to acceptance criteria.
- Change order process for new work (avoid open-ended “and other duties as assigned”).
Example (good): “Contractor will deliver a penetration testing report covering the environments listed in Exhibit A and remediation recommendations by date.”
Example (bad): “Contractor will support engineering as needed and attend standups.”
3.3 Autonomy clause: control the “control” prong
Include a section emphasizing the contractor’s control over the manner and means of performance, including:
- Contractor controls schedule and work location (subject to reasonable security requirements).
- Contractor supplies tools/equipment, except limited access credentials or company systems necessary for security.
- Contractor may use subcontractors/assistants (with prior written consent for security and confidentiality).
- No exclusivity; contractor may provide services to others.
Operational alignment matters: If you require 9–5 availability on Slack, mandatory internal standups, or manager approvals for time off, your actual practices may contradict the contract.
3.4 Payment terms: favor project fees over hourly “timesheet employment”
AB 5 analysis is fact-based, but hourly pay, tight time tracking, and indefinite engagements can look employment-like. Consider:
- Fixed fee per deliverable or milestone payments.
- Clear invoicing schedule and net terms.
- Late payment language and expense pre-approval.
If hourly billing is necessary (e.g., specialized consulting), still define a maximum cap, deliverables, and avoid internal timekeeping tools used for employees.
3.5 Term, termination, and “project end” mechanics
At-will termination is common in employment; for contractors, consider termination tied to breach, nonperformance, or convenience with notice, plus payment for work performed to date. Define how partially completed deliverables are handled and what happens to company data and credentials upon termination.
4) Build for the Exemption You’re Using (Especially Business-to-Business)
Many SaaS companies attempt to use the business-to-business structure: the contractor is a bona fide business (often an LLC or corporation) contracting to provide services. If that is your strategy, your agreement and onboarding should support it.
Key drafting elements to support a business-to-business posture
- Entity contracting party: contract with the contractor’s business entity (not the individual) where appropriate.
- Business representations: contractor represents it is properly formed, in good standing, and provides services to multiple clients.
- Business location: contractor maintains a separate business address (even if remote/home office) and is not provided a company office as a default.
- Autonomy and discretion: contractor retains discretion to set hours and sequence of work.
- Insurance: require commercially reasonable insurance appropriate to the engagement (e.g., general liability; cyber/professional liability for security consultants).
- Advertising/holding out: contractor represents it holds itself out to the public (website, portfolio, business listings) where consistent with its industry.
Important: Do not “paper” an exemption while operating like employment. For example, contracting with “DevOps Consulting LLC” won’t help if the individual works full-time under a CTO’s daily supervision doing core platform operations indefinitely.
5) SaaS-Specific Clauses You Should Not Skip
Even if AB 5 is the classification driver, SaaS startups have unique IP, data, and security exposure. A compliant agreement should also be commercially protective.
5.1 Confidentiality and trade secret protection
Define confidential information broadly (source code, product roadmaps, customer lists, pricing, security architecture) and include exceptions (public info, independently developed
