Skip to content
The configurable insurance operations platform

Insurance operations, configured around how you actually work

Quote, issue, administer, claim, reconcile and report in one platform. Your products, rate tables, documents and workflows are configured around your business — not the other way around. Built for MGAs, Lloyd's coverholders, brokers, reinsurance brokers, carriers and TPAs, and deployed in the region your regulator requires.

Book Overview
3 products
Policies in force
4,318
Across 3 products
Quotes this week
186
42 bound
Renewals due
73
Next 30 days
Bordereau
Ready
Validated, no errors
QUO-4187 — rated, awaiting bind
Quoting
END-0912 — mid-term endorsement, premium adjusted
Policy
COM-Q3 — commission statement reconciled
Finance
Enterprise-ready
ISO/IEC 27001:2022 certified
AES-256 encryption
US & Swiss / EU deployment
Immutable audit trail
Lloyd's coverholder in implementation

One system for the whole book, instead of four that don't reconcile

Most specialist insurance operations do not run inside a single system. The rates live in a spreadsheet, the submissions live in an inbox, the policy documents live on a shared drive, and the numbers only agree once someone has spent a week making them agree. Regure replaces that arrangement.

01

The spreadsheet holding your rates

Rate tables and product definitions become configuration inside the platform — versioned, permissioned and changed without a development cycle.

02

The inbox holding your submissions

Submissions arrive, are classified and extracted, and land on the right desk with the data already structured and the audit trail already started.

03

The shared drive holding your documents

Policy documents, endorsements, closings and correspondence are generated from the record itself, in the languages the market requires.

04

The month-end that never reconciles

Premium, commissions, invoicing and bordereaux come from the same records as the policies, so reporting is produced rather than rebuilt.

Where Regure is running today

We don't publish invented case studies. These are the real deployments, described without naming customers — named references are available under NDA during procurement.

In implementation and UAT

Swiss Lloyd's coverholder

Specialist medical insurance

Three insurance products configured on Regure, covering the operation end to end — from quoting through to Lloyd’s reporting — on Swiss data residency.

  • Quoting
  • Configurable rating
  • Policy administration
  • Claims
  • Commissions
  • Invoicing
  • Lloyd's bordereaux
  • Broker portal
  • Policyholder portal
  • Multilingual documents
  • Swiss data residency
Workflow evaluated against live practice

Reinsurance broking operation

Middle East / DIFC market

The reinsurance chain assessed end to end by practising reinsurance brokers, from submission intake through to closings and reporting.

  • Submission intake
  • Cedants
  • Placements
  • Markets
  • Shares
  • Premium
  • Closings
  • Debit / credit notes
  • Claims
  • Endorsements
  • Reporting
Operating today

Multi-region deployment

United States and Switzerland / Europe

Regure runs separate infrastructure per region, so data residency is a deployment choice rather than a custom build.

  • US deployment
  • Swiss / EU deployment
  • Regional data residency
  • Per-region infrastructure

From submission to renewal, with the money and the reporting attached

The same platform handles the whole cycle. Each stage is configured per product and per programme, so a specialist medical binder and a commercial property book behave differently without running on separate systems.

01

Submission and intake

Submissions arrive by email, broker portal or API. Documents are classified, key data is extracted and validated against your product rules, and the risk lands with the right underwriter with its context already attached.

ACORD extractionBroker portal intakeCompleteness checksAppetite routing
02

Quote, rate and bind

Configurable rate tables produce the premium. Referrals route to the specialist who should see them. The bind decision, the reasoning behind it and the documents it was based on all stay on the record.

Configurable rate tablesBinder terms & limitsReferral workflowsQuote versioning
03

Issue, endorse and renew

Policy documents are generated in the required languages. Mid-term endorsements recalculate premium and adjust billing. Renewals are compared against the expiring policy rather than rebuilt from scratch.

Document generationEndorsement pricingRenewal comparisonCancellations & reinstatements
04

Claims

Claims run on the same policy data that issued the cover. Documents are read on arrival, workflows route by type and value, and every decision is evidenced as it is made rather than reconstructed later.

