For many insurers, the hard part is not designing new digital channels. It is connecting them to systems that were built long before apps, partner platforms and embedded insurance existed.
Policy administration systems are very good at what they were built for: holding policies, billing and claims accurately. They were not built to serve a bank’s app, a travel booking or an AI assistant in real time. The lessons below set out a practical way to close that gap without stopping the business.
The connection problem grows faster than the business
Every new partner, channel or product usually means a new connection. When each one is built as its own project, the links multiply quickly. Ten systems connected directly to each other can need up to 45 separate links.
The cost shows up later, not at launch:
- Maintenance: each link needs its own fixes, tests and security updates.
- Change: updating one system means finding and retesting every link tied to it.
- Troubleshooting: a fault in one customer journey can sit in any of several custom connections.
- Knowledge: one-off integrations built under deadline pressure are often not documented well.
Over time, keeping existing connections running can take up more of IT’s effort than building new ones.
Aim for partner launches in weeks, not months
Partners such as banks, travel and mobility platforms, brokers and comparison sites need standard access to quote, bind and service.
A custom integration for every partner is hard to scale. Each one has to be built, tested and maintained on its own. A more scalable approach is one set of well-documented APIs, so each new partner connects to the same services instead of starting from scratch.
An API layer gives channels access without disturbing what works
A practical answer is an API layer between an insurer’s existing systems and everything that needs to reach them. Products, pricing and policy functions are exposed once, as reusable APIs. Apps, partners and AI tools use those APIs rather than connecting directly to the system of record.
This has three advantages:
- Lower risk: a new channel is built and tested against the API layer, not against systems that run the rest of the business.
- Reuse: the quote service built for one partner serves the next partner too.
- One place for control: security, versioning and monitoring are applied consistently instead of connection by connection.
Six practical lessons
1. Start with one high-value journey
Pick one product and one channel where speed matters, such as a partner quote and buy journey. Prove it there before scaling.
2. Build for the second partner, not just the first
Design APIs so the next partner can use them unchanged. Reuse is what makes each new launch faster.
3. Cover the whole lifecycle
A partner journey that can sell a policy but not service it or handle a claim sends customers back to the call centre. Plan servicing and claims access from the start.
4. Set governance early
Agree ownership, documentation and versioning before the number of connections grows. It is much harder to add later.
5. Show progress in stages
Visible milestones every few months keep leadership support. Waiting years for one big launch can erode it.
6. Involve frontline teams
Underwriters, claims handlers and service teams know where current systems fall short. Bring them in early to find problems while they are still cheap to fix.
What this looks like in practice
The announcement from Aviva Insurance Ireland DAC and insureMO (October 2026) describes the first implementation:
“Developed by Aviva Insurance Ireland DAC and enabled by insureMO’s technology, the first implementation is now live in Norway. Through distribution partner Kvikk Forsikring AS, Kvikk customers automatically benefit from day-to-day travel cover while in Norway, with travel insurance activating automatically when they travel abroad. Customers do not need to notify Aviva, activate cover or manage separate policies for different locations.”
It adds: “insureMO provided end-to-end capabilities, spanning product configuration, rating, policy administration, claims management and customer servicing, in collaboration with MSG Global, insureMO’s applications partner.”

Questions for leadership teams
- How long does it take today to connect a new distribution partner?
- How many of our integrations are one-off builds that only one or two people understand?
- Can partners reach servicing and claims, not just quote and bind?
- Who controls security, versioning and monitoring?
- Which one journey would prove the approach fastest?
Conclusion
The move from legacy systems to digital channels rarely happens in one step. A practical path is to connect what already works to new channels and partners through reusable APIs, one high-value journey at a time, planning for reuse, the full policy lifecycle and governance from the start.
insureMO is an insurance infrastructure platform for APIs, data and AI, with 2,500+ atomic insurance APIs. Learn more at insuremo.com.

Be the first to comment