BrokerageLoop
Book a demo

The problem was never the absence of a system.

BrokerageLoop is an operating system for insurance brokerages in the Middle East — bilingual, auditable, and built around how brokerages here actually work.

Why this exists

Why BrokerageLoop exists

Some brokerages here run on a spreadsheet. Many run on software older than half their staff — a real system, with a real ledger, that still expects someone to reconcile by ticking rows on a screen. Others run on the insurers’ portals, one per insurer, none of which add up to a view of their own book.

They arrive at the same place from different directions. What a broker here actually needs to answer — what does this co-broker owe me, in which currency, and can I prove it — is the thing none of them were built to answer, because none of them were built here.

A book that is mostly other brokers.

Co-broker and sub-broker business can be most of what a brokerage does, and the systems on offer treat it as a footnote to direct business — a free-text name on a commission line, not an account you can settle.

Software that keeps the books but cannot check them.

A general ledger, a collections module, more than one currency — and reconciliation that is a person, a printout and an afternoon.

Rules that changed, in a system that did not.

The 2024 Emirati broker regime turned things that used to be good practice into obligations with deadlines, and a system that cannot show what happened cannot show that you met them.

We did not start from a feature list. We started from a Tuesday morning — chase a renewal, record a cheque, work out what a co-broker owes, match an insurer’s statement line by line, answer a client in Arabic — and built the system that morning needs.

What we decided differently

Four decisions the rest of the product follows from.

Arabic is half the product, not a layer

Right-to-left first, throughout. Not a translation bolted onto a left-to-right design.

Co-broker business is first-class

Co-broker and sub-broker business is modelled as a first-class citizen, with a statement of account on demand — not as an afterthought to direct business.

A correction never overwrites history

Changes are added, never overwritten. Every change carries who, when, and what it was before.

One product, different rulebooks

Lebanese and Emirati regulatory behaviour is modelled as configuration, so the same product enforces different rules in different markets.

Who builds it

Built in the Middle East, for the Middle East.
Built on Microsoft Azure, in the UAE North region.
Designed and built by a certified Microsoft Azure Solutions Architect.

Where we are

Where we are today

Commercial

United Arab Emirates

Records held in the Azure UAE North region. The 2024 broker regime is modelled as configuration, not as a fork of the product.

Commercial

Saudi Arabia

The same product, with the rulebook that applies in the Kingdom rather than a separate build.

Pilot

Lebanon

Where the product is being run in anger before it is sold more widely here.

Ready to run your book from one register?

Book a walkthrough with our team, in English or Arabic.