Marrınn Book a demo

Agentic Aı for insurance.

Squids run operations across the insurer, from the broker submission to the claims complaint. Marrinn builds claims, underwriting and complaints workflows for insurers, brokers and MGAs, and connects them to the policy administration system, shared inboxes and document stores you already keep. A handler approves. Ledger records who did what and why.

Keep your policy administration system. See every policy on one live map.

The policy, claims and broker systems stay where they are. TagFlow keeps a current copy of each, matches their records, and Squids work from the result.

Explore Marrinn Digital Twin

Claims and underwriting, built around how you run it.

Each module an insurer runs, and where it comes from: built for you by Marrinn, in TagFlow today, or the system you already run, connected.

Floodwater around stone houses and a half-submerged car in a UK town

Select a module

  • Built for you by Marrinn
  • In TagFlow today
  • Your system, connected
Claims managementBuilt for you by Marrinn

Built for you by Marrinn

Claims management

Claim file, reserve, supplier panel and settlement.

A Squid reads the first notice of loss and the photos, checks cover and excess, and drafts the reserve and settlement. The claims handler approves.

In the FCA's 2025 review, 32% of 118,890 storm claims in 2024 ended in a payment.

Delegated authorityBuilt for you by Marrinn

Built for you by Marrinn

Delegated authority

Coverholder bordereaux checked against the binder terms.

A Squid matches each row to binder limits, flags exceptions and drafts the query list to the MGA. The delegated authority manager approves.

Each bordereau row is checked against the binder limits, and exceptions go back to the MGA as one query list.

Complaints and OmbudsmanBuilt for you by Marrinn

Built for you by Marrinn

Complaints and Ombudsman

Eight week clock, complaint file and final response.

A Squid builds the claim timeline from the policy and claims systems and drafts the final response. The senior complaints handler approves.

The Financial Ombudsman received 13,420 car and motorcycle insurance complaints in 2025/26, and 35% were upheld.

Underwriting submissionsBuilt for you by Marrinn

Built for you by Marrinn

Underwriting submissions

Broker submissions, risk data and appetite checks.

A Squid extracts the schedule and loss runs, checks appetite and drafts the broker reply. The underwriter approves.

Appetite, limits and loss history are read from the broker's schedule and checked against your underwriting guidelines.

Product governanceBuilt for you by Marrinn

Built for you by Marrinn

Product governance

Fair value assessments, target markets and outcome evidence.

A Squid collects claims, complaints and acceptance data by product and drafts the fair value assessment. The product owner approves.

The FCA's TR24/2 review of 28 manufacturers and 39 distributors found firms not adequately evidencing fair value.

Regulatory reportingIn TagFlow, extended for you

In TagFlow, extended for you

Regulatory reporting

PRA and FCA returns built from source data.

A Squid pulls source data, reconciles it to the ledger and drafts the return template. The head of regulatory reporting approves.

Each return line traces back to the source data and the ledger, and sign-off is recorded by name.

Document productionIn TagFlow today

In TagFlow today

Document production

Policy, claim and complaint letters with versions and approval.

A Squid fills the template from the case record and routes it for sign-off. The team leader approves.

One approved template set and one version history serve every team.

Already on Guidewire, Duck Creek, Open GI or Acturis? Keep it, or run it on Marrinn.

Squids read from the system you run today. Where TagFlow has the module, you move that work across; where it does not, Marrinn builds it from your requirements.

  • Guidewireor built by Marrinn
  • Duck Creekor built by Marrinn
  • Sapiensor built by Marrinn
  • Insurityor built by Marrinn
  • Open GIor built by Marrinn
  • Acturisor built by Marrinn
  • SSPor built by Marrinn
  • Oracle Documakeror TagFlow Document Studio

Where insurers lose time and trust, and what it costs.

