Founders in Arizona and California need the same set of documents. Where those two states split is enforceability. Several clauses that hold up in Arizona are void in California, and a template drafted for one state can quietly fail in the other.
Most early-stage founders download a document pack, fill in the blanks, and assume it works everywhere their company touches. It doesn't, and the reason is where your people actually sit. Non-compete enforceability turns on where the employee works, not where you incorporated (Primum Law). Incorporate in Delaware, run the company from Phoenix, hire an engineer in San Francisco, and that engineer's employment terms answer to California law regardless of what your template says.
That single mechanism breaks the copy-paste stack in ways founders rarely catch until diligence. A non-compete clause that survives Arizona's reasonableness test is void the moment the same offer letter goes to a California hire under Business and Professions Code Section 16600. A privacy policy written for an Arizona SaaS company can still trigger California obligations the day you sign a customer in Los Angeles. When an employee relocates across the AZ/CA line, the governing law often changes and the agreement never gets revisited, leaving a gap nobody planned for.
Founders who operate across both states carry this cross-border risk into every priced round, because investors read the documents that generic templates get wrong. Five categories decide whether your paperwork holds up: co-founder agreements, IP assignment agreements, NDAs, offer letters and employment agreements, and contractor agreements. Each one behaves differently depending on which side of the state line it lands on, and each is walked through below with the Arizona and California distinction that actually matters.
A co-founder agreement fixes equity splits, roles, decision rights, and departure terms while everyone still agrees, and its most important job is vesting. Vesting means each founder earns their shares over time instead of owning them outright at incorporation. Without it, a co-founder who leaves after three months keeps their full stake, and that dead equity sits on the cap table as a permanent liability.
The urgency is not theoretical. Roughly one in four founding teams loses a co-founder by year four, and the market-standard protection is four-year vesting with a one-year cliff. Structured as reverse vesting, the company holds a buyback right at cost on unvested shares, so a departing founder returns most of their equity for a fraction of a cent per share. Skip this, and sorting out equity on departure comes down to negotiation and goodwill, which usually fails when the relationship already has.
Investors treat missing vesting as a diligence red flag before any priced round. One investor called an inverted cap table, where investors collectively hold more than the founders, "essentially uninvestable" absent a full restructuring. Founders receiving restricted stock also face a hard tax deadline. You must file an 83(b) election with the IRS within 30 days of the grant, and neither Arizona nor California waives that federal clock.
Where the two states diverge is entity practice and investor expectation. California founders and their institutional backers overwhelmingly expect a Delaware C-corp with reverse vesting, and California courts scrutinize buyback and forfeiture terms closely. Arizona founders more often start as an LLC, where "vesting" runs through membership-interest and repurchase provisions that read differently and need conversion planning before a priced round.
Best for a template versus a lawyer. A clean 50/50 split between two founders with equal cash contribution and no pre-formation IP can survive a standard vesting template. Once contributions are unequal, one founder built code or filed provisional patents before incorporation, or you plan an LLC-to-C-corp conversion, a lawyer should draft the terms. The template cannot value that pre-formation work or protect it in diligence.
Every person who creates anything for your company must sign an IP assignment agreement, with no exceptions for founders, employees, contractors, or advisors. Investors treat missing assignments as a diligence dealbreaker because a gap means the company may not actually own the code, designs, or trademarks it claims as its core asset. The cost math is stark. A proper set of assignments runs $1,000 to $3,000 to prevent, while an unresolved gap becomes a deal killer that ends the round entirely.
A workable IP assignment agreement does three things. It transfers ownership of anything the person creates for the company back to the company, it covers pre-formation work so a founder's earlier prototype belongs to the corporation and not to the individual, and it includes a present assignment of future inventions so ownership vests automatically rather than requiring a signature later. Advisors and early contractors get skipped most often, and those are precisely the gaps a term sheet's diligence checklist surfaces.
In both Arizona and California, a Proprietary Information and Inventions Agreement does more practical work than a non-compete. A PIIA governs ownership and confidentiality of code, product designs, proprietary processes, and trade secrets rather than restricting where someone can work next. That distinction matters in California, where Section 16600 makes a non-compete unenforceable, so the PIIA is your only reliable protection. It matters in Arizona too, where a non-compete survives only if it clears the four-factor reasonableness test, while a well-drafted IP assignment holds up without that uncertainty. Treat the IP assignment as the load-bearing document in both states, and treat the non-compete as a supplement that may or may not survive a court.
A one-way NDA protects one party's information, and a mutual NDA protects both sides equally. The choice depends on who actually shares secrets. When you bring on an early hire or a contractor, you disclose your code, roadmap, and customer data, so a one-way NDA binding them to confidentiality fits. When you and a vendor both expose proprietary details to make a deal work, a mutual NDA reflects that reality and reads as fair rather than one-sided.
NDAs do more work in Arizona and California than founders expect, because confidentiality and non-solicit provisions stay enforceable in both states even where non-compete clauses get struck down. California bans most employee non-competes outright, and Arizona subjects them to a four-factor reasonableness test that aggressive drafting can collapse. A well-drafted NDA carries the protection a non-compete cannot, which makes it a load-bearing document rather than boilerplate.
Best for: Skip the NDA in most early investor conversations. Serious VCs decline to sign them, and pushing one signals inexperience. Reserve mutual NDAs for contractor and vendor relationships where both sides trade sensitive information, and use one-way NDAs for employees and advisors who receive your confidential material without handing over their own.
The non-compete clause is the single document term where copying a California offer letter into Arizona, or the reverse, does the most damage. California's Business and Professions Code Section 16600 bans employee non-competes outright as a bright-line rule, so any non-compete language you paste into a California offer letter is a liability rather than a protection (Primum Law). It won't hold, and including it can expose you to a claim from the employee. Arizona takes the opposite approach and enforces reasonable non-competes under a four-factor case-law test anchored in Valley Medical Specialists v. Farber (Allen Law).
Arizona courts ask four questions. You need a real protectable interest like trade secrets or customer relationships, since a general fear of competition doesn't qualify. The scope must fit that interest, the restriction can't push someone out of their profession, and the covenant has to rest on real consideration such as a new job or an ownership stake. Practically, a duration of six months to one year holds up, a 15-mile radius for six months reads as reasonable, and a statewide three-year ban on a salesperson likely fails (Arizona Employment Attorney).
Aggressive Arizona drafting carries its own trap. If a covenant is overbroad, Arizona courts strike the unenforceable parts but will not rewrite the agreement to save it, so a greedy clause can collapse entirely. A narrower non-compete that actually holds protects you more than a sweeping one that a court voids.
Non-solicits and a Proprietary Information and Inventions Agreement do the reliable protective work in both states. Customer and employee non-solicits are narrower than non-competes and survive even where non-competes are limited, which makes them the more dependable enforcement tool in Arizona and the only real restrictive option in California (Primum Law). A PIIA governs ownership of code, designs, and trade secrets rather than restricting future employment, so it protects the assets you actually care about without depending on Section 16600 or the four-factor test.
Governing law follows where the employee works, not where you incorporated. An Arizona hire who relocates to California can flip which rule applies, and founders rarely revisit the agreement after the move, which leaves a non-compete you thought was enforceable dead on arrival. Draft each offer letter to the employee's actual work location, and revisit it whenever a remote hire crosses the state line.
A contractor who signs no agreement often keeps the copyright to the code, designs, or content they produce for you. Contractor work does not automatically fall under work-for-hire the way employee output does, so ownership stays with the creator until a signed agreement assigns it. Boyer Law Firm puts it plainly: without a proper agreement, contractors may retain legal ownership of the work they create. That gap surfaces during diligence, and it kills investment when a startup can't prove it owns its own product.
Every contractor agreement needs a present-tense IP assignment and a confidentiality clause tied to your specific product, not a generic template placeholder. Pair it with the same PIIA-style ownership language you use for employees. In both Arizona and California, that assignment is the reliable protection, because it governs who owns the work rather than trying to restrict where the contractor works next.
Worker classification is where the two states diverge on penalty. California treats misclassification aggressively, with fines running $5,000 to $25,000 per violation on top of back wages and taxes (Startup Legal Basics). Preventing that costs roughly $200 per contractor in proper paperwork versus $5,000 to $50,000 per worker once a claim lands. Getting classification right upfront is not a nice-to-have when the downside runs that steep.
Arizona adds a drafting nuance on non-compete language in contractor agreements. The state applies the same four-factor reasonableness test it uses for employees, but weights hardship differently. A contractor with many clients gets far less hardship protection than one working functionally full-time for you (Allen Law). A lawyer scales the restriction to the actual relationship, so the clause survives instead of collapsing when tested.
Your CCPA obligations do not depend on where you incorporated or where your team sits. The CCPA applies to any for-profit business "doing business in California" that meets one of three thresholds. Your company can be doing business in California by running online transactions with California residents, tracking them through cookies, or employing a remote worker there, all without a physical office in the state (jacksonlewis.com). An Arizona-incorporated SaaS startup with California users can be fully covered.
The three thresholds decide whether you cross the line. You trigger the CCPA if you hit annual gross revenue over $26.625 million as of January 1, 2025, buy, sell, or share the personal information of 100,000 or more California residents or households, or derive 50% or more of your revenue from selling or sharing California residents' personal information (oag.ca.gov/privacy/ccpa). The revenue figure counts total gross revenue, not just California revenue, so a well-funded startup can qualify on size alone.
A compliant privacy policy carries specific content, and generic templates rarely include all of it. Your policy must list the categories of personal information you collect and their sources, why you collect it, and the categories of third parties you share or sell it to. It must explain the consumer rights to know, delete, correct, opt out, and limit use of sensitive personal information, and how a user exercises each one. If you sell or share data, you need a clear "Do Not Sell or Share My Personal Information" link that works without forcing account creation, and you must respond to opt-out requests within 15 business days (oag.ca.gov/privacy/ccpa).
The rules keep expanding, and a document you draft today should anticipate that. New regulations effective January 1, 2026 add obligations around automated decision-making technology, risk assessments, and cybersecurity audits. If your product uses automated decision-making, you will need to disclose the specific purpose and the decision logic, not a generic line like "to improve our services" (jacksonlewis.com). A privacy policy built around your actual data practices ages better than one pulled from a form library.
A template and a lawyer-drafted document differ most in the clauses you don't know to ask about. Courts enforce what the document says, not what founders assumed it covered, and generic templates ignore state-specific law, miss industry risk, and give founders false confidence. The table below maps that gap document by document, so you can see where a template holds up and where its silence becomes a diligence problem or a lawsuit.
A template library sells you a document. It cannot read the facts of your specific hire and tell you whether the non-compete clause you're about to sign will hold up. Promise.legal and Clerky both generate clean, standardized paperwork, and for a single-state Delaware C-corp with cookie-cutter facts, that paperwork often works. The problem starts when your facts stop being standard.
Arizona courts apply a four-factor reasonableness test to non-competes, weighing duration, geographic scope, consideration, and the legitimate interest being protected. California enforces a bright-line rule under Section 16600 that voids most non-competes outright. A template cannot run either analysis against your engineer in Phoenix or your sales lead in San Francisco. A lawyer can read the role, the location, and the equity, and then draft language that survives diligence instead of collapsing in it.
That gap widens the moment you operate across both states. If you incorporate in Arizona and hire remote in California, employment law follows the employee, and a generic offer letter can hand you an unenforceable clause you thought was protection. CCPA exposure works the same way. Serving California customers triggers obligations regardless of where you sit, and a boilerplate privacy policy rarely reflects the opt-out mechanics regulators actually require.
Zecca Ross Law Firm drafts these documents at a flat fee, so you know the cost before the work starts, and a lawyer applies the correct state rule to your actual hires. That matters most right before a priced round, when investors read every agreement in diligence and treat gaps as leverage.
If you're heading into a fundraise in the next few months, book a document review with Zecca Ross and fix the gaps before an investor finds them.
Which state's law governs if we incorporate in Delaware but operate in Arizona or California? Delaware governs your internal corporate matters, like stockholder rights and board duties. Employment enforceability follows where the employee actually works, so a non-compete for a California-based hire is void under Section 16600 no matter where you incorporated. Arizona's four-factor test applies to your Arizona staff.
Do we need separate agreements for California and Arizona employees? Yes for the restrictive-covenant provisions. A single national template either drafts non-competes that are void in California or bland language that leaves your Arizona hires under-protected. Confidentiality, IP assignment, and offer terms can share a base, but the enforceable protection differs by employee location.
When does a template actually suffice? When your facts are genuinely plain, meaning equal co-founders, no meaningful pre-formation IP, employees all in one state, and no California customer data. A mutual NDA or a straightforward contractor agreement often works off a good template. The moment contribution is unequal, IP predates the company, or you hire across the Arizona-California line, a template starts hiding real risk.
What happens if we already used a template and are now raising a priced round? Investors will catch the gaps in diligence. Missing vesting schedules, unsigned IP assignments, and an inverted cap table are common red flags, and one investor called an inverted table "essentially uninvestable" without a full restructure (CRV). Fixing these before you circulate a term sheet is far cheaper than renegotiating equity mid-round. Have a lawyer audit the stack now, close the assignment gaps, and confirm your 83(b) elections were filed within the 30-day window, since that deadline cannot be cured after it passes.
Legal clarity starts here. Partner with Zecca Ross Law Firm to transform complexity into opportunity.