Ben: Chris, thank you so much for coming onto the podcast. A little bit of context. Chris Longano: Thank you, Ben. Appreciate it. Ben: A little bit of context. I think the topic that has been on the top of all of my founders' friends' minds in the intro tech space is what's going to happen to SaaS. I think some of the old assumptions we had about. cost being shared across everyone, but everyone kind of getting a slightly worse product as a result, because SaaS is kind of always trying to find the common denominator and can't customize all the way to the end. But those assumptions might be falling. So I'd love to talk to someone about this who has been in the insure tech space and has been working on SaaS for the last better half of a decade, right? Do you want to maybe start off with just an introduction of who you are and what steps you had in that journey. Chris Longano: sure. yeah, and thanks for having me on here. so I spent, you know, I cut my teeth in the insurance industry of Verisk Analytics, filling in multiple roles, but spent a lot of time demoing XML data so that SaaS companies could actually ingest and inherit that verisk material natively. so that's a pretty interesting story there. And then you know, dunk both my feet into the water. Sold for a SaaS company for for two years, moved back in the data space for a bit, then worked for Socotra, which was kind of a pioneering company at the time, going trying to go for a headless SaaS product. and then you know, bounced around a little bit, was a founding CRO at a payments platform, built a SaaS product in the bordereaux space, and now now I'm here at Rhoads working with their product. Ben: Amazing. Let's start with the headless world. It was almost like a perfect expression of the last generation's thesis that cloud native, configurable APIs, continuous upgrades, true SaaS five years ago that sounded like the destination. What do you think has changed? Chris Longano: you know, it it's funny. In this industry, I feel like things are always cyclical and and we go through these patterns of DIY versus buy, you know, do I build it myself, do I buy it? There's also patterns of do I buy it all from one vendor, do I, do I do best to breed? so there's kind of multiple, you know, waves of patterns here. So I think with the advent of AI becoming so what's the expression? Yeah, ubiquitous now, I guess. Yeah, Ben: Ubiquitous? Chris Longano: we're all learning on the job. that that DIY trend is is heavy right now, right? Everyone thinks that them and a claw license are gonna get them everything that vendors for thirty years have been trying to build and and just can't accomplish. So I think there's a just a lot of that. And we're on a certainly a big swing of like we can build it ourselves with nothing but, you know, some elbow grease and claude. Ben: Yeah, I guess the question is a bit, if you can put an AI agent on top of these systems, write Chris Longano: Mm. Ben: integrations dramatically faster, customize workflows yourself, how much less valuable does the configurability become? Chris Longano: Yeah. Well, I you know, at least the the thesis back at Socotra, not to laud them too too much here, but Ben: You Chris Longano: something I certainly got behind was this idea of like it's the functionality that's important, not the visual or the workflows or the the things that companies are going to want to customize, right? You cannot one size fits all in this industry, despite the fact that a homeowner's writer is a homeowner's writer is a homeowner's writer, they're all gonna want something different. So To be a company like Socotra and say, you know what, we're true meaning of API first, where that's what the focus is, and it's less about what the what the look is, what the UI and UX feel is. Let's just give a web developer the tool set to basically build their own policy admin system effectively, right? Ben: Yep. Chris Longano: I think that dream is still very real, but I think our industry is a little bit slow. It it's hard to paint a picture to people. You know, we're human beings. We like to see it, feel it, and touch it. So When you're selling headless, you're just selling a hope and a dream and then somebody's gotta come up with with that creative spark. Ben: Yeah, and in theory, if you have the right sort of schema behind what you're selling headlessly, that could then be used much more efficiently also by AI agents, or do you, you don't think that's true? Chris Longano: Yeah, one would think. Yeah. I haven't experienced with that. and going back even before Socotra company I worked with, Clarion Door, we built our whole platform on web services. So even our own UIs, we would say if you don't like them, just build your own. All the functionalities here. But I would think I've not experimented myself, but to your point, I would think with the advent of AI here, you should be able to give them that web developer's toolkit and say, Here's what I want to do from point A to point B Go create the workflow for me or the UI experience that that I want. And that could really accelerate you know, that that build now. Ben: For sure. think one of the... things that these types of headless companies also desire to stay away from, is the sort of customization each of the customers they would otherwise need to do. And so I'm not too familiar with how Socotra did it, although I do know some sort of development shops and services companies, right, that partnered with them because they would then provide the Chris Longano: Exactly. Ben: professional services on that end. I'm just wondering whether you think that is likely to change, like the fact that, you know, maybe with AI professional services also becomes more interesting. Chris Longano: You know, I actually spoke to a professional services company that was starting up as a full fledged AI professional service. So what they were really selling is we'll take we'll put the requirement stock together with you so that we're building what you want, but there wasn't an actual coder behind the scenes. They were just going to leverage whether it was Claude or whatever AI model they were going Ben: Anyway, yeah. Chris Longano: to use to actually create the professional service that they were then selling. Which Ben: So interesting. Chris Longano: Makes you wonder at what point does these AI companies start getting royalties off of all the products and services that get built on Ben: Yep. And then not just that, but also what point does a large company that's buying professional services and realizing that like 95 % of the output is generated by AI would not want to in-house it, right? Chris Longano: But how many, you know, ten years ago it was okay, if you want to build it yourself, are you really attracting the best and brightest software engineers to come work for, you know, something mutual insurance company out of Wisconsin that writes in four states? Or likely not, right? Those biggest and brightest minds at the time anyway were going to Facebook or Meta or Google or Amazon. So I think the same is still true here. It's like who's going to really attract those prompt engineers or the people Ben: the talent. Chris Longano: that work with or the engineers that are really capable of working with AI, it's probably not going to be the insurance company, right? And that's the sad reality is the the people we're hiring are probably going to be the B players and C players of the world. Those A players are going to be somewhere else making twice as much money, right? Ben: Talent remains a problem and maybe even a bigger one in the age of AI. Chris Longano: It's it's unfortunate. AI almost makes us all feel like we have the talent. but you know Ben: Moving on to I had written down you went to Noldo afterwards, right, which was Chris Longano: Correct, yeah. So Noldor wasn't a policy admin play. They were a SaaS play. but we were fully serviced in-house. So we built our own software to service our clients effectively. which I think at least traditionally is the most successful way to be in the insurance industry as a vendor. Like you need to do your own implementations in order to find success with your customers. but man, we came up against the wave of, well, can't I just build an AI model to do this? instead. So I you know, I think the jury's out on that, but it was certainly a good use case to explore whether or not AI was capable. Again, it just becomes do you now want to manage all that infrastructure that's had to be built with AI going forward? And who are you paying to do that? So I think The vendor community still has a great opportunity to say, Hey, we're we're doing the things you would otherwise do in house, but we're going to manage that on your behalf. So you don't have to hire a team of three to four to five, six, however many engineers to make it happen. Ben: Yeah, I'd love to drill deeper on that. think that's kind of to your point, jumping ahead a little bit. Before we go down that road, can you just explain the value prop of Noldor once again? Chris Longano: so Noldor's focus is on border reporting. So basically the data that's coming out of these policy admin systems and have to get into the hands of usually it's a you know, a Lloyd syndicate or a reinsurance company or coming from the MGA to go to the carrier. So very heavily focused in the program space where systems aren't really communicating together. Ben: And was from the beginning, was AI a factor in making this reporting possible? Chris Longano: AI was a at least when I was there, was an idea on the roadmap, but wasn't quite in play yet. So we were still trying to build the railroad system, so to speak, before we let the AI agents run wild. Right around the time I was leaving, we started incorporating more artificial intelligence to effectively do what a business analyst would otherwise accomplish. Ben: And the plan was to integrate into policy admin systems to pull out automatically reports that would be needed for like capacity reporting border. Chris Longano: Yeah, I mean the hope and the dream was that it was a system to system connector, right? So it was just a Ben: Mm-hmm. Chris Longano: policy admin to policy admin translator, effectively. But Ben: Mmm. Chris Longano: the insurance world being what it is, and certainly the program space and Bordero world being what it is, it was a lot of taking data out and putting it into spreadsheets or taking data from spreadsheets and putting it into a system. So that true system to system connection, I think we only had one well, two clients that were actually doing that where we were Ripping out data from a SQL database and then pushing it into the carrier's data warehouse. Ben: And how do you see that particular space changing when the chief digital officer who has four or five different programs on three different policy admin systems now knows that, you know, through AI software development, they could get things done in-house, own them, right? Ideally a lot cheaper, presuming that they have the talent, which is, you know, the point we made before. Chris Longano: Sure. Yeah, I mean, my my sales pitch, at least at the time, was always, you know, if you can manage it with one to two people, good for you. And keep going, you're never gonna get it done cheaper, right? But the minute you had to hire that third person or that fourth person, or it started to become a full time hire, there you know, now you have to manage someone's career. And is that really what you got into the insurance business to do is manage a agentic AI engineer's career, right? But some people would answer yes. That's exactly what we want to do. Then hey, great. Congrats. Call us if you have problems, you know? Ben: Yeah, I think the... What I quite like and what I'm hearing more and more is sort of this switch from solution-based selling to outcome-based selling, right? Which is before with in the SaaS world, it's like you have a problem. I might have one of the solutions, but presumably to get to the outcome that you want, there will be a few more things that you will need to do. But I can provide like a really meaningful way to get there. And nowadays we've just gone even further because if I'm just a part, if I'm just, you know, one of the building blocks and there's still a lot of work that needs to be done, then that's a lot. less compelling than let's say, you know, if I can get you to the outcome that you desire. And in, you know, in the end, if it ends up being a sort of an outsourced shop that does a lot of manual work for you, but using AI and maybe gets to the outcome much faster and maybe more cost effective than you would yourself. That's, that's probably still quite a good proposition, right? Chris Longano: Yeah, I I that's an interesting way to look at. I never thought about it as outcome, but I would say, you know, and I'm gonna call him out here, but Joe Emerson, the CTO at branch insurance, I think has probably someone you should talk to. a lot of great philosophies around branch and the technology stack he uses there. But one of his big things when I was working with him a decade ago was Control the things that are most important to you as a company, right? So if that's the customer experience, if that's the internal experience, if that's the data flow, right? We want to control the data flow. Those are the things you want to invest the the human energy into and the wherewithal the knowledge base internally, but vend out those things that can really be, you know, cut and paste type of options, right? And that's where web services and and the whole now AI play really comes in. Can you have AI automate the things that We really just don't need a hu we don't care about that experience as much as what comes out of that AI engine. Now we suddenly care about that experience more. So I I don't know if that I guess that's the same thing you were saying. I mean to your original premise of the show, right? How does SaaS change? I think that's the SaaS community really needs to look at itself and say, is the user experience we're creating really that valuable or is it the functionality behind that user experience that people care most about? Ben: But yeah, your current company, Rhoads, has software, managed services, and now an AI assistant. Is that combination closer to what an insurtech company is going to look like going forward, you think? Chris Longano: I think everyone's gotta use the letters AI in order to have a have a seat at the table these days. I don't know. Ben: How much longer? How much longer? Do you think we'll just have AI in the next 20 years? Chris Longano: I'm surprised you're asking me. I thought you were a guy who was like, it's gonna be now here and forever. you know, I think I think to your point, my hope is that people start focusing more on the outcome and not the thing that's being done, right? If you went back ten years, API was the AI of the day. Everyone had its talk about how they're APIs and they have APIs and it's API first, API first, right? So that was the thing. If you weren't using those letters, you were somehow old fashioned and I think AI is just that new wave of you know, some companies have mandates where they have to start incorporating AI. So if they're going to look at different vendors and one vendor says they use it, the other one says they don't, you know, who are they gonna pick? They want to be on the cutting edge, so they're gonna select the one. So I think everyone has to use it to some extent, but again, focus on the outcome. It's not that you're using AI. What are you doing with it that's giving your customer some kind of added lift and added benefit? you know, not to give away the whole farm here of what we're trying to accomplish with roads, but you know, we see a world in the future where the the whole broker and claim adjuster licensing and appointment, onboarding schedule can be a completely to use an old term, headless process where, you know, folks can be interacting with text messaging. to their system versus logging onto their their laptops, pulling up a screen and clicking a few buttons to make sure Ben is licensed. It could be a simple text to, you know, we call our AI assistant Regina. So a simple text to Regina saying, hey, make sure Ben gets his renewal done in the next 60 days. Boom. And then that's happening. Or a Gentic AI looking at your behaviors and saying, hey, it looks like you, you know, you try to get renewal notices out. a hundred days in advance instead of ninety. So we're gonna tweak our workflows to make sure that we're doing that in advance you, right? So it's more about making the the the hero, right? The person at your company more capable so that they don't have to worry as much and there's not as much on their plate and their to do list starts to get a little bit less and they can focus more strategically on on what you're trying to do, right? as I say it's like I see AI as like if you could hire four junior assistants tomorrow, what would you have them do so you didn't have to do certain aspects of your job? Ben: Yeah, that makes sense. think the... what I kind of witness in the... startup space or in the ensure tech space more generally is that they're sort of the companies that have predated the AI wave and then those that have just been founded based on the premise that AI can revolutionize a lot and they're sort of, they can more persuasively call themselves AI native and things like that. Where would you place Rhoads in that dichotomy? And then I guess how much has Rhoads changed since they started because of this AI transformation? Chris Longano: Yeah, I would say Rhoads is in the process of change right now. so Rhoads is a twenty year old company, kind of the best of all worlds, that's been privately owned for the lion's share of their existence. So they were able to grow at a very steady and controllable clip. You know, there wasn't this was before the VC days where just millions of dollars were being pumped into firms to try and do 10x growth. so we're in a unique spot where we're in a part of the industry that's very, very niche. there's not a ton of competitors out there, but there are certainly plenty of competitors. But the scope of what we do is very limited. So, you know, we have an opportunity to actually lead the charge here a little bit and take the success we've had with the knowledge we have on how our customers, what our customers need to do every day, and start to incorporate AI into that knowledge base already, right? We're not starting from green field here where we're guessing at things. We have a lot of historical asset and knowledge base to to make these changes happen. But I would say we're very much in the beginning phases of of the change that is to come. Ben: And when you think of your customers and what they require from Rhoads, how has that changed in the last two years? Chris Longano: I I haven't been at Rhoads for two years, but I can I can guess at this one. I I Ben: Okay, sure. Chris Longano: would say connectivity. you know, this part of the industry, the compliance part, has been very we set you up with your desktop application and there's one one to five people at the insurance company that are logging in and being your primary end users. What we're seeing now is again the wave that a lot of people felt ten, fifteen years ago, and that's hey, I want these other pieces of software, right? These other workflows to now communicate into that compliance realm. And so Ben: Hmm Chris Longano: I would say in the compliance space we're only now catching up to like fifteen years ago when systems wanted to start talking to each other more easily. Ben: Yeah, I'm almost wondering whether it's not just the connectivity between systems, but also the way in which more and more folks use ChatGPT Claude, almost as their primary interface to interact with the different systems that they use underneath the hood. And what's great is that Chris Longano: Yeah. Ben: both Claude and ChatGPT are enabled to do that browser based, right? So there's actually, you can actually get quite far even without having a real MCP connector built. But ultimately I think the expectation will be that, you know, I can now draft 40 outreach emails just from the command line and I can then go through them and send them one by one, make tweaks. can even allow my AI agent to custom change them to send things out. And if that becomes a more standardized way to interact with technology, the faster all the existing companies get there, Presumably the competitive. Chris Longano: Yeah. Yeah, so it's really for us it's turning what was traditionally a back office, you know, somebody better be doing this and we only care when something goes wrong type of department into a hey, now we're front and center through the rest of the insurance operations because this information is now more accessible. And then through the use of AIs, can we start to automate or anticipate some of the needs there a little bit more in advance? Ben: Yeah, that makes sense. Can you shed some light on the business model? So is Rhoads also like a, did it have a SaaS approach where you sort of charge one licensing fee? Is it more in the professional services space already? Like, cause, cause I'd be curious to know how that may be evolving as well. Chris Longano: I think Rhoads is a Ben: She's a show. Chris Longano: perfect example of any vendor that came to life in the, you know, mid aughts to late aughts where you had a SaaS platform, but you had some customers said, We don't even have people to use your SaaS platform. We want to buy it, but we don't have people to use it. So we spun up a managed services realm and then People said, Hey, Ben: interesting. Chris Longano: this is good, but can it do this one other thing? So you build that one other thing. And then they said, Well, that one other thing is cool. Can you build another thing? And so I think Rhoads is a very good example of how a a product gets kind of piecemealed and built as you go. And so now you end up 20 years later with what looks like an a la carte menu of all these different services and teams of people and various places that can do those services for you. so you know, part of what we're looking at now is how do we how do we just simplify that, modernize the packaging of all those things. And is it really a product are these things a product or just a feature that was added ten years ago that we called a product? Ben: interesting because i i also think that there's a There's merit to an argument that goes in the following way, which is 20 years ago, if you're an IT consultancy, you you build a product, you then build managed services and all of that stuff piles on. You're not that interesting for a 10 X investor, right? You're not as interesting Chris Longano: Correct. Ben: for a VC because it, well, a few different reasons, right? Focus, but also the fact that it's much harder to grow 10 X if you don't, you know, if you don't have one thing that is clearly differentiated and you're sort of trying to swim in a lot of different lanes. And now I'm wondering all almost as if that logic has also flipped. one of reasons I'm wondering that, I don't know whether you saw the announcement of Corgi, right, where they just launched a reinsurer. And I think a couple of days before that, they had launched a claims adjuster and then Corgi had also launched an ETF portfolio and Corgi had also launched a coffee shop. you know, it's almost like they very quickly, obviously they have a lot of funding, but they very quickly are diversifying. And whether that logic gets flipped on its head when the software component itself is no longer limiting factor, right? Because one of the reasons Chris Longano: Hmm. Ben: I believe that venture capitalists were not that interested in having someone who does a lot of things is because they want all the software energy that the company has to be focused Chris Longano: Right. Ben: specifically into this one thing to differentiate it from everyone else. Like Stripe is going to do payments, you know, Chris Longano: Correct. Exactly. Ben: but if, if software is no longer the limiting factor, in fact, even, know, Joshu the company I'm working with, we have noticed that software development has just accelerated like crazy and it means that we get to things on the roadmap that previously we didn't think we might even ever get to, right? Chris Longano: if software is not the factor. I'll give like a total you know, non-answer answer to that, I guess. I I think then it becomes more around corporate focus, right? And less about the software engineering focus, right? So sure, you could say, hey, we want all of our engineering energy made on making this one thing awesome, but there's a very different approach corporately from the CEO level on down to how you manage a company that is in one part of one industry that's doing one thing really, really well. To a company like Averisk Analytics that's doing literally everything possible for a particular industry or multiple industries. so I think that's the challenge, is it becomes more of a corporate focus? How do we actively sell into those things and market into those things and operate in those places? software, to your point, is not the limiting factor, but maybe marketing talent is, maybe you Ben: Yeah. Chris Longano: know, human resource talent is. I mean, it's it's just a very different company to run. Ben: 100 % and so clearly Corgi will also have these bottlenecks that will need to solve it might just not be software related I find interesting Chris Longano: do you comprehensively address multiple industries as a company called Corgi, you know, I mean what worked in one industry isn't gonna maybe work in another. You know, you can be a good software development firm, but maybe a terrible coffee shop or vice versa. So how do you Ben: Exactly. Chris Longano: you know, you're effectively running multiple companies within a company, but to your point, it's not the software that's limiting you. Ben: for sure. And then I guess my final point that I'd love to get your take on is... how that influences, not the build versus biodynamics, we already talked about that at the insurance company, for example. They're not going to invest a lot of tokens now and resources into managing their own compliance software, presumably, and they might even be happy that they have managed services they can go to who do this way more cost effectively than them. I guess the question becomes partnerships, right? Because historically, you would have a lot of companies that are adjacent. In the Chris Longano: Mm-hmm. Ben: policy admin space, have payments companies that are adjacent, or you might have reporting plays, right? And now if software is no longer the limiting factor and someone asks for this new functionality for which you may have partnered otherwise and you may have added, you know, particular software vendors to your portfolio of offerings, you may start thinking twice about that and build certain things in-house that you would have maybe otherwise gone external for beforehand. Chris Longano: But again, to bring it maybe full circle here, again, control what's important to you. What are the outcomes that are important? And is it that user experience? If so, that's where things like AI can very quickly help you adapt a user interface or something to interact with those headless models. So to me, partnerships become more of like an OEM strategy, if anything else, where someone's doing something behind the scenes and there's there's an SLA behind it, but The customer experience can be as controlled or not controlled by you as you want. Ben: Chris, thank you so much for joining the podcast. yeah, actually. Chris Longano: Ben this was fun. I appreciate you, man. Thank you. Ben: Have a good one.