# Insurance software development company UK: policy, claims and broker platforms

Canonical: https://appagentix.co.uk/industries/insurance-software-development/

We are a UK insurance software development company for insurers, MGAs, brokers and insurtechs: we build policy administration, claims, underwriting, bordereaux and reporting systems. We tie each UK rule to the data the system keeps and the checks it runs, and discovery ends with a fixed price in pounds.

- Platform first release delivered in 12 to 14 weeks, discovery included
- Renewal price test, bordereaux checks and audit trail built into the data model
- Code, data and accounts in your name from the first commit

## What does an insurance software development company build for UK insurers?

It builds the systems of record behind each policy: policy administration, claims, underwriting, broker and MGA platforms, and the data and reporting around them. Customer quote and claims apps sit on our insurance app development page. A first release covers one line of business and one core module, and a two-week discovery fixes its price. A first release for an MGA writing commercial property through brokers comes to £36,000 fixed. Price your own version with the calculator on this page, and see every price line we sell on our app development cost page.

- Discovery: 2 weeks, ending in a fixed quote
- First release: 12 to 14 weeks
- Full platform: 5 to 8 months

## Insurance software development services, module by module

We build insurance software as modules, each a system of record labelled by who works in it.

### Policy administration software

Holds each policy from quote to renewal, with every change kept as a dated version.

### Claims management software

Runs a claim from notification to payment, with reserves and recoveries, and every decision carries a recorded reason.

### Underwriting workbench

Rules settle clear cases and refer the rest, logging each decision with its reason and maker.

### Broker and MGA platform

Each coverholder sees only its own book, and binder limits on premium, class and territory are checked before cover is bound.

### Bordereaux and delegated authority

Monthly bordereaux are checked against the binder, and bad rows are held and sent back with the reason.

### Finance and documents

A premium and claims ledger with an accounting export, and documents drawn from the policy version in force.

## What is a policy administration system?

A policy administration system is the record of every policy you write: who is covered, for what, at what price and on which terms, with every document sent.

The hard part is time, because a policy changes mid-term, so the record keeps each version with the date it takes effect. A claim dated 3 March is checked against the cover in force on 3 March.

We build the record this way from the first sprint, because adding dated versions later means rebuilding the data model.

### What the record must keep

- The date each version takes effect
- Who changed what, and when
- The price and how it was built
- Every document sent, exactly as sent

## How insurance software sits between your core system and everything around it

When your old system has an API, we connect to it. When it has none, the platform works from a read-only copy of its database or nightly export, and changes go back only through a route you approve.

1. **Your core or policy system.** Stays the record until you choose to move
2. **Integration layer.** Every link in one place, with retries and a log
3. **Policy and claims services.** The modules your staff work in
4. **Broker and MGA portal.** Each firm sees its own book
5. **Documents and finance.** Letters, ledger and accounting export
6. **Data store and reporting.** Outcome tables and regulatory feeds

## Which UK rules change how insurance software is built?

We write insurance software: we give no legal advice and hold no regulated permissions. Whether a rule covers your firm is a question for your compliance lead or adviser. Each date below is as its publisher gave it, checked in November 2026.

### ICOBS 6B renewal pricing

Applies to: Home and motor insurance only

What it changes in the build: Since 1 January 2022, a renewal price must not be higher than the equivalent new business price, tested when the renewal notice is prepared. Firms must not systematically discriminate by tenure, must keep written records, and a senior manager (or a director, outside the senior managers regime) attests each year by 31 March. The rating service we build stores both prices and holds back a renewal that fails, and tenure checks stay as a dated record you can export.

### Consumer Duty outcome data

Applies to: FCA firms whose products reach retail customers

What it changes in the build: Firms must monitor the outcomes retail customers get and report them to their governing body at least once a year. In a review of 20 larger insurance firms, the FCA found some approaches focused on processes completed, not outcomes delivered. We build outcome tables from the policy and claims records, with a board-report export.

