WorkCase study2026Product engineering
BrokerLogs
A multi-tenant workspace where an employee-benefits brokerage runs its book: team spaces for conversation and delegation, clients and policies in one place, compliance deadlines tracked, and every group’s renewal visible from start to finish. We built it for a working benefits agency, and the team there uses it every day.
- Role
- Product design, architecture, build
- Stack
- Next.js / Clerk / Drizzle + Neon
- Surface
- Multi-tenant SaaS
- Status
- Live, used in-house
A brokerage runs on email, Excel, and a dozen carrier portals.
A small benefits agency carries hundreds of groups, each with policies, carriers, and a renewal date that cannot slip. The book lives in spreadsheets, the conversation lives in email, and the deadlines live in someone’s head. When a renewal is missed, a client feels it.
BrokerLogs pulls that work into one place. The team talks in spaces, delegates with tasks, keeps the whole book of business in a shared system, and watches every group move through the renewal pipeline.
We built it multi-tenant from the first commit so it can serve more agencies later. Today it runs in-house at one agency. It handles group and policy metadata only, never protected health information, and that line is drawn in the data model itself.
Everything the agency tracks, in one workspace.
Spaces
Slack-style spaces where the team talks and hands off work. Conversations that used to sit in scattered email threads now live in the same app as the work they’re about.
Book of business
Clients, policies, and carriers live in one shared system, so everyone on the team works from the same book.
Compliance and deadlines
The dates that cannot slip are tracked and flagged before they come due. If one passes, BrokerLogs marks it overdue so the team sees it right away.
Renewal pipeline
Each group moves through defined renewal stages that the whole team can see at a glance, which makes a stalled renewal easy to spot.
The architecture is the product.
A workspace that holds an agency’s whole book has to be right about two things above all: whose data is whose, and what it will never store. Both are settled in the data model, before a single screen is drawn.
Multi-tenant from commit one
Each agency is a Clerk organization, and every query is scoped to that tenant in the data layer itself.
Type-safe data layer
Drizzle over Neon Postgres, with Zod validating data at the boundaries and TypeScript in strict mode throughout. The shape of the book of business is checked from the form to the database.
No PHI, by design
The schema is built for group and policy metadata only. It has nowhere to put protected health information, so that data can’t be stored by accident.
Tested end to end
Vitest covers the logic, and Playwright runs the real flows in a browser, including a renewal moving through the pipeline.
Observability and email
Sentry reports production errors to us. Resend sends the app’s transactional email from typed React Email templates.
Built to feel calm
Base UI primitives, a small set of components, and color used only to show status. Brokers spend the day handling their clients’ benefits and renewals, so the interface stays quiet and out of the way.
Simple enough for a veteran broker. Deep enough for a sharp new hire.
Many brokers don’t think of themselves as software people; they live in email, Excel, and carrier portals. So the design bar was explicit: an experienced broker should never need training to use it, and a sharp new hire should be able to master it.
That shows up in the details. Icons carry text labels. A confirmation says exactly what will happen. An empty screen explains what belongs there. Keyboard shortcuts are there for people who want them, and everything works without them. Small touches, like sidebar themes, give the app some personality without getting in the way of the task.
Four tools down to one, and no PHI.
The decisions that make it safe to run a book on. BrokerLogs is in daily use at one benefits agency, so adoption numbers come later.
Tools it replaces
4 to 1
Team chat, the book of business, compliance tracking, and the renewal pipeline share one workspace. That work used to be split across email, spreadsheets, and carrier portals.
PHI stored
0
BrokerLogs stores group and policy metadata only. The schema has no place for protected health information.
Tenancy model
1org each
Every agency is its own Clerk organization, and every query is scoped to it. One tenant can never see another’s book.