Insurance broking software in 2026: what a small UK brokerage should actually test

Seven tests for insurance broking software in a small UK brokerage: client records, compliance evidence, claims, renewals, reporting, integrations, exit.

By FCB.ai, ORIS editorial teamEditorial lead: The ORIS editorial teamPublished on Updated on 9 min read
Contents
  1. What you are actually buying
  2. The seven tests, in one table
  3. 1. The client and policy record
  4. 2. Compliance tracking you can evidence
  5. 3. Claims workflows
  6. 4. Renewals as a worked queue
  7. 5. Reporting for the Consumer Duty, not only for sales
  8. 6. Integrations: what works today
  9. 7. Cost, including the cost of leaving
  10. A selection process for a small brokerage
  11. Where WhatsApp fits in the stack
  12. Pitfalls to avoid
  13. Frequently asked questions

Insurance broking software for a small UK practice is not one product. It is a system of record for clients, policies and money — the broker management system, or BMS — plus whatever sits around it for messaging, tasks and reporting. The right choice is the one that lets your team service a client, prove what was said and done if the FCA or the Financial Ombudsman asks, and leave with your data intact if you ever switch. Everything else in a vendor demo is secondary.

That sounds obvious, but most small brokerages buy on the demo: a clean dashboard, a quote screen, a promise about integrations. This guide gives you seven tests to run instead, the questions that expose a weak answer, and a selection process that fits a firm where the principal is also the compliance officer.

What you are actually buying

Vendors use "BMS", "CRM" and "platform" loosely. Before comparing products, separate the three jobs:

  • The system of record: clients, policies, insurers, premiums, commission, client money and insurer ledgers, documents. This is the core of a BMS and the part you can least afford to get wrong.
  • The relationship layer: who to contact, when, about what — renewals, reviews, cross-sell, lapsed clients. Some BMSs do this well, many do it as an afterthought, which is why firms bolt on a CRM.
  • The conversation layer: email, phone notes and, increasingly, WhatsApp. This is where advice is actually given and where record-keeping most often fails.

One platform can cover all three, or you can combine a BMS with specialist tools. Neither is right in the abstract. What matters is that the joins between them are explicit, and that the record the regulator would ask for exists in one place. If you are still running the book on spreadsheets, our spreadsheets vs CRM comparison covers that first step.

The seven tests, in one table

FeatureWhat to ask in the demoRed flag
Client and policy recordShow me one client with a household, a commercial policy and a lapsed policy on one screen.Separate records per policy with no link between them.
Compliance trackingWhere is the demands and needs statement, the complaint log and the audit trail for this client?"You can upload that as a document."
Claims workflowTake me from first notification to settlement, with every chase recorded.Claims live in a free-text notes field.
RenewalsShow me the renewal pipeline for next quarter and who owns each item.Renewals are a report you run, not a queue someone works.
Reporting and MIWhat would I put in front of the board for the Consumer Duty review?Only sales and commission reports.
IntegrationsWhat connects today, in production, for a firm my size — and what is on the roadmap?Every answer is "via our API".
Cost and exitWhat does it cost to leave, and in what format do I get my data back?No written answer on data return.

1. The client and policy record

The unit of work in a small brokerage is the client, not the policy. A family has motor, home and travel; a director has a commercial package and a personal one. Software that files everything by policy forces your team to rebuild the relationship in their heads every time the phone rings. Test it with a real, messy client from your own book, not the vendor's sample data.

2. Compliance tracking you can evidence

The wider UK framework for a brokerage (FCA authorisation, ICOBS, PECR consent, the Ombudsman) is summarised on our United Kingdom broker page. For software, the baseline is SYSC 9.1.1R: orderly records of your business and all services and transactions, sufficient for the FCA to check that you have complied with your obligations to clients. Software does not make you compliant, but it decides whether that evidence is a by-product of normal work or a separate chore nobody does on a Friday.

Ask where the demands and needs statement sits, how a complaint is logged and tracked, and whether every change to a record is timestamped with who made it. Then ask the same question about conversations. If advice is given on WhatsApp and the thread lives on an adviser's phone, no BMS will fill that gap — our guide to archiving WhatsApp under SYSC and ICOBS explains what a defensible record looks like.

3. Claims workflows

A claim is the moment a client judges the broker, and in most small firms it is also the least structured process. Good software gives each claim a status, an owner, the insurer's reference, and a history of every chase. Ask to see how an adviser knows, on a Monday morning, which claims have gone quiet. If the answer is "they check their inbox", the software is a filing cabinet.

4. Renewals as a worked queue

Renewal is where a small brokerage makes or loses its year. The test is whether the system turns upcoming renewals into assigned tasks with dates, so that remarketing, the renewal invitation and the client's decision are all recorded against the policy. Commercial lines need the longest lead time; our commercial renewals playbook shows a working sequence.

5. Reporting for the Consumer Duty, not only for sales

