VeraLex

Problem

Legal service platforms need to manage complex workflows — matching lawyers to clients, reviewing applications, and tracking cases. Existing tools are fragmented, with no single system handling the full pipeline from intake to resolution.

My Role

I led product direction and built the frontend for a multi-role admin dashboard and a client-facing portal. Responsible for architecture decisions, UI implementation, and user flows.

Process

• Designed and built a 4-tier role-based dashboard (Super Admin, Admin, Reviewer, Analyst) with scoped access control and audit logging using Supabase Row Level Security.
• Implemented a case management system with status tracking and assignment workflows.
• Built a lawyer-client matching interface that surfaces relevant lawyers based on case type, jurisdiction, and availability.
• Developed the client-facing portal with application submission, status tracking, and secure document upload.
• Deployed on Vercel with Supabase (PostgreSQL + Auth) as the backend. Used shadcn/ui for consistent component design across the platform.

Outcome

Shipped a working platform with role-based access control, case management, and a client portal. Two Next.js 14 applications with a shared Supabase backend.

What I Learned

Building multi-role systems forces you to think about every screen from four different perspectives. The hardest UX problem was making the same data useful to an admin who manages everything and an analyst who only needs a slice.