A step-by-step plan for adding motor insurance to a car marketplace: where the offer belongs in the journey, the data contract, the build phases, and the operational pieces teams forget.
A car marketplace is the most natural home embedded motor insurance has. The transaction is high-intent, the vehicle data needed for a quote is already on the listing page, and in Saudi Arabia the buyer has a legal obligation to insure before the car can be registered in their name. This guide lays out how to actually build it — the journey placement, the data contract, the phasing, and the operational work that determines whether the line survives its first quarter.
The short version: start with a quote at the moment of purchase commitment, not a banner on the listing page; treat vehicle and buyer data as a formal contract with your insurance partner; and ship in three phases, each of which earns the right to the next.
Step 1 — pick the moment, not the page
Marketplaces usually ask where to put the insurance widget. The better question is when the buyer's mind turns to insurance. That moment is purchase commitment: reservation paid, financing approved, or handover being scheduled. Before that point, insurance is noise competing with the buying decision. After handover, you are competing with every aggregator the buyer can google.
- Listing page: awareness only. A line noting that insurance can be arranged at checkout is enough. A full quote here is wasted work — most viewers never buy the car.
- Checkout or reservation: the primary placement. The buyer has committed; the remaining jobs are payment, registration and insurance. Put the real quote here.
- Post-purchase handover flow: the safety net for buyers who skipped the offer. A single reminder tied to the registration task outperforms repeated promotional messages.
Step 2 — write the data contract before the UI
The quote is only as good as the fields behind it. Agree these with your insurance platform up front and treat changes like API changes, with versioning and notice.
- Vehicle: identification (sequence number or chassis/VIN), make, model, year, estimated value. Marketplaces have an advantage here — the listing already contains most of it, verified at intake.
- Buyer: national ID or iqama number and date of birth, with consent captured in your flow for passing them to the insurer.
- Transaction: sale price and financing status. A financed car usually needs comprehensive cover, which changes what you should quote first.
One integration decision matters more than teams expect: pre-fill everything you know, ask for nothing you already have. Every re-typed field is measurable drop-off, and a marketplace that asks the buyer for the car's model year signals that the offer is bolted on.
Step 3 — ship in three phases
- Phase one, referral with pre-fill. The buyer taps through to a quote flow that is already populated with the car and their details. No premium shown in your UI yet. This validates demand with minimal build and gets your data contract working under real traffic.
- Phase two, embedded quote and bind. Prices render inside your checkout; policy issuance happens without the buyer leaving your flow. This is where attach rates move meaningfully, and where you need document delivery, payment reconciliation and a support path in place on day one.
- Phase three, portfolio journeys. Renewal reminders anchored to policy expiry, cover for the seller's gap period, upgrade offers when a TPL buyer's car is still nearly new. These compound the economics but only make sense once phase two runs cleanly.
On platform choice: this is what an infrastructure layer is for. Yasmina's model — one API in front of licensed insurers, a sandbox to build against from day one, with production approval typically turned around in about a day — exists so a marketplace ships phase one in weeks, not quarters. Whatever platform you use, insist on a sandbox that behaves like production and on seeing the regulatory permission that lets the offer run in your market.
Step 4 — the operational layer nobody scopes
- Who answers the first claim call? The buyer will contact you, not the insurer, because they bought on your platform. You need a documented handoff, not a shrug.
- Refunds and cancellations. A cancelled car sale must unwind the policy inside the cooling-off rules. Build this before launch; it is miserable to retrofit under a complaint.
- Reconciliation. Finance needs premium collected, revenue share earned and refunds netted, per policy, monthly. Ask your platform to show you this report before you sign, not after.
What to measure, in order
- Offer view rate: what share of completed purchases actually saw a quote. Placement problems show up here first.
- Attach rate on viewed offers: the honest conversion number.
- Thirty-day survival: policies still active after the cooling-off window. Attach without survival is a mis-selling signal, not a revenue line.
- Renewal capture in year two: where marketplace insurance stops being a checkout feature and becomes a book of business.
A marketplace that follows this sequence has a realistic path from zero to a functioning insurance line in one quarter. The teams that struggle are almost always the ones that started with a widget and worked backwards to the data — do it in the other order.