SEASON 2 / FIELD GUIDE
Post-SaaS insurtech
Software is not disappearing. Its old bargain is.THE SHORT ANSWER
What does InsurePodcast mean by Post-SaaS insurtech?
Post-SaaS insurtech is not the end of software subscriptions. It is a change in the bargain between technology company and customer. Vendors take responsibility for more completed work, charge through a mix of access and activity, and expose governed capabilities that customer-owned AI can extend. The reliable core stays shared. The differentiated edge becomes easier to build.What changes
Responsibility moves closer to the vendor. Revenue moves closer to the work. The product becomes a set of governed capabilities that people, systems, and agents can invoke—not only an application they log into.
What does not
Software still matters. So do security, permissions, audit trails, integrations, and production reliability. Insurance remains regulated, exception-heavy, and dependent on judgment. Post-SaaS changes the commercial and product boundary; it does not abolish the hard parts.
An insurance example
A submission platform once gave an underwriting team a configurable inbox. In the emerging model, it ingests the documents, resolves missing fields, applies the carrier’s rules, records every step, and delivers a review-ready file. The underwriter still makes the underwriting decision. The platform completes more of the work before that decision.
The Season 2 question
Season 2 tests this working thesis with founders, insurers, brokers, operators, engineers, and investors. Who owns the outcome? Where does the revenue move? Can the customer’s AI build with the product? Where should standardization end?
FOUR FIELD NOTES
Follow the argument one boundary at a time.
From software access to completed work
The vendor’s job ends later.
Read the field note →02 / HOW VALUE GETS CAPTUREDThe license survives. It no longer carries the whole business.
Seats once approximated value. Software that performs work breaks that approximation.
Read the field note →03 / HOW THE PRODUCT GETS USEDFrom closed apps to governed AI-extensible platforms
If the customer’s AI cannot build with your product, it may build around it.
Read the field note →04 / WHERE STANDARDIZATION ENDSBuy the core. Build the edge.
Share what must be reliable. Own what makes the operation different.
Read the field note →