Does Your Canadian SaaS Company Need Tech Errors and Omissions Insurance?

What Is Technology Errors and Omissions Insurance?

Technology errors and omissions insurance is professional liability insurance built for companies that sell software, IT services or data products. It covers the legal defence costs, settlements and judgments that follow a claim that your product or service failed and caused a client financial loss.

You’ll hear it called tech E&O, technology professional liability or tech PL. Same thing. What separates it from the standard errors and omissions policy a consultant or accountant buys is the technology wording. A standard E&O form covers incorrect advice. A tech E&O form also covers a product that doesn’t do what you said it would, or stops doing it.

For a SaaS analytics company, that distinction is the whole point. Your “advice” is a dashboard. Your “service” is a pipeline that runs at 2 a.m. without anyone touching it. If either one is wrong, the client’s loss traces straight back to your code.

One more thing worth knowing up front: tech E&O is written on a claims-made basis. The policy responds to claims made while it’s in force, usually for work done after a retroactive date. Let it lapse, or switch carriers without carrying that date forward, and work you shipped two years ago can become uninsured. Your broker should handle this. Make sure they do.

Why Doesn’t General Liability Cover Software Mistakes?

Because Commercial General Liability (CGL) Insurance covers bodily injury and property damage, and a wrong number on a dashboard is neither. That’s the short version, and it’s the one that catches most tech companies off guard.

CGL Insurance is still worth having. It’s what responds when a client visits your office and trips over a cable, or when your laptop bag knocks a monitor off a desk at their site. Landlords and co-working spaces ask for it. Some contracts do too.

But CGL policies carry a professional services exclusion. Any claim that stems from the work you’re actually paid for – the software, the analysis, the implementation – is carved out. Most also exclude damage to electronic data outright, so even the “property damage” argument falls apart when the thing damaged is a database.

Put plainly: if the claim is about what your product did, CGL isn’t the policy that answers. Tech E&O is.

What Does Tech E&O Cover for a SaaS Analytics Company?

Tech E&O covers claims that your software, data or services caused a client to lose money. For an analytics or SaaS business, that typically includes:

• Errors in the product. A bug, a broken query or a bad data transform that produces wrong outputs the client relies on.
• Failure to perform. The platform goes down, the integration breaks or a feature you sold doesn’t work as promised.
• Missed deadlines and failure to deliver. An implementation, migration or custom build that lands late and costs the client.
• Negligence in professional services. Incorrect advice from your solutions team, a misconfigured deployment, an onboarding mistake.
• Misrepresentation. A claim that your sales deck, SLA or documentation promised something the product didn’t do.
• Breach of contract (services). Alleged failure to meet the service obligations in your MSA or SOW.
• Intellectual property infringement. Most tech E&O forms cover copyright, trademark and trade-dress claims tied to your software. Patent infringement is usually excluded, so ask.
• Legal defence costs. Often the biggest number. Lawyers, experts, discovery, court – covered from the first dollar on most Canadian tech E&O forms, whether or not you did anything wrong.

Many Canadian insurers write tech E&O on a combined form that bundles cyber liability in, or offer it as an add-on. More on that below, because it’s the single most common place SaaS companies end up under-covered.

What Doesn’t Tech E&O Insurance Cover?

Tech E&O won’t pay for a data breach, bodily injury, property damage or anything you did on purpose. The gaps that matter most for SaaS companies:

• Data breaches and ransomware. That’s cyber liability. A combined tech E&O and cyber policy closes this gap; a standalone tech E&O form does not.
• Bodily injury and property damage. CGL territory.
• Intentional or dishonest acts. Fraud, deliberate misrepresentation, knowingly shipping something broken.
• Disputes over unpaid fees. A client refusing to pay your invoice isn’t a covered claim, even if they dress it up as a complaint about the product.
• Guarantees of results. If you promised a client “20% lift in conversions” and they didn’t get it, most policies won’t treat the shortfall itself as a loss. The negligence behind it, maybe. The guaranteed number, no.
• Contractual penalties beyond legal liability. Liquidated damages and SLA credits you agreed to pay regardless of fault are typically excluded.
• Patent infringement. Almost always excluded or sublimited. If you’re in a patent-heavy space, raise it with your broker.
• Claims you knew about before buying the policy. Prior-known matters are out.
• Employment and partnership disputes. Separate coverages entirely.

None of these are reasons to skip tech E&O. They’re reasons to pair it correctly.

Tech E&O vs Cyber Liability vs. General Liability: Which Policy Pays?

Tech E&O responds when your product fails. Cyber liability responds when your data is attacked or exposed. General liability responds when someone gets hurt or something physical gets broken. Most SaaS companies need all three, and the mistake is assuming any one of them does the job of the others.

* — Canada’s privacy law requires you to report a breach of security safeguards to the Office of the Privacy Commissioner and notify affected individuals whenever there’s a real risk of significant harm. The notification, forensics and credit-monitoring costs that follow are cyber claims, not E&O claims. If your platform stores client customer data, you want both policies.

When Does a SaaS Company Need Tech E&O?

The honest answer is the day you invoice your first customer. The practical answer is that one of these six moments usually forces the decision:

