(Dan Wood, CEO, Socotra. Photo by author.)
Socotra (Austin) CEO Dan Woods views innovation in insurance as less about invention than about removing friction. “Insurance doesn’t need innovation,” he says. “It just needs to catch up.” The statement, at once provocative and pragmatic, reflects his conviction that the industry’s persistent lag behind other sectors stems from cultural and structural inertia more than technical impossibility.
Woods’ career began far outside insurance. A computer scientist by training, he was the 20th employee at data-integration and intelligence-software company Palantir Technologies (Denver), where he helped design and deploy data platforms for demanding clients across intelligence, defense, and industry. “At Palantir we built something remarkable,” he recalls. “We saw what smart people using best practices could do compared to what was generally available to a lot of industries.”
When he turned his attention to insurance, Woods was startled by the contrast. “I came out of computer science and Palantir—I understand how you build quality software,” he says. “And I thought, if four kids in a dorm room can build a photo-sharing app that doesn’t go down for upgrades and publishes its APIs, why can’t the best software companies serving an industry that represents nearly ten percent of GDP do the same?”
Progress, Friction, and Functional Conservatism
Woods acknowledges that some of the industry’s idiosyncrasies serve a legitimate purpose. “Nobody wants to be the first to use anything in this industry,” he notes. “But I’m not convinced that’s a bad thing. This is the industry that’s supposed to work when everything else falls apart. That’s what it’s there for. I think it’s built in for a reason.”
At the same time, that conservatism often morphs into friction that stifles progress. “They’re very reluctant to trust an evaluation of software,” Woods says. “They just want to know—‘Can i talk to someone like me who’s done it?’ And I don’t blame them. It’s hard to evaluate until you’re using it. And very rarely, if ever, does an insurer actually know their full requirements before they start the IT project.”
That uncertainty fuels a kind of structural defensiveness. “Their question is, not only will the software meet all my needs, but will it meet all the needs I haven’t thought of yet? That’s impossible to answer,” Woods says. “But if I know someone else who’s using it, worst case, I can solve it however they did.”
Misused Language and the Illusion of Progress
Woods says the industry’s slow progress is compounded by imprecise language and marketing spin. “The misinformation is staggering,” he remarks. “People install legacy software on AWS and just say it’s cloud. Then they call it cloud-native. You’re dealing with a thirty-year-old company saying it’s on their cloud-native platform, and no one minds.”
He sees similar confusion around configuration and implementation. “Configuration means zero change to the code,” Woods says. “It’s been misused—so many terms have been misused. When vendors say out-of-the-box, it means they did it once with something that vaguely resembles you.”
That misuse of language, he argues, perpetuates a false sense of innovation. “Historically, there’s been a lot of pandering over customization,” he continues. “Insurers are actually hungry to be told no, because they’ve been told yes by too many system integrators for too long.”
The result is an industry spending billions on the illusion of due diligence. “We’ve had customers who have used software you can imagine—spent over a billion,” Woods says. “Most of it goes to the systems integrator, not the vendor.” He describes a cycle that often repeats across large carriers: “A mainframe-bound insurer decides it needs a new system. So, they call a management consultant, who recommends a systems integrator. The integrator looks at an analyst report, picks the top five options, and runs an RFP. Then they throw out the weakest response, take the cheapest one, and use it to bargain against the rest. And they call that due diligence. Of course that’s not all the time, but it’s not uncommon.”
Woods believes this pattern is finally breaking down. “People are starting to get fired for it,” he says. “That’s sad, but it’s also good—it means delivery and results matter again.”
A Path toward Parity
For Woods, insurance’s technological lag isn’t destiny—it’s an opportunity for parity. “Look at banking, which is maybe ten years behind advertising or entertainment,” he says. “Then property and casualty insurance lags banking by another ten years, and life insurance lags that by ten more. It’s just technology arbitrage. Let’s do what grown-up software companies do—productize, keep everyone on the same version, and continually upgrade.”
That principle defines Socotra’s architecture: a single, continuously updated platform that eliminates version fragmentation. “No one asks what version of Gmail you’re running,” Woods notes. “It’s just Gmail. Every now and then your browser refreshes, and that was an upgrade. We’ve had that figured out for a while, and Socotra has brought that to insurance.”
He sums up the challenge and the promise succinctly: “It’s not rocket science—it’s just growing up.”
Mutual of Omaha Expands Digital Modernization on Socotra Platform
Socotra Names Amazon Alumna Sonny Patel Chief Product & Technology Officer
