For insurers and investors
Insurance administration cheap enough to make very small policies economically viable.
TopSure runs distribution, onboarding, policy administration and claims verification for one product: accidental death cover for gig workers, starting in Indonesia. A licensed insurer issues the policy, holds reserves and carries the risk.
Prototype. TopSure is not an insurer and does not hold an OJK insurance licence. No insurer partnership is in place yet; the console uses sandbox carriers and fictional data.
The model
Simplicity is the cost advantage: one product, one payout trigger, fixed benefit amounts and minimal data. Nothing is built that doesn't cut acquisition, servicing, claims or fraud cost.
Straight-through claims
Target: 90–95% of clean claims need little or no manual processing once the data integrations exist. The AI reads and cross-checks evidence. It does not decide.
Not a single opaque score. Each fact lists the sources that support it, each source's weight and any source that contradicts it. Insurers and auditors can see exactly why a fact counted as verified.
Coverage rules engine
The conditions below are rendered live from the product configuration. The insurer's wording sets them; the AI only supplies the facts.
Every condition passes at or above 95% confidence, nothing is missing and fraud risk is LOW. The package goes to the insurer, or is approved under delegated authority if the insurer grants it.
A fact is unknown or below threshold, or a required document is missing. The family is told exactly what to add.
Sources conflict, a condition fails or fraud risk is MEDIUM or HIGH. A person reviews. Only the insurer can decline.
Policies, payments and claim states live in a transactional database behind strict state machines.
Payouts follow an insurer decision or the insurer's written delegation, never a model output.
Coverage comes from the insurer's wording, encoded as versioned configuration.
AI cost
A model router sends each task to the cheapest tier that can do it. The reasoning model runs only when evidence conflicts or fraud signals trigger. Personal data is redacted before any external model call.
| Tier | What | Unit cost | PII |
|---|
Unit costs are placeholder assumptions in IDR, to be replaced with contracted prices.
Insurer integration
Every insurer integration sits behind one interface. Adding or replacing an insurer means writing one adapter, whether its systems use an API, file exchange or a portal. The customer app, the claims engine and existing policies stay untouched.
Regulatory architecture
Built on the assumption that TopSure is a technology and distribution company working with a licensed Indonesian insurer. The interface always names the insurer that underwrites the cover.
Each event chains to the previous one by hash, so any edit or deletion is detectable. Payloads are scrubbed: no ID numbers, phone numbers, account numbers or names.
Transitions not listed are rejected. Only insurer review can lead to a decline.
Security and privacy
Partner with TopSure
We're looking for a licensed Indonesian insurer to underwrite RideLife, and for reinsurance and investment partners.