Your Insurtech Has Been Asked for a Software Escrow Agreement. Now What?
Six months of conversations. Countless product demonstrations. Technical assessments, commercial negotiations and a final presentation to the insurer’s leadership team.
For a growing insurtech company, this could be the contract that changes everything. The platform has impressed the insurer, demonstrated its potential to transform claims processing and opened the door to a significant commercial opportunity.
Then an email arrives from procurement.
Everything looks routine until one line catches the founder’s attention:
“Please confirm that a software escrow agreement can be established as part of the contract.”
The founder reads it again.
Software escrow?
Nobody mentioned that during the demonstrations. It wasn’t part of the original discussions. Now the legal team wants to understand the agreement. The developers are concerned about access to their source code. Meanwhile, everyone is wondering whether this unfamiliar requirement could delay the deal.
It’s an uncomfortable position to be in when you’re trying to secure an important customer.
But why would an insurer ask for software escrow in the first place? What does the agreement actually involve? And does it mean giving someone else access to the technology you’ve worked so hard to develop?
For insurtech businesses encountering software escrow for the first time, understanding these questions can make an unfamiliar process much easier to navigate.
This is an illustrative scenario, but the questions reflect those that can arise when technology providers begin working with larger enterprise customers.
Why Is the Insurer Asking Your Insurtech for Software Escrow?
From the insurtech provider’s perspective, the product works, the technology is secure and the team is committed to supporting its customers. So why does the insurer need additional protection?
The answer is often about dependency. Insurers increasingly rely on external technology for activities such as underwriting, claims processing, fraud detection and customer services. Insurers may also influence how early-stage vendors develop their solutions, particularly through custom development and feature requests. Once the insurer relies on the platform, it also depends on the provider to maintain the software, resolve technical problems and keep the service running.
But what happens if that provider enters administration, withdraws support for a product or becomes unable to maintain its platform? An insurer may already have disaster recovery arrangements for technical incidents and outages, but those plans could still depend on the original software supplier being available to restore the service.
What happens when the supplier itself is no longer there?
That’s the question an insurer may be trying to answer when it requests a software escrow agreement. It isn’t necessarily a reflection of the insurer’s confidence in the provider. It may simply be part of understanding and managing the risks associated with relying on an external technology provider.
What is a software escrow agreement?
A software escrow agreement is a contractual arrangement designed to protect the interests of both the technology provider and the organisation using its software.
It typically involves three parties:
- The depositor: The software provider that owns and develops the technology.
- The beneficiary: The insurer or customer that relies on the software.
- The escrow agent: An independent third party responsible for securely holding agreed software materials.
The provider deposits specified materials with the independent escrow agent, which holds them securely under the terms of the agreement. These might include source code, technical documentation, configuration files and other components required to maintain or recover the application.
The insurer does not automatically receive these materials. Instead, the agreement defines the circumstances in which the customer may request their release.
The agreement calls these circumstances release conditions or trigger events. They might include supplier insolvency, failure to provide agreed support or another clearly defined contractual event. The purpose is to establish a controlled route for the customer to access essential materials if the software provider can no longer fulfil its obligations.
Does this mean giving away your source code?
For an insurtech founder, one of the biggest concerns may be protecting the company’s intellectual property. After all, the technology could represent years of development, significant investment and specialist knowledge, making it one of the business’s most valuable assets.
The idea of depositing source code with a third party can understandably raise questions. Who would have access to it? Could an insurer use or copy the technology? And what safeguards would prevent confidential information from being disclosed unnecessarily?
This is where the terms of a source code escrow agreement become important. The independent escrow agent securely holds the agreed materials, with access controlled by the contract. The insurer does not automatically receive the source code simply because an agreement is in place. If a release is requested, established procedures must be followed, including notifying the software provider and allowing it to challenge the request where the agreement provides for this.
Even if the materials are released, the insurer’s rights to use them remain subject to the agreement. For example, an insurer might be permitted to maintain a critical claims platform following supplier failure, without acquiring ownership of the underlying software or the right to use it for unrelated purposes.
Ultimately, software escrow is designed to balance the insurer’s need for business continuity with the software provider’s need to protect its intellectual property. Both parties should understand and agree on those protections before signing.
What Is SaaS Escrow, and Why Does It Matter for Insurtechs?
Many insurtech platforms today are delivered through Software as a Service (SaaS), with the technology hosted in the cloud rather than installed directly on an insurer’s systems. This brings considerable flexibility, but it also means that keeping a service running can depend on much more than the software itself.
Imagine an insurer using an AI-powered claims platform to assess and process thousands of claims each month. The provider manages everything behind the scenes, from the cloud infrastructure and databases to the integrations connecting the platform with the insurer’s existing systems. As far as the insurer is concerned, the service works, claims are processed and customers receive their decisions.
Now consider what recovering that platform would involve without the original provider.
Even if the insurer could obtain the source code, could another technical team actually get the platform running again? Would they have access to the databases containing the claims information? Could they recreate the cloud environment, reconnect the integrations and restore the AI components needed for the system to function?
This is where traditional source code escrow may not be sufficient. A SaaS escrow agreement can go further by addressing the additional materials and arrangements needed to recover a cloud-hosted application. Depending on the technology and the agreed recovery objectives, these might include:
- Source code and technical documentation
- Deployment scripts and container images
- Database backups and relevant data
- Cloud infrastructure configurations
- Access credentials and integration information
- AI models and supporting components, where required
The important consideration is not simply what can be deposited, but what another team would actually need to restore or maintain the service if the original provider were no longer available.
Of course, having these materials securely stored does not automatically guarantee uninterrupted operations. Successful recovery may also depend on suitable infrastructure, technical expertise, third-party licences and a recovery process that has been properly tested.
For an insurtech company developing a cloud-based platform, understanding these dependencies early can help ensure that any escrow arrangement reflects how the technology works in practice, rather than just protecting a collection of files.
The Five Questions Every Insurtech Should Ask
By this point, a founder might be feeling more reassured about what software escrow involves, but there are still practical details to work through. Before agreeing to anything, it’s worth understanding exactly what the insurer expects and whether those requirements reflect how the platform operates.
Five questions can help guide that conversation:
- What risk is the insurer trying to address?
Is it concerned about insolvency, the withdrawal of technical support or the possibility that a critical service could become unavailable? Understanding the intended protection helps determine what the agreement needs to cover.
- What would we actually need to deposit?
The answer depends on the platform. A traditional software product may have very different recovery requirements from a cloud-hosted application that depends on databases, integrations and specialist infrastructure.
- How will our intellectual property be protected?
Both parties should understand how materials are stored, the circumstances in which they can be released and the permissions granted to the customer following a valid release.
- How will we keep the arrangement up to date?
Technology rarely stands still. Software releases, infrastructure changes and new integrations can quickly make deposited materials outdated. Regular updates and appropriate verification testing can help establish whether the materials remain complete and usable for the intended recovery purpose.
- Who would be responsible for recovery?
If an agreement were triggered, would the insurer have the necessary resources to maintain the platform? Would another developer need to step in? What technical knowledge and infrastructure would be required?
These discussions help establish what is realistic rather than assuming that simply depositing source code provides a complete continuity solution.
Why wait until procurement to have this conversation?
For growing technology businesses, the immediate priorities are often clear: develop the product, attract customers, demonstrate its value and secure investment. Software escrow may not feature prominently in those early discussions, but as the business begins working with larger insurers, questions about operational resilience, third-party dependencies and recoverability may become increasingly relevant.
Understanding the practical steps involved in setting up a software escrow agreement can help technology providers prepare for customer requests before they become part of contract negotiations. It can also prompt useful internal questions about the business’s own technology. Is the technical documentation sufficiently detailed? Are the components essential to operating the platform clearly identified? Could another team maintain the system if necessary?
These questions are valuable even when a customer does not ultimately require software escrow. Not every platform presents the same risks, and not every customer will need the same level of protection. The appropriate arrangements should reflect the technology, the customer’s dependency on it and the recovery outcome both parties want to achieve.
A conversation worth having before the next contract
Let’s return to the founder opening that procurement email. The request for a software escrow agreement doesn’t have to be a last-minute complication. With an understanding of the process, the founder can ask informed questions, involve the right technical and legal colleagues, and discuss what the insurer actually needs.
As insurtech businesses grow and their technology becomes increasingly important to insurers, understanding how to protect those partnerships matters just as much as developing innovative solutions.
For our founder, that unexpected procurement email doesn’t have to be a stumbling block. With the right knowledge, it becomes another conversation they are prepared to have.
After all, the best time to understand what your next major customer might ask for is before the question arrives.