Case study · Insurance and warranty

A warranty administration platform, built in 2013 and extended every year since.

Client A UK warranty administrator working in agricultural machinery, construction plant and motor
Since 2013
What we built Policy administration, claims, dealer portal, bordereaux, finance integration

The client.

A UK warranty administrator. It designs extended warranty schemes for agricultural machinery, construction plant and vehicles, sells them through dealer networks, and handles every claim that follows.

It is a business built on detail. A warranty on a tractor is measured in engine hours. A warranty on an excavator depends on what is attached to it. A warranty on a van has a component list with tiers. Every scheme has its own cover levels, limits, excesses and prices, and the client launches new ones regularly.

The problem.

In 2013 the client needed one system for all of it, and nothing on the market fitted. Packaged insurance platforms were built for mainstream products. Each could handle some schemes, and each would have left the rest to be run in spreadsheets alongside.

That mattered for three reasons.

  • Dealers. A dealer selling a machine wants to register the warranty there and then, not send a form and wait.
  • Claims. A handler deciding a claim needs the exact cover the customer bought in front of them, not a general description of the scheme.
  • Underwriters. The insurers behind each scheme expect accurate reports every month, in their own format.

What we built.

A single web-based platform that holds every scheme, every policy and every claim.

  1. 01
    A dealer registers a warranty. At the point of sale the dealer logs in to their own portal, chooses the scheme and enters the machine. The platform works out the cover and the price from the client's rules and issues the documents.
  2. 02
    The client's team runs the schemes. Products, cover levels, terms and rates are set up by the client's own staff. Launching a new scheme does not need a developer.
  3. 03
    A claim comes in. The dealer or repairer raises it through the portal. The platform checks it against the cover actually held: what is included, the limits, the excess.
  4. 04
    The claim is decided and paid. It goes to a handler with the right authority, is authorised, and the payment is passed to the finance system.
  5. 05
    The underwriter is told. Premium and claims bordereaux are produced from the same live data, in the layout each underwriter requires.

How it has grown.

The platform went live with the client's first schemes and has been extended every year since. As the client moved into new sectors, each brought its own kind of scheme, and the platform took them on without being replaced or rebuilt.

That is the practical argument for bespoke. A packaged product would have needed a workaround for each new scheme. This one gains a new product definition.

How we work together.

One team.

The developers who built the platform are the ones who support it today.

Hosted by us.

It runs on Microsoft Azure in UK data centres, with data encrypted at rest and role-based access.

Always moving.

New schemes, reports and features are added as the client's business changes.

Twelve years in.

The platform has been in daily use since 2013.

Start a project

Tell us what you need building.

Describe the process that is causing you trouble. We will tell you plainly whether bespoke software is the right answer and roughly what it would cost.

Send us a message