Internal platforms
Planning, service, coordination and decision support shaped around the way teams actually operate.
Explore internal platformsWork · Operational software
Real operational problems. Software built around the way work actually happens.
Most of the products I build live inside private organisations. They coordinate people, information and decisions — so these case studies focus on the problem, the product choices and the outcome.
Internal platforms
Workflow design
Software delivery
AI integration
What I usually build
Products where workflow fit matters more than feature volume.
The common thread is operational complexity: software used repeatedly by teams who need clarity, reliability and room for the business to evolve.
Operational interfaces
Dense, high-frequency workflows designed to stay understandable under real daily pressure.
Explore operational softwarePractical AI integration
Classification, retrieval and decision support added where they create concrete product value.
Case study hub
Three contexts. Three different operational problems.
Each case is available as a standalone page with context, problem framing, responsibility, delivery focus and outcome.
Case 01
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.
Read full case study
Case 02
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.
Read full case study
Case 03
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.
Read full case studyExplore the details
Compare the context, role and outcome.
Select a case to read its essential structure here, or open the full standalone page.
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
Product structure, interface quality and implementation have to align.
The value is not in treating these as separate services, but in making them support the same operational outcome.
Workflow design
Map real operational behaviour before changing screens or features.
Interface systems
Design repeated, information-dense work to remain legible.
Implementation
Build the product itself, not only specifications or visual direction.
AI integration
Extend existing platforms in useful, grounded and coherent ways.
Your context
Have a similar operational problem?
Tell me what your team is doing today, where the current tools fall short and what you need to improve.