Understand the job and the constraint.
Users, evidence, business goal, technical limits and the current behavior that is creating friction.
SaaS product UX
Complex SaaS should make the next decision easier, not expose the database.
I design workflow-heavy software around what each role needs to understand and do next. That usually means working through navigation, information density, permissions, forms, states and the exceptions that create real operational friction.
When this is useful
Useful when a dashboard has accumulated features, different roles need different views or important states are buried inside tables and forms.
Typical scope
- Dashboard and workspace architecture
- Role and permission-aware journeys
- Tables, filters, records and bulk actions
- Forms, review states and recovery paths
- Reusable patterns and design-system rules
Make the product decision explicit before making the screen look finished.
Resolve flow, hierarchy and states.
Turn the problem into reviewable decisions before high-fidelity design makes ambiguity expensive.
Design for the implementation.
Responsive rules, components, interaction notes and QA make the work useful after handoff.
See the decisions in real project context.
Orkest HQ
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
piHub
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
Masteriyo
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 study