The Implementation Gap: Why Good Technology Fails Inside Good Brokerages

This article is part of a sponsored series by Fulcrum.

One of the more consistent things I have observed working with brokerage teams on technology implementation is how different the first 90 days looks from the demo that preceded it. In a demonstration, the tool performs well. The workflow is clean, the outputs are clear, and the efficiency gains are easy to see. Then implementation reveals that ecosystem has unique challenges for the technology and once the team finally goes live, and the results take longer to materialize than anyone expected.

This gap is common enough that I have come to think of it as its own category of risk — one that lives in the implementation rather than the technology, and one that responds well to the right kind of preparation.

What the Implementation Process Reveals

When a new platform goes into a brokerage, it enters a specific operational context with its own documentation habits, its own handoff patterns, its own informal systems that have developed over years. The implementation process makes all of that visible in ways that normal operations tend to obscure.

I have seen this happen in brokerages with strong reputations and talented teams. What surfaces during implementation is that the underlying processes were less standardized than anyone realized. Two account managers handling the same workflow in two different ways with policy data stored inconsistently across the book. Renewal timelines managed through individual calendars rather than a shared system. These are simply what organizations tend to look like when they have grown faster than their processes have, and implementation is often the first moment when all of it becomes visible at once.

The brokerages that use that visibility well treat implementation as an opportunity to standardize alongside deploying the technology, rather than as a project to complete and move past.

The Distance Between Demo and Daily Use

The demo environment is optimized for clarity and to sell the system. The data is clean, the workflow is linear, and the person running it knows exactly what is coming next. Daily use looks and feels very different as the data comes in from multiple sources with varying degrees of completeness. Workflows get interrupted. Staff members are handling the tool alongside everything else on their plates, and the learning curve competes with the pressure of getting the actual work done.

That distance is wider than most leaders expect, and it tends to show up most in the first 30 days. Adoption slows, questions and frustrations accumulate, and the early momentum from the rollout can stall without structured support to move through it. The teams that close that gap quickly are usually the ones that go into implementation with a realistic picture of what the transition period actually requires.

In my experience working on implementations with Fulcrum’s brokerage clients, the organizations that set expectations clearly at the start — with leadership, with staff, and with the internal owners responsible for driving adoption — tend to reach consistent daily use faster. The tool is the same. What differs is how the transition is managed.

What the First 90 Days Should Actually Look Like

The first 90 days of a technology implementation are more about process than most people anticipate. The platform is in place and the configuration work is largely done. What the first 90 days are really about is process alignment, habit formation, and building the internal accountability structures that will determine whether adoption holds.

The brokerages that move through this period well tend to share a few characteristics. They identify internal champions early — people who understand both the tool and the operation and can translate between them when questions come up. They set a clear sequence for which workflows go live first, starting with the highest-frequency, highest-variation processes where the improvement will be most visible to the team. And they build in regular checkpoints to surface what is working and what needs adjustment, rather than waiting until the end of the rollout to evaluate.

The goal of the first 90 days is to reach a point where the new process feels like the normal process. That takes longer than most rollout timelines assume, and it requires more active management than most leaders plan for. The organizations that account for that honestly at the outset tend to be in a meaningfully stronger position at the 90-day mark.

Building on a Stronger Foundation

Technology implementations that go well do more than deliver the efficiency gains in the business case. They leave the organization with better visibility into its own operations, more consistent processes across the team, and a clearer picture of where the next opportunities for improvement are.

That outcome is available to any brokerage that approaches implementation as an operational project. The platform matters. The operational foundation it is built on matters more. The brokerages that invest in getting both right during the implementation period tend to see results that hold and build over time.

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.

Topics Agencies Tech