2,000 policies booked in the platform’s first month.
InorbitX, a UAE insurance venture founded by industry veterans, set out to build the first shared booking platform for Northern Emirates insurance plans — a market where insurers, brokers, TPAs and payment providers each ran their own systems, with nothing connecting them. Damco Solutions built the platform end to end: carrier and broker onboarding, plan configuration, payment, TPA connectivity and regulatory policy issuance in one booking flow, hosted in the UAE for data residency.
- policies booked through the platform in the first month after go-live, from a standing start of zero
- 2,000+policies booked through the platform in the first month after go-live, from a standing start of zero
- weeks from build start to a live, regulator-integrated booking flow
- 3–4weeks from build start to a live, regulator-integrated booking flow
- upfront investment required from any carrier, broker or TPA on the platform
- 0upfront investment required from any carrier, broker or TPA on the platform
The policy count comes from the platform's own booking records for the first month of live operation. The build window held in part because a compliance layer proven on a prior Damco engagement was reused rather than rebuilt.
How it works
A booking becomes a policy
A broker signs in, selects a plan and books a policy. Underneath that single flow, three independent systems have to agree before the policy exists.
A policy cannot be issued without a matching successful payment. The platform reconciles the payment gateway, the TPA and the insurer on every booking, and a booking that fails anywhere in that chain is held, never issued.
How we did it
A regulated build, at startup speed
Four decisions made a build this fast possible in a regulated market.
The regulator is part of the flow.
Every policy registers with the ICP, the UAE federal authority, whose validation formats and approval cycles routinely stall integrations for months. Damco reused a compliance layer verified on a prior engagement, so regulatory issuance worked inside the build window instead of consuming it.
Three systems agree before a policy exists.
The payment gateway, the TPA and the insurer each run their own system. The platform reconciles all three in real time on every booking, with zero tolerance for a policy issued without a matching successful payment.
No participant paid to join.
Insurers, brokers and TPAs in this market had never operated on a shared platform, and none of them was asked to fund one. The commercial architecture is profit share per booked policy, which is what brought independent, siloed participants onto one platform this quickly.
Built for regulated data from the first commit.
The platform runs cloud-native in a UAE region for data residency: KYC documents isolated in dedicated storage, secrets held in a managed vault and accessed by machine identity, every service behind a locked-down virtual network. Compliance is the architecture, not a retrofit.
What it changed
From a market thesis to a transaction-earning business
InorbitX had no platform, no distribution and no revenue when the engagement began. One month after go-live, the platform had booked more than 2,000 policies and was earning on every one of them, and the venture was operating as a transaction-earning business. A second insurance carrier is now in onboarding, and an SME product line is on the roadmap.
- month from go-live to an operating, revenue-earning business
- 1month from go-live to an operating, revenue-earning business
- insurance carriers: the first live, the second in onboarding
- 2insurance carriers: the first live, the second in onboarding
- of bookings reconciled across payment, TPA and insurer before issuance
- 100%of bookings reconciled across payment, TPA and insurer before issuance
If a market opportunity is waiting on a platform that does not exist yet, the first useful conversation is about the shortest regulated path to a first booked policy.
We will tell you what the regulator will ask first.