Skip to content
Design · Product and UI/UX

UI/UX design services that validate the product before it is built

We design interfaces around real user journeys, then prototype and test them with real users before any production code is written, while changes are still cheap. Engineering receives one design system as its single source of truth.

A written scope and a fixed budget before any work is billed.

Design is where a product is cheapest to change

Moving a button in Figma takes minutes. Moving it after it has been built, tested and released takes a sprint. We do the interface work first for that reason: user journeys, a clickable prototype of the full flow, and sessions where real users try it while you watch what they do.

Because the same team designs and builds, the design is never a handoff into the unknown. The design system we deliver is the one engineering builds from, with components and rules that map to code, so what ships is what was tested.

We design web applications, SaaS products and mobile apps, and redesign existing products without forcing a rebuild. Brand work, from the logo to the guidelines, is brand identity design.

Why people get in touch

Sound familiar?

01

Users get stuck at the same step

Analytics show people dropping out of a signup or a checkout, and nobody can say why without watching them use it.

02

Engineering is building from screenshots

There is no design system, so every developer interprets the mockups differently and the product looks a little different on every screen.

03

The product was designed by whoever built it

It works, but new customers need a call before they can use it, and support spends its time explaining screens.

04

You want proof before you spend on development

Investors or the board want to see the product, and you want users to try it before you commit an engineering budget.

Four steps, each with something you keep

Interfaces are validated before they are built, in this order.

User journeys

We map who uses the product, for what, and where they get stuck today, from interviews and from the data you already have.

  • Interviews
  • User journey map

Clickable prototype

The full flow built in Figma and reviewed with you before engineering starts, clickable on a laptop and on a phone.

  • Figma
  • Prototype

User testing

Real users work through the prototype, and what they do changes the design before anything is built.

  • Usability testing
  • Findings

Design system

Components, states and rules, including accessibility, handed to engineering as one source of truth.

  • Components
  • Accessibility
Built to be owned

What you keep at the end

Everything below is yours from the first commit, under your own accounts wherever possible. Nothing in it is licensed from us, and nothing can only be maintained by us.

tree

your-company/

  • research/user-journey-map.pdfWho uses the product, for what, and where they get stuck.
  • figma/prototypeThe clickable prototype of the full flow, in your Figma account.
  • research/test-findings.mdWhat users did in testing, and what changed because of it.
  • figma/design-systemComponents, states and rules, ready for engineering.
How the work runs

Four stages, and what each one hands you

Every stage ends in something you can review and keep, including the stages that come before any code is written.

01
scope

Discovery and research

Stakeholder interviews, the data you already have and the users who will rely on the product: who they are and where they get stuck.

  • user journey map
  • scope and fixed budget
02
design

Prototype

The full flow designed in Figma and reviewed with you every week, clickable from the first review.

  • clickable prototype
  • weekly review
03
build

Test with users

Real users work through the prototype while we watch, and the design changes where they struggled.

  • test findings
  • revised prototype
04
operate

Design system and handover

Components, states and accessibility rules delivered as the single source engineering builds from, ours or yours.

  • design system
  • component library
Terms

Terms we put in writing before work begins

The figures we commit to on every engagement. Your project gets its own dated plan on top of them.

Inquiry
1 business dayA reply from someone who has read the brief.
Discovery
1 to 3 weeksEnds in a written scope and a fixed budget.
Weekly review
Every weekThe work as it stands, on a link you can open yourself.
Pricing

What UI/UX design costs

Design is priced like the rest of our work. Discovery produces a written scope listing the flows, the prototype and the testing rounds, and that scope has one price.

  1. 01How many user roles and flows the product has
  2. 02A new product, or the redesign of one that already has users
  3. 03How many rounds of user testing, and with whom
  4. 04Web, mobile or both
  5. 05Whether a design system already exists
Stack

What we build it with

Tools with long support horizons and large talent pools, so the system stays maintainable by any capable team, not only ours.

Figma

Prototype, design system and comments in one file you own and your engineers can read.

React

Components designed to map one to one onto the components engineering builds.

Tailwind CSS

Design tokens that carry from the design system straight into code.

Questions buyers ask us

The ones that come up most in first conversations about this service.

Something not covered here?
Email us at hello@kodfabrika.com.

Ask a question

Built to last.
Started this week.

Tell us what you’re building. You’ll receive a written scope, a defined budget, and a delivery plan. Not a proposal deck.