How Asia's insurance actually runs, and how to modernise it.
Writing from the team building the platform: open standards, audit-clean operations, and the mechanics of running insurance on modern infrastructure.
Featured · White paper
OPIN: carrying an open insurance standard forward, and authoring the profile each market needs.
The standard is at v1.5.0-draft and Vietnam's profile sits on top of it at v0.2. What the standard settles, where it is still thin, and what an open licence does and does not protect an insurer from.
Closing Asia's insurance gaps: systems that were never built to meet.
Three things stop insurers, their sales channels and their repair networks working as one system. Which ones costs most, which ones you cannot see, and what we have learned putting a claims operation live one insurer at a time.
From FNOL to settlement: the anatomy of a claim on ClaimFlow.
One motor claim from first notice to settlement, with the nine service levels that decide who owes the next action and by when. Plus a plain statement of which parts run today and which are still architecture.
Selling a policy where the customer already is: distribution mechanics on MicroFlow.
How an embedded policy is issued inside a transaction, allocated to an insurer behind it, and reconciled afterwards across four regulators. The design of the engine, not a count of deployments.
Audit-clean multi-tenancy: running many insurers on one backbone without mixing their data.
Separation between insurers is a property of a design. Proving it to a regulator is a record. What each one requires, where data residency fits, and the read-side question a write-side audit trail does not answer.
Outcome-based mechanics: pricing a claims operation on results, not seats.
What an outcome has to contain before a fee can attach to it: the edge cases, the calendars, the attribution problem, and why we have not signed one of these yet.
The anti-corruption adapter: connecting to a legacy core without inheriting its model.
Whose vocabulary wins at the boundary decides what every later integration costs. What the translation layer buys, what it costs every month afterwards, and the question that tells you whether a platform really holds the line.
New writing lands here as it is published. Filter by type to read only what you came for.
Start here
The papers worth the time.
The longer-form pieces that set out how the platform is built and how it is run.
OPIN: carrying an open insurance standard forward, and authoring the profile each market needs.
01
The standard is at v1.5.0-draft and Vietnam's profile sits on top of it at v0.2. What the standard settles, where it is still thin, and what an open licence does and does not protect an insurer from.
Audit-clean multi-tenancy: running many insurers on one backbone without mixing their data.
02
Separation between insurers is a property of a design. Proving it to a regulator is a record. What each one requires, where data residency fits, and the read-side question a write-side audit trail does not answer.
Outcome-based mechanics: pricing a claims operation on results, not seats.
03
What an outcome has to contain before a fee can attach to it: the edge cases, the calendars, the attribution problem, and why we have not signed one of these yet.