Skip to main content
Intellectual Property Strategy

Intellectual Property 101 for California Founders

Capture, Protect, and Monetize What You Build. A field manual for creating durable value and surviving investor diligence.

4
Core IP Types
CA-Specific
Traps to Avoid
Diligence-Ready
Checklists
Avoid
Founder Dilution

Executive Overview

For a founder, intellectual property (IP) is not an abstract legal concept; it’s the raw material of value. Your code, brand, content, and secret processes are often the only assets you have. Protecting them isn’t about legal paperwork—it’s about building a defensible, monetizable company that can survive diligence and competition.

Why IP Falls Through the Cracks

Founders are builders, not administrators. In the rush to ship product and close deals, critical IP steps are missed. This guide provides a founder’s framework for getting it right, built on four core principles:

  • IP as the Growth Engine: Value accrues when rights are clearly owned, proven, and assignable.
  • Public vs. Secret: The decision to patent (public) or maintain a trade secret (secret) must be intentional.
  • Chain of Title is Everything: Investors and acquirers diligence ownership records, not promises. Leaks in the chain of title can kill deals or cause massive dilution.
  • The California Reality: Our state has unique, founder-friendly (and sometimes tricky) rules on employee inventions, non-competes, and trade secrets that you must master.
The Cost of a Broken Chain of Title

At your Series A or acquisition, the buyer’s lawyers will conduct deep diligence on your IP. If they find that a key contractor never assigned their code, or an ex-founder still has a claim on the original concept, they will demand a significant price reduction or walk away from the deal entirely. Fixing these issues later is exponentially more expensive than getting them right from day one.

Brand, Trademarks & Clearance

A defensible name is distinctive, available, and properly filed. Before design work or launch campaigns, run a fast but structured clearance, then choose the right filing path to lock in priority.

The Distinctiveness Spectrum

Trademark distinctiveness spectrum and registrability
Category Registerable? Risk Notes / Examples
Generic No High Common name of the product/service (e.g., “Project Management App”). Never registrable.
Descriptive Hard (needs secondary meaning) High Describes a feature/quality (e.g., “Instant Invoices”). Weak and crowded; consider renaming.
Suggestive Yes (typical) Moderate Hints at qualities; requires imagination. Often the startup sweet spot.
Arbitrary Yes (strong) Low Common word out of context for your goods/services.
Fanciful Yes (strongest) Low Coined term (made up word). Strongest rights; more brand‑education required.

Run a Smart Clearance (10–20 minutes)

  1. Web test: Search the exact phrase and close variants. Look for similar products/services.
  2. USPTO (TESS): Check live applications/registrations in likely classes; read the goods/services wording for relatedness.
  3. California registry: Quick scan of state registrations for obvious conflicts.
  4. Common‑law sweep: News, Crunchbase, app stores, LinkedIn, GitHub—unregistered use can still create risk.
  5. Domains & socials: Core TLDs (.com/.io) and key handles (X/Twitter, LinkedIn, Instagram, YouTube). Watch for squatters/misspellings.
  6. Confusion pass: Would consumers think the source is the same? Compare sight, sound, meaning, and channels of trade.
Why early clearance matters

Last‑minute renames burn design work, domains, SEO, and legal fees. Clear the name before brand spend and filings.

Filing Path: Use‑in‑Commerce vs. Intent‑to‑Use

  • Use‑in‑Commerce (1(a)): You’re already offering/selling across state lines. File now with a proper specimen.
  • Intent‑to‑Use (1(b)): Not live yet but committed to the name. File to lock priority, then submit a Statement of Use (SOU) when you launch. Up to five 6‑month extensions are generally available after the Notice of Allowance (maximum ~36 months).

Classes & IDs: Claim what you actually offer. Over‑claiming invites Office Actions; under‑claiming narrows protection. Keep goods/services language accurate.

Specimens, TEAS Choices & Usage

  • Specimens (services/SaaS): A live webpage/app screen showing the mark next to the described services with a way to sign up or buy (not just a coming‑soon splash).
  • Specimens (goods): Labels, packaging, or a product page where the mark identifies the goods with a purchase path.
  • TEAS Plus vs. Standard: Plus has lower fees but stricter ID wording; Standard costs more but is more flexible.
  • ™ vs ®: Use anytime for unregistered marks. Use ® only after federal registration and only for the covered goods/services.
  • State vs. Federal: State filings are narrow. Most growth companies prioritize federal filings for nationwide protection.

