An interface audit before you pay for a redesign

An audit finds out whether a redesign is necessary before you pay for one. We trace the real user flow, rank the problems by impact and effort, and design only the changes that need visual work.

Tablet with an annotated interface, a stylus and a ranked findings panel

You are in the right place if

Low conversion

Traffic comes but does not convert, and nobody can say why

What we do

We walk the full task as a user does and show where people stop, with the reason next to each point.

Inconsistent product

The product grew and the interface stopped being consistent

What we do

We collect the repeated patterns into components and tokens, so new screens match the old ones.

Before a redesign

You are about to pay for a redesign and want a second opinion

What we do

The audit shows which problems need new design and which can be fixed in the current one.

Thinking about a redesign? Get the audit first.

Start a project

What is included

  • Interface audit

    A ranked list of problems with the reason and expected effect of each fix.

  • Screens and flows

    We design the whole task, including empty, error and return states.

  • Design system

    Tokens, components and documentation your developers can build from.

  • Brand basics

    Logo use, typography and colour rules that hold across every page.

  • Developer handover

    States, spacing and notes, so nobody has to guess during the build.

Component states panel with a token card and a spacing ruler

How the work runs

  1. Step 01

    Review

    We follow the complete task the way a user does, across phone and desktop, including empty, error and return states.

  2. Step 02

    Rank

    Each finding gets a reason, expected effect, effort and dependency so your team can decide what is worth changing.

  3. Step 03

    Design

    We design the fixes that need visual work and reuse the components you already have wherever they still serve the task.

  4. Step 04

    Hand over

    You receive the prioritised audit, design files, states, tokens and implementation notes needed to build without guessing.

Send us a link to your product. We will tell you what an audit would cover and how long it takes.

Start a project

What you get at the end

Audit document with priorities

Each finding has a reason, expected effect, effort and dependency.

Design files with components and states

Organised so any team can pick them up without a walkthrough.

Tokens exported for the code base

Colour, type and spacing in a format your developers already use.

Do we have to order a redesign after the audit?

No. The audit is a finished piece of work with a list you can hand to any team.

How long does an audit take?

It depends on the size of the product. We tell you the range before we start and hold it.

Planning something like this?

Two or three sentences are enough. We will reply with the questions needed to define a useful next step.