UI/UX design

An interface that helps people understand and buy — handed over in a form you can build from immediately.

UI/UX design is a decision about how a person finds, understands and buys — and only after that about how it looks. We build structure, interface and a design system for websites, stores and internal systems, and hand it over in a form a developer can build from immediately.

Who it's for

Users get lost

Teams that have a product, but people cannot find what they are looking for in it.

Before a rebuild

Companies that want to know the structure before they pay for a build.

Design on its own

Clients who will do the build themselves or with another team.

What's included

  • User flows and information architecture
  • Wireframes for the main pages or screens
  • Interface design for mobile and desktop
  • Design system: components, typography, colours, states
  • An interactive prototype for the main flows, when it saves time in development
  • Handover to development with a component specification

Technology and approach

A prototype for us is a step, not a product. If the goal is to test an idea with real users, it is faster and cheaper to build a working MVP.

  • Figma
  • Design systems
  • WCAG 2.2 AA
  • Tailwind handover
  • Component specification

Frequently asked questions

Can we order design only?

Yes. The deliverable is fully yours, even if another team does the build.

Do you make logos and brand identity?

Not as a standalone service. We work with your existing brand book or help apply it in the digital environment.

Is a prototype required?

No. We only make one when it shortens the build or answers a question the team does not agree on.

What usually comes with this

One team, so the next step does not start from zero.

Visi vienpadsmit pakalpojumi

Three steps to a proposal

No long intro. Usually one conversation is enough to understand scope and timing.

  1. Tell us the goal

    Enquiries, sales, speed or automation. A short note is enough.

  2. A short consult

    Goal, audience and what you already have. Usually one conversation.

  3. Proposal

    Scope, timing and the next step — before we write code.