2025 · Website development

PolisaSave

PolisaSave is the Slovene insurance-comparison site that Niro Digital built for PolisaSave in 2025: product pages across six insurance categories, a blog and FAQ, and a five-step quote form that feeds a CRM.

Client: PolisaSave
Industry: Insurance brokerage / comparison
Year: 2025
What we did: Website development

Visit polisasave.eu

The constraint

PolisaSave sells insurance to Slovenian consumers as a free, independent broker: you answer one questionnaire instead of ringing round Triglav, Sava, Generali and Allianz yourself. That promise only works if the enquiry is actually picked up, and if the paid social buying it can tell a real enquiry from a page view. So we built the site and the write path behind it. Six insurance families each get their own landing page, with a blog, an FAQ and a review carousel around them, and everything points at one five-step quote form. Submitting runs a single Next.js Server Action: Zod validates the answers, Meta's Conversions API gets the conversion server-side, and the lead is created in a self-hosted Twenty CRM. There is no database of its own — the CRM is the system of record.

The system

//01Homepage with one positioning line and a single free-quote call to action

PolisaSave insurance hub — six product families under one overview page

//02A hub listing six insurance families, each with its own landing page

//03Motor cover as a full product page, not a row in a table

PolisaSave quote questionnaire, step 1 of 5 — choosing insurance types

//04A five-step quote questionnaire, Zod-validated inside one Server Action

//05An FAQ grouping the objections about cost, process and independence

//06A rated review carousel on the homepage, above the fold

//07A blog of insurance guides as the search-facing content arm

//08The same single call to action on a phone

What changed

//01Visitors submit one questionnaire instead of approaching each insurer separately
//02Every enquiry lands in a self-hosted Twenty CRM, the system of record
//03Meta receives the conversion server-side, so paid social optimises on enquiries
//04Each insurance family has its own page to rank on and link from

What we'd do differently

PolisaSave is our client's business, not ours: we built and maintain the site, they run the brokerage. The site's "over 1000 people helped" is PolisaSave's own claim, shown on their homepage; we did not audit it and it is not our figure. Everything the site knows lives in their CRM, which keeps the build small but means the site itself can show a visitor nothing about their own enquiry beyond a status page. What we'd do differently: the review carousel and that claim are copy in the repo, so the client cannot update either without us — both belong behind something they can edit.

All projects