Car Insurance Purchase Flow Development by Roman RobertCar Insurance Purchase Flow Development by Roman Robert

Car Insurance Purchase Flow Development

Roman Robert

Roman Robert

carmatik.ro sells car insurance alongside cars. The flow had to take a visitor from a licence plate to a paid policy without leaving the site, and treat individuals and companies as two different sets of rules. I owned the frontend and contributed to the design in Figma.

What I built

Five steps: contact, vehicle, owner, period, then offers and payment, with a stepper that tracks where you are.
Two branches. Individuals and companies get their own fields, validation and steps. Logged-in users skip the contact step entirely.
A national-registry lookup. An ANAF call fills a company's data from its tax ID, so nobody retypes it.
Offers compared side by side from several insurers, with 6 and 12-month tariffs and direct-settlement pricing.
A conditional document upload for unregistered vehicles, with dual file inputs and a consent-gated submit.
Checkout through a NETOPIA payment redirect.

The hard part

This is the most conditional flow on the platform.
Rather than write bespoke fields per step, I built one type-driven input that covers every case: static option lists, backend-sourced lists like car manufacturers, and key/value maps.
All five steps compose from the same components, and the branching lives at the flow level so the shared inputs stay clean and reusable.
That is also what lets the whole module move into the insurance backoffice later without a rewrite.

Result

Live at carmatik.ro/asigurari. A visitor quotes, compares and pays in one sitting, on desktop or phone.
Screens are in Romanian, the platform's home market.
Full case study, screen by screen: www.romanrobert.com/work/insurance-purchase-flow
Like this project

Posted Aug 3, 2026

A five-step flow on carmatik.ro where individuals and companies quote, compare offers from multiple insurers and buy car insurance online, payment included.