Why Brokerages Are Adding Workflow Layers Without Replacing Their AMS

After nearly two decades working inside agencies and helping teams implement and redesign their operating models, I have come to think that most frustrations with agency management systems are pointing at the wrong target.

The AMS is doing its job. The gap tends to live in the work happening around it.

Agency management systems are exceptional at what they were designed for. They hold the record, store the policy data, organize the account history, and give the business the reporting foundation it depends on. For most brokerages, the AMS is the system everything else is built on, and it performs that role well.

Where things get more complicated is when brokerages ask the AMS to carry the full coordination load as well. Managing handoffs across people, tracking task ownership, surfacing what is overdue, keeping the next step visible — those are a different kind of problem. When the coordination load exceeds what the AMS was designed to manage, teams tend to build their own solutions around it. Spreadsheets, shared inboxes, personal tracking systems that work well for the individual who built them and become harder to interpret as the team grows. Over time, what reads as a system limitation is often a process that developed informally around the system rather than inside it.

I saw this pattern consistently across the agency integrations I worked through. Two agencies might run on the same management system and operate in very different ways. One team documents everything inside the platform and builds its coordination into the workflow. Another routes most of its day-to-day activity through email threads and relies on individual account managers to keep their own renewal calendars and follow-up lists.

Both approaches can work well enough in the short term, and both teams will say the system serves them. What becomes harder to see is what the second approach costs as the book grows. When coordination lives in individual inboxes and account status exists mainly in someone’s memory, the operation has limited visibility into where things stand across the whole book. Bottlenecks stay invisible until they produce a problem. Handoffs get dropped because ownership was assumed rather than assigned. A renewal moves slower than it should, and the reason is simply that the process depended on someone remembering rather than the system tracking. The more accounts the team carries, the more those gaps compound.

The brokerages adding workflow layers are doing so because they want to strengthen the process around their AMS. Most of them have invested years in their management system, and the goal is to make the work around that foundation easier to coordinate and easier to see.

A workflow layer handles the coordination problems that sit outside the core record-keeping function. It gives the team a way to assign work, track status, surface what is behind, and keep the next step clear without requiring everyone to maintain a personal system alongside the AMS. The system of record stays in place. What changes is how work moves through it.

When those two things operate together well, the results are practical. Account data in the AMS connects to a process that is visible and assignable. Work moves from step to step with clear ownership. And when something needs to be reviewed or explained later, the record reflects what actually happened because the process produced it along the way.

The impact tends to show up first in the workflows that run most frequently and vary most by person. Renewals, proposals, policy checks, and certificate requests are the places where informal coordination creates the most drag on team capacity.

When those processes are structured and visible, the team spends its time doing the work rather than managing around it. Senior account managers stay focused on clients rather than stepping in to untangle handoffs. Leadership gains a clearer view of where workload is concentrated and where things are running behind.

I have seen this shift the capacity picture meaningfully for teams that were weighing whether to add headcount. In most cases, the throughput challenge was a visibility problem. Bringing structure to the process created room in the operation without requiring anyone to change the core system they already relied on. The AMS stayed exactly where it was. The work around it became easier to manage, and that turned out to be the change that mattered.

Kathryn Lerch is Insurance Solutions Engineer at Fulcrum, an AI-powered workflow platform built for insurance brokerages. She brings 18 years of experience redesigning service workflows, leading technology implementations, and scaling operations across multi-location agencies, including overseeing operations through more than 25 acquisitions.