Founder Heuristics

  • If your name is descriptive or the class is crowded, rename early—rights will be thin and enforcement costly.
  • File an ITU when you’re serious about a name to stake priority, then convert when you launch.
  • Escalate to counsel when a similar live mark exists in a related class, you’re considering consent/coexistence, or planning multi‑country filings.
Need a trademark attorney? Request a referral.
Informational only; not legal advice. Use of ® is limited to federally registered marks for the listed goods/services.

Patents: Provisional vs. Non‑Provisional vs. Trade Secret

Patents make your invention public in exchange for a time‑limited monopoly. Trade secrets keep it secret as long as you maintain reasonable measures. Choose intentionally and time your filings around demos, sales, and publications.

Patent & trade secret options compared
Option What it does Use when Cost (rough) Key risks
Provisional (US) Holds a priority date for 12 months; never examined. You need an immediate filing before a demo, pilot, or disclosure; you’re refining claims. Low–moderate Doesn’t become a patent; must file a non‑provisional (or PCT) within 12 months.
Non‑Provisional (US) Full application examined by USPTO; can mature into a patent. Your invention is stable and core to your moat. Moderate–high Public disclosure; eligibility hurdles for software/business‑method claims.
PCT (International stage) Central filing that defers country choices for ~30 months. You anticipate foreign markets or acquirer interest abroad. High Still need national filings; costs add up quickly.
Trade Secret Protects valuable, secret info with economic value (as long as secrecy + reasonable measures persist). Hard to reverse‑engineer; value derives from remaining secret (e.g., models, tuning data, processes). Low–moderate (program cost) Loss upon public disclosure or poor hygiene; independent discovery is a defense.

Pre‑Demo / Pre‑Publication Checklist

  • File at least a US provisional if you’re about to disclose publicly (conference, sales deck, launch post, arXiv/paper).
  • Remember many countries have absolute novelty rules; public disclosure before filing can kill foreign rights.
  • Mark slides and pilots under NDA until filing; scrub repos and public issue trackers.

Founder Heuristics

  • Patent when the feature is visible to competitors, core to valuation, and non‑trivial to design around.
  • Trade secret when the value is in the hidden method (e.g., scoring functions, data curation, prompts/tuning, recipes) and you can maintain robust secrecy.
  • On software patent eligibility: focus claims on specific technical improvements, not abstract results.
Considering a provisional or trade‑secret route? Request an attorney referral.
Informational only; not legal advice. Foreign filing routes and timing are fact‑specific.

Trade Secrets & Operational Hygiene (CUTSA)

A trade secret is information that (1) derives independent economic value from not being generally known, and (2) is subject to reasonable measures to keep it secret. In California, misappropriation is actionable under the California Uniform Trade Secrets Act (CUTSA).

Reasonable Measures (Practical Program)

  • Access control: Role‑based access, MFA, least privilege; no personal email repo invites.
  • Labeling: Mark docs/code as CONFIDENTIAL where appropriate; segregate crown‑jewel repos.
  • NDAs: With employees, contractors, vendors, and pilot customers.
  • On/Off‑boarding: Prior‑inventions disclosure, clean‑room reminders, device return/certification, immediate access revocation.
  • Clean room: If hiring from a competitor, document a process to avoid taint (no old code, no “remembered snippets”).
  • Incident playbook: Steps for suspected leaks (pull logs, snapshot access, preserve evidence, notify counsel).
California realities

Non‑competes are generally void; protect secrets with process, not non‑competes. Train managers to avoid asking new hires for anything from a prior employer.

Want a simple trade‑secret policy? Request a referral to counsel.

Employees, Contractors, and Assignment (CA‑Specific)

Your chain of title lives or dies here. Investors diligence signed assignments, not promises.

