A data feed is not a product.
We launched Kenya's first pay-per-kilometre motor cover with two insurers. The telematics was the easy part. The product needed rating on distance, billing by the kilometre, an app for the customer, claims with first notification of loss, and a policy lifecycle the core could not run. So we built all of it, and that is what we now do for insurers with a product to bring to market.
AiCare is the operating partner for the launch, not a telematics vendor. Our team runs the pilot with yours. When the product is stable, we hand over.
Since the first launches we have moved from hardwired devices to the phone, with a six-parameter driving score that runs on the customer's handset at a fraction of the cost per vehicle. A pricing model reviewed by independent actuaries maps an insurer's existing annual rates to distance, so a pay-per-kilometre or pay-how-you-drive product is priced from the book you already have.
Product rules and rating
Cover, exclusions, rating on a distance or behaviour axis, reward mechanics that survive the actuary.
Customer onboarding app
Sign-up, consent, vehicle and driver details, odometer or trip capture, statements.
Data capture and driving score
Trips from the phone, scored on acceleration, braking, cornering, speeding, fatigue and phone use.
Policy administration and billing
Distance-native policy records, kilometre billing, top-ups and renewals on our core or through APIs into yours.
Claims
First notification from the app, trip evidence attached to the claim, reserves and payments in the same ledger.
Engagement and rewards
Feedback that changes driving, and rewards the customer notices.
Reporting
Loss ratio by band, exposure by kilometre, retention, and the board pack.
Timing, in practice: scope in weeks, integrate in weeks, pilot for one full scored window, then scale. We quote after a requirements exchange, not before.
| Route | km | Score |
|---|---|---|
| Westlands to CBD | 11.2 | 84 |
| CBD to Embakasi | 17.8 | 71 |
| Embakasi to Westlands | 19.4 | 79 |
Kenya's first pay-per-kilometre motor cover, in market with two underwriters.
The product
Motor cover for private cars driven under 10,000 km a year, priced on distance. Britam launched the first version as Motomatic; Takaful Insurance of Africa launched its own under the name TIA Switch, with a customer app, a rewards programme and a claims process.
What it took
A telematics device in the vehicle, a scoring model built on more than two million kilometres of Kenyan driving data, including a contextual speed map that sets a safe speed by hour of day for every 100 m of most major Nairobi roads, and then everything around the data: rating on distance, billing by the kilometre, onboarding, first notification of loss from the app, and a policy lifecycle the insurers' cores could not run.
What we learned
The feed was the easy part. The value sat in the systems around it, and a launch fails if the core cannot price, bill and service the product. That lesson is why AiCare builds and runs the full stack for a launch today, and why our own core is distance-native.
What changed since
Devices gave way to the phone, which removes the hardware cost per policy. The score grew to six parameters. A pricing model reviewed by independent actuaries now maps an insurer's existing annual rates to distance, so a new product is priced from the book it already has. A further launch is in evaluation with an insurer.
Portfolio results from these launches are held under the insurers' data-sharing terms and are discussed in a meeting rather than published here.
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.