A product system that captures data once and prepares bank-ready case packages.
Product system
Automation-ready
Compliance flow
Role: Product Designer• System Designer
Timeline: 2 Months
Tools used:
Figma
Cursor
Next.js
Supabase
A CRM that turns fragmented brokerage work into a single, trackable pipeline.


A product system that captures data once and prepares bank-ready case packages.
Product system
Automation-ready
Compliance flow
Role: Product Designer• System Designer
Timeline: 2 Months
Tools used:
Figma
Cursor
Next.js
Supabase
A CRM that turns fragmented brokerage work into a single, trackable pipeline.
Credit brokerage work is typically spread across messages, spreadsheets, scans, and bank-specific requirements. FCZone needed one operational system that standardizes intake, reduces manual steps, and prepares consistent packages for bank submission.
Key journeys: Intake • Validation • Document set • Bank package • Status tracking
Broker work is fragmented across channels and formats. That slows handling, increases mistakes, and makes tracking difficult.
Designed a CRM workflow where client data is entered once, structured for compliance, and reused across the pipeline. Added statuses, ownership, and history so every case is traceable.
Faster handling per case, fewer manual errors, and a scalable foundation to connect website calculators and forms to operational processing.
Built as an automation-ready product system using Supabase and Next.js, enhanced with LLM-assisted workflows and Cursor-driven iteration.
• Structured client profile and case record
• Consistent fields for downstream packaging
Why it matters: Less retyping, fewer inconsistencies.


• Structured client profile and case record
• Consistent fields for downstream packaging
Why it matters: Less retyping, fewer inconsistencies.
• Defined stages from intake to submission
• Ownership and progress visibility
Why it matters: Faster coordination and fewer stalled cases.


• Defined stages from intake to submission
• Ownership and progress visibility
Why it matters: Faster coordination and fewer stalled cases.
• Organized documents and data in a consistent structure
• Ready for bank-specific formatting layers
Why it matters: Reduces last-minute chaos and missing items.


• Organized documents and data in a consistent structure
• Ready for bank-specific formatting layers
Why it matters: Reduces last-minute chaos and missing items.
• Case notes and structured updates
• Clear timeline of what happened and when
Why it matters: Better compliance and accountability.


• Case notes and structured updates
• Clear timeline of what happened and when
Why it matters: Better compliance and accountability.
• Designed to accept calculator and form outputs
• Foundation for automation workflows
Why it matters: Website becomes the front door of operations.


• Designed to accept calculator and form outputs
• Foundation for automation workflows
Why it matters: Website becomes the front door of operations.
When clients submit data, the clock starts. Brokers need a system that reduces context switching and makes the next action obvious. Speed matters, but clarity matters more.
Bank requirements change. Case complexity varies. Data quality must be consistent. The CRM must stay flexible without losing structure, and it must support automation without sacrificing control.
I design product systems that connect customer inputs to operational processing.

Rebuilt IA and task-first journeys. Unified templates for scalable updates.
View case study

Designed a readable FIDS UX/UI system for distance viewing and speed.
View case study