The other four are things your firm already has: Open GI, the insurer's form, Outlook and Microsoft 365. One small program joins them.
Left to right, in the order it happens. The blue box is the only thing we build. Everything else is your own software, used as it is.
Every night, or on demand, the client, policy and claims data leaves Open GI as a file. Route A is a scheduled report, which every Open GI licence can run and save to a folder. Route B is Open GI's data connection, where your licence includes it. Route A is enough for this job and needs nothing bought.
Reads that file, opens the insurer's form template and fills every box it has a match for. Marks amber anything it does not hold, or anything older than twelve months. Drafts the email. Files the copies back.
A list saying "this box on the insurer's form is this field in Open GI". Written once per insurer form by us, then it is just a list your team can read. A second insurer's form is a second list, about an afternoon.
One web page your handler opens in their browser, signed in with their normal Microsoft login. Every field, its value and where it came from. Amber rows have a box to type in. Two buttons: save draft, open the email.
A draft appears in your handler's own Outlook, from their own address, to the underwriter on the policy record, with the form and schedule attached. When it is sent, the sent copy and the form are saved back against the client with the date.
Copying a value from one box to another is done by ordinary code, exactly, every time. No AI touches a number.
Reading your free-text file notes to suggest a first draft of a claims narrative, and reading a new insurer's form to propose its field map. Both are suggestions, both marked as such, both checked by a person.
Ordinary code is exact and cheap where the answer is known. AI earns its place where a person would otherwise read and write, and never where a wrong guess costs a claim.
The small server, about £10 a month, or nothing if it runs inside your Microsoft 365. Microsoft Graph is included in the Outlook you already pay for.
The service notices a box it cannot find, marks the whole form amber and tells us. Half a day to remap. This is the most common breakage, and it is visible, never silent.
The same. A missing column marks its fields amber rather than filling them wrong.
Not part of this build. Where an insurer allows it, a second step can push the same record into their portal. Where they forbid it, your handler types from a form that is already filled and checked.
You do. The program, the field maps and the server login are yours on handover. Nothing is rented from us.
Half a day with your team, one handler for an hour a week during the build, and someone who can run an Open GI report and sign in to Microsoft 365 as an administrator.
Bring the three forms your team retypes most. We count the fields together and you see the saving before anyone builds anything.
Email Byron