Insurance for systems integrators, built around the statement of work.
Your liability lives in the project documents: the statement of work, the milestones, the acceptance criteria. When a go-live fails, the client reads those documents back to you. We build integrator insurance programs around them.
Projects, not products.
An integrator's risk is project-shaped. The system does not do what the statement of work said it would do, the go-live fails, the client's business is disrupted, and the claim follows the project plan line by line. The question is never abstract. It is whether the deliverable met the document.
Then there is time. Implementations run late, and contracts increasingly price the delay: delay damages, liquidated damages, termination rights that trigger on missed milestones. An honest word about delay claims: they test the edges of most E&O wordings. This is exactly the line we review before anything is placed, not after a claim arrives.
And there are the people doing the work. Subcontractors on your engagements create vicarious exposure: their mistake on your project is your liability to the client. The program has to contemplate the work performed under your contract, whoever performs it.
Meanwhile you spend long hours inside client environments with access to their systems and data, which brings the same cyber and E&O overlap every services firm carries.
Coverage mapped to how an integrator operates.
- Technology Errors & Omissions: the core of the program. Responds when a client alleges that your implementation work, advice, or project delivery caused them financial loss: the failed go-live, the deliverable that missed the specification. Financial loss from professional services; not bodily injury or property damage. Delay and liquidated damages get specific attention in the wording review.
- Commercial General Liability: for the physical side of project work: third-party bodily injury and property damage, including long engagements on client premises. The honest limit stands: CGL typically excludes electronic data.
- Cyber Liability: for the access the work requires. Policies can include breach response and forensics, notification, and third-party claims when client data you touched is compromised, plus network-interruption income loss and cyber extortion.
- Umbrella / Excess Liability: large projects and enterprise clients demand higher limits than a base program provides. Excess layers add limits above the primary policies.
The right program is built from your contracts and your operations. Coverage is defined by the actual policy wording, not by this page.
Bring the statement of work.
The fastest way to the right program is to start from the project documents: the SOW, the milestones, the acceptance criteria, the delay provisions, the subcontractor arrangements. We read them with you and build the program around what they actually obligate you to.
Client procurement will ask for E&O and cyber at stated limits before the project starts. We make sure the certificates match the contract.
Start with a conversation.
Integrator programs are built from project documents, and documents need discussion. Bring the statement of work, or just bring the story of the project. A short conversation gets the program right.
Working in more than one of these areas?
Many technology companies do. Each segment page describes the exposure from that side of the business:
MSPs · SaaS & Software · Cybersecurity Firms & MSSPs · Cloud & Hosting · VARs
Or start from the full picture: who we insure and the coverages we place.