1. A client contract asks for it. The most common trigger by a mile. Enterprise MSAs, vendor onboarding packages and government RFPs routinely require $1 million to $5 million in professional liability, with a certificate of insurance before signature. Procurement doesn’t negotiate this. You either have it or you lose the deal.
2. You move upmarket. Selling to a 20-person agency is one thing. Selling to a bank, a hospital network or a public company means their losses from your bug are bigger, and their lawyers are better.
3. You add services. Onboarding, implementation, custom dashboards, data migrations, managed analytics. The moment humans at your company are doing work for a specific client, professional negligence becomes a live exposure.
4. You sell into the United States. American clients litigate more, and damages run higher. Make sure your policy’s territory and jurisdiction wording covers U.S. claims, not just Canadian ones. Not all do by default.
5. You raise money or add a board. Investors and directors ask what happens if a customer sues. “Nothing’s in place” is a bad answer in a diligence room.
6. Your product makes decisions. Predictive models, automated reporting, anything a client acts on without a human checking. The more your software replaces judgment, the more a wrong output costs someone.

If you’ve got paying customers, you can’t wait.

How Much Tech E&O Coverage Do You Need, and What Does It Cost in Canada?

Most Canadian SaaS companies carry $1 million or $2 million in tech E&O coverage, and a basic policy starts at a few hundred dollars a year. Enterprise contracts push both numbers up.

Choosing a limit. Start with whatever your biggest client contract requires, because that number is non-negotiable. Then think about the worst realistic outcome of a bug: what would your largest client lose if your product were wrong for a month? That’s the floor. $1 million is the entry point and satisfies a lot of mid-market contracts. $2 million is the comfortable default for a company with real revenue. $5 million shows up in bank, healthcare, telecom and government contracts, and it’s cheaper to carry than to scramble for mid-deal.

What it costs. A small-business E&O policy in Canada averages roughly $500 a year. Tech E&O for a SaaS company with revenue, enterprise clients and cyber bundled in lands higher, because the exposure is bigger. What moves your premium:

• Annual revenue. The biggest factor. More revenue, more clients, more exposure.
• What you sell, and to whom. Analytics for a fintech or a hospital network costs more to insure than analytics for a retailer.
• Services mix. Pure self-serve SaaS is cheaper than SaaS plus implementation and consulting.
• Limits and deductible. $2 million costs more than $1 million; a $5,000 deductible costs less than a $1,000 one.
• Where your clients are. U.S. revenue raises the rate.
• Your contracts. Clean MSAs with limitation-of-liability clauses and clear SLAs make underwriters happy.
• Claims history and security posture. No claims plus a SOC 2 or ISO 27001 report helps, especially on the cyber side.

The only way to get a real number is to get a free quote. It takes a few minutes online, and you don’t have to buy anything to see it.

Frequently Asked Questions About Tech E&O Insurance in Canada

Is tech E&O the same as professional liability insurance?

Tech E&O is professional liability insurance written for technology companies. It covers everything a standard professional liability policy does (negligence, errors, incorrect advice) and adds coverage for technology products that fail to perform. If you sell software, ask for the tech form specifically.

Does tech E&O insurance cover data breaches?

No. Data breaches, ransomware and privacy violations are covered by cyber liability insurance. Many Canadian insurers bundle tech E&O and cyber into one policy for software companies, which is usually the simplest way to close both gaps.

Do I need tech E&O if I already have general liability insurance?

Yes. General liability covers bodily injury and property damage, and it excludes claims arising from your professional services or technology products. A client suing you because your software gave them bad data is a tech E&O claim, and a CGL policy won’t respond to it.

Is tech E&O insurance required by law in Canada?

No. There’s no law requiring software companies to carry it. In practice, client contracts require it constantly – most enterprise MSAs, vendor onboarding processes and government RFPs call for $1 million to $5 million in professional liability coverage before you can sign.

How much tech E&O coverage does a SaaS company need?

Most carry $1 million or $2 million. Your largest client contract sets the minimum, and contracts with banks, healthcare organizations and governments often require $5 million. When in doubt, match the highest limit any current or near-term contract asks for.

What does “claims-made” mean on a tech E&O policy?

It means the policy covers claims made against you while the policy is active, for work done after the policy’s retroactive date. If you cancel the policy, claims that arrive later for older work won’t be covered unless you buy an extended reporting period. When you switch insurers, make sure the new policy carries your original retroactive date forward.

Can a startup or solo founder get tech E&O insurance?

Yes. Tech E&O is available to companies of any size, including pre-revenue startups and sole proprietors. Premiums scale with revenue, so an early-stage company typically pays at the low end of the range.

How to Get Tech E&O Insurance for Your SaaS Company

Getting tech E&O takes a few minutes online. Zensurance partners with more than 50 Canadian insurers, so instead of filling out one application per carrier, you fill out one application and compare quotes built for technology businesses.

A few things to have handy before you start:

• Last year’s revenue and this year’s projection
• A one-line description of what your product does and who buys it
• Any contract that spells out a required limit (bring the exact wording – it matters)
• Whether you store client data, and roughly how much
• Where your customers are: Canada only, or U.S. and beyond

What you’ll get back is a tech E&O quote, usually with cyber liability and general liability priced alongside it so you can see the full picture, not just one piece of it. Pick what fits. Bind it online. Your certificate of insurance is ready to be sent to procurement often the same day.