Risk selection & pricing
Kinematic and contextual signals — speed, harsh events, night exposure, route type — into your rating factors. Price on observed behaviour, not proxies.
Motor underwriting · Claims · Distribution
Underwrite the driver. Settle on the evidence.
Telematics-based risk selection, usage-based pricing and automated FNOL for commercial and public-transport motor books — with the device written into the policy as a condition, so every risk you write is a risk you can see.
SUNTRACK · COMMAND CENTRE
LIVE
NOVA — “Fuel 61% · coolant 88 °C · no faults. 312 verified km today.”
Per driverRISK SCORED, NOT PER POSTCODE
On eventFNOL WITH A CRASH PACK
VerifiedMILEAGE FOR PRICING & RENEWAL
APIINTO RATING, POLICY ADMIN & CLAIMS
01 · What you get
From risk selection to settlement.
Usage-based renewal
Verified mileage and driver scores at renewal. Reward the good risks, re-price the bad ones, cut premium leakage.
Automated FNOL
Impact and rollover detection triggers first notice of loss with a crash pack: position, speed, driver and the seconds around the event.
Claims triage & fraud
Was the vehicle parked at the time of the alleged loss? Was the device active? Staged-accident and mileage anomalies, surfaced before the assessor is booked.
Policy-condition compliance
Active-device status per policy. Non-compliance visible before a loss, not argued after it.
Distribution
Fitted, consenting risks offered your cover at fitment. The device is the condition; the customer is already on the platform.
02 · Data products
What lands in your systems.
Driver risk score feed
Per identified driver, per policy, by API — with the contextual signals behind the score.
Verified mileage & exposure
Engine-bus distance, night and route exposure for pricing and renewal.
FNOL & crash packs
Event detection with position, speed, driver and the seconds around impact.
Compliance status feed
Active-device status per policy, with history — for underwriting and for claims.
03 · How it works
From policy wording to renewal.
01
Policy wording
Active device as a condition, with the data terms.
02
Data feed
Scores, exposure and events by API into rating and policy admin.
03
Claims workflow
FNOL, crash packs and fraud flags into your process.
04
Distribution & renewal
Fitted risks offered your cover; renewals priced on observed behaviour.
04 · Questions
What underwriters ask.
Is the device VESA-certified?
Certification is part of our programme and progressing — ask us for the current status. Where your wording requires a VESA-listed unit for theft cover, we will tell you exactly where we stand before you write a policy.
How is driver identity established?
Drivers identify with a physical ID at ignition. Scores are per driver, not per vehicle, with consent taken at fitment under POPIA and benefits that reward good scores.
Can this feed our rating and claims platforms?
Yes — per-policy scores, exposure and events by API, FNOL and crash packs into your claims workflow, and exports for actuarial review.
Do you work with UMAs?
Yes. We work with insurers directly and with UMAs under their binder arrangements. Distribution is structured to your licensing.
What is usage-based insurance (UBI)?
Motor cover priced on observed behaviour — kilometres actually driven, how and when the vehicle is driven — rather than on proxies like postcode and vehicle age. Telematics supplies the observed behaviour, per driver, at pricing and at renewal.
What is automated FNOL?
First notice of loss raised by the device itself when an impact or rollover is detected, with a crash pack attached — position, speed, driver and the seconds around the event — so the claim opens before the policyholder calls.
05 · Talk to us
Price the risk you can see.
Tell us about the book — a data-feed spec and a pilot proposal within one business day.