Skip to content
TestimonialsGet a Free Blueprint

Case study · Insurance

Every broker's own portal, on one platform

An insurance technology company wanted to give independent brokers an online quote-and-buy journey under their own brand. This is how we built a white-label SaaS platform with a quote engine driven by rules, policy documents, renewals and the records a regulator expects.

Start a project like thisSee more of our work

Project overview

A white-label SaaS platform in a regulated market.

Industry
Insurance
Client
Confidential
Solution
White-label quote and policy SaaS
Platform
React and .NET on Azure
Timeline
32–40 weeks
Team
7 people
Tenancy
Multi-tenant, branded per broker
Rules
Products and pricing held as configuration
Compliance
Audit trail and document retention

Expected business outcomes

What the client set out to achieve

Brokers judge the platform by how quickly a customer can get a price and a policy.

  • Minutes From a customer starting a quote to holding a policy

    Questions, price, payment and documents in one journey.

    Target for standard risks

  • 2–4 weeks To launch a new broker

    A broker's brand, products and rates are configuration, not development.

    Target once insurer agreements are in place

  • 100% Of quotes and changes recorded

    Every answer, price and document version is kept.

    By design; required by the regulator

Business challenges

Where the client started

Brokers were losing customers to websites that gave a price at once.

Quotes

Forms emailed to the broker, and a price returned a day later.

Products

Rates in spreadsheets supplied by each insurer.

Documents

Policy schedules assembled by hand.

Renewals

Reminders that depended on a diary.

Regulation

A duty to show what each customer was asked and told.

Proposed solution

What the platform covers

One engine, with each broker's brand, products and rates on top.

  • Branded broker portals

    Each broker's own address, brand and product range.

  • Quote engine

    Questions, eligibility and pricing held as rules a product team can change.

  • Payments

    Card and instalment payments, with premiums split correctly.

  • Policy documents

    Schedules and certificates generated and versioned.

  • Renewals and changes

    Renewal invitations and mid-term adjustments.

  • Audit trail

    Every question, answer and price kept for each customer.

Project requirements

What the client asked us for

The request was a platform the client could sell to many brokers. That meant nothing about a single broker or a single product could live in the code.

Products, questions and rates were therefore built as configuration, with versions, so a rate change on a given date is a setting rather than a release.

What the project had to deliver

  • 01A branded journey for each broker
  • 02New brokers live in weeks
  • 03Rates changed without a release
  • 04A record the regulator accepts

Key challenges & considerations

What made it harder, and what we did

  1. Financial regulation on sales journeys and records

    What we did

    Compliance staff reviewed every journey, and each quote kept a full record of what the customer was asked and told.

  2. Rates that change on set dates and must not apply early

    What we did

    Rates were versioned with effective dates, and tested to make sure a new rate could not apply early.

  3. Insurers with different products and data requirements

    What we did

    Each insurer's product was held as its own configuration, with its questions and data requirements.

  4. Brokers migrating existing policies

    What we did

    Existing policies were imported with their renewal dates, and checked against the broker's own records.

What we watched for

  • Keep brokers and products out of the code
  • Version every rate and rule
  • Involve compliance from the first workshop
  • Test dates and effective times carefully

Development process

The rules engine before the first product

A pilot broker and its insurer reviewed every stage.

  1. Stage 1

    Discovery

    Products, rates and regulatory duties mapped with a pilot broker.

  2. Stage 2

    Rules engine

    Questions, eligibility and pricing as versioned configuration.

  3. Stage 3

    Quote and buy

    The customer journey, payments and documents.

  4. Stage 4

    White-labelling

    Branding, domains and product ranges per broker.

  5. Stage 5

    Renewals and migration

    Renewal cycle and import of existing policies.

  6. Stage 6

    Go-live

    Compliance review and security testing, then the first brokers.

Technology stack

Products held as configuration

The code knows how to quote; the configuration knows what to quote.

Front end

  • React
  • TypeScript
  • Themed portals

Back end

  • .NET
  • Azure SQL
  • Azure

Rules

  • Versioned rating tables
  • Rules engine
  • Document templates

Platform

  • Audit log
  • Automated tests
  • CI/CD
  • Penetration testing

Quality assurance & deployment

Tested as a product many customers share

A SaaS product is one codebase serving every customer, so a defect reaches all of them at once. Tenant isolation, billing and upgrades were tested as deliberately as the features.

  • Automated unit and API tests, run on every change
  • Tenant isolation tests: one customer can never see another's data
  • Billing, plan and permission scenarios tested end to end
  • Code review by a second engineer before anything was merged
  • Load tests at the expected number of tenants and users

Deployment

  • 01Renewals and migrationRenewal cycle and import of existing policies.
  • 02Go-liveCompliance review and security testing, then the first brokers.
  • 03Releases without downtimeUpdates shipped behind feature flags, with database changes that can be rolled back.
  • 04Monitoring and warrantyUptime, errors and usage per tenant monitored from day one, and six months of free bug fixing.

Final deliverables

A price in minutes, under the broker's name

A broker's customers now answer a few questions, see a price, pay and receive their documents in one sitting, on a site that carries the broker's brand.

The client adds a broker or a product by configuration, and can show for any policy exactly what was asked, answered and charged.

  • A branded portal for each broker
  • Rates and questions as configuration
  • Documents generated automatically
  • A complete record of every quote
Talk about a project like this

Handed over to the client

  • 01Production SaaS platformMulti-tenant, deployed and monitored
  • 02Source codeIn a repository the client can access
  • 03Billing and admin consolePlans, tenants and permissions
  • 04Test suite and pipelineIncluding tenant isolation tests
  • 05Six-month warrantyFree bug fixing after delivery

Success metrics

How success is measured

MeasureOutcomeHow it is measured
From a customer starting a quote to holding a policy Minutes Target for standard risks
To launch a new broker 2–4 weeks Target once insurer agreements are in place
Of quotes and changes recorded 100% By design; required by the regulator

Verified reviews

What clients say about our SaaS development work

Verified reviews from our clients on the same kind of work, published on Clutch.

5.0 27 verified reviews
See All Testimonials Read All Reviews on Clutch

Related

Services we used on this project

Free discovery call

Have an idea? Let's turn it into AI-powered software.

Book a free discovery call with our experts. Share your idea and we will help you shape the scope, timeline and budget, under NDA.

  • Free consultation
  • NDA before we talk
  • Transparent estimate
Book a Discovery Call [email protected]