### ICOBS claims handling

Applies to: Insurers and those acting for them

What it changes in the build: The FCA says insurers must treat customers fairly when handling claims, and handle claims promptly and fairly. So each claim stage has a clock, every decline or part-payment has a recorded reason, and the customer can be sent a status at any point.

### Solvency UK reporting

Applies to: Firms within the scope of Solvency UK

What it changes in the build: From reporting reference dates of 31 December 2024, returns go in XBRL on the Bank of England taxonomy through the BEEDS portal. Taxonomy v2.2.0 applies from 1 January 2027, to returns whose reference date is 31 December 2026 or later. We build the feed with a versioned mapping to each template, and your actuarial and finance teams sign off the returns.

### Lloyd’s delegated authority reporting

Applies to: Managing agents, coverholders and brokers placing at Lloyd’s

What it changes in the build: All syndicates must collect data in line with the Coverholder Reporting Standards. Core reporting covers binders incepting since July 2017. In May 2026 the market’s Data Council said a Core Data Record for delegated binders was still being developed. In the platforms we build, each binder has its own checks and mapping, so a new version is a mapping change.

### UK GDPR

Applies to: Firms that process customer data

What it changes in the build: A data protection impact assessment comes before high-risk processing, and the ICO cites an insurer processing customer data as large-scale processing. The ICO expects standard retention periods to be documented, and firms must be able to restore access to data in good time after an incident. We build retention rules per record class, a route to a person for automated declines, and tested restores.

### Operational resilience and third parties

Applies to: Insurers, including Lloyd’s managing agents

What it changes in the build: Incident and third-party rules take effect on 18 March 2027. Under them, firms will keep a register of material third-party arrangements and file it yearly, so we build a supplier register you can export.

## Where each rule lands in the system

Discovery ends with this map filled in for your firm.

| Rule | System behaviour |
| --- | --- |
| ICOBS 6B renewal pricing | Rating service stores the new business price beside each renewal price |
| Consumer Duty outcome data | Outcome tables from policy and claims records, exported as a board report |
| ICOBS claims handling | A clock on each claim stage and a reason on each decision |
| Solvency UK reporting | Versioned mapping from your data to each template |
| Lloyd’s delegated authority reporting | Checks and mapping set per binder |
| UK GDPR | Retention rules per record class, a route to a person and tested restores |
| Operational resilience | Supplier register you can export |

## A renewal price test record

The renewal pricing rules apply to home and motor insurance only, and the test runs when each renewal notice is prepared.

**Renewal price test, notices prepared 2 November 2026**

| Policy | Renewal date | Renewal price against the equivalent new business price | Result | What happens next |
| --- | --- | --- | --- | --- |
| HM-204118, home | 4 December 2026 | Lower | Pass | Notice released |
| MT-337902, motor | 6 December 2026 | Higher | Open | Renewal held back; the reset to the new business price awaits underwriter approval |
| MT-338440, motor | 9 December 2026 | Equal | Pass | Equal is not higher, so the notice is released |
| HM-205377, home | 12 December 2026 | Higher, reset to equal | Pass after fix | Reset approved and the notice released |

The tenure check and the test result are stored with each policy, ready for the annual attestation.

## What are the four stages of the insurance claim process?

The claims module we build models four stages: report, check, decide, and pay and close. Stage names vary by insurer and by line, so ours are settings you can rename or split.

Report captures the loss and the policy version in force on the day. Check covers the cover, the excess and any fraud flags. Decide sets the outcome and the reserve. Pay and close handles payments and recoveries.

The FCA’s rules require firms to handle claims promptly and fairly, so each stage runs a clock, and a slow claim shows up before the customer chases. Every decision records its reason, and the customer can be sent a status at any time.

At the volumes below, those clocks and recorded reasons are what let your team answer a complaint with evidence.

## Claims management software: claim volumes across the market