Published figures on what slow claims handling and complaints cost an insurer.

  • 6 of 23home and travel insurers lacked a documented claims oversight frameworkFCA, Home and travel claims handling arrangements, good practice and areas for improvement, July 2025.
  • 70%of claims-service complaints upheld at one firm whose service levels were outside tolerance through 2024FCA, Home and travel claims handling arrangements, July 2025.
  • 32%of 118,890 storm claims in 2024 resulted in a paymentFCA, Home and travel claims handling arrangements, July 2025.
  • £11.9bnpaid on 2.5 million motor claims in 2025, of which repairs were £7.5bnAssociation of British Insurers, 2025 motor claims data; FCA, Motor insurance claims analysis, updated December 2025.

Each system acts on half the picture.

  1. 1Two systems
  2. 2One acts alone
  3. 3What goes wrong
  4. 4The Digital Twin
  5. 5A person decides

Daniel Okafor is in Guidewire and Duck Creek. Each holds a different fact.

The policy system cancels his cover. It cannot see what Duck Creek knows.

Daniel's cover ends while his claim is still open. The insurer has to explain that to him and to the regulator.

The Digital Twin puts both on one record for Daniel Okafor and flags the clash.

The claims manager approves holding the cancellation. Nothing goes out before that.

GuidewirePolicy adminActing now

Two payments missed. Cancellation queued.

Duck CreekClaims system

Open claim. Loss adjuster visit booked.

Nobody sees itCancellation on a policy with an open claim

FlaggedCancellation on a policy with an open claim

Claims managerApproves holding the cancellation ApproveApproved

The cost of not having a Digital Twin.

Each system acts on what it can see. These mistakes happen in the gaps between them.

Without a Digital Twin6 failures between your systems
  1. Cover cancelled during a claimA customer with an open claim loses cover for one missed payment.BillingClaims
  2. The same loss paid twiceOne loss is claimed on two policies, and both pay.ClaimsPolicy
  3. Renewals priced without the historyThe renewal price ignores the claims in another system.PricingClaims
  4. Broker records that disagreeThe broker holds the customer under another spelling.BrokerPolicy
  5. Complaints that reach the OmbudsmanMistakes like this end in redress payments.ClaimsComplaints
  6. Fair value you cannot showEach case is rebuilt by hand for the regulator.Every system
AI agents make these mistakes too, because each one reads only the systems it is connected to.The policy agent sees two missed payments, but not Daniel's open claim, so it cancels his cover.
See the Digital Twin catch one

Keep the systems you run. TagFlow joins each policyholder’s records into one page, and Squids work from it.

Daniel Okafor is policy HM-0098213 in Guidewire, claim CL-55102 in Duck Creek and Danial Okafor, client OK-4471, in Acturis. TagFlow matches the first two exactly; the Acturis record scores 79 percent on address and birth date and a person confirms it, so TagFlow keeps one page for him, linked to the cancellation date of 14 November, his open water damage claim, two missed payments of £62.40 and the booked loss adjuster visit. At 07:30 Guidewire queues a cancellation notice for him, with 6 policies queued this morning. Claims Squid finds his open claim CL-55102 in Duck Creek. Letter Squid drafts a letter that holds the cancellation, from the policy record in Guidewire. Customer Squid drafts a portal message and a payment link from his details in Acturis, found under Danial Okafor. The claims manager approves Daniel and 5 others at 07:44. At 07:45 his letter is sent and his cancellation is held, the 5 others the same, and Guidewire is unchanged.

  1. Match his records
  2. Cancellation queued
  3. Squids work
  4. Manager approves
  5. Daniel's policy held

Guidewire stays where it is. TagFlow keeps a current copy. How we connect what you keep

Squids that know how your organisation runs.

Before a Squid acts, it reads the record, its history, your procedures and the duty that applies. Then it hands the work to the next module, and a named role decides.

A storm hits and 1,900 notifications arrive in two days. Each one is grouped, triaged and on a handler's list before anyone opens the inbox.

Claims inbox and weather alert feedEvent EV-2611Amber wind warning confirmed, notifications up sharply from the Yorkshire postcodes

AWhat the Event Squid reads first

  • RecordClaims management, built to order412 notifications so far, 331 home, 81 motor
  • HistoryPolicy administration systemRoof claim here, repaired badly in 2024
  • PolicyDocument ManagementStorm playbook v5: tarp and board-up first
  • PeopleApprovals & SLADuty manager Priya Shah, deputy Tom Reid, on call