Employees: PIIA Essentials

  • Use a Proprietary Information and Inventions Assignment (PIIA) with “hereby assigns” present‑tense language.
  • Include the California Labor Code §2870 notice (and obtain employee acknowledgement): inventions developed entirely on the employee’s own time without company resources are excluded, except those that relate to the company’s business or result from the employee’s work.
  • Attach a Prior Inventions schedule (blank if none). Train HR to ensure it’s completed on day one.
  • Non‑competes are generally void under CA law; focus on confidentiality and conflict‑of‑interest covenants.

Contractors & Agencies

  • Contract must include both (a) a “work made for hire” attempt and (b) an express assignment fallback: “Contractor hereby assigns…”
  • Deliverables should be defined; acceptance can trigger the assignment clause if you prefer.
  • License back any contractor tools/templates they need for future clients; you own the deliverables, not their generic know‑how.

On/Off‑Boarding Checklist

  • Collect signed PIIA/contractor agreements and prior‑inventions schedules.
  • Provision least‑privilege access; document devices; restrict personal cloud syncing.
  • Exit: confirm return/deletion of confidential info; obtain certification; shut off access same day.
Red flags investors notice

Missing PIIAs, unsigned prior‑inventions schedules, agency logos without assignments, and code from moonlighters with no written agreement.

Need a CA‑compliant PIIA set? Request an attorney referral.

Open Source & Third‑Party Assets

Open source accelerates development—and can accidentally “open” your own code if you choose the wrong license. Track it from day one.

License Families (Very Short Map)

Common OSS licenses and obligations
License Type Obligations (simplified) Notes
MIT / BSD‑2/3 Permissive Keep copyright + license notice. Generally business‑friendly.
Apache‑2.0 Permissive Notices + patent license/termination terms. Good default for many teams.
LGPL Weak copyleft Modifications to the library must be shared; dynamic linking usually okay. Be careful with static linking.
GPLv2/v3 Strong copyleft Derivative works must be GPL; provide source to recipients. Hard to combine with proprietary code.
AGPL Network copyleft Serving over a network may trigger source‑availability obligations. High risk for SaaS if integrated into core code.

Third‑Party Assets

  • Fonts, images, music, video: Keep license files and IDs; ensure commercial/ad/web embedding rights.
  • SDKs/APIs: Review ToS for attribution/brand use, data rights, and audit clauses.

OSS Hygiene

  • Run software composition analysis (SCA) and maintain a bill of materials (SBOM).
  • Centralize approvals for GPL/AGPL/LGPL; involve counsel for AGPL or GPL in server‑side code.
  • Publish required notices for your distributions; automate NOTICE file generation.
Investor hot button

GPL/AGPL deep in a proprietary SaaS app with no plan. Have an inventory and a mitigation story.

IP in Your Commercial Contracts

Your MSA/SaaS terms should preserve your IP, manage customer data rights, and fence in indemnity risk.

Key Clauses to Get Right

  • IP Ownership: You own your platform and improvements; customer owns their data. Grant a limited license to host/process customer data.
  • Feedback: Customer grants you a license to use feedback without obligation (no IP trap doors).
  • Deliverables: If you do custom work, specify whether it’s licensed (preferred) or assigned (priced accordingly).
  • Indemnity: Standard vendor IP indemnity for third‑party claims; include process (notice, control of defense) and remedies (modify/replace/refund cap).
  • Open‑source disclosures: Reserve the right to use OSS in the service and to provide required notices.
  • Publicity: Permission to use name/logo unless customer opts out.
Need an MSA/SaaS template reviewed? Request a referral to contract counsel.

Domains, Handles, and Brand Enforcement

Own the namespace around your brand, secure it, and know your takedown routes.

Ownership & Security

  • Register domains in the company’s name (not a founder). Lock at the registrar and enable 2FA.
  • Set SPF/DKIM/DMARC to protect outbound email reputation.
  • Secure core social handles early; store recovery emails and phones in a shared vault.

Enforcement Options

  • Platforms: Use in‑platform trademark/impersonation tools for quick wins.
  • Domains: Consider a UDRP complaint for bad‑faith registrations; escalate to litigation for cybersquatting if needed.
  • Marketplaces/Ads: Trademark program portals can remove misleading listings/ads.
Practical tip

Register obvious misspellings and core country codes you plan to use. It is cheaper than recovering later.

