One CRM Across Four Insurance Channels: The Gap Between Rollout and Adoption

CRM Implementation · Sales Operations · Workflow Assessment · Operating Governance · Insurance

Multi-channel insurance organization

CRM implementation ownership and operating-model assessment

How a shared CRM implementation reached completion across four insurance sales channels, but differences in workflows, adoption and system integration prevented it from becoming a complete operating foundation.

AT A GLANCE

THE PROBLEM

THE PROBLEM

Four insurance sales channels moved toward a shared CRM, but their distinct workflows and disconnected customer information were not fully accommodated by the original system design.

MY CONTRIBUTION

MY CONTRIBUTION

I completed the predefined CRM implementation across all four channels, then assessed inconsistent adoption, identified workflow gaps and proposed improvements with business stakeholders.

DELIVERED

DELIVERED

All four channels transitioned to the CRM. The subsequent assessment identified gaps in channel workflows, system integration and management visibility; one workflow-consolidation proposal was approved.

SCOPE & EVIDENCE

SCOPE & EVIDENCE

Adoption remained uneven, and manual data transfers persisted. The approved workflow change was not implemented during my involvement, and I did not control the original architecture or broader project scope.

A multi-channel insurance organization was transitioning from its previous CRM to a shared platform across four distinct sales channels. Each channel operated with different commercial processes, customer requirements and operational dependencies. The implementation scope and underlying CRM structure had largely been established before I joined the project. I took ownership of completing the implementation within that defined scope, bringing the migration to completion and enabling all four channels to begin using the new CRM. However, completing the migration did not mean that every channel could conduct its work effectively within the system.

A shared platform did not create a shared operating reality.

Although all four channels began using the CRM, their ability to rely on it varied considerably. One channel could manage almost its entire workflow within the platform. Others continued using separate spreadsheets and work-management tools because the implemented CRM structure did not adequately accommodate their requirements, particularly where complex underwriting processes were involved.

This created an uneven operational picture. For some teams, CRM reporting and management visibility reflected how work was actually being performed. For others, important activities continued outside the system, leaving significant gaps in the information available to leadership.

A separate integration gap compounded the problem. The CRM was not connected to the organization’s internal customer database, which also captured customers registering directly through its website. Even teams that used the CRM consistently still needed to monitor that system separately and manually ensure new leads were recorded in the CRM.

The implementation had delivered a common platform without eliminating the fragmented processes surrounding it.

CRM implementation ownership and identification of unresolved operating requirements

I was responsible for completing the CRM implementation within the scope and architectural decisions that had already been established. My responsibility included managing the remaining implementation work and supporting the transition to the shared platform across the four channels.

Following that work, I was given the opportunity to examine why certain teams were not using the CRM extensively and identify what would be necessary to improve adoption. I worked with business stakeholders to understand the gaps between existing workflows and the implemented system, including differences in channel requirements, continued reliance on external tools and disconnected information flows.

Although I could identify problems and recommend improvements, my authority to change the implementation’s broader scope remained limited.

Distinguishing implementation completion from operational readiness

The initial priority was completing the agreed CRM transition. Once the platform was in use, attention turned to understanding why adoption varied between channels.

The assessment considered which business processes the CRM supported effectively, where teams depended on external systems and which requirements had not been sufficiently addressed during the original design. Rather than treating inconsistent usage solely as an employee adoption problem, I examined whether the deployed system could support the work those teams needed to perform.

This identified opportunities to bring additional workflows into the CRM and reduce fragmentation between operational tools.

One proposal to incorporate workflows managed through Smartsheet into the CRM was approved. However, implementation was not completed during my involvement.

Completing a CRM implementation is not the same as completing an operating-model transformation. When a platform does not support how teams actually work, inconsistent adoption may be a symptom of incomplete business requirements rather than resistance to change. Delivery accountability must also be accompanied by sufficient decision-making authority to address gaps discovered during implementation. Otherwise, a project can meet its defined scope while leaving the organization dependent on the fragmented processes it was intended to replace.

A completed CRM migration with significant operating-model gaps remaining

All four insurance channels transitioned to the shared CRM, completing the implementation within its established scope. The operational results were mixed.

Some teams adopted the platform extensively and were able to conduct their work effectively within it. Others continued relying on external tools because the deployed configuration did not adequately support their processes. Consequently, reporting and management visibility were more reliable for some channels than others.

The absence of integration with the organization’s internal customer database also meant that manual lead monitoring and data transfer remained necessary, including for teams otherwise committed to using the CRM.

The additional workflow-consolidation proposal received approval but was not implemented before my involvement ended.

The project therefore demonstrates both a completed technical migration and the limitations of implementing a predefined system design without resolving the operating requirements it does not accommodate.

DEALING WITH A SIMILAR CHALLENGE?

Has your CRM gone live while teams still depend on separate tools?

Has your CRM gone live while teams still depend on separate tools?

I can help distinguish training issues from missing business requirements, identify workflow and integration dependencies, and clarify the decisions needed to improve operational usefulness.

EXPLORE MORE WORK

REVENUE OPERATING SYSTEMS
HS

Start with the operating problem.

If a CRM or CPQ implementation has stalled, revenue handoffs are breaking, or teams are constrained by unclear ownership, I help establish the decisions and operating requirements needed to move forward.

Bring the specific operating problem. We can explore whether a focused engagement would help.

REVENUE OPERATING SYSTEMS
HS

Start with the operating problem.

If a CRM or CPQ implementation has stalled, revenue handoffs are breaking, or teams are constrained by unclear ownership, I help establish the decisions and operating requirements needed to move forward.

Bring the specific operating problem. We can explore whether a focused engagement would help.

REVENUE OPERATING SYSTEMS
HS

Start with the
operating problem.

If a CRM or CPQ implementation has stalled, revenue handoffs are breaking, or teams are constrained by unclear ownership, I help establish the decisions and operating requirements needed to move forward.

Bring the specific operating problem. We can explore whether a focused engagement would help.