At Versured I was the product manager for a Salesforce-based agency management system: the place where insurance sales teams sold, tracked, and wrote policies. I owned it from discovery through rollout, where it became the system of record for two sales orgs and a partnerships team.
Insurance selling is a two-system job. Reps work their deals in one place, but policies actually get written in carrier-side systems reached through IVANS, the industry's central policy-writing exchange. Every handoff between those worlds was a swivel-chair step: duplicated data entry, records that disagreed, and no single place where a sales leader could see the truth of the book.
The partnerships team made it harder still: a third group writing business alongside two sales organizations, each needing visibility into the same customers without stepping on each other's records.
I owned the product end to end: discovery with the people selling every day, the roadmap, and the requirements. I managed delivery through a team of developers and Salesforce architects who built to those specs. Classic PM seat: I didn't write the code; I decided what got built, in what order, and what "done" meant.
Rather than adopt a vertical AMS, we built on the platform the sales teams already lived in: policy data as native objects next to pipeline, with Salesforce's reporting, permissions, and admin surface for free.
I designed the integration architecture connecting the platform to IVANS so reps and partners could write policies without leaving their system of record, removing the swivel-chair step that caused the data drift.
Two sales organizations and a partnerships team sold and wrote policies on the platform as their system of record.
This project is where my systems-of-record obsession began: the conviction that the highest-leverage product work in B2B is making the system people already live in do the whole job. Years later, the same conviction produced the AI operators for the GTM stack: different technology, same product thesis.