X Sigorta Product concept

Gradually renewing a 20-year-old policy system.

Agencies prepare quotes on one screen; the legacy core is modernised in stages, taking data and migration risks into account.

X Sigorta product concept with sample data: the agency portal's comprehensive motor insurance quotation screen puts vehicle details, coverage and package selection on one page; a TRY 18,420 Extended Comprehensive quote card and Issue Policy button appear on the right. Behind it is the legacy nine-screen policy entry interface navigated with function keys.
Policy renewal listFull screen ↗
Product concept: a solution study presented through screen designs, not an interactive demo. X Sigorta is fictional; screen data is illustrative.
Industry
Insurance
Capabilities
Platform Modernisation, Experience Design, Cloud & DevOps
Platform
Web

Problem and approach

Problem

At an established insurer, every policy passes through a single core system patched for twenty years.

In this scenario, 2,300 agencies prepare motor insurance quotes across nine screens, and the system closes for a weekend for every release. Most business rules exist only in the code and a few experts' memories; neither leaving the system untouched nor replacing it all at once is acceptable.

Approach

We plan to modernise the core through small, verifiable stages.

In a two-week discovery sprint, we extract business rules from code with domain experts and test a prototype with actual agencies in week three. The jointly scoped first phase, such as the motor insurance quote screen and event bridge, targets a launch in 6–12 weeks; migration of other products follows the roadmap.

Solution

One screen for the agency, supported by three components.

The X Sigorta concept's agency desktop dashboard, with sample data: a side menu; cards for active policies, September production, renewals due and average quote time; a monthly premium production chart, a product distribution doughnut chart and a recent policies table.
Policy distributionFull screen ↗
Agency dashboard: renewals, premium production and recent policies in one view. Migration continues behind the scenes; the agency sees a faster interface.
A migration map showing an intermediate stage of the X Sigorta concept's sample plan. At the top, the new platform contains the agency portal, a product-routing API gateway and quotation, policy, collection and business-rule services. A Kafka event bridge in the middle keeps both systems synchronised in both directions. Below, the legacy core is gradually retired: comprehensive motor, compulsory motor and business insurance are on the new platform, home and DASK earthquake insurance are at 64%, and remaining modules are queued.
New platform and migration bridgeFull screen ↗
Migration map: the new platform and legacy core synchronised through an event bridge.
  1. Quotes on one screen

    A nine-screen flow becomes one form. Vehicle, coverage and package share one page; the premium updates with every choice.

  2. Event-driven bridge

    The old and new systems stay synchronised through Kafka events. Both sides see the same policy throughout migration.

  3. Controlled release transition

    Blue-green deployment simplifies traffic switching in this scenario. Rollback of data changes is planned and rehearsed separately.

  4. Business rules catalogue

    Rules extracted from code are documented in a readable catalogue and protected by tests. The impact of changes is visible before production.

Scenario and scope

Example users

Agency user, product and operations specialist, IT team and data owner.

Example workflow

The agency prepares a quote in the new interface; results are compared with legacy rules and the authorised team reviews differences. An approved module opens to pilot users; rollout expands as data reconciliation is completed.

Decisions for a real project

Define source code and data access, the first module, side-effect-free parallel testing, a maintenance window and how new records will be preserved during rollback. Zero downtime is an illustrative target for this concept, not a guarantee for every real project.

Related service: Software modernization. You can list your own users and systems in the project brief tool.

Timelines, teams and technologies in this scenario are illustrative planning choices; actual scope, schedule and team are defined during discovery. Product names do not imply partnerships.

What we measure

%50Target: reduction in quotation preparation time
0Target: planned downtime during migration
%90Target: test coverage of catalogued business rules
%20Target: reduction in infrastructure cost

These targets are example measures defined for this scenario; actual results vary by project.

Technology and team

Technology

  • .NET 8
  • C#
  • Azure
  • Kafka
  • React
  • TypeScript
  • SQL Server → PostgreSQL

For scope, data synchronisation and delivery terms when modernising a core system in stages, see the software modernization page.

Suggested team 7 people

  • 1 solution architect
  • 1 product designer
  • 4 software engineer
  • 1 DevOps engineer

Your process

Are you working with a similar system? Let's schedule a 30-minute conversation about modernising a legacy policy system while managing migration risks.

Let's discuss this concept

This is an example, not a limit; we apply the same approach to similar processes in other industries.