Systems shaped around how teams actually operate.
Planning, service, coordination, decision support — the dense workflows that generic software rarely fits well.
Work
Private systems, real constraints, serious product work.
Most of the products I’ve built in recent years live inside private organizations. They support working teams, solve operational problems, and don’t lend themselves to a public showcase.
What I describe here are the systems, constraints, decisions, and delivery patterns behind that work.
Confidential case studies
Operational systems
AI-aware platforms
What I usually build
Software built around operations, coordination, and decisions that actually matter.
My recent work has focused mostly on custom business software: operational suites, workflow-driven applications, order and service systems, sales support tools — products where clarity, reliability, and adaptability matter more than novelty.
Interfaces designed for repeated, high-frequency use.
Not showcase pages, but products that need to stay legible, stable, and useful under real daily pressure.
New capabilities added where they improve the product.
I’m interested in using AI for concrete product gains such as assisted classification, guided retrieval, and faster access to structured information inside real workflows.
Confidential case studies
Confidential Case Study 01
Operational Planning And Service Management Suite
A custom internal suite unifying planning, call handling, service interventions, notifications, and shared operational data for a 20-person company.
Context
A growing company needed a central environment where multiple departments could coordinate planning, support activity, and service work without relying on fragmented tools or disconnected processes.
Problem
Planning, phone activity, and assistance workflows were distributed across separate habits and tools. The result was low visibility, weak auditability, and friction between departments that needed to act on the same information.
My role
- Product designer
- Main developer
- UX/UI designer
- DevOps owner
What I focused on
- Shared planning across departments
- Real-time frontend updates
- Integrated notifications and reminders
- Cross-application data coordination
- Continuous business-specific iteration
Outcome
The suite became a shared operational layer for the company: tailored to the way the business actually worked, flexible enough to evolve continuously, and stable enough to support daily coordination across teams.
Confidential Case Study 02
Tablet-Based Order Entry System For A Distributed Sales Network
A field-oriented order entry product combining structured order capture, real-time product and pricing data, and integrated sales support for a nationwide sales force.
Context
A commercial organization with agents operating across the country needed a tool that could support real sales activity in the field while keeping data aligned with headquarters.
Problem
The challenge was not just collecting orders. The system had to support the sales conversation, work well on tablets, present rich product information, and maintain a structured, always-updated flow of data between agents and central operations.
My role
- Product designer
- Main developer
- UX/UI designer
What I focused on
- Tablet-first interaction model
- Realtime product and pricing updates
- Structured order flow
- Integrated catalog with media-rich content
- Alignment between field operations and headquarters
Outcome
The final product made ordering more reliable and structured while also functioning as a practical sales-support environment, helping agents work with current information instead of disconnected materials.
Working Pattern 03
Modernizing Operational Software Without Breaking Daily Work
A recurring pattern in my work: improving mature internal systems while preserving the business logic and operational trust teams already depend on.
Context
Many of the systems I work on are not greenfield products. They are existing operational tools that grew around real work, often becoming harder to use and harder to evolve over time.
Problem
The challenge is not simply redesigning the interface. It is reducing workflow debt, clarifying dense interactions, and making change possible without disrupting the teams who rely on the system every day.
My role
- Product and UX lead
- Main implementation owner
- Progressive modernization partner
What I focused on
- Workflow mapping before UI redesign
- Reduction of friction in high-frequency tasks
- Progressive modernization rather than destructive rewrites
- Closer alignment between system structure and business logic
Outcome
This kind of work usually leads to the same result: clearer interfaces, faster execution inside complex flows, and software that becomes easier to maintain and extend without losing the trust of the people using it.
Skills in context
I work where product structure, interface systems, and implementation quality need to align.
Workflow design
Mapping real operational behavior before changing screens or features.
Interface systems
Designing dense, high-frequency interfaces that remain legible under real usage.
Implementation
Building the product itself, not stopping at specifications or visual direction.
AI integration
Extending traditional platforms with AI in ways that stay useful, grounded, and operationally coherent.