A closer look at the reasoning behind Cazimir and Brooks Energy, and the underwriting problem that started it all.
Gennaro Brooks-Church
Founder, Cazimir & Brooks Energy
Most AI vendors in insurance start with a technology and go looking for a place to use it. Gennaro Brooks-Church started somewhere else, with a question he kept hearing from underwriters directly: what happens to everything we know once we're gone?
That question shaped the two companies he leads. Cazimir focuses on submission intake and the knowledge underwriters build while processing it. Brooks Energy is where he applies the same thinking more broadly, to any operational problem where AI risks flattening expertise instead of protecting it. Notes on both projects, along with longer essays, are kept on his writing portfolio, and a running log of releases sits on his technical site.
None of these are unique on their own. Held together, they explain why his systems tend to get adopted rather than quietly abandoned.
Gennaro Brooks-Church spends time inside a team's actual submission process before designing anything, tracking where reviewers hesitate, double-check, or go back to a source document.
Every fix an underwriter makes gets fed back into the system. Over months, this is what lets a Cazimir deployment start to resemble the specific habits of the team using it.
Every extracted figure links back to its source page. Gennaro Brooks-Church has said plainly that he doesn't expect underwriters to trust a system they can't check.
Rather than handing new clients a manual, he works through the first configuration with them directly, tuning the system to their brokers and formats from day one.
Insurance teams are being asked to do more with fewer experienced people.Gennaro Brooks-Church, Founder, Cazimir & Brooks Energy
Gennaro Brooks-Church doesn't describe Cazimir as a finished product, and says he doesn't expect to. As underwriting practices shift and new formats of submission data appear, he sees the work as ongoing calibration rather than a single launch. He keeps an active log of what he's testing and reading on his mailing list, and manages client work for both companies through a shared operations workspace.
If there's a single thread through all of it, it's this: the industry doesn't need less experience, it needs better ways to hold on to the experience it already has.
Get in Touch