The answer
Technology errors and omissions insurance pays defense costs, settlements, and judgments when a client alleges that software, consulting, or managed services failed to perform, were delivered late, or caused financial loss. No state requires it to do business, but client contracts and vendor onboarding almost always do. Coverage mechanics are the same everywhere: a claims-made and reported form, a retroactive date set at inception, and limits driven by the largest contract in the portfolio. Premium is set by service mix, revenue, client size, data handled, limits, and claims history rather than by state alone.
States where PRIA writes coverage
Texas (TX)
Texas tech firms face E&O claims from enterprise software contracts, implementation delays, and energy and healthcare data work; no state rule requires coverage, but client contracts usually do.
Florida (FL)
Florida tech and fintech firms see E&O exposure from payment integrations, healthcare data, and government contracts, where certificates and specific limit wording are usually required before work starts.
Illinois (IL)
Illinois SaaS, fintech, and data firms are usually asked for tech E&O by enterprise clients in Chicago and by vendors upstream in their own supply chain.
New Jersey (NJ)
New Jersey tech firms serving pharma, financial services, and telecom clients carry tech E&O to satisfy vendor agreements and to cover work delivered across state lines.
Nevada (NV)
Nevada tech firms working in gaming systems, hospitality platforms, and data center operations carry tech E&O because uptime failures and integration errors translate directly into client revenue loss.
Delaware (DE)
Delaware is where many tech companies are incorporated but not where they operate, so tech E&O here usually means matching the entity on the policy to the state of incorporation and the states where work is actually performed.
Typical limits and contract requirements by state
The limits below are the placements carriers most often quote for tech firms in each state, not state requirements. The contract column describes what client agreements usually ask for, and the notes column covers what underwriting tends to focus on. Confirm your own contracts before relying on any row.
| State | Typical limits | Contract requirements | Underwriting notes | What we need to quote |
|---|---|---|---|---|
| Texas (TX) | $1M per claim / $1M aggregate for a small SaaS or consulting firm; $1M / $2M for enterprise implementations; $2M / $4M for firms with revenue-driving systems | Enterprise MSAs commonly require a $1M professional liability limit, a certificate before the first invoice, and sometimes additional insured wording | Energy, healthcare, and industrial clients ask more underwriting questions about data handling and service credits than about state rules | Application, entity and ownership details, revenue split by service line, largest client contract insurance clause, 5 years of claims and incident history, retroactive date and prior acts details, subcontractor use |
| Florida (FL) | $1M / $1M for a small firm; $1M / $2M for payments and healthcare integrations; $2M / $4M for public sector and multi-client platforms | Public sector and enterprise clients often require proof of coverage before award and may ask to be named as an additional insured | Payment and healthcare data work draws questions about PCI scope, breach response, and whether cyber sits inside or outside the E&O limit | Application, entity and ownership details, revenue split by service line, public sector or enterprise contract insurance clauses, 5 years of claims and incident history, retroactive date and prior acts details, data types handled |
| Illinois (IL) | $1M / $1M for a small firm; $1M / $2M for SaaS and data services; $2M / $4M for fintech and firms inside larger vendor chains | Enterprise clients commonly ask for a $1M or $2M limit, a stated retroactive date, and written confirmation that the policy is claims-made | Firms subcontracting to larger vendors inherit insurance obligations upstream, so the policy often has to satisfy two contracts at once | Application, entity and ownership details, revenue split by service line, upstream vendor agreement insurance requirements, 5 years of claims and incident history, retroactive date and prior acts details, subcontractor and offshore use |
| New Jersey (NJ) | $1M / $1M for a small firm; $1M / $2M for life sciences and financial services IT; $2M / $4M for firms serving regulated clients | Pharma and financial services clients usually require documented security controls alongside a $1M to $2M limit and certificates | Firms delivering most work to clients in other states should schedule every state where work is performed, not just the home office | Application, entity and ownership details, revenue split by service line, client security and insurance requirements, 5 years of claims and incident history, retroactive date and prior acts details, states where work is performed |
| Nevada (NV) | $1M / $1M for a small firm; $1M / $2M for hospitality and construction software; $2M / $4M for gaming systems and data center operations | Licensed gaming vendors and resort clients typically require a certificate as part of vendor onboarding and may specify limit and notice wording | Uptime and service credit commitments drive underwriting, so document availability terms and incident response before applying | Application, entity and ownership details, revenue split by service line, uptime and service credit commitments, 5 years of claims and incident history, retroactive date and prior acts details, vendor licensing status |
| Delaware (DE) | $1M / $1M for a small firm; $1M / $2M for data and corporate services; $2M / $4M for firms covering multiple entities | Corporate clients usually require the named insured to match the contracting entity exactly, with certificates issued to each affiliate that signs | Delaware incorporation with operations elsewhere is common, so the policy must name the right entity and schedule every state where work is performed | Application, legal entity name and state of incorporation, ownership and affiliate structure, revenue split by service line, 5 years of claims and incident history, retroactive date and prior acts details, states where employees and contractors work |
Limits shown are indicative market placements and are subject to underwriting. Coverage is not required by any state on this list, but client contracts, vendor onboarding, and procurement reviews usually require a certificate. Policy language controls.
What tech E&O covers, in any state
Technology errors and omissions insurance pays defense costs, settlements, and judgments when a client alleges that software, consulting, or managed services failed to perform as promised, were delivered late, or caused the client financial loss. Most forms also respond to a network security or privacy event, sometimes as a separate cyber policy with its own limit.
Coverage is written claims-made and reported: the claim must be reported while the policy is in force, and the work giving rise to it must have occurred after the retroactive date. That structure does not change by state, which is why the retroactive date and the prior acts wording matter more than the carrier's address.
What to check before you bind
- Confirm the retroactive date, and whether prior acts are honored without exclusions when you switch carriers.
- Confirm the named insured matches the entity that signs client contracts, including any subsidiary or DBA.
- Confirm whether defense costs are inside or outside the limit, and whether contract defense is included.
- Confirm exclusions for AI model outputs, hardware, bodily injury, and professional services you subcontract.
- Confirm the policy satisfies the limit, additional insured, and certificate wording your client contracts require.
- Ask for tail (extended reporting period) pricing before a carrier change or a shutdown.
Typical limits
A $1,000,000 per claim / $1,000,000 aggregate policy is a common starting point for a small software or consulting firm, and $1M / $2M or $1M / $3M is common once enterprise contracts and larger implementations enter the mix. Firms handling payments, healthcare data, or systems that drive client revenue often carry $2M / $4M or higher, sometimes with a separate cyber limit.
Multi-state firms and California
Tech E&O is not written state by state: a firm with staff, contractors, and clients in several states can be covered on one policy with the states scheduled, which keeps one retroactive date and one set of limits. California coverage details are on the California tech E&O guide, and the long-form answer is on the tech E&O Q&A page. Firms that also need lawyers professional liability can compare states on the lawyers by-state hub.
PRIA Brokers (Professional Resource Insurance Agency, LLC), CA License #0G81238, compares A-rated carriers and matches limits to your contracts. Request a quote at /tech-quote or call (888) 998-7742.
Multi-state tech firms and retroactive dates
Short answers on scheduling several states on one policy, why the retroactive date decides so much, and how AI work is treated.
Can one tech E&O policy cover a firm working in several states?
Yes. Technology errors and omissions coverage is not written state by state: one policy can respond to work performed anywhere in the United States, with the states scheduled so underwriting and certificates reflect where the firm actually operates. Tell us every state where employees, contractors, and clients are located, and flag any work performed outside the country, because some carriers exclude it or require an endorsement.
Why does the retroactive date matter so much for tech E&O?
Coverage is claims-made and reported, so a claim must be reported while the policy is in force and the work giving rise to it must fall on or after the retroactive date. Technology claims often arrive a year or more after a project closes, which means a policy bought after the work was delivered may not respond to it at all. Confirm the retroactive date in writing, and ask whether the carrier will honor prior acts back to your first E&O policy.
Do client contracts set my limits, or should I pick my own?
Both. Client contracts set the floor: many enterprise, healthcare, financial services, and public sector agreements name a required limit, additional insured wording, and a certificate before the first invoice. Your own exposure sets the ceiling, because a failed implementation or data error can cost a client far more than the contract's required minimum. Read the largest three contracts, then choose limits that satisfy all of them and still cover a realistic claim.
Is AI work covered under a standard tech E&O policy?
It depends on the form. Many policies cover technology services broadly, but some carriers now attach exclusions or sub-limits for generative AI outputs, model performance, and training data claims. If any part of your revenue comes from AI development, model deployment, or AI-assisted advice, tell the underwriter in the application and confirm in writing how AI-related claims are treated before you bind.
General information, not insurance or legal advice. Client contract requirements and carrier underwriting rules vary and change over time; confirm your own agreements and read the policy wording. Premium figures are indicative and subject to underwriting. Policy language controls.