FNOL intakeCoverage verificationApproval thresholdsSLA monitoring
05

Money and reporting

Premium, invoicing and commissions sit against the same policies, so statements reconcile against what was actually received. Bordereaux and delegated authority reporting are generated from those records.

Invoicing & premiumCommission reconciliationLloyd's bordereauxOperational reporting

Find the version of this that matches your operation

Regure is configured to an operating model rather than sold as one shape. Start where your business actually is.

“I run an MGA or a binder”

Quote against binder terms, issue, endorse, handle the claims, reconcile the commissions and produce a bordereau that passes first time — in one place.

  • Product and rate configuration per binder
  • Binder limits and aggregate monitoring
  • Delegated authority evidence
  • Bordereaux and capacity-provider reporting

“I'm a Lloyd's coverholder”

Run the products on your binder end to end, with Lloyd's reporting, multilingual documentation and the audit trail a managing agent expects to see.

  • Multiple products on one configuration
  • Lloyd's bordereaux and reporting
  • Broker and policyholder portals
  • Coverholder audit evidence

“I place reinsurance”

Submission intake, cedants, placements, market panels, shares, premium and closings — tracked in a system instead of a spreadsheet and a chain of emails.

  • Placement and market panel tracking
  • Closings, slips, debit and credit notes
  • FX and sanctions workflows
  • Cedant reporting and bordereaux

“I'm a broker with a book to run”

Compare policies and renewals in minutes rather than hours, keep client documentation in one place, and reconcile commissions against what carriers actually paid.

  • Policy and renewal comparison
  • One view of clients across lines
  • Commission reconciliation
  • Client portal with live status

“I administer claims for carriers”

Every carrier client wants a different format, a different SLA and a different report. Configure each one separately without running separate systems.

  • Per-client workflows and SLAs
  • Carrier-facing evidence packs
  • High-volume document intake
  • Separation between client books

“I'm a carrier with something to launch”

Stand up a specialty product or programme your core system cannot accommodate quickly — or connect Regure alongside the core you are keeping.

  • New programmes without a core change request
  • Delegated authority oversight
  • API integration with the existing core
  • Document intelligence and reporting

The platform reads the market's paper

Insurance runs on documents that were never designed to be machine-readable — slips, binders, bordereaux, ACORD forms, schedules, loss runs. Reading them accurately is what turns a workflow tool into an operating platform.

Classification and extraction built for insurance documents

Every document entering the operation — scanned, digital, photographed or emailed — is classified, tagged and routed, with the key fields extracted and mapped to structured data. Not a generic OCR tool pointed at insurance, but models built around the forms this market actually uses.

Identifies and routes ACORD forms, slips, bordereaux, schedules, loss runs, medical records and correspondence
Extracts insured details, risk data, limits, premium and policy references
Flags missing documentation before it creates a downstream delay
Detects duplicates across submissions and historical records
Document intake — live
Lloyds_Market_Slip_B0507.pdf
Classified
Bordereau_Q3_Medical.xlsx
Extracting
ACORD_125_Commercial.pdf
Classified
Renewal_Schedule_v2.docx
Review
Loss_Run_2023-2026.pdf
Classified

Policy comparison, renewal comparison and risk signals

Comparing two wordings by hand is one of the most expensive habits in the market. Regure compares policies and renewals against each other, surfaces what actually changed, and flags the differences that matter — which is also the cheapest way to put the platform in front of a team for the first time.

Side-by-side comparison of wordings, limits, deductibles and exclusions
Renewal compared against the expiring policy, with changes surfaced
Document generation from the record, in multiple languages
Risk signals raised from the documents themselves
Renewal comparison
Limit increased — GBP 5m to 7.5m
Changed
Exclusion added — cyber endorsement
Changed
Deductible — unchanged
Match
Insured details — unchanged
Match

Placement to closing, without the spreadsheet

Regure covers the reinsurance chain end to end — submission intake, cedants, placements, markets, shares, premium, closings, slips, debit and credit notes, claims, endorsements, FX, sanctions workflows and bordereaux. If you place risk for a living, you already know whether a vendor has seen this work. Read how we think about it:

