Cover sold inside another purchase — how it works, who carries the risk, why it converts, and where the model has real limits.
Embedded insurance is cover sold inside the purchase it protects: the policy offered at the moment you buy the car, book the trip, or onboard the employee — not on an insurance website afterwards. The definition is one sentence. The implications for who sells insurance, who profits from it, and how customers experience it are much bigger.
The short answer
In an embedded model, three roles that used to live in one company get split. A licensed insurer underwrites the policy and carries the risk. A distribution platform — a marketplace, a bank, an HR system, an airline — offers the policy inside its own product. And an infrastructure layer in between (this is where Yasmina sits) connects the two: quoting, compliance, policy issuance, and the revenue accounting that pays the platform its share.
The customer never meets this machinery. They see one extra card in a checkout they already trust, priced against the exact thing they are buying, purchasable in a tap.
Why the model exists
Insurance has always been sold at the point of need when someone could manage it — travel agents sold travel cover, dealerships sold motor policies, appliance stores sold warranties. What changed is scale and precision. Digital checkouts know exactly what is being bought, by whom, and when — which means the quote can be exact rather than approximate, and the offer can arrive at the one moment the customer's intent is certain.
The economics follow the moment. Standalone insurance brands pay heavily to acquire customers who mostly ignore them; platforms already own the transaction and the trust. Analysts have put numbers on the shift: Conning projects US property and casualty premiums sold through embedded channels to reach roughly $70 billion by 2030, and widely-cited industry estimates place the global embedded opportunity in the hundreds of billions of dollars over the same horizon.
Who does what — and who carries the risk
The most common misunderstanding is that platforms selling embedded insurance "become insurers." They do not, and in regulated markets they legally cannot without a license.
- The insurer files the product, sets the price, holds the premium, pays the claims and answers to the regulator for solvency.
- The platform distributes: it surfaces the offer, passes the customer's data (with consent) to pre-fill the quote, and collects payment inside its own checkout.
- The infrastructure layer holds the regulatory permissions for distribution, routes each sale to the underwriting insurer, issues documents instantly, and accounts for the platform's revenue share.
This separation is what makes the model fast to adopt. A platform integrating embedded insurance takes on a product decision and an engineering task — not an insurance license, premium float, or claims liability.
What embedded insurance is not
Honest limits matter more in insurance than in most industries.
- It is not a fit for complex, advice-heavy products. Life insurance with underwriting questionnaires, bespoke commercial programmes and high-value specialty risks still need human advice. Embedded works where the product is standard and the context supplies the data.
- It is not a growth hack for a broken product. A policy with slow claims or weak coverage does not improve because it was sold at checkout; it just disappoints faster.
- It is not unregulated. Distribution rules, disclosure duties and cooling-off rights apply exactly as they do in any other channel — the infrastructure layer's job is to make compliance automatic, not optional.
Where it works today
Motor is the global beachhead: mandatory cover, data-rich transactions, instant issuance. Travel attaches at visa application and booking. Device and appliance protection ships inside electronics checkouts. Health and SME medical attach where employment data already lives. Gig platforms embed per-shift accident cover. The pattern across every category is the same: the transaction already contains the data the quote needs, and the customer's intent is already settled.
Questions to ask before you embed
- Does our transaction naturally imply an insurable need — or would the offer feel bolted on?
- Do we hold the data that pre-fills the quote, and can we pass it lawfully?
- Who is licensed for distribution in our market — us, or the infrastructure we integrate?
- What does the claims experience look like, and who does the customer call?
- How is our revenue share calculated, reported and paid — and can our finance team audit it?
If those five questions have good answers, embedded insurance stops being a trend to watch and becomes a product line to run. For how the Saudi market specifically regulates this model, see our guide to Insurance Authority approval; for what the economics look like in practice, our partners' revenue-share models are documented across this blog.