The Consumer Duty requires firms to put customers' needs first and to monitor the outcomes they deliver, and the FCA keeps publishing good and poor practice on outcomes monitoring. A small firm does not need a data team, but it does need the software to answer plain questions: how many clients renewed, how many lapsed and why, how long claims took, how many complaints came in and how they were resolved. If the reporting only shows premium and commission, you will be building the board report by hand every year. Our guide to the four Consumer Duty outcomes and the evidence on each client file lists what those reports need to show.

6. Integrations: what works today

This is where demos are most optimistic. Separate three things: connections that run in production for firms like yours, connections that exist but need a project, and roadmap. Ask for the first list in writing. The floor, for any tool you add around the BMS, is clean import and export — CSV at minimum — so that you are never locked into re-keying.

The FCA's outsourcing provisions in SYSC 8 apply to most insurance intermediaries as guidance rather than rules, but the questions they raise are the right ones for any critical software supplier: does relying on this vendor add undue operational risk, and will you keep effective access to your data?

7. Cost, including the cost of leaving

Compare the full cost, not the licence line: implementation and data migration, training, extra modules you will need in year two, integrations priced separately, and support. Then price the exit. Under UK GDPR the vendor processes client data on your behalf, and the ICO's guidance on controller–processor contracts expects the contract to say what happens to the data when it ends. Get the format, the timing and any fee for returning it written into the agreement before you sign, not when you are trying to leave.

A selection process for a small brokerage

  1. Write down your five worst processes today — the ones that generate complaints, missed renewals or rework. These become your test scripts.
  2. Shortlist on the system of record first. Messaging, marketing and AI features are easier to add later than a ledger is to replace.
  3. Run the demo on your data. Send the vendor anonymised real cases and ask them to walk through them.
  4. Get integrations and data return in writing, including what is live, what needs a project and what is roadmap.
  5. Do the supplier due diligence you would expect an auditor to see: security, where data is hosted, sub-processors, the processor contract, business continuity.
  6. Plan the migration as a project, with an owner, a cut-over date and a check that every active policy arrived with its history.
  7. Review after one full renewal cycle. That is the first honest test of whether the software fits.

Where WhatsApp fits in the stack

Many UK clients now prefer to answer a message rather than a call, and advisers already use WhatsApp — often from their own phones. That is the gap most BMS evaluations miss: the software records the policy perfectly while the conversation that led to it sits outside the firm. Our piece on a shared WhatsApp inbox under the Consumer Duty sets out why that matters.

ORIS is built for that conversation layer rather than as a replacement BMS: a shared inbox on the brokerage's own WhatsApp Business number, Customers & Segments with risk and engagement scores, campaigns from Meta-approved templates, lifecycle triggers for renewals and policy anniversaries, and AI draft replies an adviser approves. Clients come in by CSV import and data goes back out by CSV export; connection to the tools a firm already uses is scoped per project. Two messages of the kind a small practice would send from a shared number:

Hi {first_name}, your home insurance with {insurer} renews on {date}. We are checking the market for you and will send the options this week. Anything changed at the property we should know about? — {adviser}, {firm}

Hi {first_name}, quick update on your claim {claim_ref}: the loss adjuster has the photos you sent and we have asked the insurer for a decision date. We will message you as soon as we hear. — {firm}

Pitfalls to avoid

  • Buying the demo instead of testing your own awkward cases.
  • Accepting "we integrate with everything" without a written list of live connections.
  • Leaving client conversations on personal phones while the new system records everything else.
  • Signing without a data-return clause, then discovering the exit fee at renewal of the contract.
  • Migrating active policies without their history, so the first complaint after go-live has no file behind it.

More on running the practice day to day is in our organisation articles.

Frequently asked questions

What is the difference between a BMS and a CRM for insurance brokers?

A broker management system is the system of record for policies, insurers, premiums, commission and client money. A CRM manages the relationship: contacts, tasks, pipelines and campaigns. Some BMSs include CRM features; many small brokerages run a BMS with a separate relationship or messaging tool alongside it.

Does the FCA require a particular type of broking software?

No. The FCA does not approve or require any product. It requires orderly records sufficient to show you have met your obligations to clients, under SYSC 9, and expects you to monitor customer outcomes under the Consumer Duty. The software is a means to that evidence, not a substitute for it.

Is cloud-hosted broking software acceptable for a UK brokerage?

Yes, provided you do the due diligence: know where the data is hosted, who the sub-processors are, what the processor contract says, and how you get your data back. The FCA's outsourcing guidance in SYSC 8 is a useful checklist even where it applies only as guidance.

Can WhatsApp conversations be part of the brokerage's records?

They should be, if advice or client instructions pass through them. That means a business number the firm controls, conversations attached to the client record rather than to an adviser's phone, and the ability to export them when a complaint or subject access request arrives.

How long should a small brokerage allow for choosing and moving to new software?

There is no standard timeline; it depends on the size of the book, the quality of the existing data and how many integrations are involved. Plan the selection and the migration as separate stages, and judge the result only after a full renewal cycle.

See ORIS in action

Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.

Book a demo

Free kit : WhatsApp template pack for insurance brokers

This guide and its companions as a printable PDF, with a sourced checklist up front. 15 pages · PDF · 601 KB.

See the kit
Book a demo