The whole insurance lifecycle. One AI-native platform.
Integual runs quoting, policy admin, claims, document production, insurance accounting, reinsurance and self-service portals for brokers, suppliers and policyholders on one shared data model — for personal, commercial and London Market business. Built for lean UK MGAs, Lloyd's coverholders and claims operations that can't justify enterprise cost or a year-long implementation.
The problem isn't your team. It's the patchwork.
Most lean UK insurance operations run on one system for policy admin, something separate for claims, a bolt-on for documents, and spreadsheets and email for everything else. The costs are predictable:
Data is re-keyed between systems
The same customer, policy and claim details are typed into three places — so they drift, and errors creep in.
Handlers work slowly
Claims context lives in five places. Every decision starts with twenty minutes of hunting for it.
Legacy platforms resist change
Expensive licences, 6–12+ month implementations, and a change-request queue for anything new.
No modern self-service
Policyholders and repairers have no portal, so every update, booking and estimate routes through a handler.
Genuinely AI-native. Not a bolt-on.
The AI does real handler work — drafting from your actual claim and policy context, not from a blank page. That's where the time savings live.
Claims read against your own wording
Upload the policy wording for a product and every claim notified under it is read against that document at first notification — covered, not covered, or needs review, with the clauses it turned on quoted and referenced, and the questions the notification hasn't answered listed. An unclear answer is never recorded as cover: it comes back for a person.
AI claim action plans
Drafts a prioritised action plan from the live claim file — parties, injuries, damage, suppliers, correspondence — the moment a handler opens the claim.
AI letter drafting
Turns those actions into ready-to-review correspondence in DocPro, grounded in the claim file. Handlers edit and approve; they don't start from scratch.
AI product building
Describe a product in plain English and the builder drafts the whole data-capture definition — tabs, fields, conditional questions and repeating groups — validated against the same rules a hand-built product has to pass. Change it later the same way.
Ask your own book
Brokers ask questions of their own portfolio in plain English and get answers from live figures rather than a static report — and can only ever reach their own business.
A knowledge base that knows your setup
Every user gets in-app documentation — a user guide for each toolset and each portal, with the architecture, security and API references reserved for the roles entitled to them — and an assistant that answers against your organisation's own live configuration, citing the pages it drew on. It sees only what the person asking is allowed to see, and it is never given the keys to your customer records.
Work summaries that read the file
Each handler's dashboard opens with what actually needs attention across their own live workload — drawn from the real claims and policies in front of them, not a static queue count.
Every call metered and priced
Each AI action is recorded against the organisation and the person who ran it, at a fixed credit price per operation — so the bill doesn't move because a prompt got longer. Usage, remaining allowance and the cost of each feature are on screen in the platform, not reconstructed from an invoice.
A capacity-winning asset
Capacity providers increasingly weigh an MGA's technology and data operations when granting and renewing delegated authority. AI-driven operations are now table stakes — and a differentiator when you have them and rivals don't.
Human-in-the-loop, by design
AI drafts; your people decide. Nothing the AI produces is accepted without a person, its reach is bounded by the same permissions and tenant isolation as the person asking, and everything it touches lands through the same immutable audit trail as every other change — so you can evidence what was done and who approved it, and walk into AI-scope audits and regulator conversations prepared.
Nine pieces. One platform. Integrated by design.
A customer, policy or claim is entered once and reused everywhere — through underwriting, claims, reinsurance and the ledger. No integration project, no re-keying, no drift.
Policy Administration
Quote, bind, adjust and renew. A no-code product builder — with an AI drafting assistant — puts a new insurance product live in days. Broker EDI import, mid-term adjustments, a real renewal engine that re-underwrites the risk on screen, per-product document capture and delegated-authority placement — every risk written under a binder or direct — are all built in.
Claims
Full claims handling from first notification to settlement — a coverage check against your own policy wording at first notification, AI-drafted action plans, reserves and payments posted on an accrual basis, supplier coordination, catastrophe-event linking and total-loss logic in one place.
Insurance Accounting
A real double-entry ledger underneath the operation: premium debt and broker statements, claims reserves and payments, supplier payables and reinsurance movements — posted as the work happens, with a trial balance and P&L that tie back to the policy or claim that created them.
DocPro
Reach customers on the channel they actually read — post, email, SMS or WhatsApp — from one compose screen, with AI drafting and a reusable template library.
Reinsurance
Treaties, cessions, recoveries and bordereaux on one audited ledger. Every premium and claim transaction is allocated automatically against the treaties that actually apply — no month-end spreadsheet, no manual reconciliation.
Partner API
Outside systems quote, bind, adjust, renew, notify claims and declare shipments over a scoped, per-organisation API key — rate-limited, attributed per key in the audit trail, with developer documentation inside the platform.
Supplier Portal
Repairers and suppliers receive instructions, confirm bookings and submit estimates online — without ever touching your internal systems.
Policyholder Portal
A mobile self-service app: customers view their policies and claims, and file a claim themselves with photos and location — installable straight to their home screen.
Broker Portal
Brokers log in and see their own book — risks, claims and their own commercial performance — plus an AI assistant they can ask about their portfolio. Read-only by design, with cargo shipment declarations the one thing they can submit. Nothing of yours is exposed beyond their own business.
Underneath it all: admin, audit and oversight
Users and granular permissions, per-organisation branding, platform performance metrics, a searchable audit log of every change, your policy wordings held per product, an AI usage and credit ledger, an integration-health queue that surfaces failed outbound calls instead of swallowing them, and a prioritised product backlog fed by in-app feedback.
End-to-end, not stitched together
Nobody else bundles the full lifecycle for operations this size. The alternatives cover part of the job and leave you to integrate the rest — or they're enterprise suites built for carriers ten times your scale.
The ledger under the operation, not beside it
Premium debt, claims reserves, supplier payables and reinsurance movements post themselves to a real double-entry ledger as the work happens — so the number the underwriter sees and the number in the accounts are the same number, and neither of them is somebody's spreadsheet.
Double-entry, tamper-evident
A chart of accounts and a journal that application code cannot write to directly. Every entry goes through one validated routine that refuses to record anything which doesn't balance — and a correction is always a new reversing entry, never an edit to history.
Premium debt that ties out
Outstanding premium is the premium-debtor balance on the trial balance — not a figure derived on the side. Mid-term adjustments, renewals and manual corrections are all reflected without anyone reconciling them by hand.
Claims on an accrual basis
Raising a reserve recognises the cost; paying releases it rather than expensing it twice. Approved supplier estimates become payables you can settle, and reinsurance recoveries and ceded premium post straight from the treaty engine.
Broker statements
Per-broker balances and a printable Statement of Account, headed with the right legal entity, produced from the same ledger the accounts are built on — not re-keyed into a template.
Trial balance & P&L
Reports generated straight from posted journal lines, with a trial balance that balances by construction. Every figure drills back to the transaction — and the policy or claim — that produced it.
Segregated by permission
Accounts is its own permission rather than a job title, so the person who can bind a policy doesn't automatically get to post a journal correction. One organisation's books at a time, always.
It complements your accounts package — it doesn't replace it
This is the insurance ledger a general accounting package can't produce on its own: premium debt, claims reserves and reinsurance movements, posted as they happen and traceable to the risk that caused them. Statutory period close, VAT returns and payroll stay exactly where they are today.
From personal lines to Lloyd's coverholder business — one platform
The same no-code product builder and shared data model that puts a motor or pet product live in days also runs binding authorities by UMR, Marine Hull & Cargo, a deterministic reinsurance treaty engine, catastrophe occurrences, multi-carrier paper and eight bordereaux types — built for coverholders and specialty MGAs, not bolted on afterwards.
Binding authorities, as the contract
A binder is the contract the business sits under, not a field on a policy. Register each one by UMR with its period, products, territories, capacity and carrier, and every risk you write is placed under a binder or written direct — never both, never neither. There is no “unclassified” pile to reconcile at month end.
The binder's limits, enforced at bind
Quote a risk outside the product schedule, outside the territories, outside the binder period or against a binder that isn't active and the bind is refused — with every reason listed at once, not one at a time. Capacity is different: writing the line that crosses the limit is an underwriting judgement, so utilisation warns rather than blocks. Misplaced business can be re-placed later from the policy record, with the claims following it.
Marine Hull & Cargo, no-code
Marine Hull & Machinery and Marine Cargo product templates — fleet schedules, survey & classification status, trading patterns and claims history for Hull; Institute Cargo Clauses, conveyance and trade details for Cargo — built through the same product wizard as every other line, with slips and survey reports captured against the risk at bind.
A real reinsurance treaty engine
Quota share, surplus, excess of loss, cat XL, stop loss, aggregate XL and facultative — with deterministic eligibility and tie-break rules, multi-layer towers, and non-proportional layers that can attach netof whatever the proportional treaties have already taken. Cession and recovery are calculated and logged on every premium and claim transaction — and business written under a binder is left out, because it sits on the carrier's paper and is already reported to them.
Catastrophe XL that behaves like one
A cat programme responds to the aggregate loss from a single occurrence, not to each payment separately. Link claims to a catastrophe event and the attachment is charged once across the whole event — with a recompute when a claim is linked after the fact, and each claim's pro-rata share reported alongside the marginal figures.
Exposure & capacity, monitored
Aggregate insured value across a treaty's eligible book, converted into the treaty's own currency and measured against its stated capacity — alongside remaining layer limit, reinstatements consumed, and consumption broken down by occurrence.
Eight bordereaux, one audited ledger
Premium, claims, outstanding claims, accounts, reinstatement, profit commission, exposure and catastrophe — all generated from the same transaction ledger, each on its own reporting frequency, due-date offset and submission method, with CSV export and scheduled email submission.
Coverholder reporting, per UMR
Premium and claims bordereaux are produced for one binding authority at a time — every product written under that UMR, the Lloyd's convention — and for your direct business separately. Both types generate together on a monthly schedule, because a coverholder submits them together. Every submitted report is frozen as sent: correcting a placement changes future reporting, never a report already at market.
Open Cover & shipment declarations
Cargo open covers accept individual pre-sailing declarations — auto-issuing a certificate of insurance — or a broker's bulk batch upload, with live utilisation against the facility's limit and a reminder when a declaration is overdue against the agreed cadence.
Facultative, on the same ledger
Facultative is negotiated risk by risk, so it's never auto-ceded — but a placement agreed outside the system is recorded against the same append-only ledger as everything else, by policy or claim reference, with the arithmetic derived rather than typed in twice.
Multi-carrier paper
Write on more than one capacity provider's paper and the treaties follow the carrier: policies carry a legal entity, treaties can be restricted to specific ones, and where there's only one it's allocated automatically rather than asked.
A dedicated Broker Portal
Brokers and producing offices get their own login — their risks, their claims, their own commercial performance, and an AI assistant grounded in their book — with the same depth as the internal screens, minus the write controls. No broker chasing your team for a policy schedule.
An Exceptions Queue instead of a spreadsheet
Anything the engine can't resolve deterministically — an ambiguous treaty match, a missing FX rate — lands in a reviewable Exceptions Queue rather than silently going unallocated. Every cession, recovery and bordereau traces back through the same immutable audit trail as the rest of the platform.
Built for how UK insurance actually works
Market plumbing is baked in, not configured in. Integual speaks the UK market's language out of the box.
Right-sized for the firms the big vendors ignore
Integual is a painkiller for lean operations stitched across disconnected systems — not another enterprise suite.
MGAs & Lloyd's coverholders
Startup and scaling MGAs writing personal, commercial and London Market business — motor, pet, travel and home through to Marine Hull & Cargo — outgrowing spreadsheets or a legacy PAS that only does part of the job.
- No-code product builder: a new product live in days
- Commercial & company policyholders alongside personal lines, on the same policy admin
- Binding authorities by UMR — placement enforced at bind, premium and claims bordereaux per binder
- A deterministic reinsurance treaty engine and eight Lloyd's-format bordereaux, built in rather than bolted on
- Premium debt, claims reserves and cessions posted to a real double-entry ledger as you write
- A dedicated Broker Portal — and a Partner API — keep your distribution self-service
Claims operations (CMCs & TPAs)
The claims half of the platform stands alone — a complete claims-operations stack with no policy-admin dependency, on claims-volume pricing.
- AI action plans and letter drafting for every handler
- Notified losses read against the wording you hold for the product, before the file is worked
- Supplier instruction, booking and estimate loop
- Policyholder self-service FNOL with photos
- Reserves, payments and supplier payables on an accrual ledger, not a spreadsheet
- Referring brokers get their own read-only view via the Broker Portal
Scheme & specialty insurers
Small and mid-size insurers replacing legacy systems — often starting claims-first or with a single line rather than a big-bang migration.
- Land one line or one function; expand from there
- Dedicated instance, full audit trail, exportable data
- EDI import and a Partner API as the migration on-ramp
Simple tiers. Transparent AI pricing.
A flat monthly platform fee sized to your book on a 12-month term, AI metered in credits you can see, and onboarding at a fraction of what the market charges.
Launch
- Full platform — every module, portals included
- Up to 10 users
- 1,500 AI credits per month
- Dedicated instance & audit trail
Growth
- Everything in Launch
- Up to 25 users
- 4,000 AI credits per month
- White-labelling — your logo and colours across the console and every portal
Scale
- Everything in Growth
- Unlimited users
- 10,000 AI credits per month
- Priority roadmap input & support
Claims-only pricing for CMCs & TPAs
Running claims without a book of premium? The Claims Ops tier prices on open-claim volume instead of GWP — from £1,500 a month for up to 500 open claims — with the same AI credit mechanics.
AI credits, metered transparently
Every AI action has a fixed credit price — a claim action plan is 5 credits, a drafted letter or a coverage review 10 — and every call is recorded against the person who ran it, so usage and remaining allowance are on screen rather than reconstructed later. Top-up packs are available when you need more; unused allowance never blocks the work.
Onboarding from £5,000
Product build and data load, priced £5,000–£15,000 depending on complexity — deliberately an order of magnitude under the implementation fees this market is used to.
Design-partner terms
Our first partners get a substantial year-one discount in exchange for a named case study and reference calls — paid, never free, so both sides are committed.
All prices exclude VAT. 12-month minimum term; discount for annual prepayment.
A security posture that surprises people
Insurance data deserves better than “trust us”. Integual is built security-first, and the protections are contractual as well as technical.
Dedicated instance
Your own isolated database and deployment — your data never shares an instance with another customer.
Enforced at the data layer
Row-level security on every table, not just checks in application code — and uploaded documents, wordings and claim photographs held in private storage, reachable only through short-lived signed links.
Full audit trail
Every change to policies, claims, payments and customer records is logged immutably — who, what, when — alongside a financial journal application code cannot rewrite, where corrections are reversing entries rather than edits.
Hardened logins
MFA for privileged roles, breach-screened passwords, secure httpOnly sessions and CSRF protection throughout.
Human-in-the-loop AI
AI drafts, people decide — a governance posture designed for AI-scope audits, including Lloyd's coverholder audit requirements.
Your data, exportable
Standard Postgres under the hood, with contractual data-export and exit provisions — no lock-in by obscurity.
FCA-outsourcing-ready
Contracts built around SYSC 8: your inspection, information and termination rights, with all sub-processors disclosed.
Continuity protections
Source-code escrow, documented runbooks and defined support SLAs available — sensible answers to sensible due-diligence questions.
We're choosing our founding customers now.
Integual is early — and for the right firm, that's the opportunity. Design partners get a level of influence and responsiveness no incumbent can match: you shape the product around your book instead of queuing for change requests.
- Preferential year-one commercial terms on a 12-month partnership
- A direct line to the people building the platform — decisions in days, not quarters
- Your first product live inside two weeks
- A named case-study partnership — you take the credit for modernising
Book a 30-minute demo
A live, seeded instance with real workflows — quote to claim to customer document, end to end, in one session.
Talk to the founderhello@integual.com