From a product idea to a complete SaaS for the insurance industry

We addressed a risk even though it was not part of the brief

The initial solution included custom multi-tenant sign-in built on AWS Cognito.

During analysis we identified risks in how individual customer organisations were separated. We described the problem, proposed changes and, together with the client, included them in further development.

It was not a feature visible on screen.

It was, however, something that could decide whether the product could be operated safely for multiple financial institutions.

Responsibility for the product does not end at the boundary of the original backlog.

Instead of an expensive service, we looked for a simpler way

One of the key parts of the product was scheduling meetings between the claims adjuster and other participants.

The first option relied on external services which, together with the rest of the cloud infrastructure, would have meant running costs of roughly USD 2,000–4,000 a month.

For a start-up, that difference is fundamental.

So we looked at the problem again and designed our own scheduling component built specifically for the needs of the product.

The resulting cloud architecture has estimated running costs of roughly USD 150 a month.

We did not optimise the infrastructure just to make it technically elegant.

We optimised it so that it made sense for the business that is meant to grow on it.

Individual features became one process

A calendar, e-mail, SMS, video calls, recordings or an AI transcript do not make a product on their own.

What mattered was connecting them into one process the user understands.

The claims adjuster therefore works with a single insurance claim, in which they can:

• schedule a meeting
• coordinate multiple participants
• send invitations and notifications
• hold a video call
• work with its recording
• view the full transcript
• quickly go through the AI summary

The individual technologies stay in the background.

The user sees one product.