Loresse / Reading list

From legacy to AI-native.

What an AI-native claims administrator and an established insurance business reveal about changing the way work gets done.

Loresse AI · October 2026 · Annotated reading

Archival claim files branching into connected charcoal channels and copper threads

The distinction

Two paths to a new operating model.

“AI-native” can describe two very different journeys. A new company can design its processes, systems, and roles together from the beginning. An established enterprise must change live operations while carrying the responsibilities, data, and relationships it already has.

Reserv is the first kind of story: a newer third-party claims administrator built around a modern operating model. It is not an old TPA that converted itself. Acrisure is the more direct example of an incumbent trying to reshape core insurance workflows rather than attach AI to a separate innovation program.

The selected reporting below is a starting point for understanding that difference. It includes company statements, interviews, and industry coverage; none proves that every workflow or outcome described has been independently validated.

The Loresse view

The work is the point.

What makes this shift interesting is not the label. It is whether knowledge from experienced people becomes part of a connected, reviewable process: from the first record through the exception, decision, and handoff.

Our reading is that an AI-native operation should make specialist judgment more available and more accountable, not simply automate whichever task is easiest. That is Loresse’s interpretation of these stories, not a claim of endorsement or a measured outcome for Loresse.

Original reporting

Follow the story at its source.

These articles remain with their original publishers. The notes are brief Loresse summaries, not reproductions or endorsements.

The AI-native entrant

The incumbent's transition

Start a conversation