Embedded insurance keeps hitting the same wall — is anyone actually solving the data problem?

Working on embedded insurance product development and I want to talk about the specific problem that keeps derailing implementation timelines: insurance data is not structured for real-time consumption.

The embedded insurance pitch is compelling: offer relevant insurance at the point of need, reduce friction, increase attachment rates. The execution keeps breaking down on:

1. Policy data that lives in carrier systems formatted for their own internal use, not for API consumption

2. Coverage verification that requires a human lookup even when it should be automatable

3. Premium calculation that requires back-and-forth with underwriting when it should be instant

4. Claims data that's locked in legacy systems

The companies trying to solve embedded insurance from the consumer side are building on a foundation of sand because the data infrastructure underneath is still 1985.

From what I've seen, the companies that are going to win in embedded insurance long-term are the ones solving the data layer first, not the ones building the prettiest consumer experience on top of broken infrastructure.

Is anyone seeing real solutions to the data layer problem? Or are we all building workarounds?