• Product
    BrokerageLoop, by Deecoding
  • Markets
    UAE and Saudi Arabia; Lebanon pilot
  • Platform
    Microsoft Azure, one deployment per country
  • Languages
    Arabic and English, right-to-left first
  • 29modules, one system of record
  • 11role bundles, deny-by-default
  • 2apps: web and a mobile field app

The challenge

What had to be true

Brokerages in the region run on spreadsheets: renewals slip through, commissions are reconciled by hand, and co-broker statements are rebuilt every month.

The 2024 Emirati broker regime turned things that used to be good practice into obligations with deadlines, and a product for this market has to work in Arabic first, not as a translation.

The work

What we built

  • The whole book in one registerLead, quote, bind, policy, endorsement, renewal, claim, collection, commission, reconciliation and counterparty statements, in one system.
  • Right-to-left firstArabic throughout, not a translation bolted onto a left-to-right design.
  • Market rules as configurationLebanese and Emirati regulatory behaviour is configured, so the same product enforces different rules in different markets.
  • Co-brokers as first-classCo-broker and sub-broker business is modelled directly, with a statement of account on demand.
  • An AI assistant inside your permissionsIt answers from the brokerage’s own book, and only from what the person asking is allowed to see.
The BrokerageLoop dashboard: renewals due, overdue premium, commission receivable and premium at risk, with the items that need a look.
The BrokerageLoop dashboard: renewals due, overdue premium, commission receivable and premium at risk, with the items that need a look.

Security

How the data is protected

  • Tenant isolation enforced in the database, with PostgreSQL row-level security
  • Changes are added, never overwritten: every change records who, when and what it was before
  • Eleven role bundles, deny-by-default
  • Alerting on cross-tenant access attempts and bulk reads
  • Infrastructure as code with Terraform; deployments authenticate with OIDC, no stored cloud keys
  • Encrypted in transit and at rest

Designed and built by a certified Microsoft Azure Solutions Architect.

Questions brokerages ask

Moving to BrokerageLoop

Can you migrate years of historical data out of our current system?

Yes. We migrate data from any source: legacy Windows or desktop applications, online and SaaS systems, and Excel workbooks. That covers policy registers, claims history and unpaid client premiums, mapped into BrokerageLoop’s records, together with the files, scanned documents and images attached to them.

Can our management switch between our Lebanon entity and our UAE entity from one place?

Yes. Each entity runs as its own isolated tenant, so each country’s data and compliance rules stay separate, and the same user can easily switch between the tenants they have access to.

We do not use Odoo yet. Do we have to build our chart of accounts from scratch?

No. We start from a ready-made chart of accounts and payroll configuration for Lebanon, the UAE and Saudi Arabia, validated by auditors, so the accounting side is not built from a blank ledger while BrokerageLoop’s insurance modules are being configured.

Stack

What it runs on

  • Next.js
  • NestJS
  • PostgreSQL 16
  • Prisma
  • Expo / React Native
  • Azure Container Apps
  • Azure Key Vault
  • Application Gateway WAF
  • Azure OpenAI
  • Log Analytics
  • Terraform
  • GitHub Actions

Running a brokerage?

Tell us what you are building. We will come back with what we would need to know, a rough shape for the work, and whether we are the right people for it.

Ask for a demo