I’ve worked across mobile products, workflow-heavy SaaS, Web3, fintech, technical websites and design systems. The case studies focus on what I owned, what made the problem difficult and how the product logic changed.
No invented conversion lifts. No fictional research rounds. If a result is not public, I describe the design outcome I can actually defend.
Flagship evidence
Complex SaaS architecture, financial-product state design, and design-to-engineering systems. The point is not project count. It is showing how I reason when the product has real structure, risk, and implementation constraints.
A shared product grammar across CRM, Sales, Inventory, Finance, and workspace modules without flattening different business tasks into one admin template.
Inspect navigation scopes, information density, reusable patterns, and legitimate variation.
Read Orkest case studyInvestor, creditor, application, verification, and admin journeys organized around status, requirements, next actions, and recovery.
Inspect role divergence, verification states, task-based density, and recovery paths.
Read piHub case studyA public workflow connecting design tokens, content, media, motion, accessibility, performance, implementation, and release tasks.
Public proof includes token transformation, audit tasks, asset pipelines, release automation, and handoff-oriented documentation.
Inspect public repositoryEvidence boundary: public artifacts vary by project. Where client metrics, research data, or private files are unavailable, the portfolio stays explicit about that instead of manufacturing impact.
The flagship set shows high-stakes interaction, multi-role workflows, SaaS architecture and mature product collaboration. The supporting pair adds technical storytelling and data-product range.
The strongest view of how I structure complex product behavior and carry decisions into interface systems.
A mobile chat product where wallet actions, Solana blinks and transaction states had to feel connected to conversation without making approval feel casual.
Read case study
Investment, credit, application and verification experiences organized around the information financial users need most: current status, missing requirements and the next useful action.
Read case study
A shared product grammar for CRM, Sales, Inventory and Finance, designed so the modules feel related without pretending their operational jobs are identical.
Read case study
Product-design work inside an established LMS, covering course authoring, quizzes, learner states and reusable patterns that had to fit an existing system and a larger design team.
Read case studyTwo shorter cases showing technical communication and a data-heavy side project.
A technical protocol website structured so first-time visitors can understand the product while developers can reach mechanism, evidence and deeper context without wading through marketing filler.
Read case study
A live parser that turns noisy combat events into readable performance information while keeping uncertainty and incomplete data visible instead of pretending every number is equally trustworthy.
Read case study
Customer, driver and operations experiences built around one delivery lifecycle, with role-specific priorities and explicit handling for delays, reassignment and failure.
Read case study
Marketplace design work balancing luxury photography with stable rental information, comparison patterns and practical decision support.
Read case study
A software-studio rebrand and multi-page website designed and built as one system, from positioning and service architecture to responsive implementation and search structure.
Read case study
A consulting website organized around the way prospective clients describe their problems, with service and sector paths that lead toward a more relevant inquiry.
Read case study
A website for a content, device and data-management platform, translating technical capability into a clearer buyer-facing story and responsive front-end.
Read case study
Commercial website design focused on plan comparison, buyer questions and making technical hosting choices easier to scan.
Read case study
A CMS-aware furniture storefront balancing image-led browsing with reusable catalogue patterns that can survive real content and non-designer editing.
Read case study
A small Sass starter focused on predictable structure, low setup cost and conventions that are easy for another developer to understand or remove.
Read case studyThat can mean states and permissions in SaaS, trust and signing in Web3, dense financial workflows, technical product storytelling or simply a handoff that needs fewer unanswered questions.
Discuss a role or product