- **£11.9 billion** paid out by motor insurers across 2.5 million claims in 2025 (Association of British Insurers, 2025 figures)
- **£6.1 billion** paid out in property claims in 2025, the highest annual total on record (ABI, 2025 figures)
- **13,420** new complaints about car or motorcycle insurance, with a 35% uphold rate (Financial Ombudsman Service, 2025/26)

## Can AI do insurance underwriting?

Partly. Rules or a model can settle the clear cases, such as a standard risk inside every limit. The rest go to a referral queue, where an underwriter decides with the reasons in front of them.

UK GDPR restricts solely automated decisions with legal or similarly significant effects, as the ICO’s draft guidance of 31 March 2026 sets out. So a decline or price decision made by a model has a route to a person, and we test that route.

The rules or model are first tried on your own closed cases, and you get the list of misses before launch. The monthly running cost sits on the quote beside the build price.

## How broker and MGA software checks a monthly bordereau

Every broker and MGA platform we build runs this check, binder by binder, before data reaches the ledger. Lloyd’s standards define the core data; the checks below are binder terms.

**Bordereau check, binder B-2207, October 2026**

| Row | Check | Value received | Result | What happens next |
| --- | --- | --- | --- | --- |
| 14 | Inception inside the binder period | 1 October 2026; binder runs for calendar 2026 | Pass | Posted to the premium ledger |
| 22 | Risk location inside the territory | Belfast; binder territory is Great Britain | Open | Held and sent back to the coverholder with the reason |
| 31 | Gross premium equals the sum of the instalments | Gross premium above the instalment total | Pass after fix | Coverholder added the missing instalment and resubmitted |
| 38 | Class of business allowed by the binder | Commercial property | Pass | Posted to the premium ledger |
| 45 | Claims paid within the limit | Claims paid below the binder claims limit | Pass | Posted to the claims ledger |

A new reporting standard means a new mapping, not a rebuild. Delegated underwriting brings in about 45% of Lloyd’s premium income, as the figures below show.

## Delegated authority at Lloyd’s, in figures

- **About 45%** of Lloyd’s premium income comes through delegated underwriting (Lloyd’s, November 2026)
- **3,415** coverholder global branches and 412 service companies listed by Lloyd’s (figures as of 9 November 2026)

## Build, buy, extend or wrap your core insurance software?

Most firms do not need a new core system, while custom insurance software development pays off on the parts that win business.

What should you do with your core system?

- If Your lines are standard and a vendor core system already fits them, choose **Buy and extend**. The vendor carries the core, and we build the portals, feeds and integrations around it.
- If Your rating, binders or referral rules set you apart, choose **Build that module, buy the rest**. The part that wins business is yours to change, while plain parts such as accounting stay bought.
- If The old system works but has no API, choose **Wrap it**. A read-only copy and an integration layer feed its data to new modules, moved one at a time.
- If The old system blocks every change and its vendor support is ending, choose **Replace in stages**. Each stage runs beside the old system until the figures match. The data decides the work, so it is quoted after discovery.
- If One team needs a fix this quarter, choose **A single module on its own data**. A claims tracker or bordereau checker can run alone and link up later.

## Records systems we have built

A few examples from the many systems we have built. Each has user roles, controlled access and links to the systems around it, the same shape as a policy platform.

### Clinic records system

Healthcare

Eight modules take a patient from registration through to billing. Doctors, patients and clinic staff each have their own view, and a link to the laboratory exchanges data over HL7 and FHIR.

