I've been convening senior practitioners in embedded insurance for long enough to notice when a room shifts. Not in the direction of the conversations--we've been covering the same structural questions for years--but in the quality of the answers. My London conference this year felt different. More candid. Less performative. The gap between what people say on stage and what they actually believe seems to be narrowing, and that, in itself, is a signal worth unpacking.
Here is what I took away:
The industry's real scaling problem is organizational, not technical
We have been telling ourselves for years that legacy technology is the primary obstacle to scaling embedded insurance. I no longer believe that. The technology solutions are broadly available. The market is well-supplied with capable enablers. What consistently breaks down is the internal will and mandate to treat embedded insurance as a genuine strategic priority rather than a distribution experiment.
The organizations that have scaled are not, on average, better resourced or more technologically advanced than those that haven't. They tend to have one thing in common: someone at the top who decided this mattered and organized accordingly. That means cross-functional accountability, not departmental delegation. It means a mandate to build repeatable infrastructure - the second and third partnership must be structurally easier than the first, or you haven't scaled, you've just shipped.
The debate around core systems transformation is a useful proxy for this. The question isn't really whether to fix the core first or build around it. The question is whether your organization has the internal clarity to make that call and act on it consistently across geographies and business units. Most don't, not because of technical constraints, but because embedded insurance still lacks the internal political capital to force alignment.
Three debates, one underlying argument
We structured several sessions as explicit point-counterpoint debates this year, on branding, on value architecture, and on the vertical versus horizontal scaling question. I find structured disagreement useful because it forces articulation of positions that practitioners might otherwise hedge in polite company. What I didn't fully anticipate was how consistently all three debates would reveal the same underlying argument, approached from different angles.
Visible brand or white label?
The branding debate is one the industry has been having for a decade, usually with the same result: it depends. But the London conversation surfaced something I found more useful than the standard answer: a sharper articulation of what the choice actually turns on.
The case for invisibility is not primarily about aesthetics or customer experience. It is a claim about where trust already lives. Large platforms with deep customer relationships, in logistics, in financial services, in retail, have earned a form of trust that an insurer, however well-branded, has not earned in that context. Embedding insurance invisibly within that relationship is not concealment; it is recognition of where the trust actually resides. The moment-of-truth argument is compelling: at the point of claim, the customer wants the problem solved. The entity that solves it fastest earns the relationship. Brand attribution at that moment is secondary.
The counter-argument is a different kind of claim about trust, not contextual trust but category trust. Insurance is a promise, and promises benefit from a recognizable guarantor. Insurers invest substantially in brand precisely because recognition carries its own form of reassurance in a category where the customer is being asked to pay now for a commitment that may not be called upon for years. Invisibility, in this argument, is not neutral; it progressively commoditizes the underwriting capacity and exerts structural downward pressure on pricing.
What I found most honest about this debate was the convergence point: neither position is universally correct, and the most sophisticated operators are not choosing between them. They are managing both simultaneously, calibrating by geography, product complexity and the relative trust equity of the parties. In certain markets, the platform brand is the primary trust anchor and the insurer's presence is genuinely better invisible. In others, where the insurer brand carries regulatory or reputational weight that the platform does not, visibility is a feature, not an intrusion. The practical implication is that embedded insurance partnerships need to settle the branding question explicitly by market, not as a default, and that any insurer agreeing to white-label terms without a market-by-market rationale is leaving value on the table.
Ecosystem-led or asset-led?
This was the debate I found most intellectually generative, partly because the two positions reflect genuinely different theories of where value in embedded insurance ultimately concentrates.
The ecosystem argument is essentially a claim about adaptability. In a market characterized by real-time data, API-enabled partnerships and rapidly shifting customer preferences, the ability to orchestrate components quickly, to assemble and reassemble the proposition as conditions evolve, is worth more than ownership of any single asset. Speed, in this framing, is not a source of risk but of resilience. A system that can continuously adapt is more durable than one that must wait for static underwriting cycles to catch up with events.
The asset-led argument is a claim about accountability. Banks and asset owners possess something that ecosystem orchestrators do not: a long-term relationship with the customer, built on financial trust, that is transferred to the insurance experience at the moment it matters most. The moment of claim is not the moment customers turn to the orchestrator. It is the moment they turn to the institution that has stood behind their financial life. That equity is real, and it cannot be replicated by a platform that routes transactions without bearing the underlying relationship.
The debate converged on an important practical point about IT security and integration complexity that I think is underweighted in most ecosystem discussions. Multi-party governance in highly regulated financial institutions is not a solvable engineering problem, it is a political and institutional problem that consistently moves slower than the technology. The ecosystem model's promise of rapid reconfiguration depends on all parties agreeing on a common API and governance framework in real time. That is feasible in a well-designed bilateral partnership; it becomes significantly harder at genuine ecosystem scale, particularly when participants include regulated entities with differing risk appetites and compliance timelines.
My read: the most enduring embedded insurance businesses will be those that have asset-level accountability - genuine ownership of the claims moment and the data loop - delivered through ecosystem-grade infrastructure. The two are not in opposition; they describe different layers of the same value proposition.
Vertical specialization or horizontal scale?
The final debate of the day was, I think, the one with the longest strategic half-life for the industry, and the one where I have the most personal conviction.
The verticality argument is intuitive and largely correct on its own terms. Deep specialization in a specific customer segment or risk context produces richer data, higher-intent customer journeys, better conversion and superior retention. The economics are real. An insurer embedded at the precise moment a logistics operator is managing a freight shipment, or a small business is hiring a new employee or issuing an invoice, is operating with intent and context that a general distribution channel cannot replicate.
But the counter-argument challenged something more fundamental: whether the insurance industry's definition of specialization is actually fit for purpose in a modern market context. The most successful companies globally are not vertically organized in the traditional sense. They specialize in a core capability that is simultaneously deep and wide - a logistics system, an operating system - and they extend that capability into strategic adjacencies rather than optimizing a narrowly defined vertical silo. The insurance industry, by organizing itself around vertical customer segments, may be limiting its own conception of the serviceable market.
The synthesis I found most useful, and the one I've been turning over since the event, is that the question may be structurally misconceived. The genuinely admired companies didn't choose between vertical depth and horizontal reach; they went impossibly deep on a core capability and impossibly wide with it simultaneously. The real question for the insurance industry is whether it can build the internal capability to do both, or whether the attempt to do both results in doing neither well.
There is a second, more uncomfortable implication buried in this debate. Vertical specialists enjoy genuine advantages in acquisition cost, customer intent and alignment with the carrier's risk appetite, but those advantages may erode rapidly when a horizontal platform with an existing customer relationship enters the same niche. Owning the customer relationship and serving the customer well are different capabilities. Vertical players build the latter but must continuously work to defend or acquire the former. In a world where platform scale is increasingly available to non-insurance brands, that defense is getting harder.
Data governance is the new product
Across every conversation in London, mobility, bancassurance, ecosystem architecture, AI readiness, the same underlying tension surfaced: data is available in abundance, but governance over who owns it, who benefits from it, and how it flows back into operations remains immature.
This isn't a compliance problem. It's a value architecture problem. The organizations that will disproportionately capture value in embedded insurance over the next five years are those that treat data governance not as a legal prerequisite but as a strategic asset — something to be actively designed, not reluctantly managed. That means closing the loop from claims back into operations. It means structuring partnerships so that behavioral signals flow in both directions. And it means being willing to share data-derived value with distribution partners in ways that create genuine alignment, not just transactional capacity contracts.
The bancassurance discussions were particularly instructive here. The genuinely new element in modern bancassurance is not the channel or the product, it is the serious, structured effort to join banking and insurance data to build propensity models at a level of granularity that wasn't previously feasible. The organizations making that work are not those with the richest data sets; they are those that have been willing to rethink their operating model around the customer journey rather than the product portfolio.
The industry has made progress on building data capability. It has made far less progress on building data culture.
The claims moment is still the only one that counts
Every debate we had in London about branding, about partnership architecture, about whether the insurer should be visible or invisible, about who owns the customer, all of it ultimately collapsed into the same point: none of it matters as much as what happens when something goes wrong.
This isn't a new observation. But what struck me in London was how consistently senior practitioners, across very different organizational contexts and strategic philosophies, returned to it independently. The embedded insurance models that have genuinely earned customer trust are those where the claim experience was treated as a design problem from day one, not a delivery problem to be solved at first incident. The ones that haven't are the ones where the partnership was structured around acquisition and the operational commitments were underspecified.
For practitioners building or renegotiating embedded partnerships right now: if the claims journey hasn't been explicitly co-designed and agreed upon before signing, the partnership is incomplete. Distribution agreements without claims governance are a liability.
Agentic AI is not a future scenario, it is a current design constraint
The London conversation about AI agents and autonomous commerce was the one that generated the most visible discomfort in the room — not because the topic was unfamiliar, but because the timeline was more compressed than many had assumed. We are not talking about a three- to five-year horizon for the first wave of agentic distribution. We are already in it.
My read of where this leaves embedded insurance practitioners is straightforward. The architectural decisions being made today — about API design, product modularity, data standards, and underwriting velocity — are simultaneously decisions about AI readiness. Carriers whose products cannot be parsed and quoted by an AI agent are already invisible to the fastest-growing distribution channel. That is not a future risk; it is a current condition.
The more interesting question is not whether to prepare for agentic distribution but how to build governance structures capable of operating within it — licensing accountability when agents transact autonomously, identity verification when the buyer is not human, and underwriting velocity measured in milliseconds rather than minutes. These are not technology problems. They are regulatory, organizational and commercial design problems that the industry has not yet seriously engaged with.
Where this leaves me
After seven years of convening this community, I remain struck by how much intellectual honesty there is in the room when conditions are right for it — and how much of the industry's public discourse still lags behind what its most thoughtful practitioners actually believe.
London confirmed several things for me. The embedded insurance market is maturing, but unevenly. The organizations that will define it over the next decade are already distinguishable — not by their technology stack or their partnership roster, but by their organizational clarity and their willingness to treat data, governance and claims as strategic imperatives rather than operational overhead.
