Portfolio case study

QuoteWise: Motor insurance quote comparison and policy checkout platform

A motor insurance quote comparison and policy checkout platform that connects vehicle intake, driver details, insurer rules, policy feature comparisons, payment choices, and admin controls into one broker-ready web application.

Name changed to respect NDA.

Motor insurance quote comparison platform visual with vehicle details, insurer quote rows, policy feature toggles, checkout summary, and admin rule cards
Project scope

Product engineering, insurance quote workflow, admin rule management, payment flow, and legacy web application delivery

4
quote-to-policy journey steps
30
quote comparison positioning
Rules
insurer and agency pricing controls
Admin
broker operations console

Timeline

Insurance marketplace web application build with customer quote journeys and broker operations workflows

Buying motor insurance needed a faster digital path

Drivers needed a way to enter vehicle and driver details once, compare multiple policy options, understand included benefits, and move toward payment without calling each insurer separately.

  • Vehicle, driver, valuation, and policy data had to be collected across a guided flow
  • Quote comparison needed to make insurer premiums, features, repair options, and discounts understandable
  • Broker teams needed admin screens for agencies, companies, makes, categories, features, rules, users, and quote requests
  • The platform had to bridge customer-facing checkout with operational controls for pricing and policy configuration

A web marketplace for quote comparison, policy selection, and broker control

QuoteWise turns motor insurance shopping into a structured journey: vehicle lookup, driver capture, insurer quote comparison, policy feature review, checkout, and backend administration.

  • Step-based customer journey for vehicle details, driver details, quote comparison, account details, and checkout
  • Quote comparison cards with policy costs, insurer context, benefits, add-ons, terms confirmation, and buy-policy actions
  • Admin modules for insurance companies, agencies, body types, makes, categories, blacklists, users, and feature assignment
  • Pricing-rule workflows for agency repair, age, body type, excess, make, no-claim discount, premium, and nationality logic

Product surfaces

What the platform brought together

The work spanned core product operations, daily user workflows, data-heavy coordination, and resilient platform management.

Vehicle and driver intake

The customer journey captures the information needed to prepare quote options without forcing the user through separate insurer forms.

  • Vehicle year, make, model, trim, body type, engine size, VIN, and valuation-assisted data collection
  • Driver and account detail steps that keep quote context connected to the user journey
  • Saved quote requests that broker teams can review from the operations side

Quote comparison and policy selection

Insurer options are presented in a decision-friendly comparison flow with price, policy details, benefits, and add-on context.

  • Comparison screen with insurer rows, policy cost, insured value, agency repair context, and feature disclosure
  • Policy feature sections for legal cover, personal accident, breakdown, windscreen, courtesy car, and related benefits
  • Terms agreement and buy-policy actions that move the user from research into checkout

Checkout and payment choices

The checkout surface brings selected policy details, premium totals, tax rows, and payment options into one final step.

  • Payment summary with premium, VAT, total payable, selected policy detail, and insurer context
  • Card, installment, cash, and bank deposit payment-choice UI patterns
  • Secure-payment messaging and receipt-ready policy purchase flow

Broker admin and rules engine

Operations teams can manage the master data and rule tables that shape quote availability, discounting, exclusions, and premium logic.

  • Admin areas for agencies, companies, features, body types, makes, categories, blacklists, nationalities, and users
  • Rule screens for agency repair, age, body type, excess, make discounts, make eligibility, no-claim discount, and premiums
  • Authenticated management flows that separate operational controls from the public quote journey

Module depth

Dedicated product blocks for the highest-value workflows

For large platforms, the conversion story depends on showing how each major module solves a specific operating problem, not only listing features.

Customer journey

Quote Intake And Comparison

Drivers move through a guided flow that turns vehicle and driver details into comparable insurance options.

Source evidence includes VehicleDetails, DriverDetails, CompareQuotes, YourQuotes, and quote request models.

  • Vehicle lookup and valuation support reduce duplicate manual entry
  • Driver details remain tied to the selected vehicle and quote request
  • Policy comparison helps customers evaluate premium, benefits, and repair choices side by side

Operations layer

Insurer Rules And Master Data

The admin console gives broker teams a place to maintain the pricing and eligibility inputs behind the marketplace.

Source evidence includes RulesController plus agency, company, feature, make, category, body type, blacklist, nationality, and admin controllers.

  • Agency, insurer, feature, body type, make, category, nationality, and blacklist management
  • Premium, no-claim, excess, body type, make, and agency repair rules
  • Authenticated admin workflows for users and operational setup

Buyer priorities

What mattered most to the people evaluating the platform

Prospective buyers want to know whether the work solved real workflow, adoption, reliability, data, and operations problems. These priorities shaped the product decisions.

Conversion clarity

Insurance shoppers need confidence before they buy, especially when policy benefits and exclusions are hard to compare.

  • Step navigation explains where the user is in the quote-to-policy journey
  • Quote rows make premium and insurer choices easier to scan
  • Policy benefit toggles surface key coverage categories before checkout

Operational control

Brokers and insurance operators need to update rules and product data without changing customer-facing code for every pricing adjustment.

  • Master data modules separate agencies, companies, vehicles, categories, features, and users
  • Pricing-rule screens help maintain eligibility and discount logic
  • Quote request lists give staff a view into customer demand

Modernization readiness

The legacy MVC codebase maps a clear insurance marketplace domain that can be modernized into a typed API, modern frontend, and cloud deployment.

  • Controllers reveal stable boundaries for quote intake, comparison, checkout, rules, and admin operations
  • Razor views expose the real customer journey and broker back-office screens
  • Service integrations and data-access patterns can be lifted into safer typed service boundaries

System model

How the platform connects roles, workflows, and product surfaces

