top of page
Logo Negro Transparente.png
  • LinkedIn
  • Youtube

Why embedded insurance can become a new layer of value, but should not become an operational burden

Updated: 10 hours ago

Why embedded insurance can become a new layer of value, but should not become an operational burden

Vertical SaaS companies are in a unique position. They do not only sell software. They sit inside the daily operating flow of specific industries: construction, logistics, field services, healthcare, property management, mobility, commerce, restaurants, professional services, or manufacturing.


That means they see what others do not. They see assets, jobs, payments, bookings, deliveries, incidents, employees, vendors, customers, usage frequency, and risk patterns. That information turns Vertical SaaS into a natural channel for embedded insurance.


BCG points out that vertical software is often used daily by SMEs, creating a highly efficient channel for embedded financial products through contextual messaging and targeting strategies. BCG also notes that SME adoption of vertical software in the U.S. reached 59% in 2024, compared with 50% two years earlier. [1] a16z has made a similar point from the SaaS monetization angle: vertical software companies can expand into financial services, including insurance, when they own transaction data that can improve underwriting and product relevance. [2]


But there is a major difference between having risk context and operating insurance.

The risk is already inside the workflow


Construction software may know when a project starts, which contractors are involved, which assets are on site, and which operational milestones exist. A logistics SaaS may know what is moving, when, by whom, and under which conditions. A field service system may know visits, equipment, technicians, routes, and incident frequency.


That context is valuable because it allows protection to be offered at the right moment. Not as a generic policy, but as coverage connected to a real activity.


Gangkhar summarizes this logic clearly in its Vertical SaaS use case: when a platform sits at the center of jobs, assets, payments, subscriptions, field operations, or service delivery, risk is already present inside the software. [3]


The opportunity is clear: turn that operational context into relevant protection, additional revenue, and greater customer value.



The first friction: the SaaS company does not want to become an insurer


The issue is that a SaaS company does not want to operate as a carrier, broker, MGA, claims administrator, or compliance department. It wants to add value to its product, improve retention, increase ARPU, and solve a real customer pain point.


That creates the first tension: insurance can be strategic, but it can also bring legal complexity, additional support, customer questions, claims management, experience conflicts, data processing obligations, and third-party dependency.


Stripe’s guide to digital embedded insurance recommends starting with the risk, choosing products that address a clear transaction-specific exposure, and selecting partners with API-first capabilities, regulatory coverage, and strong claims operations. [4]


This recommendation is especially relevant for Vertical SaaS: if insurance does not improve the core operation, it becomes noise.

The second friction: compliance and distribution


A Vertical SaaS company may be tempted to present protection as just another feature. Legally, it is not always that simple.


Depending on the market, the SaaS provider may need to limit its role to referral, operate under an authorized model, work with regulated intermediaries, or ensure that disclosures and consents are properly integrated. It must also define who answers questions, who collects payment, who issues the policy, who cancels it, who manages claims, and who retains documentation.


This matters because the user does not distinguish between “the platform” and “the insurer.” If something fails, trust breaks with the software.

The third friction: claims and support


For Vertical SaaS, claims are the most sensitive point. If the user buys protection inside the software and then has to move into a manual, slow, or disconnected process, the experience deteriorates.


The challenge is that the claim should connect with the operational data the SaaS already has: event, date, asset, user, transaction, location, documents, and status. This can reduce friction and improve traceability, but it requires real integration between policy systems, claims systems, and the platform.


Accenture identifies speed to settlement as a key driver of customer satisfaction in claims. For a Vertical SaaS company, this has a direct implication: embedded insurance cannot be designed only up to the sale. It must be designed all the way to resolution. [5]


The fourth friction: profitability and unit economics


Embedded insurance can create a new revenue line. But if implemented poorly, it can affect conversion, support, churn, or brand perception.


The question is not only “how much revenue does it generate?” The more precise questions are:

  • Does it improve margin per customer?

  • Does it increase retention?

  • Does it reduce operational friction?

  • Does it solve a frequent problem?

  • Is it activated at the right moment?

  • Does it keep the experience simple?

  • Does the insurance partner respond well?

  • Are claims manageable?

  • Does the data allow the program to improve?


In Vertical SaaS, the insurance product must align with the workflow. It can be protection by project, asset, trip, delivery, job, subscription, user, or event. But it should never feel like an external sale.


The fifth friction: truly implementable AI


AI can help with segmentation, pricing adjustment, message optimization, behavioral pattern detection, and attachment rate improvement. But it should not be used as an abstract promise.


In insurance, AI must be explainable, monitored, and governed. The NAIC has established expectations for insurers around AI governance, documentation, oversight, and compliance with applicable insurance laws. [6]


EIOPA has also published guidance on AI governance and risk management for the insurance sector, reinforcing that AI systems must be supervised and aligned with sector-specific requirements. [7]


For Vertical SaaS, this means AI cannot operate as an opaque layer. It must run on permitted data, with clear objectives, technical boundaries, traceability, and performance visibility.

The sixth friction: security and trust


Vertical SaaS platforms already manage sensitive operational data. Adding insurance introduces additional data flows: user identity, transactions, assets, risk signals, policy records, claims documentation, payment status, and potentially health, mobility, property, or business information depending on the vertical.


IBM reports that the global average cost of a data breach in 2025 was approximately USD 4.44 million. [8] For Vertical SaaS companies, this reinforces a simple point: embedded insurance cannot compromise trust in the core platform.


Security, privacy, permissions, data minimization, logging, and third-party controls must be part of the embedded insurance model from day one.



Where Gangkhar fits


Gangkhar enables a Vertical SaaS platform to turn its operational context into embedded protection without taking on the full burden of operating insurance.


Its Vertical SaaS use case positions Gangkhar as a way for software platforms to turn operational context into embedded protection that is relevant, scalable, and commercially viable. [9]


Gangkhar’s broader Sherpa+ Platform includes Sherpa+, Sherpa+Lens, and Sherpa+Engage, designed to support embedded insurance infrastructure, real-time optimization, and digital platform integration globally. [10]


The proposal is not that Vertical SaaS companies should “sell insurance.” The proposal is more strategic: they can use embedded protection to solve real risks inside their vertical, create a new layer of value, and strengthen customer relationships without becoming insurance companies.


Sources

[3] Gangkhar — Vertical SaaS Case

[9] Gangkhar — Vertical SaaS Case[

10] Gangkhar — Sherpa+ Platform



Embedded insurance is no longer just a distribution opportunity. It is becoming an infrastructure challenge.

Insurers, MGAs, capacity providers, and digital platforms need to launch faster, operate with stronger compliance, connect claims, protect data, and optimize performance continuously. That requires more than another API. It requires a scalable operating layer built for the real complexity of embedded protection.

Gangkhar helps organizations turn embedded insurance into a repeatable, measurable, and global capability — connecting capacity, compliance, pricing, claims, data, and AI-powered optimization through one infrastructure layer.

Climb Higher. Protect Smarter.


To explore how Gangkhar can help your organization launch and scale embedded protection, contact us at info@gangkhar.com.


Comments

bottom of page