BSquids across your modules

  1. Claims management, built to orderEvent SquidGroups notifications into one event by postcodeHands to Triage Squid
  2. Service DeskTriage SquidRanks cases by urgency and flags priority customersHands to Finance Squid
  3. TagFlow FinanceFinance SquidStages emergency payment requests under the capHands to Customer Squid
  4. Customer PortalCustomer SquidDrafts the first reply with next steps per case

CWho decides

DCDuty claims managerApprove the emergency payment list and the repairer allocation for the event ApproveApproved

LedgerEvery step, with the time and the role

An MGA sends the October bordereau on the 9th. By lunch the exceptions are listed, the query to the MGA is drafted and the accrual is staged.

Delegated authority inboxBDX-2610-ALDOctober premium and claims bordereau received from an MGA, 2,140 rows

AWhat the Bordereaux Squid reads first

  • RecordDocument ManagementSpreadsheet, 2,140 policy rows, 61 claim rows
  • HistoryTagFlow FinanceSeptember had 38 exceptions, 9 still open
  • PolicyContracts CLMBinder: UK property, limit £1m per risk
  • PeopleApprovals & SLADelegated authority manager signs off; deputy is on leave

BSquids across your modules

  1. Document ManagementBordereaux SquidReads the file and checks fields, countries and currenciesHands to Binder Squid
  2. Contracts CLMBinder SquidMatches each row to binder limits, territory and classHands to Finance Squid
  3. TagFlow FinanceFinance SquidStages the premium accrual and reconciles to the ledger

CWho decides

DADelegated authority managerApprove the exception list and the query email to the MGA ApproveApproved

LedgerEvery step, with the time and the role

A policyholder mentions a bereavement in a claim email. The handler sees a flag, an adjusted plan and the evidence trail within minutes.

Claims inboxClaim 2026/6102Email on an open escape of water claim says the policyholder's husband died last week

AWhat the Vulnerability Squid reads first

  • RecordClaims management, built to orderEscape of water, repair booked for 3 November
  • HistoryService DeskThree chasers sent in 14 days, two unanswered
  • PolicyDocument ManagementVulnerability procedure: one named handler, no chasers
  • PeopleApprovals & SLAHandler Maya Clarke, vulnerability lead Ben Foster

BSquids across your modules

  1. Service DeskVulnerability SquidReads the email and proposes a flag and support needsHands to Claims Squid
  2. Claims management, built to orderClaims SquidDrafts the adjusted contact plan and pauses the chasersHands to Compliance Squid
  3. Risk & ComplianceCompliance SquidAdds the case to the vulnerability register for reporting

CWho decides

CHClaims handlerConfirm the flag and approve the adjusted contact plan ApproveApproved

LedgerEvery step, with the time and the role

What Marrinn runs for an insurer.

Every part runs under one permission model, with one record of every action.

  • Claims and complaints handling

    Notification, triage, assessment, settlement and complaints, each case with a reference, a route, a deadline and a full history.

    How we build it

  • Workflow and approvals

    Approval gates, reminders, escalation and service level targets, with business-hours calendars.

    See TagFlow

  • Squids for claims and underwriting

    Agents that read, draft and chase inside the permissions you set and a budget you control.

  • Records and audit trail

    Every action is recorded with who approved it and why. Exports and a configurable retention period are supported.

  • Policy system migration

    Move records out of a legacy policy or claims system in dry runs before anything is switched over.

    See Marrinn Migrate

  • Voice agents for the claims line

    Agents that answer the call, having already read the number and pulled the policyholder’s record. 31 languages per agent, about 90 percent of the world’s population.

    See voice agents

  • Reports and board packs

    Claims handled in time, complaints by cause and cases by stage, with plain-English queries.

    See Marrinn Reports

  • Secrets for connected systems

    Encrypted credentials, rotation and an access log for every system a Squid connects to.

    See Marrinn Vault

  • Systems built to your requirements

    Custom software built in short rounds, with a first working, secure version in about 10 days.

    Read how we build

