California · 6 min read
For most California software companies, the first time errors and omissions insurance in California becomes urgent isn't a lawsuit — it's a contract. A prospective enterprise customer sends over their MSA, the insurance section requires "professional liability / errors & omissions insurance with limits of not less than $2,000,000 per claim," and your deal is now blocked until a certificate of insurance lands in their procurement inbox. OnePark Risk specializes in exactly this: placing tech E&O for venture-backed software companies in San Francisco, Silicon Valley, and Los Angeles. Here's what the coverage does, why California contract norms make it unavoidable, what it costs, and how to get quoted fast enough to keep your deal moving.
E&O insurance in California — for software companies, usually written as technology errors & omissions — covers claims that your product or professional services failed, underperformed, or caused a client financial loss. Core coverage includes: Defense costs — attorneys' fees from day one, which in California's legal market are often the largest part of any claim. Damages and settlements — amounts you become legally obligated to pay for a covered claim. Software failure and negligence claims — your platform goes down during a customer's critical window, a data migration corrupts records, an integration error costs a client revenue, a missed deliverable triggers a dispute. Contractual liability tied to your services — including liability you assume under the indemnification clauses customers demand (more on that below). A modern tech E&O policy is typically paired — often on the same form — with cyber coverage, because a security failure and a service failure are frequently the same incident. If a breach takes your platform offline and customers sue over the outage, you want one carrier responding, not two arguing about whose problem it is.
California's tech economy runs on master services agreements, and those agreements have hardened into a fairly predictable set of demands on vendors: Indemnification clauses. Nearly every enterprise MSA out of a Bay Area or LA legal department requires you to indemnify the customer for losses arising from your negligence, your product's failure, or third-party claims. You're contractually absorbing risk — E&O is how you finance it. Required insurance schedules. California enterprise contracts routinely specify minimum E&O limits — $1M per claim is the floor, and $2M–$5M is common once you're selling to large enterprises, financial institutions, or healthcare organizations. Many also require coverage to continue for a period after the contract ends. Certificates before kickoff. Procurement teams won't issue a PO or grant production access until they hold a certificate of insurance matching the contract. We issue certificates same-day for our clients precisely because deals stall on this. Limitation-of-liability carve-outs. Sophisticated buyers increasingly carve indemnification and confidentiality breaches out of liability caps — meaning your theoretical exposure under a single contract can far exceed the contract's value. That asymmetry is the strongest argument for real E&O limits, not minimum ones. If you're selling into Silicon Valley enterprises, this isn't a someday problem. It usually shows up in your first or second meaningful enterprise negotiation.