The product architecture brings every role into the same operating model, with shared data moving cleanly between web, mobile, media, and notification layers.

Quote-to-policy workflow

The customer journey moves from vehicle details and driver data to quote comparison, policy review, and checkout.

Broker and customer roles

Customers, brokers, insurers, admins, and support staff use the same platform through different controls and responsibilities.

Marketplace and operations layers

The quote journey, rules engine, insurer data, checkout flow, and admin console work together as one insurance platform.

Technology

The Stack We Used And Why

The stack section is written for buyers who need to understand the product architecture, operational trade-offs, and long-term maintainability of the system.

Web application

Used for the public quote journey, broker admin pages, Razor-rendered forms, comparison screens, and checkout surfaces.

ASP.NET MVCC#Razor ViewsBootstrapjQuery

Insurance data and rules

Used to manage insurers, agencies, vehicle attributes, policy features, premium rules, discount rules, blacklist data, and quote requests.

SQL-backed data accessRepository-style Common servicesInsurance rule tablesASP.NET Identity

Vehicle and quote integrations

Used to enrich quote intake with vehicle lookup, model-year, make, model, trim, body type, engine-size, VIN, and valuation workflows.

WCF service clientVehicle data API integrationVIN lookupQuote request workflow

Modern target stack

A suitable rebuild direction for the same insurance marketplace with stronger maintainability, observability, and secure configuration.

Next.jsTypeScriptPostgreSQLPrismaRole-Based Access ControlPayment Gateway Integration

Why A Rules Layer Matters

Insurance marketplaces depend on constantly changing pricing, eligibility, repair, discount, and policy feature rules.

  • Admin-maintained rules reduce the need for code changes whenever insurer logic changes
  • Feature assignment keeps policy benefit disclosure close to quote comparison
  • Blacklist and eligibility records help operations teams manage edge cases

Why The Customer Flow Is Step-Based

Insurance quote journeys collect sensitive and detailed information, so a step-based flow keeps the user oriented.

  • Vehicle details establish the quote context before driver data is requested
  • Comparison happens before checkout so the user can evaluate value and coverage
  • Account and payment details sit at the end after policy intent is clear

Delivery

How the product came together

The work moved from domain modeling to core platform delivery, mobile adoption, and operational hardening.

1

Map the insurance journey

Define the information customers need to provide and the points where broker teams need operational control.

2

Build comparison and checkout flows

Create the screens that help customers evaluate insurer options, review policy benefits, accept terms, and proceed to payment.

3

Add insurer operations

Layer in admin workflows for insurers, agencies, features, vehicle data, blacklist records, users, and quote requests.

4

Prepare modernization path

Use the legacy implementation as a product map for a modern insurance platform with typed APIs, secure secrets, and cloud-native deployment.

Operational depth

What made the platform usable after launch

The strongest case studies are not only feature lists. They show how the system is operated, monitored, governed, and improved when real users depend on it.

Pricing and eligibility rule coverage

Agency repair, age, body type, excess, make, make discount, no-claim, nationality, and premium screens support broker-side configuration.

  • Premium rules
  • Discount rules
  • Eligibility rules

Vehicle data enrichment

Vehicle lookup and valuation workflows help reduce form friction and keep quote inputs closer to insurer data requirements.

  • VIN lookup
  • Make/model/trim lists
  • Vehicle valuation

Quote request visibility

Customer quote requests can be reviewed by operations teams, giving brokers a path to follow up beyond the online journey.

  • Quote list
  • User records
  • Account details

Results

The measurable and observable lift from the work

The strongest improvements are the ones a buyer can connect to daily work: fewer disconnected tools, safer operations, clearer workflows, and more reliable product behavior.

Quotes

Comparison Flow

Customers can enter their details once and review insurer options in a structured comparison experience.

Rules

Broker Control

Operations teams can manage pricing, eligibility, feature, repair, and discount logic through authenticated admin screens.

Checkout

Policy Purchase Path

Selected policy details, premium totals, VAT rows, and payment choices are brought into a final checkout step.

Modernize

Rebuild Blueprint

The legacy MVC source provides a clear domain map for rebuilding the same insurance marketplace on a modern stack.

Outcome

A stronger operating system for motor insurance quote comparison platform

The platform reduced tool fragmentation and gave each role a clearer path from live activity to day-to-day action.

A customer-facing motor insurance marketplace journey for vehicle intake, driver details, insurer comparison, policy review, and checkout

Broker operations modules for insurer companies, agencies, features, categories, vehicle attributes, users, quote requests, and blacklist records

Rule management workflows for premiums, no-claim discounts, agency repair, excess, age, body type, make, and nationality logic

A public-safe modernization case study that translates private legacy MVC evidence into a complete motor insurance quote platform story

FAQ

Frequently Asked Questions About QuoteWise

Answers about the motor insurance quote comparison platform scope, platform model, technology choices, operational workflows, and related build patterns.

What Kind Of Product Does QuoteWise Represent?

QuoteWise represents a motor insurance quote comparison and policy checkout platform with a customer quote journey, policy comparison screens, payment choices, and broker-side rule management.

Why Do Insurance Quote Platforms Need Admin Rule Management?

Premiums, repair options, discounts, vehicle classes, eligibility, and policy features change often. Admin rule management lets broker teams update operational logic without rebuilding the customer journey for every change.

Can A Legacy ASP.NET MVC Insurance Platform Be Modernized?

Yes. The same quote intake, comparison, checkout, admin, rules, and integration boundaries can be moved into a modern frontend, typed API layer, secure configuration, payment gateway integration, and cloud deployment model.

Related services

Build a similarly ambitious product without starting from a blank page.

We can help scope the web, mobile, AI, media, and operating layers needed for your own platform.

Start a project inquiry