View more
Zepoch Logo White
Contact
info@zepoch.ioLugano, Switzerland
Language
Status
online

accepting_projects · lugano_ch

© 2026 Zepoch Sagl

Services
Design·2-12 weeks

UX/UI, Portals & Operational Tools

Interfaces, portals and work tools designed around the real tasks of operators, customers, admins and internal teams.

Timeline2-12 weeks
Stack
PortalsReusable UI patternsPrototypesAdmin UX
01

About

Design for people who need to work

An operational interface is used while orders arrive, operators scan codes, admins correct data or customers look for precise information. The priority is to reduce errors, doubt and unnecessary steps.

Flow first, screen second

We map roles, tasks, states, permissions, data fields, recurring errors and moments where the user must decide. From there come portals, dashboards, admin panels and internal tools that hold up in real work.

Design close to implementation

Prototypes, states, components and specs stay connected to the frontend that will be built. Design should help development, not create a separate document that must be reinterpreted from scratch.

Validate with real use

After the first release we look at where users slow down, make mistakes or work around the system. The best fixes often come from a misplaced field, a missing confirmation or a table that does not show the right data.

02

Features

01

UX from the workflow

We start from tasks, roles, data, errors and edge cases before deciding screens, components or layout.

02

Portals and internal tools

Flows for operators, customers, suppliers, administration, catalogs, approvals and dashboards.

03

Components ready for development

Reusable UI patterns, states, interaction rules and specs intended to be implemented without unnecessary reinterpretation.

04

Usability after release

We iterate on real feedback, friction points and daily use, not only on screens that look good in a presentation.

03

Examples

Example 01

Operator Flow Audit

A focused redesign of one screen or internal workflow, starting from how users actually work with the system under pressure.

•Workflow and usability audit
•Wireframes and interaction states
•One redesigned operator screen or workflow
•Handoff ready for development
•Reusable UI patterns
•Structured user testing

Timeline: 1-3 weeks

Example 02

Interface System

A complete design path for dashboards, portals, admin tools, catalogs or shop-floor screens that need to be used by real people.

•User roles, tasks and constraints
•Wireframes, mockups and states
•Reusable interface components
•Interactive prototype of critical flows
•Usability review and iteration
•Development handoff tied to implementation

Timeline: 3-8 weeks

Example 03

Ongoing Interface Support

Ongoing UX and interface support for internal tools, dashboards, portals and CMS or catalog workflows after launch.

•Monthly interface/design hours
•Iteration on real user feedback
•Usability checks on critical flows
•Reusable UI pattern maintenance and handover

Timeline: Monthly

04

Proven by real work

What would you like to work better?

It might be an Excel file that has become unmanageable, a manual process, business software that does not talk to other systems, or a task that takes too much time.