ITC Vegas.
Assistants recommend. Co-deciders decide.
Shoaib Mohammad and Rohit Nagpal on the floor at Mandalay Bay for the largest gathering in insurance technology, for three days of meetings on one question: who keeps accountability when software closes the decision.
The hardest case in the queue
The invitation was deliberately awkward: bring the file that sits in the queue because nobody wants to own the call, not a clean one. We showed the decision in minutes, with the reasoning attached and the policy line it was decided under.
One workflow
Forty minutes, walked against your own underwriting manual rather than a demo script built on somebody else’s data.
Live, not piloted
LEO, the Life Insurance Underwriter, has run in production for over a year at a top life carrier — around eight minutes from intake to an issued decision, and 75 to 80 percent of the book cleared with no underwriter touch.
Who widens it
Less about the model, more about the mandate: who sets the boundary, who can widen it, and what the log looks like when an examiner asks for it.
On the floor at Mandalay Bay
Shoaib Mohammad
Thirteen years building only for financial services, the most recent of them spent on what it takes for an institution to let software close a decision rather than hand one back.
Rohit Nagpal
Runs LUMIQ’s North America business out of Dallas, which puts him on the question US carriers are working through right now: who signs off on the decision.
The forty minutes still stands
The conversation does not need a conference. Bring the workflow you would staff first and we will come back with the shape of the mandate, the oversight settings, and what the first ninety days look like.