OIP Insurtech

Partner Perspective

Bridge Specialty Group & OIP Insurtech/BoundAI: Lessons From Three Years of Submission Automation

November 16, 2026

This Partner Perspective is part of a series brought to you by OIP Insurtech.

View series

Three years ago, Bridge Specialty Group partnered with OIP Insurtech to automate its submission workflows, well ahead of most peers who were still having the conversation. What they built, how they launched it, and what they learned from the experience is the subject of a recent episode of Bound and Beyond (a BoundAI podcast produced in conjunction with Insurance Journal that looks at the people, the capital, and the technology that will shape the future of insurance).

The conversation was between Ted Stuckey (Regional President – Central, West, and LocalEdge at Bridge Specialty Group) and Joe Failla (COO at Bridge Specialty Group). Ted’s career has been in underwriting, with roles at Travelers, QBE, Markel, and Arrowhead Programs. Joe has been with Bridge Specialty Group for several years, having led the underwriting, product, and personal lines divisions before taking on his current role in 2025. Mladen Subasic (Chief Product Officer at OIP Insurtech and BoundAI) also joined the call. AJ Beatovic hosted the podcast.

Balancing local autonomy with operational scale

Bridge Specialty Group has grown almost entirely through acquisition, and that history shapes how it thinks about standardization. The tension between efficiency and local autonomy is largely structural.

“We hold that tension very closely,” Ted said. “More often than not, it’s actually listening to those local offices and hearing where they’re struggling, where their gaps are, and then finding common threads amongst those that we can then go after.”

Joe added that the pace of AI and automation has made this tension much harder to ignore. “We can’t go build it 30-something different or 40-something different ways by office. We’ve gotta scale this,” he said, adding that “we can’t lose that entrepreneurial, you know, selling gene that our offices have.”

The submission automation initiative

Three to four years ago, BSG decided to implement a submission automation engine in conjunction with OIP Insurtech and BoundAI. That was an early move for them and definitely a conscious decision.

Joe was very clear on the original driver. “The one pain point we had was getting that data,” he said. “What you don’t always want to do is go to the front lines and ask our people sitting at the desk to go enter countless amounts of data. They’re already busy, you know, their days are full.”

Ted (who joined post-launch) was very much aware of the downstream impact. “I can’t imagine not having that data,” he said. On the roadmap, “all the other things we’re talking about wanting to do and build out, the roadmap from a technology perspective at Bridge, I can’t think of one that doesn’t tie back into submission engine in some way.”

Mladen pointed out what made the initiative work from the product side. “You had a workflow problem,” he told the Bridge team, and “you wanted to solve it ahead of the market.”

People, change management, and adoption

Adoption across a decentralized organization with dozens of offices wasn’t immediate. The discussion on that point was very frank.

“There was a very broad distribution of utilization upfront,” Ted explained. “Some offices fully embraced it and other offices we saw next to no adoption. But without our ability to measure that, we couldn’t have had the conversations that were needed.”

Joe explained what it takes to get adoption moving. “You’ve got to tell the story, and that’s really what operations does,” he said, explaining “why we’re using the technology, how to use the technology, and getting people on board.” He added: “You have to win hearts and minds. You’re ultimately thinking about people that have been doing a process probably for ten, fifteen years in some cases, and they are really good at their process.”

Mladen put it as a product-launch mindset. “If we treat the rollout of technologies inside our organization as a product launch to the market and give it the care that the product launch would get… then we are going to get all these benefits.” In his view, adoption follows the value people can see and feel.

Where AI actually delivers: the 80/20 problem

One of the more pointed exchanges in the conversation was about where organizations are spending their AI budgets and where they’re actually seeing returns.

Mladen was very clear on the gap. “80% of the attention and budgets are going towards growing the business with AI,” he said. “What we are actually seeing producing today is on the flip side. We see 80% of gains on the execution operational layers while 20% are only made on the growth side.”

Joe agreed that “it’s easier to get the bang for your buck on the operational side” because it’s a workflow. “You could add in AI into certain parts of that workflow that make it quicker and faster and less of a touch,” he said. “And you could measure that.” On the growth side, he said, it’s “harder to kind of quantify what that is.”

Build versus buy (and why the question is changing)

The discussion ended on the build versus buy issue, with both Ted and Mladen clearly unhappy with the way it had been framed.

“I almost think that the build versus buy discussion is antiquated at this point,” said Ted. “Technology means absolutely nothing if it’s not adopted. What should matter is how quickly we’re able to realize those benefits and how easily it is for us to sustain those benefits over time.”

Mladen went on. “It’s not build or buy anymore by a mile,” he said. “What you build, what you experiment with, should be your alpha.” He described that alpha as “the thing that makes customers come to you and not come to the shop next to you.” Everything else, in his words: “And hire everything else.”

Was this article valuable?

Here are more articles you may enjoy.