[Read the Clinic records system case study](https://appagentix.co.uk/our-work/clinic-records-system/)

### MyUTHealth patient portal

Healthcare

A patient portal app joined to a health provider’s record system. Patients ask for visits, read their test results, reorder medicines and write to their care team.

[Read the MyUTHealth case study](https://appagentix.co.uk/our-work/myuthealth/)

## How an insurance software build runs, week by week

A 14-week first release for one line of business. More than 95% of our projects are delivered on or before the agreed date. Two stages set it apart from an app build: migration rehearsals and a parallel run beside your old system.

### Discovery and system map (Weeks 1 to 2)

Every system a policy touches goes on a map, and we draft the data model and agree one line and one core module.

You receive: System map, data model, rules map and a fixed quote.

### Data model and roles (Weeks 3 to 4)

The dated policy record, staff roles and the audit trail come first, because every module rests on them.

You receive: A signed-off data model and roles.

### Module sprints (Weeks 5 to 10)

We build the core module and its system connection in three two-week sprints, and you test each build on sample data.

You receive: A testable build per sprint.

### Migration rehearsals (Weeks 10 to 11)

Where old policies move across, we rehearse the move twice on a copy, and policy counts and premium totals must match.

You receive: A reconciliation report per rehearsal.

### Test run on your policies (Week 12)

Your own policies run through renewals, changes and claims in the new system, and every miss is listed with its cause.

You receive: A test report, misses included.

### Parallel run and cut-over (Weeks 13 to 14)

Old and new systems handle the same work side by side until the figures agree, and you choose the cut-over day.

You receive: A difference log and a cut-over plan.

### Run and improve (Monthly)

For 3 months after launch, fixes cost nothing extra, and after that, monthly support starts.

You receive: Monthly figures on errors, data checks and running cost.

## How you can work with us

- **Ways of working.** Fixed price, time and materials, or a dedicated team.
- **Payment.** You pay by milestone.
- **Team.** A project team is usually 4 to 6 people.
- **First conversation.** A free 30-minute consultation.
- **Replies.** We reply to new enquiries within 30 minutes.

## How much does insurance software development cost in the UK?

A first release costs £20,000 to £40,000, excluding VAT, for insurer, MGA, insurtech and insurance broker software development alike. Each stage below lists what you receive, and the calculator below prices your own mix.

| Option | Price | Time | Includes |
| --- | --- | --- | --- |
| Discovery | Deducted from the build | 2 weeks | A map of your systems, the data model, a rules map and a fixed quote. |
| Insurance platform first release | Quoted after discovery | 12 to 14 weeks, including discovery | One line of business, one core module, roles and audit trail, one system connection, a read-only staff view and a test run on your own policies. |
| Full insurance platform | Quoted after discovery | 5 to 8 months | More than one line, the modules you need, more system connections and the reporting feeds. |
| Replacing a core policy system | Quoted after discovery | Set in discovery | Staged replacement with migration rehearsals and a parallel run. |
| One AI feature | Quoted after discovery | 6 to 10 weeks | A whole workflow, for example reading claim or submission documents, tested on your closed cases. Reading one claim document type is a smaller job, 3 to 4 weeks. The running cost is on the quote. |
| Support | After launch | monthly | We watch the platform, fix faults, apply updates and send a report each month. A 3-month minimum, then 30 days’ notice. |

The first release starts above our general MVP floor because the data model and audit trail come first. Request a quote to book discovery.

## Estimate your insurance software build in a minute

Pick the modules your first release needs.

Discovery, a systems map, the data model, roles with an audit trail, a staff records view and a first system link: £9,000 to £12,000, 7 to 8 weeks.

### Product lines

- One line, fixed rating tables: included
- Several lines, own rating each: £6,000 to £10,000

### Policy data

- Start clean, no migration: included
- Migrate one policy file, 2 rehearsals: £6,000 to £10,000

### Connections beyond the first

- None: included
- One more system with an API: £2,500 to £4,000
- Several, or an old system, no API: £6,000 to £10,000

### Modules

- Policy changes and renewals: £6,000 to £10,000
- Claims, notification to payment: £7,000 to £12,000
- Underwriting and referral queue: £5,000 to £9,000
- Broker or MGA portal: £6,000 to £10,000
- Schedules, certificates, letters: £3,000 to £5,000
- Bordereaux import and checks: £6,000 to £10,000
- Premium and claims ledger: £5,000 to £8,000
- Renewal price test and outcome data: £4,000 to £7,000
- Working admin: edit, roles, audit: £9,000 to £14,000
- Management dashboard, 3 to 5 views: £8,000 to £12,500
- Solvency UK data extract: £8,000 to £12,000
- Reading one claim document type with AI: £8,000 to £12,000

This estimate is not a quote and excludes VAT and vendor licence fees. Each option is priced from its days of work at £500 a day, and AI work at £600. A selection above £90,000 is quoted after discovery.

## Who owns the code, the data and the accounts, and what is not included?

Whichever insurance software development company you hire in the UK, get ownership in writing. Everything we build belongs to you, in writing.

- **Code.** Held in your own repository from day one and assigned to you on payment.
- **Data and accounts.** Cloud accounts and databases sit in your company’s name, and we join as invited users. An exit is a handover, not a migration.
- **Supplier register.** Lists each service, the data it holds, its region and its owner, ready for your outsourcing review.
- **Access.** Staff work through named roles, and the audit trail logs every change.
- **Audit.** Your accounts, code and logs sit in your name, so your own auditors can inspect them.
- **Refund.** If we do not deliver what the written scope promises, we refund what you paid for the undelivered work within 7 days.
- **Fixes after launch.** Covered by the build price for the first 3 months.
- **Support terms.** A monthly plan. The minimum term is 3 months, then 30 days’ notice ends it.
- **Not included.** Vendor licence fees, regulator submissions and legal advice. Your firm files its own returns.

## Questions about custom insurance software development in the UK

### What tools do underwriters use?

Underwriters work with rules and rating tables that price a risk, data checks that flag gaps, and a referral queue for cases outside their authority. The underwriter’s file holds the submission, notes and decision, and an audit trail records who decided what, and why. In the insurance software we build, these sit in one workbench.

### Can AI do insurance underwriting?

Partly: rules or a model can settle a standard risk inside every limit, while referred cases go to an underwriter. UK GDPR restricts solely automated decisions, so a model’s decline or price decision has a route to a person, which we test. The rules are first tried on your own closed cases, and you see the misses before launch.

### What is an MGA company?

A managing general agent works under delegated authority from an insurer. It can bind cover, and often handle claims, within limits the insurer sets in a binder. Its system must check those limits, send bordereaux to the insurer and refer anything outside its authority.

### What is the best software for processing insurance claims?

In our view, the best is the one that fits your line, your claim volume and the systems it must feed. A standard book may suit bought claims management software, while unusual cover or a long delegated chain may need a built module. The decision table above sets out each case.

### What is underwriting automation?

It means rules or models settle the clear cases, and a referral queue carries the rest to an underwriter, so a person makes the decisions that matter. UK GDPR restricts solely automated decisions with legal or similarly significant effects, so every decline gets a route to a person.

[Agentic AI development](/services/agentic-ai-development/)

### What is an agency management system for insurance?

It is the system a broker or agent uses to run the business: clients, policies, documents and commission. It tracks renewals and holds each client’s file. We build the portals, data feeds and integrations around it, so it can exchange data with insurers, MGAs and the broker’s own reporting.

## Related pages

- [Insurance app development](https://appagentix.co.uk/industries/insurance-app-development/)
- [Software modernisation](https://appagentix.co.uk/services/software-modernisation/)
- [Custom CRM and ERP development](https://appagentix.co.uk/services/custom-crm-erp-development/)
- [Web app development company](https://appagentix.co.uk/services/web-app-development-company/)
- [IT staff augmentation](https://appagentix.co.uk/services/it-staff-augmentation/)
- [Fintech app development](https://appagentix.co.uk/industries/fintech-app-development/)
- [Healthcare software development](https://appagentix.co.uk/industries/healthcare-software-development/)

By Hemant Paliwal, Senior SEO Expert, AppAgentix. Reviewed November 2026.

[Book a call](https://appagentix.co.uk/requestaquote/)