See how reinsurance operations run in Regure, or bring us one submission and we will run it through the chain in a working session.

Configuration, not code

Products, rate tables, commission structures, documents, languages, roles, workflows and portals are set up as configuration rather than built as bespoke software. That is why a new product line is a configuration exercise measured in days, and why a new market is a deployment choice rather than a rebuild. Today our implementation team does that configuration with you; we are progressively opening the same surface to customer implementation managers.

Products & rate tables

Product definitions and rating structures per product, programme and market — changed without waiting for a release.

Commissions

Commission structures per product, broker and agreement, with statements and reconciliation against what was received.

Documents & languages

Document templates generated from the record, in the languages the market and the regulator require.

Workflows & roles

Routing, approval thresholds, SLAs, roles and permissions configured per line of business and per programme.

Portals

Broker and policyholder portals running on the same data, with no separate integration project.

Regional deployment

Which region the operation runs in is a deployment choice, with separate infrastructure per region.

Regure vs. the status quo

The honest competitor for most specialist insurance operations is not another platform. It is a spreadsheet, an inbox and a shared drive.

CapabilitySpreadsheets, email and a shared driveRegure
Rates and productsA spreadsheet one person owns and nobody else fully understandsConfigured, versioned and permissioned in the platform
SubmissionsAn inbox, sorted by handClassified and extracted on arrival, routed by appetite
Policy documentsTemplates edited by hand, versions diverging over timeGenerated from the record, in the required languages
Endorsements and renewalsRe-keyed, with the prior year reconstructed manuallyPriced from the policy, compared against the expiring cover
CommissionsReconciled against carrier statements by hand each monthReconciled against the same records that hold the policies
BordereauxRebuilt each period, then corrected after rejectionGenerated and validated before submission
Audit trailPartial, scattered across inboxes and drivesComplete, immutable, cryptographically verified
ImplementationCobbled together over yearsFocused deployments live in as little as 14 days; broader rollouts scoped to the operation
Data securityDocuments in personal folders and emailAES-256, role-based access, regional data residency

What insurance operations leaders ask us

Both are supported. Regure can run as the core operating platform for a specialist book — quoting, configurable rating, policy administration, claims, commissions and reporting. Where you are keeping an existing core system, RESTful APIs and webhook support connect Regure to Guidewire, Duck Creek, Sapiens, Applied Epic and others, and you can start with document processing and workflow automation without touching that system.
Yes. Rate tables and product definitions are held as configuration per product, programme and market, so a rate change or a new product variant is a configuration exercise rather than a development release. Where an existing rating engine is staying in place, Regure works with the rating that system produces.
Yes. The reinsurance chain is covered end to end — submission intake, cedants, placements, markets, shares, premium, closings, slips, debit and credit notes, claims, endorsements, FX, sanctions workflows, bordereaux and reporting.
It depends on scope. A focused, single-scope deployment can go live in as little as 14 days; broader implementations covering multiple products, rating, commissions, portals or regional data residency are scoped to the operation. You can start with one line of business — say a single binder or product — and expand later without re-implementation.
Every action on every document is logged in immutable, tamper-evident audit trails. Automated retention and disposal policies enforce jurisdiction-specific requirements. Data residency options ensure documents stay where regulators require. Role-based access controls ensure only authorized personnel handle sensitive data.
Yes. Regure's workflow engine lets you define standardized processes with configurable rules per region, line of business, or team. SLAs, approval chains, and escalation triggers are enforced automatically — whether your team is in New York, London, Zurich or Dubai.
On what you run, not per seat. Commercially it is a platform fee, a one-time configuration scope, infrastructure where dedicated deployment or data residency is required, and optional custom development. There are three ways to buy — a focused point solution, the operations platform, or a regulated multi-region deployment.

Walk us through your operation

A 30-minute working session against your own material — a submission, a rate table, a bordereau, a renewal pack. We show you how it is configured in Regure. No slide deck.

Book a working session