FIELD NOTE 03 / HOW THE PRODUCT GETS USED
From closed apps to governed AI-extensible platforms
If the customer’s AI cannot build with your product, it may build around it.DIRECT ANSWER
The short version
An AI-extensible insurance platform exposes governed capabilities that customer-owned agents can discover, invoke, and combine. Beneath the screen are APIs, connectors, permissions, durable data models, tests, approvals, and audit trails. The customer can assemble a specific workflow without rebuilding the reliable core or giving an agent uncontrolled production access.What changes
The application is no longer the only meaningful interface. A customer may begin inside Claude, Codex, an enterprise copilot, or an internal agent. Product strategy therefore includes whether those systems can understand the platform’s actions and safely compose them into customer-specific work.
What does not
Governance remains non-negotiable. Permissions, testing, human review, approvals, observability, and audit records define what an agent may do. Extensibility is not permissionless code generation inside production systems.
An insurance example
A carrier’s internal agent reads appetite, checks policy data, prepares a quote draft, and routes an exception to an underwriter. It invokes controlled platform actions rather than scraping a screen. The underwriter retains authority, and every action remains reviewable.
The Season 2 question
Season 2 asks which capabilities agents should reach, who governs them, and whether closed products become a detour that customer intelligence learns to route around.