Skip to content
Aivex
All work

Independent insurance agency · Operations portal

An operations portal for an independent insurance agency

We built an independent insurance agency a single portal that pulls leads, content, tasks, inquiries, calendar, and analytics into one place — the agency's whole working layer.

An operations portal for an independent insurance agency — screenshot

The agency's day-to-day work lived across a half-dozen tools and a lot of memory. Leads came in by phone, web form, and referral. Content drafts sat in three different inboxes. Follow-up was tracked in someone's head. The owner was the bottleneck for almost every approval.

We built them a single operations portal — the agency's whole working layer in one place.

What's in it

  • Overview — the agency's pulse: active leads, content drafts in progress, pending tasks, new inquiries this week
  • Leads — capture, score, assign, and follow up; the review queue surfaces what needs attention today
  • Content pipeline — drafts, scheduled posts, and approval flow with priority and status
  • Tasks — owner-driven work with priorities and a recent-activity log
  • Inquiries — first-touch triage before something becomes a lead
  • Calendar, quotes, reviews, feedback, analytics — the rest of the agency's operating surface, in the same shell

The point isn't that each module is novel. It's that they all live in one portal, talk to each other, and the team learns one place instead of six.

How it gets used day to day

A team member opens the portal in the morning. The Overview shows the day's queue: leads to review, content drafts ready for sign-off, tasks coming due, fresh inquiries to triage. Each panel deep-links into the full module — Leads to Review opens the lead, Pending Tasks opens the task, Content Pipeline opens the draft.

The owner sees the same surface but with a higher signal-to-noise filter. Only the things that actually need their decision land on their dashboard.

What it replaced

Inboxes. Spreadsheets. Sticky notes. Group texts. The "where are we on that thing" Slack messages that nobody answered. A loose collection of tools where work got lost in the gaps between them.

What's underneath

Standard production stack: Next.js, Convex, Clerk, Resend, plus integrations with the tools the agency was already using. Built so the agency owns the data and the system can grow with the team rather than locking them into someone else's roadmap.

This is the kind of work we like — a small, owner-led business with messy operations and no patience for vendor sprawl. One portal. The whole agency.

Working on something similar?

Let's see if we can help.

Request a discovery call