Main Topic: The conversation revolves around the challenges of implementing technology in the insurance industry, particularly in agencies, and how to overcome these challenges to create a more efficient and effective business process.
Key Points:
Participants:
Takeaways:
Became a Master of the Close: https://masteroftheclose.com
Unlock the secrets to balancing the human touch with high-tech efficiency in our latest podcast, featuring a renowned insurance industry expert, Margeaux Giles.
✅ Join the Insurance Growth Masterclass: https://masterclass.insure
✅ For daily insights and ideas on peak performance: https://www.instagram.com/ryan_hanley/
✅ Hire me to speak at your next event: https://ryanhanley.com/speaking
Connect with Margeaux Giles
✅ Margeaux's LinkedIn: https://www.linkedin.com/in/margogiles/
✅ Website: https://iryscloud.com/
Their insights illuminate the delicate dance of automation—where too much can alienate clients, but just the right amount enhances interactions and frees agents to do what they do best: connect.
We grapple with the realities of over-automation, advocating for an approach that prioritizes personal connections by relegating the mundane to machines, thus enabling agents to elevate the customer experience with their expertise and empathy.
The conversation shifts to the transformation of commercial insurance placement, where artificial intelligence meets the seasoned agent's wisdom.
Our guest's profound knowledge sheds light on the symbiosis of tech and human experience, revolutionizing policy placement and market analysis. We examine the challenges of training newcomers in the field, the potential of AI chatbots for internal data management, and the pressing need to overhaul legacy systems.
All this is juxtaposed with the realities of technology adoption within the workforce—how it can either spur growth or stifle it, depending on how closely it aligns with both employees' expectations and the company's strategic goals.
Finally, we wrap up with reflections on fostering a progressive work environment in an era where legacy technology can be a deal-breaker for the tech-savvy generations entering the workforce. We discuss the importance of offering tools that not only meet but exceed their expectations, ensuring a satisfying and productive work life.
Our guest departs with a hearty message of innovation and the unyielding importance of the human element in a world marching steadily towards automation.
Join us for this journey through the intersection of insurance, technology, and the timeless value of genuine relationships.
Learn more about your ad choices. Visit megaphone.fm/adchoices
Episodes You Might Enjoy:
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Ryan Hanley
No, but that, so for us, as a core, that was a huge hurdle in my agencies as well. Right. Like I said, I have age ranges all over the place that are agents, but a technology adoption. So I went from, I think we've done two or three really large, and I'm talking like AMS overhaul, CRM overhauls through the 15 years. And it didn't matter what it was, there's always resistance to change. Right. And I learned very early on that change management is so critical. I mean, it is so critical.
Hello, everyone, and welcome back to the show. Today we have a tremendous episode for you, a conversation with Margo Giles, broker and InsurTech CEO of Iris InsurTech, a next-generation insurance software. This is a conversation I've been looking forward to for a while. We've been going back and forth with our schedules, which happens a lot when you're booking guests for a show. It's an absolute pleasure to have Margo on.
We had a chance to connect IRL out in Utah at an event and watched her present her product to InsurTech Utah, an event that Wes Anderson put on. Phenomenal, phenomenal stuff. Margo's perspective blends the perfect mix of that gutsy entrepreneur who has to make waves with a pragmatic and real understanding of what it takes to be successful in our industry. That is exactly what you need to build productive and useful technology in this space. It's an absolute pleasure to have her on the show and share her perspective with you.
If you have not had a chance to connect, I highly recommend you connect with Margo on LinkedIn and follow along with what's going on with Iris. Even if you have no intention of moving AMSs or any of that kind of stuff, you're perfectly happy. She is one of the individuals, and her technology is one of such, that I believe we just need to have it on our radar. At a minimum, have this stuff on your radar.
Guys, great conversation, very nerdy, very geeky insurance conversation. If you're into that kind of stuff, you're going to love this. Before we get there, I want to remind you that depending on when you're listening to this, either the Insurance Growth Masterclass is coming very soon and you want to get on the waitlist, or we've already launched and you want to become part of this community, this membership group, this masterclass, learning how to grow your agency through inbound marketing and inbound sales.
Guys, there is nobody teaching this stuff on the market. It is what has made me successful over and over again in every venture that I've been a part of, whether it's a traditional independent agency, my own independent agency, and all the technology companies that I've worked for in between. These strategies are first principles in building sustainable, consistent, qualified growth into your agency. That's what we're teaching at the masterclass. I could not be more excited to launch this program. This is 18 years in the making.
To get on that list or to learn how to join, go to masterclass.insure. That's masterclass.insure. Either plug in your information so you can get notified when we go live, or learn how to sign up and join this group of incredible insurance agencies and professionals learning how to grow their business through inbound leads.
Guys, I love doing this show. I love you for listening to this show. Let's get on to Margo Giles. I really appreciate you coming on the show. I'm excited to chat with you. I think we got a lot to talk about. You've obviously been kicking butt and it's been fun to watch. I wanted to connect again since Utah, but life is so crazy. I'm actually in Utah again. I'm in Park City right now.
Margo Giles
Are you really?
Ryan Hanley
Yeah, I'm at MarshBerry. They have like an executive...
Margo Giles
Oh, cool. State of the Union for retail and distribution. So, yeah.
Ryan Hanley
Awesome. I have never worked with MarshBerry. That's one of the few organizations, literally one of the very few organizations in the insurance industry that I have never...
Margo Giles
You haven't? They're fantastic.
Ryan Hanley
That's everything I've ever heard about them.
Margo Giles
Yeah. Really, really good. So many good stats this morning where it's just all the things you want to know about retail and distribution and brokers and agents. I was just eating it up this morning. So that's awesome.
Ryan Hanley
That's awesome. Well, I want to get into it with actually a not a back and forth, because that means it's not adversarial, but something that I saw on LinkedIn today, a comment that you posted. For the audience at home, we'll throw this up on the video or whatever. I thought this was a really interesting place to start our conversation.
Ryan Matheson from Glovebox posted, "Is it possible that agents are over automating currently? The client experience can degrade quickly. If you try to automate every step in the customer journey, the industry's tech just isn't there yet." There were a ton of comments. But you commented: "There's no possible scenario where agents are automating too much. They don't have access to the kind of technology that can even facilitate that. They are, however, automating the wrong shit." Which I firmly and utterly agree with you on. It can feel like their processes are very impersonal. Then you went on to talk about Racko bind on websites, which I also agree with you on.
I wanted to start with this idea of over automating. What I liked particularly about your comment wasn't the first part, but that second part: they're automating the wrong things. I think some of that has to do with a slightly out of context reference, but like the medium is the message kind of thing. The actual tools that they're currently using don't allow them to automate the right stuff. I'd love to expand on that a little bit because this is so much of what you're building.
Margo Giles
Well, it's funny because the focus is always on sales. How do we make sales more efficient? How do we drive ROI? That's the first place people automate. But to me, that is the last place you actually want to automate. What you want to do is get menial tasks automated. In automation or business process management or workflow, whatever you call it, that gives you enough time and energy to focus on the consumer, the customer, the human being that you're speaking to, to procure insurance.
You see a lot right now, and I'm going to try not to use vendor names because I don't want to call anybody out, but there's a lot on the CRM side. There's a lot of automate mass emails, automate mass text messaging, get them to your website, get them quotes. I think I commented that in the comment on Ryan's post. To me, if you look at any of the data right now, mass email campaigns are dying. No one is responding. These cold blast emails, you're not getting the customers you want from them. So why are you investing in automating something that's not working?
Same thing with text messages. We're coming up against the timeframe now where people don't want mass texts. There's a lot of regulation going into it. What kind of clients are you getting in response to those things? Are you looking for someone that wants the cheapest price? Is that really how you want to build your book? This is where the concentration is, especially with AI too. I feel like the concentration is on the wrong part.
You should be using automation for things like data gathering, scraping information. When you have that first contact with that customer, you're coming to the conversation educated. That is a really great use of automation, technology, AI. Then feeding all of that back into the AMS. Your AMS really should be your war chest. This is where you go to do everything. That piece where we're just going to automate the entire process of building a connection with our customers is way off the mark.
Ryan Hanley
I did a post a couple of weeks ago where I basically said everything AI is trying to be more human, yet everything we do with AI makes us less human. I'm like, are we missing the connection there? Everybody that's building tech right now is trying to make the AI more human, yet we are disconnecting ourselves. We're trying to spend less time with our customers. We're trying to be more arm's length with them. That is the exact opposite of what we should be doing.
We should be leveraging these tools so that we can be more face-to-face with them, more phone calls, more time in market, in person, whatever, because all these things in the background are getting done. This is where I would love for you to take your next answer. How do we get them done accurately? There's a lot of stuff that happens and it sounds amazing, but then when you see the output, you're like, this might actually be more work. I run this automation, but then I have to hire a VA to make sure the automation is accurate. I'm not sure how all that happens.
Margo Giles
Because it's not embedded in the workflow. When I think of how we build workflows at Iris, the first thing I think of is how does a customer interact with the workflow? We all used to think of workflow as step one, step two, step three, step four. A lot of that is you might have four or five tools, but you're still putting data in here, then you're leaving that screen and going to another tool and putting data in there. The tool is giving you the response that it sold you, but they're not captured in any type of coalesced way. You end up having to go back to whatever that platform is to go back to that data or the output.
My goal is, if I'm doing something like quoting and I'm entering customer data, where is my AI that's popping up as I'm typing and saying things like, "Hey, have you thought about this?" or "This data is X, Y, Z, therefore we think you should offer the client this package." Instead of going somewhere to do something, getting a result, and then me as the human putting all the pieces together to figure out what the outcome is, that should be happening in a single interface. The user is not the one going out and doing all of the actual business process. The AI is giving us breadcrumbs as we're going. Think of it a lot like a personal assistant.
For me, that's where I'm focusing. Less of "I'm going to go chat to a bot and get an answer back from the bot," which is still light years ahead of where we are today. But how does that AI actually integrate into the workflow so that as I'm doing my physical work, it's redirecting me and directing me in the way that I need to be directed? If that makes sense.
Ryan Hanley
It completely does. I've been saying for a while, and this was something my mind was changed on. When I first started Rogue Risk back in 2020, I was all about commercial lines rating. I was like, this is going to be a game changer. Over the course from 2020 to now 2024, my mind has completely changed. I believe that commercial lines rating is actually an antiquated technology already. Going into a rater, it's another system, another disconnect, another place for this API not to talk to that API.
What we found, and where we became the most efficient and our conversion ratios were the highest, was when we got to the point where we knew the market before we quoted. We just knew this is Hartford, this is Travelers, this is a wholesaler. We just knew where to go. Independent agents have been doing this in their brain and their local markets forever. They had that engine in their mind. They just knew, "Tammy knows the bot business, so go ask Tammy. She'll know exactly where to go. Where do I put a church? Go to this person."
I speak about this a lot because my own mother, who's 62, works at our agency. She's our highest producing commercial agent. She has all of this knowledge in her brain. She's talking about retirement. I'm thinking to myself, how do we extract all of this amazing institutional knowledge that these producers who have been in the market for 30 years have? There's nowhere in an AMS to put that kind of data. There's nowhere in a CRM to put that kind of data. So what are they doing? They have their own spreadsheets or they've got their own matrix somewhere in a notebook. Why are we not leveraging that as an agency?
That is a fantastic first place for an AI use case. If I look at your historical policy placement and I can do things like line of business, coverage type, the type of risk, the location of the risk, some of the profiles of the people — this is not complicated algorithm stuff. You can build this. You put that into a machine learning or an AI bot. You can get those types of results even through Gen AI. You could type into an AI and say, "Hey, I have a risk. Here's the characteristics of this risk. Where should I place it?"
When the AI gets good enough and the data is large enough, and agents band together — because I'm going to pitch this — and we all discuss whether or not we're going to share our data, that is where we leverage things where we are actually determining where the market goes. We are analyzing the market before the carrier even knows where the appetite is moving towards, because we can't rely on carrier appetite guides. They're not accurate.
Then we get into how do we train new employees that are coming into insurance to be effective? Let's just give them a rater and we spaghetti against the wall. If you know anything about the technical inner workings of most rating platforms, their indications are at best. They're not bindable. Very few can go all the way through to binding and give you a bindable quote that you're still having to jump to that carrier portal. It's an RCE or an MBR. Raters are a great data transfer mechanism. What they do well is they take data from your one place and they put them into all your carrier portals. Beyond that, they're not really that great.
The big awakening for me was at some point we got a call from one of our reps of our better carriers. They asked, "What happened to all your quote volume?" I looked at it at a large level and saw that this particular carrier's quote volume was way down. I come to find out this person who called me didn't even realize that internally that carrier had decided to remove a discount that they previously had allowed to push through to the rater. They had removed the ability to push it through. That discount was legitimate. It actually applied, but now we just weren't seeing it. Now all of a sudden they're ranking X higher than other carriers because that discount isn't being pushed through based on a technical decision. My people weren't putting business with them, even though they were probably the right carrier to go through for that business.
I'm going, this is insane. We know automatically for this type of business, this is the right carrier. They're not getting the quotes because of some technical decision made in an API. It doesn't pass through. I'm just like, this has to be solved. How we solved this — and you guys are building a better mousetrap, so I don't want to pretend — but we started exactly what you said. We found an internal AI chatbot that ran off ChatGPT or whatever. It was internal only. We put all the appetites for the carriers in. Then we put very anonymous type of business policies that we had written. Then we created a PDF that was our rules document that was literally "this carrier rank one, this carrier rank two." It was very basic, but it gave our people a snappy answer. "Bakery, Wisconsin? Hartford, then Travelers, then Chubb." They would know, try this, and if it doesn't work, go here. Just that very hacked up version of things, there was a significant efficiency increase.
The other thing people don't think about — and I'll be quiet because I know you're supposed to be doing the talking here, but I'm a terrible interviewer — is one of the things I think we don't think about... I'd love your idea.
Ad break
Being a technology creator, I'd love your thoughts on this. We don't consider the brain cycles that it takes our people to get things done. Towards the end of Rogue Risk, we started making our technology decisions. One of the primary data points that we would take in and whether we took a new piece of technology on was how easy it was to train people on that tool.
Margo Giles
Oh, my gosh. This is our third pillar.
Ryan Hanley
Yes. That became like, to me, if it takes a month to train someone on a piece of technology or three months to train someone, I don't want it. That doesn't help me. It just bogs us down. It's brain cycles that people are using to do things. Instead of making good decisions or using that brain energy to communicate with a customer, they're thinking about all these other things.
Margo Giles
No, but that, so for us, as a core, that was a huge hurdle in my agencies as well. I have age ranges all over the place that are agents, but technology adoption. I went from, I think we've done two or three really large AMS overhauls, CRM overhauls through the 15 years. It didn't matter what it was, there's always resistance to change. I learned very early on that change management is so critical. I mean, it is so critical.
I would tell anybody listening — we're going to do a whole bunch of education around this this year, it's one of our initiatives — you need to understand your business processes and what your goals are before you even think about buying a piece of technology. If you're just constantly buying the shiny thing and you have no strategy behind what it's going to provide and how it's going to be implemented and what the rollout of that implementation looks like, even if it's a small piece of technology, there has to be strategy around it. You need buy-in from your employees.
If you are an operator or an agent or an agency owner and you are not bringing in your best CSR, your bookkeeper, your biggest advocates on your sales team, and they are not a part of the buying process, you are already set up for failure. Once you buy that technology, you're placing the responsibility of selling that technology on your technology providers. They may or may not be good at that job. Now you're immediately creating an environment where it's like you're butting heads. "I purchased this thing. You must use it. I don't care if it's useful to you. I didn't ask your opinion, but you're going to use it now." Immediately that's adversarial. It never works out well.
In change management, a lot of times ownership is looking at everything from a managerial, high-level KPIs point of view. "I need a system that gives me this result." A lot of times those results are not user-based. "I need a system that's going to give me the ability to see a report that looks like X." That's really important to management and ownership. It's not even tracking on your CSR's mind. They're worried about how do I get this process done that takes me 70 minutes to complete. I'm producing your KPI now, but you've just made my workday infinitely harder. What's that going to cause? People are going to leave because no one wants to do that. They're going to reject the technology because there was no holistic approach to it.
That's my soapbox. It makes my sales cycles longer, but in reality, when we have clients that approach it that way, they are always more successful with the rollout. The tech sticks longer and they're happier in general with the overall result. I would tell owners to think about those things before they even look at it.
Ryan Hanley
I had a very interesting experience. I became incredibly frustrated about two years in with Rogue with our inability to do what you're building at Iris. Bringing it all in, making it modern. I went on this probably biggest boondoggle mistake I've ever made. We tried to wedge our business into HubSpot.
Margo Giles
I have been there.
Ryan Hanley
The hard part for me was, and I really did try to get buy-in. I did have some buy-in from people, but probably not everyone I needed. The issue was the way HubSpot approached sales, customer service, the gathering of it, how you brought people into one account, how you track things. I was like, this is exactly what we need. This is it. This is how it should work. This is how insurance should be. But then there were all these other pieces that were wedging in and you couldn't get this data in. The data wasn't for me.
It became this boondoggle. The problem, and why it became a mistake, was that I brought in sales and sales loved it. Service hated it. Accounting wanted to stab me. If she wasn't remote, she probably would have stabbed me. Some of the other leaders loved it because they could see everything their team was doing. You started to create these factions. I allowed it to go too long. That was really the mistake. I didn't get everyone's buy-in. I got what I thought was most important at the time, sales's buy-in. These factions created where half the team loved this thing. It was helping them. They could see everything. The other half of the team was just poking my voodoo doll every day at their desk because it was so miserable. Ultimately we had to unwind it. That ended up being an expensive and valuable lesson.
If I had, to your point, brought all of the relevant decision makers or influencers in the company in and gotten their feedback, I probably could have missed that. Sales loved it. Service from the jump hated it. If I got that feedback, maybe I don't make that mistake. I think that's really valuable.
Margo Giles
That speaks to the difficulties of marrying CRM and AMS or PMS, whatever it is. Marrying a sales and service system. What we're doing is not easy. We're not the only vertical in industry having this sort of moment either. It's happening in banking. We see it a lot in financial services. We're not unique in this problem because those two people have very different needs out of a system.
The problem with insurance is that we are not like retail. We're cyclical. There is no difference between sales and service realistically because our whole model is built on renewal business. Our whole goal is to get somebody back into the loop to begin with and keep them in the loop. If you think of retail, it's very linear. You go on a website, you buy a shirt, you got the shirt. You may not find the same shirt again unless it tears. It's not cyclical. Systems like HubSpot are made for more of a retail type business.
If you want to dissect it, what we sell is highly complex when you talk about data modeling and data structure. You're talking about what fields do I need? When you have a very static product and you're in a CRM, it's really easy to point to a product and say, "I sold a car. The car has some attributes. Here's the VIN number. I sold it. Now we track it." When you're talking about insurance, you're talking about coverage and limits and clauses and contracts. You're trying to dissect this person is associated with this coverage on this policy. It gets wildly complex really fast.
When we started building the data structure around how could we point an opportunity — we call it opportunity, I think most people do — and how do we marry that with a product? If you're trying to run data analytics and there are many people listening that probably have a sales system where they're entering customer data, maybe a high level line of business, or they're just saying, "I have a sale. It's worth this much. It's in this stage of my pipeline. I'm going to close it out." Then the service person picks it up and puts it into a separate system. That chasm is where all of your data that you need lives.
How did you get from sales to service? What were the versions of that? Did you offer them these coverages and they rejected them? Then they came back and you settled on this coverage. Then you took that coverage and you took it to market and you sent those out. What was the market's response? Did they return the exact coverage you requested or did you have to negotiate with the market? All of that data is what drives AI. That's what drives analytics. That's what drives the market prediction. Most agencies are missing the best part of their data because that drives things like how efficient your renewal process is, what are you offering them next time around, are you upselling, are you cross-selling.
You can't see any of that data. But the problem is that even if you do get it in a unified system, it's a lot of data to enter. It's cumbersome amounts of data. So the first thing you have to do is marry the two. Then you have to figure out the connectivity between all the parties because you're getting data from an insured. Then you're supplementing that data a lot of times with your own research, your own underwriting stuff. You're going to their website or you're getting data about their credits or whatever it is. Then you're having to take that to a bunch of different third parties in the marketplace. It's not an easy feat.
When we started looking at Iris in the beginning, we really wanted to focus on the human connection. We really wanted to gather more data about the person and their buying habits and how they affected our agencies. But we couldn't leave out the fact that eventually we were going to have to compare that against coverage that we were offering. So it's a huge problem to solve. There are many people involved, lots of stakeholders that have to buy in. But at the end of the day, we couldn't build a one-off product. We had to build the arc because somewhere down the line, somebody has to have a system that allows for seamless communication between multiple stakeholders, and not just via API, but also future-proofing.
We talk a lot about API. There's an entire world beyond API too, where we're talking about how do we transfer data that is anonymized, that is secure. How do we run AI modeling off of very segmented submetadata? That's a problem that we can fix right now because of the way that core systems are structured still from the 80s and 90s that don't allow for that. So there was no other option but to go back and fix the root of the problem so that then we could interact with the insuretechs that are popping up everywhere that have really great solutions and offer what we need, but not outside of the workflow that we need them to be done in.
Ryan Hanley
Let me ask you this question. How much data does an agency actually need to be successful?
Margo Giles
Agencies have no idea. I want to write a book about this one day. Agencies in particular, and if agencies ever decided they were going to band together, which we're seeing a lot of right now in the market, we would control carrier appetite. We are the underwriter. We are the first contact with the customer. A lot of times I know that carriers have different views on this, especially for underwriters. The agent is always lying, right? That might be true for some agencies and it may be true for really small premiums that are very transactional, but I'm not putting my E&O on the line for a $3 million trucking policy. I'm underwriting that file.
The amount of data we collect — and you see this with the Ivan's problem with commercial download. If you've ever tried to do Ivan's commercial download, I'm curating so much data. I'm then sending that, I'm then putting it in a PDF, which is ridiculous because that PDF doesn't even allow me to put the data I need. If you ever look at a cord and its structure, it's not even capturing the actual underwriting data that an underwriter needs, which is why we have supplementals to supplement the fact that the form we all decided to use doesn't work. I'm putting that in a PDF. I'm sending it in an email. A carrier has taken that PDF, they're scraping the data off of it, putting it into their system. It's the worst game of telephone that I have ever seen.
We need to get to a point where there's more trust between the agent and the carrier. We can facilitate trust by verifying data in the beginnings as agents. If we're using the same data providers and we're using the same type of technologies that a carrier is using and we're transferring those things to the carrier securely, why is the carrier doing double, triple work of the work that we've just done? Why is that happening? Because that slows down all of the processing. That's why you're waiting two weeks for a quote back for anything over $10,000 in premium on a commercial P&C policy. It's not necessary. The reason why is because all of the technology that's in place when you go between those things is antiquated. And it is meant to divide us because there's a financial incentive to divide, to keep us separate. Because if we decided that we didn't want to be separated and we wanted to exchange data this way, then how would all these middlemen make all their money?
Ryan Hanley
One of the things that I've been advocating for as a mindset shift that I think solves some of these things is — and not everyone likes to hear this — but I've been saying we have to stop thinking about carriers as partners. They're suppliers.
Margo Giles
Yeah.
Ryan Hanley
It doesn't mean we can't have a great relationship with them. It doesn't mean they can't be important to us. But we give carriers in particular so much leeway because they're partners. We're sold this partnership idea. Anybody who's ever been on any internal agency council, any carrier ever or any side conversation, they refer to agents as their distribution arm. We're their distribution arm, but they are our partners. We have to stop this fantasy that you are anything more than essentially a manufacturing distribution chain here. You have to think about this.
My point is not to say carriers are wrong. It's that we have to start to be rational about what they really are, about the role that they play. They're a supplier. When the product that they're supplying is no longer addressing my market, I have to go find a new supplier. Because we've locked in this mental concept of partnership, we feel loyalty to them. I learned this the hard way. I had a carrier who spouts partnership, partnership, partnership, agents, agents, agents. I'm like, okay. We'd been building with them and growing with them. I got invited to this sales thing. You would think that we're a good partner of theirs. Then we got this really nice account. It was like a half a million dollar premium account. Comes to us, we package it up. It is a perfect fit. I can show them on their website, it's a perfect fit. I can show them in their internal documents, perfect fit. I send it to them. Finally, some guy that I don't know, in some office with a VP in front of his name decides that for some reason, this is an account we don't want and blows the whole thing up. It doesn't happen. I'm left after a month of work and their response is, sorry.
I'm like, wait, that's how you treat a partner? No, that's how you treat a distributor of your product that you don't care about. To me, we just have to realign our relationship so that we can start to do things like what you're saying. If I have a group of suppliers, I have no problem pooling my data with other people to better understand how my suppliers provide. But when I have a partner, and I know this sounds like semantics, but I do think it's an important psychological thing. When I have partners, it's like, I don't want to do that. They're my partner. They take care of me. And I'm like, no, Tammy the underwriter takes care of you. The carrier does not take care of you. You have a great relationship with Tammy. Tammy's awesome. She's great. But the rest of the people in that building don't know you from Adam or Eve and they don't care.
Margo Giles
It's your partner until you have a shock loss. Anybody that's owned an agency long enough has been through that. I live in Florida. I had to book roll my entire business every two years because a carrier would come into the market, undercut the market by 20% on the commercial P&C side, usually auto. Then they'd get their ass kicked in losses. Then they'd say, we don't write this business anymore. You have 30, 60, 90 days to move this book to another carrier. We were doing that every two years. So in Florida, I'm with you that we definitely had more of a supplier type relationship as opposed to partnership.
What irks me a lot about the workflow that's so common right now in the insurance space is this idea — five, 10 years ago, everybody started building carrier portals. Agents said, instead of collecting the data and then having to go to every agent portal, which again, not the way that should have been built. If anybody had taken five minutes to think that process through. But now what they were doing was giving up everything to the carrier. You're taking all of the autonomy, which is your data, your customers, and you're just saying, I'm not going to capture any of this information. This is so true in personal lines. If you look at personal lines flow, it's like lead comes in, they go right to the rater. They splatter the stuff to the rater. They pick out their one carrier. Then at the end of all that telephone game, they let Ivan's deposit the data back into their database. You have just given up all rights to everything that makes your business your business in that type of a workflow.
I know why it's happening because it's impossible. In our agency, we have tons of agencies all over the country now, and we have hundreds of portals between brokers and wholesalers and carriers. How do you even manage that process? I know why it's happening, but agents need to wake up and realize that that is not a symbiotic partnership. You dumping data to carriers and then hoping they give it back to you — that's not how you should be running your business.
Ryan Hanley
It's a sticking point for me. It's a hard one. I know the guys and gals who are listening who are like, yeah, but I only have so much time. How do I get this done? I get it. The four years that I ran Rogue, it was so interesting. The emotional struggles you have with data. It really is like an emotional journey. You're like, I want all the data. Then you're like, yeah, but it's so much work. What data do I really need? All that matters is that more money comes in and goes out. You have all these crazy mood swings and thought swings.
Where I'd like to take this now in our conversation is, you're building a solution to this. What does that look like? How are you starting to address some of these things? For the people who are listening who are fed up or have seen what you guys are doing, what are you guys building? Where is this differentiation? How did all these ideas that we spent the first 30, 40 minutes talking about — how do all these things start to come together in your tool?
Margo Giles
We started with three big differentiators. I wrote down what are the three things that are just killing me. I got to a point with our agency where we could not do business with the technology that we had. It was so preventative for my CSRs and my agents. I am not going to be the kind of owner that makes my agents go to seven portals to enter data. We're not going to do it. But we also didn't have technology providers that were solving that problem. Beyond a rater, that was the answer. "Here's a rater." That's not good enough. When are we as agents going to start saying, I'm not going to pay for your shitty software anymore? It doesn't do what I need it to do. That was the catalyst for me. Especially in larger agencies where you're paying hundreds of thousands and millions of dollars to providers that are not providing you the base level.
First, I cannot see the people I am selling insurance to. They're listed as a contact on an account somewhere. Maybe they're listed as a driver inside of a policy that lives in a PDF. Who are the people that are buying from me? Why can't I see them? In legacy tech, there's an account, there's a policy, and there's a premium number. Then somewhere along one of those three objects, there may be a contact or a person or multiple people associated with that. Typically you see an account and it's a household or it's a business or it's a person. There's no standard there whatsoever.
I called into my own agency one time. I needed to make a policy change. I was listed as a driver on my husband's account. The person in the call center saw the name and thought this is just a driver on an account. They had no insight to the fact that I own the damn agency. But also that I was a driver on this personal policy, but we had group benefits through the corporation, we had rental properties, I had RVs. Immediately I was like, these people cannot at the basic level see where I influence the book that's already on the books, let alone how I could potentially influence things you may not even know about. How I might be on the board of directors for a charity. When you talk about cross-sell, upsell, there's no insight to that.
We had to go back and build cutting edge technology to look at human beings with personas in a database that may play many roles in many different ways. There may be people in your database that don't even have a policy. How are those people represented in your database now? Maybe they're a member of a household and now they've aged out and they're 18 in their own household. How are you going after that business? How do you know that's even happening? We had to fix all of that.
Once we fixed that, it led us to the second differentiator: how do we allow the free flow of external data? Supplemental data. If I wanted to have Equifax or ZoomInfo come in and help me populate bins and property information and people information so I'm not having to manually type that in. Then how do we get all of this coalesced so we can push it out to different vendors? Different services behind the scenes to perform some of the functions that Iris is not going to build. We are not going to go rebuild e-signature. I am not going to go rebuild DocuSign or doc management. I'm not going to go rebuild on cork or process management. How do we become an experience layer where the user is having a single journey, but the software is having a whole bunch of journeys on the backend that the user is not aware of?
That's really technologically advanced. It's also incredibly expensive. It's what has been stopping AMSs from coming to the market. It's not just this hill we have to climb of "another AMS, it's not going to work or it's going to get bought." The business model behind it, the technology that you actually need in place is incredibly expensive. You have to create this platform that may have multiple pieces of other people's services that you have to wrap together and then serve to an agency. If that wrapper cost $100,000 a year for me to provide to you, you're not going to be able to afford it. We had to figure out how to get a platform wrapped that would allow the service layer to be separate from the UI layer. We could call on all these typically expensive underlying platforms and hand it to an agent in a way that made sense. That was the secret sauce of how we figured out how to do that. That's why no one can beat us. I can offer tech that an agency that's $400 million in revenue can pay for to an agency that's four people. That was the hardest part.
The third part was, how much money can we just dump into user experience? How can we make this so easy and so intuitive that somebody who has never been in insurance before can come into an agency, turn the thing on, and understand in plain English how they start a process, where they need to enter the data? Insurance people love our acronyms. We love our complicated data sets. That doesn't really serve us well. If you're looking at legacy platforms and you look at field names and you're like, what does this field even mean? Sometimes as a tenured agent, I'm looking at it and I'm really not sure what they're asking me to put in here.
Let alone, I have a gray screen that's a box with a thousand fields on it. As a new insurance person, I don't know what's important to fill out. Do I have to get all of this information from the client? Now your brand new agent is like, no thanks, I'll go work in retail. I'll pick something else up because this is way too complicated. The system is not offering them easy adaptability and onboarding. With 50% of this insurance market retiring in the next five years, this is a problem that you cannot get ahead of soon enough. How are we going to get people into insurance, especially on the agency side?
We're going to plop them in front of a Windows 95 screen and say, I hope you can figure this out.
Ryan Hanley
This is a major problem. It's why towards the end of my time at Rogue, everything we did was about how easy it was to train people. I was asked by an AMS vendor to come on a webinar. I'm talking to him about answering different questions, a lot of it about marketing. Someone made an offhanded comment about recruiting and how we never really had a problem recruiting. One of the agents in the room asked, how can that be the case? Everyone has such a hard time recruiting. There are recruiting keynotes at every conference. I said, I actually don't understand why it's hard. One, would you work for your business? Two, is the technology built in the last five years? It's really not hard because nobody young wants to come in and be using Instagram and Slack and then go to some technology that they see in 1980s movies. They're like, wait a minute. That's a complete turnoff to them. It's not exciting because it doesn't feel like growth and innovation. Nobody who's 25 wants to be in a business that isn't going anywhere.
Ask yourself, would you work there? Is your agency fun to work for? A 55-year-old person who's been coming to the same place for 30 years, you're used to it. It's fine. You don't see these things. But when you're 25 to 35 and hard charging, ambitious, you have time, you want to grow — some of the biggest leaps in your career are going to happen during this time period. You walk into a place and the technology is slow and tough to manage, tough to learn. It doesn't feel like growth. Your brand, everything about you feels slow and stodgy. Why would they come work there? No duh, it's hard to recruit people. Would you at 25 go work for your agency? If the answer is no, there you go.
Margo Giles
The systems that you're asking them to utilize are not giving them anything in return. I'm a sales rep and a sales manager says, you got to enter your leads. You got to go back in. They're like, that is a menial task because it's just showing you what I did today. Managers are using that. They're not getting anything. The system is not doing anything to help them tomorrow when they sign on. It's just a black box repository for data. If you are not giving people reasons to interact with software, whether that's insights or what we do at Iris — filling their pipeline with suggested opportunities that we find through our machine learning algorithms — there's an incentive for a salesperson to enter data into Iris because when they wake up the next morning, they're going to have a warm lead list that they can work through. If your system isn't doing that, what is the point? They're not going to engage with it. You might have shiny tech that you think is great, but if it's not providing any use to the people that are using it, they're not going to use it no matter how nice it looks.
Ryan Hanley
It is insane that we want people to sell and then we force them to use tools that don't help them sell. We're like, sell, sell. What's wrong with this generation? Why won't they sell? And they're like, because half my day is putting information into this thing just so it's in there. 25 years ago, maybe that was acceptable. But every other business that they're applying for, every other industry they're considering working in — they're looking at all these other enterprises going, wow, there I'm completely facilitated. Life insurance. It's just go, go, go. Then they come here and it's like, no, half my day is data entry into systems I can't stand that hurt my eyes. I get data back that doesn't make sense. I'm fighting constantly with our quoting team and our account management team over where the data is. I didn't put a comma in and this system can't handle the fact that if there's not a comma, it doesn't think it's a number. It thinks it's a word. There's not a dash in the right spot. Then we wonder why these people don't want to come work here.
You have to build something that they want to use. When you can show them — and I love the predictive pipeline building that you're describing — when you can say, hey, you come here, you're going to be selling. Yeah, there's a little bit of whatever, but what this tool is going to do, if you learn it and you commit to it the way we're asking you to, is it's going to give you more and more opportunities. If you put something in a long drip, it's going to cycle it back in when there's a change. Now all of a sudden your job is 80% of the day is just call, close. That gets people jacked up because now what they're seeing is dollar signs. Play to what they want. They want to make money. That's why they're a salesperson. Facilitate that.
How many agencies do you know that have a rounded book? I have never walked into an agency and been like, wow, your book is so rounded out. Every possible upsell cross-sell is there. It's not because they don't want to, it's because they don't have the tools to see what the cross-sell upsell even could be. For us, that was place one. That's where we wanted to start: how do we look at the people? Then how do we understand what they could potentially need to buy? People are not static. These systems are so point in time. Once that data is in, it's in and that's it. People move, they get married, they buy houses, they have babies, they buy businesses, they sell properties. This is a constant thing that people in your business are doing. If you're just point in time, not being able to adjust — you can put a sticky note on the file so that when someone comes back in, they know. You can also throw the credit card number on that sticky note and any of their HIPAA data on there, which is the worst thing, which we all know is happening.
Margo Giles
The sticky note and the notes field — this is getting really nerdy with my data. If I see a notes field, I know that whoever engineered that data structure had no idea what they were doing. They're basically like, here's a big empty text field, put whatever I forgot in this box. You're never going to see it again. You can't report on it. You can't do anything with it.
Ryan Hanley
When you think about the concept that is so unique to our business, coming back to your T-shirt idea — and we're coming up against a number, so this will be towards the end of our conversation — the concept that I always come back to is that everyone who builds technology in our space, obviously not everyone, but the vast majority of the systems that we are commenting on were seemingly built by people who don't understand the concept of earned premium. They don't understand that our sale — we make zero money when we sell something. It is every day that the person uses our product and that policy is enforced that we are actually making money.
Margo Giles
Depending on the policy type, there can be differences. If it's fully earned on the commercial side, yeah.
Ryan Hanley
The idea is that we are literally earning their business every single day. When you build a system that is a point-in-time system, it does not take into account that you could have a major policy change three-quarters of the way in that drastically changes the nature, the dynamic, the quality, whether it's a level one or a level three. You could add a 15-vehicle fleet and all of a sudden it goes from just servicing this at this level to this, and there's no way of changing that dynamic. You can do that manually. You can go into the field and your CSR, your service person can remember in their mind that once this is a certain premium, I better change this SLA level to gold instead. But that's stupid because that's the easiest thing to put into a system. If you're constantly evaluating whether or not your system is still accurate for your market — the biggest thing that I've seen with legacy is the unwillingness to evolve the technology. To truly evolve.
Margo Giles
Honest question. Do you think that it's an unwillingness or do you think the legacy code bloat in so many of these systems has made it almost impossible for them to make a change?
Ryan Hanley
That's an honest question.
Margo Giles
When you are operating an almost billion dollar revenue company, that's a choice. I'm not saying it's an overnight thing, but how many other industries? You've got innovation labs. You've got departments within these tech companies that do nothing but sit around and think about how the next big thing is going to come around. Have you seen that in insurance anywhere?
Because I have not. So you're making a conscious choice to say this is the product. We're going to incrementally maybe make it better over time. But we have no plans to completely reinvent this. And here's the timeline. We're going to do it. And here's what we're looking at. None of that is happening. It's like, here's the thing: come to the event every year, we're going to tell you how we made this field go from 40 characters to 180, and everybody's supposed to be excited. Like, where is the innovation?
Ryan Hanley
Yeah, I love it. Where can people—this has been an awesome conversation. I appreciate the hell out of you. Where can people connect? Where should people go to learn more, connect with you personally, with Iris, and all that? Where do you want to send them?
Margo Giles
Yeah, we have a great LinkedIn presence. We do a lot of work there. My team is—you can always message me on LinkedIn or anyone else on the Iris team. And then our website, iriscloud.com. I can give you the specifics on that. We maybe put them up on the screen or something. But yeah, I mean, we're very active on social, so we're always available.
Ryan Hanley
Well, I'm glad you're doing what you're doing. I love that you're pushing the envelope. I think you're getting a ton of attention, which is phenomenal. And I love these conversations. I wish you nothing but success. Guys, I'll have links—if you didn't pick up on it just verbally, we'll have links both in the show notes wherever you're watching this, listening, etc. And if you just Google, you'll find all the information too, I'm sure. So thank you so much for your time, and I wish you nothing but the best.
Margo Giles
Thank you.
Ryan Hanley
All right, Ryan, thanks. Bye-bye.
End of interview. Transition to promotional segment.
Announcer
I'm going to shop. Boom! Thank you. Thank you. Close twice as many deals by this time next week. Sound impossible? It's not. With the One Call Close System, you'll stop chasing leads and start closing deals in one call. This is the exact method we use to close 1,200 clients in under three years during the pandemic. No fluff, no endless follow-ups, just results fast. Based in behavioral psychology and battle-tested, the One Call Close System eliminates excuses and gets the prospect saying yes more than you ever thought possible. If you're ready to stop losing opportunities and start winning, visit masteroftheclose.com. That's masteroftheclose.com. Do it today. Thank you.