UI/UX Design

Interfaces people understand the first time they use them.

What's included

  • User flows and information architecture
  • Wireframes for every key screen
  • High-fidelity designs in Figma
  • Clickable prototype for testing
  • Component library and style guide
  • Developer handoff with specs and assets

What is ui/ux design?

UI/UX design plans how a product works and how it looks. UX (user experience) covers structure and flow, so people can finish their task. UI (user interface) covers the visual layer, such as layout, type, colour and buttons. The usual output is a tested Figma prototype that developers can build from.

Last updated

How we approach it

Good UI/UX starts before anything is drawn. We map who is using the product, what they came to do and where they currently get stuck, then turn that into wireframes and a clickable Figma prototype you can test with real people.

By the time development starts, every screen, state and edge case is already decided. That means fewer changes mid-build, and a handoff your developers can follow without guessing.

Typical timeline

1–3 weeks, depending on the number of screens

Best for

  • New products that need a clear structure before code
  • Existing apps with drop-offs or support complaints
  • Teams with developers but no in-house designer

Is it right for you?

When should you choose this?

  • Users get stuck or leave partway through a process
  • You are building an app and want to get it right before coding
  • Your product has grown messy and inconsistent
  • You need investor or stakeholder-ready prototypes

How much does it cost?

UI/UX design is quoted after the brief, because the price depends mostly on the number of screens and flows.

What affects the price

  • Number of screens and states
  • Research and user testing required
  • Whether a design system is included
  • Web, mobile or both

The process

How does the work happen?

  1. 1

    Understand users and goals

    We review your product, analytics and competitors and speak to your team.

  2. 2

    Map flows and wireframes

    Plain layouts settle the structure before visual design starts.

  3. 3

    Create the visual design

    We apply your brand across key screens in Figma.

  4. 4

    Prototype and test

    A clickable prototype lets people try it, so problems are found early.

  5. 5

    Hand over to developers

    You get organised files, components and specs.

Compare your options

UX or UI: what's the difference?

FeatureUX designUI design
Question it answersDoes this work for the user?Does this look clear and consistent?
Typical outputUser flows, wireframesScreens, components, styles
When it matters mostBefore visualsAfter structure is settled

Before you start

Which mistakes should you avoid?

Starting with visuals

Polishing a poor flow makes it look better, but it won't work better.

Designing only the ideal case

Empty, error and loading states are part of the product.

Testing only with your team

People who built it can't see it fresh. Even a few outside users can reveal major problems.

No shared components

Without them, every new screen drifts and development slows down.

FAQ

UI/UX Design: common questions

Usually yes. Developers build what is specified, and design is where those decisions get made. A prototype is much cheaper to change than finished code.

The complete Figma file, the prototype link, the component library and exported assets. You own all of it.

Yes. We can start with the flow causing the most trouble, such as sign-up or checkout, and work outward from there.

Usually 1–3 weeks, depending on the number of screens.

Yes. You receive the editable files along with the components and styles.

Yes. Having design and development in one team reduces handover mistakes.