Legal Practice OS
A multi-tenant legal operations platform that connects inquiry intake, conflict checking, consultations, onboarding, matters, documents, billing, reporting, and firm administration.
Role
Product Designer, Systems Architect, AI-Assisted Full-Stack Developer
Platform
SaaS Platform
Status
Live Beta
Year
2026
Private product environment
The live application contains authenticated legal records. This case study focuses on architecture, workflows, quality, and verified outcomes without exposing private client data.
Overview
Legal Practice OS connects the complete legal-service lifecycle into one organization-scoped workspace. It gives firms a single operational system for intake, conflict checks, consultations, client onboarding, matters, documents, deadlines, billing, reports, and administration.
The product is designed for authenticated legal records, so the public portfolio focuses on architecture, workflows, quality, and verified audit results rather than exposing private repositories or client data.
Problem or opportunity
Legal operations often break down when intake, checks, matters, deadlines, and billing live in separate tools.
- Fragmented legal workflows
- Incomplete intake information
- Missed conflict checks
- Disconnected matter records
- Unclear task and deadline ownership
- Inconsistent billing
- Weak role and tenant controls
- Limited operational reporting
Solution
The platform organizes legal work around a governed matter lifecycle. Each workspace validates organization membership, role permissions, and active context before users can access firm data.
The result is a practical operating system for legal teams: structured enough to protect records and flexible enough to follow real client-service workflows.
Core workflow
The lifecycle is modeled as one connected path from first inquiry to reporting and administration.
- 1
Inquiry
- 2
Conflict Check
- 3
Consultation
- 4
Engagement
- 5
Onboarding
- 6
Client & Matter
- 7
Work Management
Tasks, documents, notes, and deadlines stay connected to the matter record.
- 8
Billing Records
- 9
Invoicing
- 10
Reporting
Key platform features
Grouped modules show the operating system without turning the case study into product documentation.
Intake and engagement
Structures the journey from first contact through client acceptance.
- Inquiry intake
- Conflict checking
- Consultations
- Engagement and onboarding
Client and matter operations
Keeps client records, matter context, and communication history connected.
- Client management
- Matter management
- Notes and communications
Work management
Organizes the day-to-day execution layer around deadlines and matter activity.
- Tasks and deadlines
- Calendar and events
- Document management
Billing and invoicing
Turns tracked work into billing records and production-ready invoice output.
- Time and expense tracking
- PDF invoicing
Firm operations
Gives administrators visibility into activity, settings, and operational reporting.
- Reporting
- Administration
SaaS foundation
Supports organization onboarding and secure access controls for firm workspaces.
- Organization onboarding
- Role-based permissions
Gallery
Product media can be added here without changing the page renderer.
Dashboard overview
A workspace overview for legal operations and firm activity.
Matter workflow
A connected workflow for matters, tasks, documents, and deadlines.
Billing and invoicing
Time, expenses, and invoice generation inside the firm workspace.
My role
I defined the product architecture, legal workflows, relational data model, permission system, user-experience direction, acceptance criteria, testing process, and deployment strategy. AI-assisted development accelerated implementation and iteration, while product decisions, security boundaries, review, testing, and final validation remained under my direction.
AI-assisted, human-directed development
AI accelerated implementation, debugging, refactoring, documentation, and test scaffolding. Product architecture, workflow decisions, security boundaries, acceptance criteria, review, and final validation remained human-directed.
AI accelerated
- Implementation scaffolding
- TypeScript fixes
- Prisma query construction
- Component refactoring
- Debugging
- Documentation
- Test scaffolding
- Deployment troubleshooting
Human direction and ownership
- Product requirements
- System architecture
- Workflow design
- Data model decisions
- Permissions and security
- UX direction
- Acceptance criteria
- Code review
- Manual testing
- Deployment decisions
- Final validation
Architecture and stack
Application flow
- Next.js Interface
- Server Components & Actions
- Organization + Permission Resolver
- Prisma ORM
- Supabase PostgreSQL
Identity flow
- Supabase Auth
- Verified User
- User Profile
- Organization Membership
- Active Workspace
Technology stack
Technical challenges
Multi-tenant workspace isolation
Every sensitive workflow is scoped around organization membership and active workspace context.
Server-side role enforcement
Permissions are validated server-side instead of relying on UI-only visibility.
Secure organization switching
Workspace changes maintain tenant boundaries and prevent accidental cross-organization access.
Invitation-token security
Invitations are handled as controlled entry points into organization membership.
Idempotent profile creation
Profile setup is designed to avoid duplicate user records across auth lifecycle events.
Transactional organization creation
Organization setup keeps membership, workspace, and user state consistent.
Prisma server/client separation
Database logic remains server-side to protect credentials and tenant data.
Server Component cookie restrictions
Auth and workspace reads account for App Router server boundaries.
Production invoice PDF generation
PDF invoice output was validated for production runtime behavior.
Quality assurance
Build integrity
- Prisma schema validation
- Prisma Client generation
- TypeScript checking
- ESLint
- Production builds
Functional validation
- Targeted automated tests
- Manual workflow testing
- Manual role testing
UI and live validation
- Live-domain authentication testing
- Tenant-isolation testing
- Lighthouse audits
Results
Dashboard Lighthouse audit
90
Performance
98
Accessibility
100
Best Practices
100
SEO
0.6s
First Contentful Paint
0.8s
Largest Contentful Paint
0ms
Total Blocking Time
0
Cumulative Layout Shift
Project takeaways
The practical takeaways from translating a regulated service workflow into a private beta SaaS product.
Scope
Designed as an end-to-end legal operations platform covering intake, conflicts, onboarding, matters, work management, billing, reporting, and administration.
Implementation approach
Combined human-led product architecture with AI-assisted implementation, manual review, and production validation at key stages.
Refinement backlog
Continue improving form labeling, heading structure, visual documentation, and production observability as the private beta expands.
What this project demonstrates
Legal Practice OS demonstrates how a complex, regulated service workflow can become a usable, role-aware SaaS product without flattening the nuance of legal operations.
- Secure multi-tenant product architecture
- Workflow-driven system design
- AI-assisted, human-directed delivery
- Production deployment and validation
More work is being documented.