Who we work with/Insurance brokers
Insurance brokers
Agents that start on their own ahead of a renewal date, when a risk is ready for market or a claim goes quiet, do the preparation and chasing, then stop for the broker to approve. Built in your own Microsoft 365.
FiveForward builds AI agents for UK insurance brokers inside their own Microsoft 365: renewal preparation that starts a set number of days before the renewal date, submission pack assembly, claims chasing and meeting notes, while placement decisions, advice and sign-off stay with the broker.
Broking work is heavy in exactly the areas agents handle well: assembling files, drafting correspondence, chasing and turning calls into notes. Renewals, submissions and claims all leave a long trail of email and documents, and much of that trail is repeatable work.
The useful agents run on the broking calendar. A renewal agent starts a set number of days before the renewal date; a claims agent starts when a claim has gone quiet for too long. They do the preparation in your own Microsoft 365, then stop for the broker.
Placement decisions, advice on cover and anything a client relies on stay with a named person. The agent prepares the file; the broker decides.
Run an accountancy firm? The accountancy page has the detail: six accountancy agents, what starts each one and where your team approves.
The agents
Each one starts from the file or the calendar and stops for the broker.
Proof
Both builds are from accountancy firms. Here's where the same pattern fits yours.
Case study · Accountancy
An AI post room built for an accountancy firm: scanned letters read, matched to the right client and filed, with people handling only the exceptions. A broking office dealing with proposal forms, schedules and claims correspondence runs on the same intake problem.
Case study · Client acceptance
Standard letters generated from a form into controlled Word templates, reviewed rather than drafted. The same pattern produces renewal invitations and client updates.
What to watch
Your data and who approves
You decide what each agent may do on its own and where a person has to approve. By default, anything that goes to a client or raises a bill waits for one of your team.
Agents are built in your own Microsoft 365, and your own Azure subscription where a job needs it, not on our servers. We don't host your data.
An agent your team talks to only sees what the person using it can already see.
Agents that run on their own use a dedicated service account. Its access is limited to the mailboxes, folders and systems the job needs, agreed with you in advance.
Every run is logged: what came in, what the agent did and who approved it.
Microsoft's own usage charges, such as Copilot Credits, are billed by Microsoft to your firm, separately from our fees. All prices exclude VAT.
Rather your own team learned to do more of this themselves? Training is hands-on and built around your firm's own processes, from using Copilot in day-to-day work through to building their own agents, with no Discover needed first.
Further reading
Other sectors
Six accountancy agents for the admin every practice shares: WIP and billing, client checks, meeting notes, records chasing, onboarding and VAT review. Each one waits for one of your team to approve.
Agents that start on their own when a new matter opens, a meeting ends or post arrives, do the checking, drafting and filing, then stop for the fee earner to approve. Built in your own Microsoft 365.
Agents that brief the adviser before a review, draft the file note and a first suitability report afterwards and pull provider responses into your schedule, then stop for the adviser to approve. Built in your own Microsoft 365.
Agents that start on their own when an email arrives, a meeting ends or a report is exported, do the checking, drafting and filing, then stop for one of your team to approve.
Next step
A free 30-minute call with James. No pitch and no obligation.
Concierge