MyAdmin360:
one command center
for insurance ops.
An insurance agency was losing new agents to an onboarding process spread across three portals that never shared data. Admins spent most of their day re-keying what another tool already knew. I designed one platform where admins, agents, and sub-agents each see their own slice of the same system, cut contracting from seven steps to three, and built the component library that now runs every product the company ships.
The fragmentation problem
Insurance agencies operate across a complex hierarchy. Admins, agents, and sub-agents all need different views of the same data. The legacy system at 834 Labs was a patchwork of disconnected tools: separate portals for contracting, production tracking, and agent management, none of which talked to each other. The result was duplicated data entry, missed contracting deadlines, and an onboarding process so painful it was losing agents before they ever sold a policy.
I designed MyAdmin360 to unify this chaos into a single, role-aware platform. Every user gets a tailored experience, from a top-level admin managing hundreds of agents to a brand-new sub-agent checking their first commission statement, all built from the same underlying design system.
Contracting went from seven steps to three, and a $1.2M book of business became readable on one screen.
The permission-aware navigation system scales the same interface from a 3-field sub-agent view to a 40-column admin production dashboard, without either user feeling like the tool wasn’t built for them.
Stakeholder discovery & legacy audit
I shadowed ops teams across three roles, documented every tool they touched, and mapped the existing data flows. The critical finding: 60% of admin time was spent on tasks that existed only because the tools didn’t share data: re-entering agent information, manually reconciling production reports, and chasing contracting status across three different portals.
Information architecture & role mapping
I designed the permission hierarchy first, before any visual work. Each of the three user tiers (Admin, Agent, Sub-Agent) got a tailored navigation structure, dashboard layout, and data scope, but all built from the same base components. This meant I could add a new data module once and have it automatically adapt to all three permission levels.
Design system & component library
I built the design system using Atomic Design principles: atoms (buttons, inputs, badges), molecules (form groups, stat cards, table rows), organisms (dashboard panels, agent profile cards, contracting wizards), and templates (role-specific page layouts). The system included a strict color language for status states and a data-density scale that could shift from summary view to full-detail with a single toggle.
Contracting workflow redesign
The original 7-step contracting process was the biggest pain point. I redesigned it as a 3-step wizard with smart defaults (pre-filling known carrier requirements), inline validation (catching errors before submission), and a real-time status tracker that shows exactly where each contract sits in the approval pipeline. The result: agents can go from “start contracting” to “submitted” in under 5 minutes.
One dashboard, three realities
Admins see the full org. Agents see their downline. Sub-agents see their own numbers. Same underlying component, zero redundant engineering, zero user confusion.
7 steps → 3, with guardrails
Smart defaults pre-fill known carrier requirements. Inline validation catches errors before submission. Real-time status tracking shows exactly where each contract sits, so agents go from “start contracting” to “submitted” in under 5 minutes.
Production analytics
Interactive production dashboards with drill-down capability, from org-wide totals to individual agent performance, with filterable date ranges, carrier breakdowns, and export functionality.
Agent hierarchy management
Visual org-chart navigation for managing agent relationships, upline/downline structures, and commission splits, with drag-and-drop reassignment and bulk operations.
Commission statements
Automated commission statement generation with carrier-level detail, adjustable splits, and downloadable PDF exports, replacing the manual spreadsheet process that consumed 8+ hours per month.
50+ components. Zero design bottlenecks.
A fully documented component library with 50+ reusable components, consistent status color coding, responsive grid system, and accessibility guidelines, so engineering can ship new features without design bottlenecks.
I built this working prototype myself with AI-assisted development, from the role-aware navigation to the contracting wizard, so stakeholders could click through the real flow before engineering committed to it. What usually waits on a sprint took days. It’s live at app.myadmin360.com.
Three roles is one product, not three
The temptation was to design an admin app, an agent app, and a sub-agent app. Designing the permission model first meant one navigation, one table component, and one dashboard layout that change scope with the role. A sub-agent sees three fields; an admin sees forty columns; both are the same screen. That is why adding a module later costs one design, not three.
Workarounds are requirements in disguise
Admins were reconciling production reports by hand because the old portals disagreed with each other. Those manual steps were not noise to remove; they were the clearest spec for what the analytics view had to do. Shadowing people before scoping is how you find the feature hiding inside the workaround.
The design system paid for itself on the next product
Building the component library up front felt slow. By the time the commission calculator, compliance tracker, and carrier portal came along, each was assembled from existing parts and designed in days rather than weeks. The library is now what engineering builds from, not a reference they look at.
A clickable build ends arguments a Figma file cannot
Static mockups of the three-step contracting flow invited opinions. A prototype where stakeholders could actually submit a contract invited decisions. I now build the working version of anything contentious before asking for sign-off on it.
Have a complex problem
that needs untangling?
I’m available for new roles and the right freelance projects.