Book a systems review
How we work

Scope, configure, migrate, run beside you.

The team sits in Nairobi and knows how premium, claims and reinsurance move in this market. The engagement is staged so that nothing is switched off until its replacement reconciles.

Step 1

Scope

We sit with underwriting, claims and finance and map your products, rates, workflows, reports and integrations. You get a written scope with what migrates, what is configured and what is out.

Step 2

Configure and migrate

Classes, products, rates, clauses and treaties are set up in configuration. Policies, clients and open claims are migrated in cohorts with checker sign-off and a reconciliation you can audit.

Step 3

Run beside you

Our team runs the first cycles with yours: month-end, renewals, a claims run, the returns. Then we hand over, with a named contact and an escalation path that stays.

Three routes in

Route A

Modules beside your core

Claims, reserves and reinsurance run on AiCare and exchange data with the existing core through APIs. One system of record per aggregate, documented.

Route B

A new class or channel first

A new product, a bancassurance channel or a PSV book goes live on AiCare while the legacy book stays put. The team learns the system on business with no migration risk.

Route C

Full core, cohort by cohort

Migration in cohorts, cutover recorded per cohort, the old core retired when the last one reconciles.

Security and access control

Roles and permissions per screen and action, enforced at runtime. Maker-checker on receipts, payments, reserves, recoveries and requisitions, with the maker unable to approve their own work. Immutable audit logs with actor, timestamp and reason. Sign-in through your Active Directory or LDAP if you use one.

Privacy and data handling

A data processing agreement under Kenya's Data Protection Act, a named data protection contact on our side, and your data protection officer's sign-off before any record is migrated. Sanitised data for demonstrations; client data never leaves the agreed environment.

Hosting and data residency

PostgreSQL. A cloud region you choose, or your own servers. Residency, access and encryption at rest and in transit are agreed in the scope.

Backup, recovery and continuity

Backup schedule, retention, recovery objectives and restore tests are agreed in the scope and written into the contract, then evidenced on a schedule you set.

Implementation and migration controls

Cohort migration with checker sign-off. Reconciliation reports per cohort. A cutover register that names the system of record for every aggregate, so no record is written in two systems at once.

Support and escalation

A Nairobi team, a named contact, response times agreed per severity and a written escalation path. Support is someone who understands PSV risk and a treaty statement.

Integration

Documented APIs and a quotation web service. DMVIC through AKI, M-Pesa, SMS and email, bank payment files and sanctions screening are built in; anything else is scoped with its owner and a sandbox before it goes live.

Company

Founded in Nairobi in 2020 through Antler, backed by Antler and Mobility54. Two products launched with Kenyan insurers. BimaLab accelerator, 2021.

Does it replace our core, or sit beside it?
Either. It runs as the full core for general, medical and life, or the claims and reinsurance modules run beside an existing core and exchange data through APIs. The rule is that a record has one system of record at a time; we document which.
How is a new class of business added?
In configuration. Product Studio defines a class through its risk fields, rating inputs, cover period rules, clauses, taxes and levies, on the subclass. The underwriting team does it with us the first time and alone after that.
What about DMVIC, M-Pesa and our reinsurers?
DMVIC certificate issue, re-issue, verification and cancellation are built in through AKI. M-Pesa receipting is built in. Quota share and excess of loss treaties are set up as configuration and applied at underwriting and claim, with cessions, recoveries, cash calls and settlements tracked per policy.
How long does it take?
It depends on the book, the data and how many integrations are live. We say so after the scope, in writing, rather than quoting a number on a website.
Is it in production today?
The system runs on live workflows in a demonstration environment and is in evaluation with insurers. We would rather show you the motor, medical and life scenarios on cases shaped like your own than describe them.
What does a systems review involve?
Thirty minutes. You describe what runs the book today and what it cannot do. We come back with a short written view of what would migrate, what would be configured and how we would stage it. No customer data is needed.

Start with a thirty-minute systems review.

Tell us what runs your book today and what it cannot do. We come back with a written view of what would migrate, what would be configured and how we would stage it. If it makes sense, the next step is a demonstration on scenarios shaped like your own portfolio. Sanitised cases are fine; no customer data changes hands.

Book a systems review or call +254 719 453 171