Software for insurance agency networks: platforms that aggregate carrier data, integrations with ERP and long-standing systems, migrations done with the service live.
For an insurance group we built the platform that replaced a twenty-year-old system, today used by more than 400 agencies in Northern Italy, and we keep making it evolve without stopping it. Here the constraints are carrier data, continuity of service and agencies that have to sell every day.
Where we step in
- 01Platforms for agency networks
- 02Carrier data synchronisation
- 03Sales, portfolio and accounting
What you find when you step in
An insurance agency network has layered software: a long-standing platform where selling and accounting happen, the data feeds that arrive from the carriers, the spreadsheets that fill the gaps between them. Every piece was born at a different time. One constraint binds them: the agency has to be able to sell today, and selling needs data from carriers that do not all send it the same way.
Between 2021 and 2023 we built, for an insurance group, the platform that replaced a twenty-year-old system, used today by more than 400 agencies in Northern Italy. Since then the platform has kept changing: microservices, micro-frontends, serverless infrastructure, a common schema across applications.
What we have done here
The new platform in place of the twenty-year-old system: a distributed system on AWS, Laravel and Node for the services, Vue for the interfaces, put into production one domain at a time with the old one switched off by degrees. Carrier data aligns every night and, where needed, in real time, on Redis queues governed by Horizon.
In between, the work that makes no headline but holds the rest up: synchronisations made repeatable and observable, the ERP integration made switchable while the ERP itself was changing, a serverless function over its limit in production fixed without a wholesale refactor.
How we work in insurance
Continuity before elegance: every change has a compatibility layer in front and a way back, because on the other side there is an agency in the middle of a sale. Data arriving from carriers is treated as input that will change: versioned formats, visible errors, synchronisations that can be re-run without duplicating anything. Acceptance tests readable by the people who use the system, not only by those who write it.
Here we bring above all custom software development, cloud and infrastructure and application security.
What we bring here
Constraints met here
Describe the system. We'll tell you what we see.
Ten minutes, one question at a time. At the end, our honest read of the case. It's the filter, before the call.