Skip to content
AktwinsTrust. Transparency. Technology

Case study

A CRM built for insurance work, not generic contacts

We designed and built Jisper end to end as a SaaS CRM for an insurance-tech client: insureds, policies, locations, contacts, tasks, shared email and WhatsApp, plus Stripe subscriptions — on one product they can run.

ClientAn insurance-tech team that needed a CRM around policies and insureds, not a bolted-on contacts list.

End-to-end SaaS Product EngineeringInsurance

SaaSInsuranceProduct Engineering

Tech stack

  • AWS
  • Python
  • React
  • FastAPI
  • RabbitMQ
  • Celery
  • Stripe
All case studies

Insurance CRM with shared inbox and WhatsApp views

Jisper insurance CRM workspace

The problem

Insurance work does not fit a generic CRM

The team needed to hold insureds and policies, across more than one location, and keep contacts and tasks next to that record. Off-the-shelf CRMs treat that as notes on a person.

They also needed the day-to-day work in the same product: a Kanban board for tasks, a shared email inbox, WhatsApp, and a SaaS commercial layer with Stripe subscriptions. That is a product, not a spreadsheet with a login.

What we built

Jisper, built as an end-to-end SaaS product

We took Jisper from the brief through to a working SaaS product: React on the front, Python and FastAPI on the API, RabbitMQ and Celery for background jobs, Stripe for subscriptions, hosted on AWS.

  • 01

    Insureds, policies and locations

    • Records for insureds and policies, not just a contact card
    • Multi-location support so the same book of business can sit across sites

  • 02

    Contacts, tasks and a Kanban board

    • Contacts and tasks live on the work, not in a side tool
    • A Kanban board for the pipeline the team actually runs

  • 03

    Shared email and WhatsApp

    • Shared email so conversations are not trapped in one inbox
    • WhatsApp in the same product so messages sit with the insured and the policy

  • 04

    SaaS, billing and the jobs behind the UI

    • Stripe subscriptions so the product can be sold and billed as SaaS
    • RabbitMQ and Celery for background jobs so the product can send mail, messages and billing work without blocking the UI

What changed

One product for the book of business and the work around it.

  • Insurance records in the CRM

    • Insured and policy management in the same system as contacts
    • Locations handled as part of the product, not as a custom field

  • Work stays in Jisper

    • Tasks on a Kanban board, shared email and WhatsApp next to the record
    • The team does not have to bounce between a CRM, a mailbox and a chat tool to finish a follow-up

  • A SaaS they can run

    • Subscriptions through Stripe, hosted on AWS
    • An API and job queue built to carry the product after launch, not only the first demo

What this unlocks

Jisper is an insurance CRM we built and shipped as a SaaS product — policies, insureds, locations, the team's work, and billing — not a prototype of a contact list.

Need a SaaS CRM that matches how your book actually works?

Tell us what sits around the record today — policies, locations, mail, WhatsApp, billing. We'll tell you what belongs in the product.

All case studies