Know exactly where your product stands.

A focused week that maps your product's structure, flows and consistency, prioritised, with a roadmap. What holds up, what deserves attention, and what to leave alone.

01

Sound familiar?

"Every feature made sense on its own. Together they feel heavier than they should."
"The numbers show where users stop. They don't tell us why."
"We're planning a redesign and want to know what is worth keeping."
"The same design debate keeps coming back. We need an outside view."
02

What we look at.

One lens, two depths. The Snapshot applies it to a single screen or flow. The full audit applies it across the whole product.
Consistency & UI patterns (edge, empty, error states)
Both audits
Architecture & navigation (what is grouped, buried, overlapping; how users move)
Both audits
Critical user flows (3 to 5 paths, walked step by step)
Both audits
System map (surfaces, roles, permissions)
Full audit only
Design system health (tokens, duplication, documentation, adoption + AI-readiness)
Full audit only
Accessibility & compliance (WCAG 2.2 + procurement answers)
Full audit only
Method
Where you have analytics, session recordings or support tickets, we use them. Findings are cross-checked against real behaviour, and every finding cites the principle it rests on, with a severity rating. Strengths documented too. A document, not a slide deck.
03

Scored against a standard.

The full audit runs against our Enterprise Readiness Standard: six dimensions, around 190 measurable criteria, each scored 0 to 4. Your overall score is your lowest dimension. Enterprise deals fail on the weakest link, not on the average.
UX & interaction patterns

Density, tables, navigation, states, latency.

Accessibility & regulation

WCAG 2.2, EN 301 549, EAA readiness.

Design system

Tokens, component contract, governance, adoption.

Product & platform

SSO, SCIM, roles, audit log, tenancy.

Process & measurement

Discovery, benchmarks, definition of done.

AI-ready

A system agents can read, call and be constrained by.

The same standard our own work has to pass.
Automated checks catch about 57 percent of accessibility issues. The rest is manual review. We do both. Every threshold is verifiable. Target sizes in CSS pixels, completion rates against published benchmarks, adoption in percent.
04

What you get.

Findings document (P0/P1/P2)
New IA and navigation proposal
Critical flows reviewed
Accessibility and contrast check
Implementation roadmap (2 weeks / 1 month / 1 quarter)
60-min walkthrough call
Output is AI-readable. Clean markdown, structured findings. Your team and their AI tools act on it directly.
findings.md
Finding 07 of 23
## Two menus compete for one task.
 
**Severity:** P1 · Navigation
**Principle:** Consistency and standards.
**Fix scope:** Days, not weeks.
 
Users reach the same screen three ways.
Each way shows different context.

Plain text. Opens in any editor, pastes into any AI tool, versions in git.

05

How it works.

01
Confirm scope

Roles, surfaces, flows; fixed scope, fixed price; 15 min

02
Kickoff

Day 1

03
Diagnosis

Days 2–4

04
Walkthrough

Day 5

Audit pricing starts at €2,500.

Questions, answered.

Different from a regular UX audit?

Structure is the cause, not just heuristics.

Who needs to be involved?

Roles, surfaces and flows are confirmed on a 15 min call before we start.

What if we disagree with findings?

Every finding is evidence-based. Discussion is welcome.

Does this work pre-launch?

Yes. Where analytics do not exist yet, every finding still cites the principle it rests on.

Can we continue with you?

The typical next step is Design. Continue into design within 60 days and the audit is included in the design price.

Start with a clear picture.