How Many Systems Does It Take to Onboard a Producer? (The Answer Might Surprise You)

Ping! A new IT ticket just came in. It’s another producer stuck in onboarding, this time because the system isn’t showing their appointment status. IT checks the integration and…it’s working fine. So what’s the issue? This is a moment that repeats, in some form, at nearly every insurance carrier or distributor and often raises the question: how many systems does it take to onboard a single producer?

Ask five people across five different departments, and you’ll walk away with five different answers. A licensing platform, an appointment tool, a commission system, a CRM, an HR system, and don’t forget about any spreadsheets or piecemeal solutions quietly holding the gaps together. 

A 2026 IT Help Desk benchmark report found that support tickets at organizations under 100 employees touch roughly five distinct applications on average, while those with over 1,000 employees average around 63. Producer lifecycle management at any medium to large insurance organization is happening somewhere in that range and every one of those systems has its own department owner, its own data, and its own definition of “done”. 

The first instinct when producers hit friction is to blame the technology. But the ticket you received at the start of this article is the tell. The application was never broken to begin with and the integration was working exactly as intended. The problem was already baked into the data before it ever reached IT.

The producer lifecycle tech stack nobody full owns

Every one of the systems named previously has an owner outside of IT. Compliance teams own licensing data. Distribution teams own appointment timing. Finance owns the commission structure. IT is tasked with making it all work together—building the integrations, maintaining the APIs, and keeping the data flowing between departments that each only see their own slice of the full process pie. 

But IT rarely owns what goes into those systems in the first place. That’s an important distinction, because it means the systems can be built and integrated flawlessly, but still result in a poor producer experience. The breakdowns happen not because the system architecture is wrong. But because the data flowing through it is inconsistent or lagging from the start. 

Why another integration won’t solve the problem

When producer complaints or IT tickets spike, the default response tends to hinge on more technology: another integration between two systems that don’t sync well, another automation to reduce the amount of manual entry, another dashboard built for leadership to see the problem more clearly. 

Each of these fixes can help at the margins, but none of them get to the underlying issue. For example, adding another tool may move commission structure data off of spreadsheets, but it won’t solve what’s wrong with the data or the processes that created it to begin with. 

Findings from the same 2026 IT benchmark report reinforce the story. Even when automated, onboarding and offboarding tickets still take anywhere from 25 to 75+ hours to resolve. This is far longer than nearly any other ticket category, and it has nothing to do with poor ticket queue management. The report attributes the delay to the multi-step approvals and third-party coordination native to the workflows themselves.

Think about it like this: You’ve built a perfectly engineered pipe system, but then connected it to a contaminated source. No matter how well built and expertly placed the pipes are, what comes out the other end is only as good as what went in. 

Where the fragmentation actually starts (and why IT gets blamed for it)

The root fragmentation usually doesn’t start in a system IT manages at all. It starts upstream—in how your organization’s compliance team defines and hands off licensing requirements, in how your distribution team times appointment requests, in how commission structures get communicated (or not) between departments before a producer even begins onboarding. 

By the time that data and information reaches an IT-managed system, it’s already inconsistent, incomplete, or arriving on a different timeline from the other data it needs to match up with. The result is that IT ends up building the infrastructure to reconcile problems they didn’t create and don’t fully control and absorbing the blame when a producer hits a dead end. 

Continued findings from the report reveal a not so fun fact: insurance IT tickets carry the highest negative sentiment—almost 28 percent—of all the industries surveyed, driven largely by identity, hardware, and compliance driven access issues. Coincidentally, the insurance sector also reported the leanest IT staffing ratio in the dataset at just under 1 FTE per 100 employees. Put that all together and you’re left with exactly what a lot of IT leaders in the space already feel: the thinnest coverage, fielding the most friction, for problems that mostly started somewhere else. 

If you’re an IT leader at an insurance organization, you might have already sensed that the fragmentation isn’t just an inconvenience, it’s an inherent result of a poor producer experience. 

5 signs fragmentation is part of a larger producer experience issue

A few practical signals that upstream data and process fragmentation are causing producer frustration:

1. Producers are asked to submit the same information more than once across different steps of onboarding
2. Help desk tickets that read like technical issues at first glance turn out to be a missing data or mismatched data issue
3. Manual reconciliation is still happening behind the scenes to make two integrated systems agree with each other
4. Different departments can’t agree on which system holds the “source of truth” for distribution network data
5. Dashboards show onboarding progress that don’t match what the producer is actually experiencing

If more than one or two of these resonate, the conversation worth having next is “where is this data coming from, and why isn’t it consistent by the time it gets to the next step?”

Producer experience: the business case hiding in plain sight

The point of this article is not that IT should stop building integrations or investing in infrastructure. Better systems are crucial to long term success, but it’s worth finding the root cause before purchasing another surface-level solution. If fragmentation is tainting producer experience at your insurance business, it’s a problem IT can and should surface, but can’t solve alone. 

What IT can do is make the case that’s been hiding in plain sight all along: A poor producer experience isn’t just cultivated through a series of isolated technical gaps, it’s a warning sign of a deeper data and process problem. It’s a tougher conversation to start than just adding in another layer of integration, but it has the potential to move the numbers in a real way. 

Framed that way, IT isn’t just the department fielding tickets about a broken system. It is the function best positioned to make the business case for fixing producer onboarding and lifecycle management processes at the root, using the producer experience as evidence. 

Curious who actually owns the producer experience at your organization?

IT might be where the friction becomes most visible, but it’s rarely the only function feeling it. Other core parts of your insurance organization are each absorbing their own version of this same breakdown, often without realizing the root cause is shared.

See the full cross-departmental picture, including what a modern producer experience looks like, in the eBook “Who Owns the Producer Experience?”.