The vision

Product Studio & Marketplace

Launch an insurance product without writing software: configure the listing, the proposal form, the pricing and the approval workflow — then publish it to a storefront where customers quote, apply and buy in minutes, on the web or mobile.

Rolling out in phases

The distribution suite is being built in independently shippable phases on top of iqava's live connected core — every sale it makes becomes a real policy on a real general ledger, not a lead in a spreadsheet. Some capabilities described below (pricing engine, visual workflow designer, in-app payment & the AI advisor) are on the roadmap — see What's live today for exactly what you can use right now. Talk to us about early access for your products.

What's live today

You can design a product end-to-end and publish it to a working public storefront where customers apply — right now, in the console under Marketplace → Studio:

  1. Create a product
    In Product Studio, add a product (motor, life, health, savings — any class). Give it a listing: title, tagline, benefits, badges, a call-to-action, price-from, currency and the countries it's available in.
  2. Build the proposal form
    Use the v2 form builder — multi-step, sections, conditional show/hide & require, calculated fields, signature, file uploads. Or upload your existing proposal-form PDF and let the AI draft the fields and rules for you to review.
  3. Publish
    A readiness check confirms the must-haves (name, category, at least one form field), then publishing takes a permanent version snapshot and puts a listing on your public storefront. Every publish is a new immutable version.
  4. Customers find & apply
    The cover appears on your marketplace and via the public API. The cover page renders your real proposal form; a signed-in customer's saved details pre-fill it automatically("apply on the go"). Their full answers are captured for you.
  5. Accept & onboard
    Review the application and accept it — iqava creates the customer's wallet identity and a CRM policyholder record from their answers. The proposal form is the onboarding definition.

Also live: the public API

Every published cover is available over a no-auth JSON API — GET /api/marketplace/listings (browse/search), GET /api/marketplace/listings/{id} (detail incl. the proposal form) and POST /api/marketplace/listings/{id}/apply — the surface a mobile app or partner integration consumes.

Coming in later phases

The pricing engine (rate books → an automatic quote), the visual workflow designer (routing & approvals), in-app checkout & payment (quote → pay → bind → certificate in the wallet), the AI advisor / clause-explainer, the native mobile app and embedded partner APIs are on the roadmap and described below as the intended end state — not yet available in the console.

The idea

Most insurance marketplaces are comparison sites: listings are brochures, a "quote" is an email, and a purchase is a callback. iqava is different because the marketplace sits on the same platform that runs the insurer's back office. A listing here is a running system: the quote executes the insurer's real rating rules, the application flows through their real approval workflow, and the purchase binds a real policy — with the certificate delivered to the customer's digital wallet in seconds.

ListingProposal formWorkflow & approvalPaymentPolicy in your wallet

Product Studio — launch products without code

Product Studio is where an insurer creates a complete, sellable product — like building an e-commerce listing, but for insurance. Each product brings together its listing (branding, images, benefits, badges, the call-to-action), its proposal form, its required documents, its pricing, its approval workflow and its full version history — published versions are permanent records, changes are new versions. Templates for the common lines (motor, medical, travel, fire, marine, life, group life, WIBA, SME and more) mean you start from a working product, not a blank page.

Proposal forms — including from your existing PDF

A drag-and-drop form builder with the field types real proposals need — repeatable sections (multiple drivers, multiple beneficiaries), calculated fields, signatures, GPS, file uploads — and conditional logic: select "commercial use" and the commercial section appears; exceed a value threshold and a valuation report becomes required.

Better still: upload the proposal form you already print. iqava reads the PDF and drafts the digital form for you — fields, sections, validation, and the conditional rules it can infer ("If YES, complete section B"). You review and correct the draft in the builder before anything is published; the AI proposes, you approve.

Workflows & pricing you control

Every insurer approves business differently. A visual workflow designer routes each application through your process — validation, document checks, underwriter review, manager approval above your authority limits, with SLA timers and escalation — while the pricing engine holds your rate tables, age and value bands, loadings, discounts, taxes and levies as configuration you edit, version and schedule. The final decision always remains with your underwriters.

For customers — insurance that behaves like a modern app

Customers keep one iqava account: a digital wallet holding their policies, certificates, receipts and renewal notices, and a stored profile that pre-fills any application — so buying cover on the go takes minutes. Claims are tracked like a parcel, renewals are one tap, and an AI assistant explains any clause of any policy in plain language.

Embedded distribution

The same products are available through APIs, so banks, SACCOs, dealerships and travel platforms can quote and sell inside their own apps — with iqava running the product, the workflow and the policy behind the scenes.

Who it's for

Insurers who want to launch and iterate products digitally without an IT project; brokers and bancassurance channels who want a storefront; and businesses that want insurance embedded in their own customer journeys. It runs standalone — you can use the distribution suite without adopting the full iqava back office, and grow into it later.

Want your products on it first? Talk to our team.