Three things make this role the one I have been preparing for: the President's-operator structure of the seat, the post-acquisition platform-integration phase InsureOne is in, and the standard personal lines and small commercial wedge where the operating system I have spent twenty years building applies cleanly. The Venn diagram between where I am and where InsureOne is going is unusually tight.
I am an enterprise operator who happens to have started in distribution — not the inverse. At PacificComp under Alleghany and then CopperPoint, I took a $65M book to $311M while moving the combined ratio from over 200% to underwriting profit in 32 months. I was second-in-command to the Regional President of a 700-FTE carrier, running a 250-FTE unit. When our Chief Underwriting Officer was released, I covered Underwriting for 120 days through the leadership transition — running distribution and underwriting in parallel, which is the operating-system integration this seat is structured to deliver.
The JD calls for M&A integration across people, process, technology, and culture. I have done it on all three sides of the deal. Carrier-side, I was retained as a strategic asset through Alleghany's sale to CopperPoint and led the rollover of the Alaska National California book onto PacificComp paper after closing. Agency-side, I have folded acquired retail agencies into a parent platform and integrated cluster groups — ISU, UVIS, PIIB, United Agencies, Combined Agents of America — into a coherent broker-accountability framework. The thread is consistent: protect producer relationships and customer continuity while swapping the operating layer underneath.
The "Strategic Consulting Experience" listed as required in the JD is a qualification most insurance executives do not have. I do. Before insurance I sold enterprise solutions — Y2K, PeopleSoft, business process re-engineering, strategic planning — to Fortune 1000 buyers at Parsons Group and Accenture. Bank of America, Disney, NBC, Avery Dennison, Countrywide, DreamWorks. The buyer was usually a CFO, CIO, or CTO. That cross-functional fluency is the reason I can sit across from a carrier partner, a technology vendor, and our own CFO and operate at the same altitude in three different conversations — which is what the "integration of third-party services that streamline operations and enhance customer experience" line in the JD actually demands.
On AI and automation: I sit on Berkley's AI Committee and am in the Co-Pilot Power User Program. My view is that AI in distribution is an operating-model question, not a technology project, and the right deployment sequence is intake and triage first, then underwriting assist, then customer communications — because the data foundations exist in those zones already. Practical, not theoretical.
Honest acknowledgment, before you have to ask. My career has been commercial — workers' comp, transportation, BOP, GL/Property — not personal lines. Personal auto is a product I would learn from your line leaders in the first sixty days. The operating system around it is the operating system I have built five times. My career arc has been a steady walk toward more compulsory lines; personal auto sits at the end of that arc, not outside it. What I would bring is not personal-lines product expertise on day one. It is the operator who makes your line experts' work scale.
I would welcome a conversation. References, supporting materials, and a 90-day operating plan are available on request, or accessible directly at ronnieodell.com.