INSUREPODCAST / SEASON 2

What happens to SaaS
when AI can do
more of the work?

Season 2: Post-SaaS Insurtech

An open inquiry into what AI changes and what it doesn’t.

InsurePodcast brings together SaaS founders, insurance leaders, engineers, investors, and AI builders to examine how AI may change what software delivers, how value is measured, and how people and AI work with reliable platforms.

For the people building, buying, and shaping insurance technology.

A WORKING DEFINITION

What is Post-SaaS insurtech?

“Post-SaaS Insurtech” is InsurePodcast’s working term, not a verdict on SaaS. Shared software is deeply embedded in insurance today. The open question is what AI changes, what it leaves intact, and how product boundaries may move when customer-specific layers become easier to build.

What stays shared, and what becomes easier to adapt?Read the field guide

SEASON 2 / THE OPEN QUESTION

What changes, and what endures?

SaaS solved an important economic problem.

The question is what AI changes, what it leaves intact, and what that means for SaaS.

THE SAAS FOUNDATIONA reliable shared productCommon infrastructure spreads cost across many customers.

THE EMERGING POSSIBILITYAn adaptable customer layerAI makes differentiated workflows easier to build.

Traditional SaaS pooled the cost of building and maintaining one product across many customers.

Customers accepted standardization because bespoke software was dramatically more expensive.

AI may lower the relative cost of customer-specific workflows, interfaces, integrations, and logic.

Keep the reliable foundation.Reconsider the boundary around it.

SEASON 2 / THREE QUESTIONS TO TEST

What software delivers.
How value is measured.
How AI uses the product.

01 / 03WHAT THE PRODUCT DOES

From software access to more completed work

SaaS gives customers powerful tools. As AI expands what those tools can do, some vendors are taking responsibility for more of the surrounding workflow.

That might mean preparing a submission, triaging a risk, or assembling a review-ready file. It does not mean removing insurance judgment or forcing every contract toward outcome pricing. Season 2 asks where product responsibility should begin and end, and what a credible handoff looks like.

The tool remains valuable. The boundary of responsibility may move.

How much of the workflow should the product own?

02 / 03HOW VALUE IS MEASURED

From seats alone to broader measures of value

Seats and subscriptions give vendors and buyers useful predictability. As software performs more work, they may explain only part of the value being created.

Some companies will remain license-led. Others may combine access with usage, transactions, workflow volume, managed operations, engineering capacity, or agreed outcomes. Season 2 examines how founders and buyers balance alignment, simplicity, and cost certainty.

The license can remain, joined by other ways to measure value.

What should pricing measure when people are no longer the only users?

03 / 03HOW AI USES THE PRODUCT

From application interfaces to governed AI extensibility

Customers may increasingly use software through AI systems as well as through the application itself.

That makes APIs, connectors, tools, permissions, testing, review, and auditability part of product strategy. The application remains important; governed AI access becomes another interface to the product. Season 2 asks what model providers, application companies, and customers should each control.

The opportunity is governed access, not uncontrolled production changes.

What should AI be able to discover, invoke, and extend under appropriate permissions?

01 / 0302 / 0303 / 03

CURRENT MODELCapability access

POLICY WORKFLOW / ADMIN

Submission workflowDRAFT

CONFIGURATION12 required fields

USER SEATS24 assigned

INTEGRATIONS3 pending

IMPLEMENTATION62% complete

Map fields Train team Configure rules

CONFIGUREINTEGRATETRAINSTAFFOPERATEMEASURE

WORK COMPLETED✓

1,240submissions processedConfigured · integrated · operated · measured

POSSIBLE MODELCompleted work

How much of the workflow should the product own?

What should pricing measure as the work changes?

How should AI interact with the platforms insurers rely on?

Post-SaaS is a working lens for three changing boundaries: responsibility, economics, and access.

SEASON 2 / FIELD GUIDE

Explore the working thesis.

Four concise notes define the working thesis, its limits, and the objections Season 2 needs to test.

01 / WHAT THE PRODUCT DOESFrom software access to more completed work 02 / HOW VALUE IS MEASUREDFrom seats alone to broader measures of value 03 / HOW AI USES THE PRODUCTFrom application interfaces to governed AI extensibility 04 / WHERE STANDARDIZATION ENDSBuy the core. Build the edge.

WHY INSURANCE

Insurance is a
demanding test case

Insurers share core needs for security, permissions, audit trails, transactions, and reliability. They differ in products, underwriting rules, forms, jurisdictions, workflows, and claims practices.

WHAT CAN BE SHARED

Transactions
Security
Audit trails
Permissions
Documents
Integrations
Regulatory controls
Production reliability

WHAT REMAINS DIFFERENT

Products
Underwriting appetite
Authority
Rating logic
Forms
Jurisdictions
Workflows
Distribution models
Claims philosophies

Insurance makes the trade-offs between shared infrastructure, customer-specific work, and human judgment impossible to hide.

It is a useful place to ask what should stay standardized, what should adapt, and what AI should be trusted to do.

THE THESIS / DIRECT ANSWERS

The useful version, without the slogan.

Does Post-SaaS mean SaaS disappears?: Post-SaaS does not assume an answer. Security, permissions, integrations, auditability, data, and production reliability make shared infrastructure valuable today. Season 2 asks how those advantages may change, along with the product boundary around them.
How does AI change insurtech pricing?: When AI performs work previously performed by licensed users, seats may explain less of the value. Pricing can spread across platform access, usage, transactions, completed workflows, engineering capacity, managed operations, and outcomes.
What is an AI-extensible insurance platform?: Software whose capabilities can be discovered and invoked through governed APIs, connectors, tools, and documentation. Permissions, testing, review, approval, and audit trails govern their use.
Why is insurance a useful test market?: Insurance requires common infrastructure but highly specific products, underwriting rules, forms, jurisdictions, workflows, distribution models, and claims practices. That favors a reliable shared core with differentiated layers built around it.

INSUREPODCAST / SEASON 2

A working thesis,
tested in public

InsurePodcast brings together SaaS founders, insurers, operators, engineers, AI researchers, and investors who bring first-hand evidence and different answers.

The aim is to test what remains durable, what AI genuinely changes, and where the difficult product, economic, and governance decisions now sit. The strongest guest may support the thesis, complicate it, or overturn it.