Multiple policy admin systems create a bottleneck that disconnects insurers from their customers. The problem has a name.
11 March 2026
A large insurer running 40+ brands will typically operate multiple policy administration systems -- one per brand, per line, per acquisition. Each system holds its own customer records, claims data, and underwriting history. None of them talk to each other. The result is a communication bottleneck at the centre of the business.
Lemonade Insurance processes 96% of first notices of loss without a human touching them. Their AI settled a claim in 2 seconds -- reviewing the policy, running 18 anti-fraud algorithms, and paying the customer. They can do this because they have one system, one data model, one view of the customer. The bottleneck does not exist.
For traditional insurers, the bottleneck means the customer, the claims handler, the underwriter, and the board all live in different information universes. Data flows one way -- upward, into reports that nobody reads until the regulator arrives.
We looked at the structure. This is what we found.
There are fundamentally two architectures for how information moves through an insurance organisation. Most companies use the first. The ones winning use the second.
In the traditional model, a claims handler in Portsmouth has no idea what the underwriter in London priced the risk at, what the customer said on Trustpilot last week, or what the FOS upheld about a similar claim last month. Each silo generates its own reports. Nobody connects them.
In the connected model, every interaction -- a quote, a claim, a complaint, a renewal, a phone call -- becomes a node in a knowledge graph. The relationships between these nodes are the intelligence. The shape of the data is the answer.
These are not projections. These are audited results from a company that started in 2015 with no actuarial history, no broker network, and no legacy systems. What they had was a communication architecture where every piece of data feeds back into every decision.
Traditional insurers are not stupid. They are structurally constrained. The root cause is specific and identifiable:
1. Multiple policy admin systems. A group with 40+ brands will typically run a separate policy administration system for each brand, line of business, or acquisition. Each system holds its own customer records, its own claims history, its own underwriting data. A customer complaint about one brand never reaches the underwriting team that priced the policy under a different brand. The systems are the bottleneck. Everything downstream -- the one-way reporting, the disconnected customer experience, the regulatory blind spots -- flows from this.
2. One-way data flow. Because no single system holds the full picture, information can only move upward through management reporting. It never flows laterally between functions, and it never flows back to the point of customer contact. A claims handler cannot see what the customer said on social media. A social media manager (if one exists) cannot see claims data. The result is what we call the Panopticon problem -- a system designed for surveillance that nobody watches.
3. Legacy communication channels. Phone, email, and letter are still the primary customer contact methods. These are inherently one-to-one, synchronous, and unstructured. They generate no graph. Every conversation dies when the call ends.
| Capability | Disconnected | Connected |
|---|---|---|
| Claim notification | Phone call, 15-min hold | App message, instant acknowledgement |
| Fraud detection | Manual review, days | 18 algorithms in 2 seconds |
| Customer sentiment | Quarterly board report | Real-time graph signal |
| Cross-sell signal | Batch marketing campaign | Event-driven, contextual |
| Complaint resolution | Escalation ladder, weeks | Root cause visible instantly in graph |
| Employee knowledge | Tribal, lost on turnover | Encoded in graph, permanent |
| Regulatory evidence | Retrospective data gathering | Continuous, auditable provenance |
An ontology is a formal map of what an organisation knows and how those things relate. In insurance, this means: a Customer holds a Policy, which covers a Risk, which has a Claim, which references a Loss Event, which occurred at a Location, which was assessed by a Handler, who works in a Team, which reports to a Division.
When these relationships live in a knowledge graph rather than in spreadsheets, something emerges that no flat report can deliver: you can ask questions that cross boundaries.
Which handlers have the highest customer satisfaction for pet claims in the South East?
Which broker relationships produce policies with the lowest loss ratios?
Which complaint patterns predict FOS escalation before it happens?
These are not hypothetical questions. They are the questions that connected organisations answer every day and disconnected ones cannot even ask.
An insurer with 8 million customers and 30 million quotes per day sits on one of the largest behavioural datasets in the UK. Every quote that does not convert is a signal. Every claim that takes longer than average is a signal. Every customer who leaves without complaining is a signal.
The question is not whether these signals exist. It is whether anyone can hear them.
A connected communication architecture -- graph-based, real-time, bidirectional -- turns those signals into action. Not through more meetings, more reports, or more dashboards. Through structure. Through making the hidden connections visible.
The 60-point gap between testing and scaling is not a technology problem. It is a communication problem. The data exists. The connections do not.
The traditional insurance model is a panopticon: the insurer watches the customer. Surveillance-based underwriting, claims investigation, fraud detection. The customer submits; the insurer judges. Information flows one way.
Lemonade inverted this. They made themselves transparent to the customer. Open-source insurance policies on GitHub. Transparency Chronicles publishing their failures and internal metrics. A flat-fee model where the insurer has no financial incentive to deny claims. The Giveback program donating unclaimed premiums to the customer's chosen charity -- over $12 million since 2017.
The result: customers who feel watched become adversarial. Customers who feel trusted become honest. Dan Ariely, Lemonade's Chief Behavioral Officer, designed this deliberately. When fraud feels like stealing from charity rather than from a faceless corporation, dishonesty drops. When the insurer's incentives are visibly aligned with the customer's, trust becomes structural rather than aspirational.
The panopticon works. It just works better when the customer holds the watchtower.
We explored the Panopticon concept -- why one-way data architectures kill organisational performance -- in a separate analysis:
The Panopticon: Communications for Business →
And our analysis of pension fund AI concentration -- the same structural blindness applied to investment:
Your Pension's Hidden AI Bet →
Knowledge graphs. Ontology design. Communication architecture that makes hidden connections visible.
If your organisation has the data but not the structure, we should talk.