Named references

Five insurance operations in Southeast Asia, already in production.

An automotive claims network in Vietnam, a mobility super-app distributing cover across three markets, and the carriers underwriting behind both. These are the receipts, not the roadmap.

The insurance value chain
Distribution
Underwriting
Policy admin
Claims
Servicing
The InsureFlow products, in market
MicroFlowLive
Vietnam Indonesia Philippines
ClaimFlowLive
Vietnam Indonesia Philippines
UnderwriteFlow · PolicyFlow · ServeFlowPlanned
Standards enabled
InsureFlow the AI-native insurance backbone every product runs on Open Insurance StandardsCountry-specific Adaptation

InsureFlow, live across Southeast Asia and built on open standards

Trusted where insurance operations actually run

Vingroup VinFast Green SM BeeVN
Who runs on Trisilva

What each one runs, and what changed.

A small, real set: two client operations, the carrier panel behind them, the underwriters on the book, and the network it is scaling into. What we run, one outcome, and the industry it sits in.

Automotive claims

Built to reach 11 days from 44, across an automotive service network

BeeVN arranges the cover and runs the claims operation. The VinFast service-centre network answers for the vehicles. Both work on ClaimFlow, first notice of loss to settlement, on an outcome-based commercial model. See how ClaimFlow works.

Service levels managed before breach, on a trail an auditor can read
Mobility distribution

Three markets, one embedded engine: Green SM

MicroFlow distributes trip, food-delivery, and express-delivery cover inside the app, and spreads it across multiple insurers by design. See how MicroFlow works.

Sold inside the app, live in three markets
Carrier integration

A new carrier in days: the Vietnam insurer panel

ClaimFlow runs a ten-carrier Vietnamese insurer panel, each carrier connected through the same carrier-API adapter library.

A new carrier added in days rather than months
Underwriting

Multi-insurer routing on live premium: PVI and Oona

The carriers underwriting the cover MicroFlow distributes, each allocated its share by quota caps and routing rules.

Live premium routed across multiple carriers
Network scale

420+ centres: the VinFast national network

The service-centre network ClaimFlow is scaling toward. This is the target being built to, not a current count.

Rolling out across a national network
How it plays out

Two operations, in their own words.

Automotive claims · Vietnam

Claims across an automotive network

CLM‑2026‑0841 Tracking to SLA
  1. First notice of lossCaptured at the service centre
  2. Policy and coverage matchedSeconds, not a callback
  3. Severity scored, claim routedAI triage on intake
  4. Assessment drafted, fraud flaggedAdjuster co-pilot
  5. Workshop and parts dispatchedTracked against the SLA clock
Before 44 days
Built to reach 11 days

Every action on a per-tenant audit trail, which is what makes an outcome-based fee verifiable.

The challenge

An automotive-insurance claim touches a service centre, a workshop, a parts supplier and an insurer, each one built for its own part of the job and none of them built to hold the claim itself. Status sits in whichever conversation last happened, and the service-level clock becomes readable only after it has run out. Across a national network of hundreds of service centres that is not a staffing problem. It is a coordination problem that more staff would only make more expensive.

What we run

ClaimFlow runs the whole operation on one AI-native platform, on an outcome-based commercial model, with BeeVN across the VinFast service-centre network. First notice of loss is captured at the service centre and matched to policy and coverage in seconds. AI scores severity and routes the claim. An adjuster co-pilot drafts the assessment and flags fraud signals. Workshops and parts suppliers are dispatched and tracked against a real-time clock on the service-level deadline. Every action lands on a clean, per-tenant audit trail, which is what makes an outcome-based fee verifiable rather than argued.

The outcome

The operation is built to compress the cycle by roughly four fifths, service levels are tracked in real time rather than reconstructed after the fact, and a coordination problem becomes a running operation. The network is scaling toward its full 420-plus service-centre footprint.

Mobility distribution · Vietnam, Indonesia, Philippines

Distribution through a mobility super-app

TRIP‑COVER · IN‑APP Live in 3 markets
  1. Offered at the moment of needInside the booking, not after it
  2. Priced and confirmedMilliseconds
  3. Policy issued instantlyNo form, no branch
  4. Routed to the right insurerQuota caps and allocation rules
  5. Premium matched, period closedReconciliation that closes itself
Spread across the panel by design
Insurer AInsurer BInsurer C

One engine across Vietnam, Indonesia, and the Philippines. The next market is a configuration, not a rebuild.

The challenge

Insurance is usually sold where the customer is not: at a branch, through an agent, on a form filled out long after the moment of need. A mobility super-app has the opposite shape. The customer is already booking a trip or placing a delivery, and the moment cover is relevant lasts seconds. The hard part is not the product. It is issuing a policy inside that moment, routing it to the right underwriter, and reconciling the premium cleanly afterwards, across three markets with different carriers in each.

What we run

MicroFlow is a distribution engine that works with any broker and connects channels to underwriters, spreading business across multiple insurers by design, live through Green SM across Vietnam, Indonesia, and the Philippines. Cover is offered in-app the moment it becomes relevant, priced and confirmed in milliseconds, and issued instantly. The routing engine allocates each policy to the right insurer by quota caps and allocation rules, then matches premiums and closes the period automatically, on a clean audit trail. Capacity spreads across carriers as volume grows, and the period closes without a manual pass.

The outcome

Cover sold at the point of need rather than after it, across three markets on one engine, with reconciliation that closes itself rather than consuming a finance team. New carriers and new channels attach to connections that already exist, so the next market is a configuration, not a rebuild.

We author the standard, not just consume it

Open standards, authored per market.

Trisilva builds on OPIN, the open insurance standard, and authors the market profile that makes it operable in each market. Vietnam is the first profile: we write it, we keep it open, and every product runs on it. Authoring the profile, rather than only consuming it, is why the data model a carrier builds against is one they keep.

Read the open standards

Put the operation on the same platform.

Tell us what you run today. We will show you what it looks like in production on InsureFlow.

Singapore · Vietnam · Indonesia · Philippines