How mid-tier insurance carriers actually build a single customer view that holds up in production - the architecture decisions that work, the data engineering reality most vendors hide, and the 360-degree customer experience that follows.
In my decade running the Agent Portal product at Decerto, I've watched many mid-tier carriers fund "Customer 360" programs that produced beautiful slide decks and very little working data integration. The pattern is consistent. The carrier hires a vendor whose demo shows a perfectly unified customer record. Two years later, the underlying systems still don't talk, the producer still calls operations to check claim status, and the marketing team is still emailing the wrong household. The slide deck moved. The data didn't.
This piece is the operational view of what a single customer view (SCV) actually requires in 2026 - drawn from deployments where the data integration was the hard part, and the CRM software was the easy part. For the broader buying framework, see the 2026 buyer's guide to the best CRM for insurance agents.
Why the single customer viewmatters more in 2026 than ever
Insurance carriers carry customer data across many disconnected systems. A typical mid-tier P&C carrier I work with runs the policy administration system separately from claims, separately from billing, separately from marketing, separately from the agent portal, and often separately from each line of business's legacy stack. The customer is the same person across all of these. The data doesn't know that.
The cost shows up in three places.
- Operational inefficiency. Producers and customer service representatives spend a meaningful share of every day switching between screens, searching for information, and reconstructing the customer's history before they can serve them. Industry research from Datos Insights (formerly Aite-Novarica Group) on insurance CRM strategy has repeatedly flagged this "swivel-chair integration" cost as one of the largest and most persistent drains on producer and service rep productivity at carriers without a unified customer view.
- Missed financial opportunities. Without the unified view, cross-sell propensity scoring doesn't work. An auto customer with a new home purchase, who would have bought home insurance from the carrier if asked, instead gets generic marketing. Bain & Company's research on insurance customer loyalty has found that carriers who convert satisfied policyholders into active promoters see materially stronger retention and cross-sell economics than carriers who don't - and "the carrier knows me" is one of the largest single drivers of that promoter behavior.
- Customer attrition through service failure. A long-time high-value customer experiences a clunky claim because the adjuster lacks the full relationship context, then re-shops the policy. The single bad service interaction wasn't an isolated problem - it was a data integration problem with a human face.
Industry research from Datos Insights (formerly Aite-Novarica Group) on insurance CRM strategy has repeatedly found that most mid-tier P&C carriers have not yet achieved a full 360-degree customer view across PAS, CRM, and claims systems. Most are still working on it. This is not because the technology doesn't exist. It's because the data engineering is harder than the demo suggests.
The honest reality of building a single customer view
A note before we get to architecture. In my experience, identity resolution across legacy carrier data is far more data engineering than software. Vendors who pitch "Customer 360" as a software feature are misrepresenting the work. The hard part is the data layer:
- Identityresolution - the same person appears in PAS as John A. Smith, in claims as J.Smith, in billing as John Smith with a different address from three years ago.Resolving these to one customer master is the foundational work.
- Dataquality - missing fields, duplicate records, stale addresses, conflictingpolicy data. Carriers consistently underestimate the data hygiene work.
- Real-timevs batch - "real-time customer view" requires real-time dataintegration. Many carriers still run overnight batches from PAS to CRM. Theview is then 24 hours stale.
- Masterdata management (MDM) - which system owns which field? When the customerchanges their address through self-service, does that update propagate toclaims? PAS? Billing?
I tell carriers in the discovery call that the data engineering phase is typically 6-12 months. If a vendor tells you they can deliver a working Customer 360 in 90 days at mid-tier scale, ask which corners they're planning to cut.
CRM-first architecture - what it actually means
A CRM-first strategy makes the insurance CRM the system of record for the customer relationship - not the policy. It does not mean replacing your PAS, claims, or billing systems. It means integrating them as data sources into a central customer profile owned by the CRM.
Think of it as hub-and-spoke. The CRM is the hub. The policy administration system feeds policy data. The claims system feeds claims data. The billing system feeds payment records. The marketing automation platform feeds engagement metrics. The CRM holds the 360-degree view of who the customer is, what they own, what they've experienced with you, and what your relationship with them looks like.
For the deeper conversation on insurance CRM scope, see the role of AI in modern insurance CRM systems and how insurance CRM supports customer relationship management.
The architecture decisions that matter:
Two-way data flow, not one-way feeds
A nightly batch from PAS to CRM produces a view that's 24 hours stale. Real-time integration via APIs and event-driven webhooks produces a view that's current. The cost difference between one-way nightly and two-way real-time is meaningful in implementation, and the customer experience difference is meaningful in production.
Master data management with clear ownership
For each field on the customer record, one system owns the truth. Address might be owned by self-service (the customer updates it directly). Policy data might be owned by PAS. Claims history is owned by claims. The CRM consolidates the view but doesn't try to be the source of truth for every field. Carriers who skip this design step end up with three different addresses for the same customer across three systems.
Identity resolution before integration
If your customer "John A. Smith" exists three times across PAS, claims, and marketing, integrating those systems just gives you three customer records in the CRM. Identity resolution must happen first - typically through deterministic matching (exact field matches) layered with probabilistic matching (fuzzy matches with confidence scoring).
In practice, deterministic-only matching misses a meaningful share of records whenever there's a minor formatting difference, a typo, or a changed address - which is common in legacy carrier data spanning years. Probabilistic matching (fuzzy matches with confidence scoring) is what closes that gap. Carriers that skip the probabilistic layer routinely rediscover the same customer as "new" the next time a name is misspelled or an address changes.
Privacy and consent management built in
Customer 360 by definition pulls together everything the carrier knows about the customer. That triggers every privacy framework in scope - CCPA / CPRA, GLBA, GDPR for European policyholders, the NAIC's privacy model laws, state-level equivalents. Consent management must be part of the CRM design, not bolted on after launch.
How a 360-degree view changes the producer and service experience
Once the data is unified, the day-to-day for producers and service teams changes - a pattern McKinsey's research on customer experience in insurance also ties directly to faster, more profitable growth.
The features that show up in mid-tier deployments:
- Producer logs into the agent portal and sees the customer's full portfolio - all policies, all claims, all prior interactions, in one screen
- Service rep takes a customer call and starts from "I see you had a claim two months ago, how is everything going with that?" - not from "may I have your policy number"
- Marketing sends renewal communications that reference the customer's specific policies - not generic blasts
- Cross-sell propensity scoring shows the producer the next-best-product with the reasoning attached
- The customer self-service portal shows the same complete view the producer sees, in customer-appropriate terms
For the agent portal companion, see top features of an insurance agent portal.
Implementation - phased, not big bang
A CRM-first transformation is a multi-year program, not a 90-day project. The phased approach that works:
Phase 1 (months 1-3) - Discovery and data audit. Map every system holding customer data. Run a data quality assessment. Identify the worst data quality issues (duplicates, missing fields, stale addresses). Decide which systems integrate first.
Phase 2 (months 3-9) - Foundational integration. Build the PAS-to-CRM integration with two-way real-time data flow. Solve identity resolution. Establish master data management rules.
Phase 3 (months 9-15) - Customer-facing surfaces. Light up the unified view in the agent portal and service team workstations. Run training. Measure adoption.
Phase 4 (months 12-24) - Expansion. Add claims, billing, marketing automation, customer self-service.
The carriers who try to do this as one big-bang project routinely fail. The ones who phase it succeed - even if the timeline feels long.
How Decerto's Agent Portal and CRM approach SCV
A note on positioning. Decerto's Agent Portal and CRM-first architecture are built for mid-tier P&C carriers in the $500M-$5B GWP range. We are not the right fit for $5B+ enterprise carriers running Guidewire end-to-end. For mid-tier, what carriers tell us after deployment:
- Honestdata engineering scoping. We tell carriers in the discovery call that identityresolution is 6-12 months. We don't pretend it's a software feature.
- Hub-and-spokearchitecture by default. The CRM is the customer relationship hub. PAS, claims,billing, marketing automation integrate via real-time APIs.
- Two-wayintegration with insurance-native standards. ACORD AL3/AL5, IVANS Download forAMS integration, SAML 2.0 SSO with the carrier's identity provider.
- Customer360 surfaced in the producer workflow. Not a separate "Customer 360dashboard" the producer ignores - the unified view is the producer's dailyhome screen.
- Honestabout what won't work. We're transparent in the discovery call about whichscenarios we don't fit (enterprise scale, single-line carriers where the datasilos are minor) and which we do (multi-line mid-tier P&C with serious datafragmentation).
For the broader Decerto technology view, see the policy administration system as the core of digital insurance - the system the CRM-first architecture integrates with first.
FAQ
What is a single customer view in insurance?
A single customer view (SCV), sometimes called Customer 360, is a unified customer profile that consolidates data from every system the insurance carrier uses - PAS, claims, billing, marketing, agent portal, customer self-service. The SCV gives producers, service teams, and marketing one consistent view of who the customer is, what they own, and what their relationship with the carrier looks like.
How do you build a 360-degree customer view in insurance?
Build it in phases. Phase 1 is discovery and data audit - map every system holding customer data. Phase 2 is foundational integration (typically PAS-to-CRM with two-way real-time data flow and identity resolution). Phase 3 is surfacing the unified view in the producer workflow. Phase 4 is expansion to claims, billing, marketing automation. Total program usually runs 18-24 months for mid-tier carriers.
What is the difference between insurance CRM and Customer 360?
Insurance CRM is the relationship management system (the platform). Customer 360 (or single customer view) is what you build inside it - the unified view of each customer across all data sources. You can have a CRM without Customer 360 (just a relationship tool with siloed data). You can't have Customer 360 without a CRM-first or similar central architecture.
How long does it take to build a single customer view?
For mid-tier P&C carriers, a phased CRM-first program typically runs 18-24 months end to end, with first benefits (PAS-to-CRM integration plus producer-facing unified view) visible by month 9-12. Carriers who try to do this as a 90-day project at mid-tier scale routinely fail. Anyone promising 90-day Customer 360 should be asked which corners they're cutting.
What compliance frameworks apply to a single customer view?
For US carriers: GLBA, CCPA / CPRA (and state equivalents like Colorado CPA, Connecticut CTDPA), the NAIC's Insurance Data Security Model Law (#668), the NAIC's privacy model laws, NY DFS Cybersecurity Regulation. International: GDPR for European policyholders, including cross-border data transfer documentation. Consent management must be part of the CRM design, not bolted on later.
What is the biggest mistake carriers make with Customer 360 programs?
Treating it as a software purchase instead of a data engineering program. Identity resolution across legacy carrier data is far more data engineering than software. Vendors who pitch Customer 360 as a quick software install are misrepresenting the work. The carriers who succeed scope the data engineering honestly upfront.
Talk to Decerto about your single customer view program
If your team is about to fund a Customer 360 initiative, the most useful thing we can do in a first call is the honest scoping conversation. How fragmented is your current customer data? Which two or three systems integrated first would unlock the most producer and service value? What is your existing identity resolution approach?
What you'll get from the call: an operational Q&A with me and one of our integration architects, not a Customer 360 demo. We'll walk through your specific data landscape, your existing PAS, and the phased path that produces value in 9-12 months. No demo loop.
A note on fit: if you are a $5B+ enterprise carrier with a dedicated MDM team running Guidewire ecosystem tooling, Decerto is not your right partner. If you are mid-tier P&C ($500M-$5B GWP) and your customer data is fragmented across legacy systems, this is exactly the shape we built for - the same shape we deployed at Allianz, the Talanx Group (including Warta), and Generali across their European footprints.
Sources
- Datos Insights (formerly Aite-Novarica Group), CRM Solutions for US Insurers (March 2021)
- Datos Insights (formerly Aite-Novarica Group), CRM in Insurance: Overview and Key Issues (October 2020)
- Bain & Company, After Years of Customer Loyalty Programs in Insurance: What Works, and What's Next? (October 2025)
- McKinsey & Company, The Growth Engine: Superior Customer Experience in Insurance
- NAIC, Insurance Data Security Model Law (#668), full model text
- NAIC, Data Privacy and Insurance (overview of Models #668, #670, #672, #673)
- Federal Trade Commission, Gramm-Leach-Bliley Act (Privacy Rule, Safeguards Rule)
Subscribe to receive the latest blog posts to your inbox every week.