Enforce & Defend (Practical Ladder)

Start cheap, escalate only when needed. Document everything.

Ladder

  1. Evidence pack: Screenshots, timestamps, whois, traffic impact, confusion examples.
  2. Platform routes: DMCA, trademark, impersonation portals; often fastest.
  3. Letter: Short, factual, with attachments (registrations, comparisons) and a concrete ask and deadline.
  4. Registries/TTAB: Oppositions/cancellations for trademark conflicts; UDRP for domains.
  5. Litigation: Reserve for material harm (injunctions/damages). Evaluate insurance.

Common Defenses You’ll See

  • Trademark: Descriptive/fair use, lack of likelihood of confusion.
  • Copyright: Fair use, independent creation, license.
  • Trade secret: Not secret/no reasonable measures; independent development.

Investor/M&A Diligence Readiness

Buyers will test whether you own what you say you own. Make it easy to say yes.

IP Data Room (Suggested Index)

Suggested IP data room structure
Folder Contents
01_Registrations Trademark certificates, copyright certificates, patent filings/status.
02_Applications Pending apps (trademark/patent), Office Actions and responses.
03_Assignments Founder/employee/contractor assignments, agency assignments, prior‑inventions schedules.
04_OSS_Scan SBOM, license inventory, approvals/exceptions.
05_Policies Trade‑secret policy, security policy, incident response, IP review checklist.
06_Contracts MSA/SaaS template, major customer/vendor agreements (with IP/indemnity terms flagged).
07_Domains_Social Domain list (registrar, lock/auto‑renew), social handles, 2FA/ownership proof.

Pre‑Diligence Sweep

  • Confirm every contributor has a signed assignment (map contributors → agreements).
  • Run an OSS scan; mitigate GPL/AGPL risks; produce a clean SBOM.
  • Align your brand filings with what you actually sell today.
  • Ensure all domains/socials are company‑owned and 2FA‑protected.

Action Checklists

Use these at key stages. Keep them in your ops wiki and check quarterly.

Day 0: Before Incorporation
  • ☐ Founder IP assignments to the future company (pre‑formation).
  • ☐ Trademark clearance for company/product names; reserve core domains/handles.
  • ☐ Document any “prior inventions” excluded from assignment.
  • ☐ If you must disclose publicly, file a provisional patent.
Pre‑Launch
  • ☐ File ITU/Use‑in‑Commerce trademark applications for primary marks.
  • ☐ Register copyrights (code/UI/marketing) within 90 days of publication.
  • ☐ Implement trade‑secret measures (access, labels, NDAs).
  • ☐ OSS inventory + SBOM; remediate high‑risk licenses.
  • ☐ Terms of Service/Privacy Policy live and accurate.
Hiring / Contracting
  • ☐ Employee PIIA with CA §2870 notice + prior‑inventions schedule.
  • ☐ Contractor agreement with work‑for‑hire + express assignment language.
  • ☐ Onboarding training: trade‑secret hygiene; no materials from prior employers.
  • ☐ Off‑boarding: return/certify deletion; access revocation; reminder of ongoing obligations.
Pre‑Fundraise / M&A
  • ☐ Build IP data room (registrations, assignments, OSS, policies).
  • ☐ Contributor → agreement mapping; fix gaps.
  • ☐ Domain/social audit; transfer to company where needed; lock/2FA.
  • ☐ Counsel review for diligence‑readiness; address red flags proactively.
Quarterly Ops
  • ☐ File new brand variants; refresh OSS SBOM; register major release copyrights.
  • ☐ Access review on secret repos; rotate keys; spot‑check NDA coverage.
  • ☐ Update the chain‑of‑title spreadsheet.

Frequently Asked Questions

Disclaimer: This guide is for informational purposes only and does not constitute legal advice. No attorney-client relationship is created by its use. Attorney Advertising.
Your Next Step

Protect the IP—and the Entity.

A 30-minute IP review can prevent assignment gaps that derail financing. A properly formed LLC or corporation is the vessel that holds these valuable assets and shields you from liability. LAWINC focuses on entity formation for small businesses; for trademarks, copyrights, or patents we connect you with vetted attorneys.