The rules your systems have to show they follow.

Marrinn builds the records and controls that show an insurer follows the rules it is held to.

  • FCA Consumer DutyEvidence of good outcomes, including fair value and claims support, and an annual board report.
  • ICOBSClaims are handled promptly and fairly, and a rejection comes with reasons.
  • DISP complaints rulesA final response within eight weeks, then the Financial Ombudsman Service.
  • Solvency UKThe PRA regime for capital, governance and reporting.
  • IFRS 17Insurance contract accounting, in force since 2023.
  • Insurance Act 2015 and Consumer Insurance Act 2012Duties of fair presentation and disclosure.
  • Value measures and GIPPAnnual reporting of claims frequency, acceptance and complaints, and general insurance pricing rules with no loyalty penalty on renewal.
  • Senior Managers and Certification RegimeNamed senior managers for claims, underwriting and operations.
  • Operational resilience and outsourcingImpact tolerances for important business services, and oversight of claims and IT outsourcers.
  • UK GDPRSpecial-category health data in claims and underwriting needs a lawful basis and strict access.

rules answered from one record: who, what, when and why. You show it. You do not rebuild it.

The regulator’s own findings make the case for approved workflows.

The figures below come from the FCA, the Financial Ombudsman Service and a KPMG summary of FCA activity. Marrinn connects to what you run and records every decision.

A first version in about 10 days

A first working, secure version in about 10 days, then rounds of change until you sign it off.

  • Your systems stay connected. Squids work through connections to the policy administration system, claims inbox, rater and document stores you already run.
  • Legacy retired on your timetable. Marrinn Migrate moves records in dry runs, so a legacy system is switched off when you are ready.
  • 11 of 23home and travel insurers did not have sufficient monitoring of outcomes for vulnerable customersFCA, Home and travel claims handling arrangements, July 2025.
  • 305,726complaints to the Financial Ombudsman Service in 2024/25, a record, up 54%Financial Ombudsman Service, annual complaints data 2024/25.
  • 3skilled-person reviews commissioned by the FCA after its home and travel reviewKPMG summary of FCA activity, 2026.

Hosted where your security policy requires.

Licensing and hosting are agreed before the first round of work begins.

  1. Our cloudHosted and run by Marrinn
  2. Your cloud accountIn your own tenancy, under your keys
  3. Your own serversOn your premises, with your records on your hardware

Licensed per user. You own your data and can export it at any time.

Questions an insurer asks first.

Questions buyers ask before a demo.

Can Marrinn connect to our policy administration and claims systems?

Yes. Squids work through connections to the systems you already run, and Marrinn Migrate moves records out of a legacy system in dry runs before anything is switched over. Which systems to connect first is decided in the discovery session.

Does a Squid decide a claim or a price?

Decisions stay with people. A Squid reads, drafts and chases, a named role that you set approves each action, and the Ledger records who approved it and when. Pricing stays in your own rater.

How soon do we see a working system?

A first working, secure version in about 10 days, then rounds of change until you sign it off.

Where is our data held?

On our cloud, in your own cloud account or on your own servers. You choose, and you can export your records at any time.

Do we have to replace our core system in one move?

Marrinn connects to what you run first. A legacy system is retired when its records have been moved and checked in a dry run.

Can Marrinn build for an insurer?

Yes. Marrinn has delivered a correspondence and business process system for Kuwait Municipality, a risk management system for National Investment Company, and KYC checks and a CRM for Arzan. Claims and underwriting work is the same kind of work: cases, approvals, connected systems and one record of every action, on the same platform and the same build method. Marrinn builds from your requirements in short rounds, connects to your policy, claims and document systems, and puts a named role on every approval. The first working, secure version arrives in about 10 days, so you can judge it on your own claims process before you commit.

See an insurance workflow run on your own claims.

Thirty minutes with the Marrinn team. Bring the process that takes your team longest. We reply within one UK business day.

Book a demo

By submitting you agree to be contacted about Marrinn. We never share your details. See our privacy notice.