Insizwe
An insurance broker's quote wizard, lead pipeline and staff back office
Website and back office for Insizwe, a Zambian insurance broker. Visitors price a policy in a four-step wizard, the quote lands in a staff system as a tracked lead with its marketing source attached, and staff work it through to won or lost behind two-factor sign-in.

- Built for
- Insizwe Insurance (via Ballo Innovations)
- My role
- Design and full build: the public site, the quote wizard and pricing, and the admin API the team works leads in.
- When
- 2026
- Next.js
- TypeScript
- GSAP
- Framer Motion
- Fastify
- Prisma
- PostgreSQL
- Argon2
- Zod
The longer version
What it is
A broker sells trust and a quick answer to "how much will this cost". The site leads with both: a plain-language home page, and a quote wizard that gives a real indicative number in four steps instead of a "we'll call you" form.
From quote to follow-up
A quote isn't the end of the journey; it's the start of a sales conversation. So every submission becomes a lead with a status (new, contacted, qualified, won, lost or spam), a reference number, notes that keep their author even after a staff account is removed, and the marketing source that brought the visitor in.
What isn't built yet
There is a customer portal page, but it's a placeholder; the work so far is the public site, the pricing and the staff side.
Screens and demos
What it looks like in use, not just what it was designed to do.

Home page 
Products 
Quote wizard, step one 
On a phone
What made it hard
The problems worth reading about. Everything else in this system was ordinary work.
- 01
The quote wizard prices thirteen products, from motor to employers' liability, as sum insured times the broker's published rate plus the 5% levy, and shows basic premium, levy and total. Sliders are tuned per product, and every figure is labelled indicative, subject to underwriting.
- 02
Each quote gets a short INS reference that staff and customer can both read over the phone, and arrives in the back office with its UTM source, ad click id, landing page and visit count, so the team can see which campaigns produce business.
- 03
Leads reach the admin API server to server only, behind an API key and schema validation, with the public endpoint rate limited per visitor.
- 04
Staff sign in with an Argon2id password and an emailed one-time code. Refresh tokens rotate on every use with a short grace window, so two open tabs refreshing at once don't sign each other out. Four roles plus per-person overrides control what each person can do.