Services/S/04/UI / UX design

Interfaces that ship without compromise.

Product UX, design systems and brand-aligned interfaces — designed with engineers in the room from the first sketch. We're not a design agency that throws Figma over a wall; we design the thing we're going to build, and then we build it.

Timeline3–12 weeks
Team size1–3
EngagementFixed or retainer
OutputDesign system
01 — Overview

Design is a decision, not a deliverable.

The best interface is the one you don't have to think about. We design for the person using the software at 3am, not the person who signed the contract. That means fewer screens, clearer defaults, and flows that survive contact with a real workload.

An engagement usually starts with an audit and a week of watching people work. We map the actual tasks, the dead ends, and the workarounds users have already invented. Then we prototype in the real stack — not a clickable mock that lies about latency — so what you sign off is what you get.

We leave you with a design system your engineers can extend without us: tokens, components, accessibility baked in, and documentation that reads like it was written by someone who'll have to maintain it. Because usually, we are.

02 — Process

Watch, draw, build, codify.

Four phases that move from the real world into a system. We don't start in Figma and we don't end there.

i.

Research

We watch real users do the real job. Task analysis, an honest heuristic audit, and a short written account of where the current product fights the people using it.

Task analysisUX auditFindings
ii.

Direction

Two or three distinct directions, not forty variations of the same one. We pick one with you, on evidence, and write down why so the decision survives the next opinion.

ConceptsArt directionRationale
iii.

Production

High-fidelity design built against the real component constraints. Prototyped in code where it matters, so interaction, motion and edge states are designed — not discovered in QA.

UI designPrototypesEdge states
iv.

System

The work becomes a system: tokens, components, usage rules, and accessibility notes. Handed over so your team can keep designing after we've gone.

Design systemTokensDocs
03 — Capabilities

What we actually do.

Operational software, mostly. The screens people live in, not the ones they screenshot.

/01

Product UX

Flows, information architecture and interaction design for software people use all day. We optimise for the hundredth use, not the first.

/02

Design systems

Token-driven component libraries that map one-to-one onto your front-end code. One source of truth, not a Figma file and a codebase that disagree.

/03

Brand-aligned interface design

Visual systems that carry a brand into a product without sacrificing clarity. Restraint as a feature.

/04

Prototyping

Coded prototypes for the flows that are too important to evaluate on a static frame. Real data, real latency, real decisions.

/05

Accessibility

WCAG 2.2 AA as a baseline, not a retrofit. Keyboard paths, contrast, focus order and screen-reader behaviour designed in.

/06

Design–engineering handover

The unglamorous part that decides whether design survives implementation. We do it because we're usually on both sides of it.

04 — Toolkit

Tools we keep returning to.

A small, sharp toolkit. The point is the thinking, not the software it's done in.

Design
Figma · FigJam
Variables · Tokens
Prototype
React · Storybook
Framer · Rive
System
Style Dictionary
Radix · Tailwind
Verify
Axe · VoiceOver
Maze · Polypane
05 — Selected work

Recent design work.

Most of it lives behind a login. These are the ones we can describe.

Hospitality · 2025

A PMS people stopped fighting

Redesigned the daily workflow of a property-management system around the night auditor. Task time down 40%, training time from two days to two hours.

Design system · 2024

One system, six products

A token-driven system shared across a B2B suite. New screens ship in days, not sprints, and finally look like they belong together.

Fintech · 2024

Reconciliation, made legible

Turned a wall of numbers into a dashboard an operator can read in one glance. Fewer escalations, faster breaks resolved.

Accessibility · 2023

AA, without the retrofit

Brought a guest-facing booking flow to WCAG 2.2 AA as part of a redesign — no contrast band-aids, no separate accessible version.

Start

Have an interface
worth getting right?

Tell us a little about what you're trying to build. We reply within two working days, in plain language, with an honest read on whether we're the right team.

AgencyPlateon 55, 104 35
Athens, Greece
Write to us