UX Audit & Product Discovery

A product UX audit is a structured diagnostic of a live product: real people complete real missions on live accounts, every friction point is recorded and evidenced, and each finding becomes a prioritized task with severity, rationale, and an evidence link. The deliverable is a backlog your team works from, with the report as supporting material.

An Express Audit starts from €3,500 – one week of work covering a critical UX/UI heuristic review, a technical health and speed check, and a list of Quick Wins. Product Discovery & Vision starts from €5,500 and adds competitor analysis, 1–2 visual concepts and a strategic roadmap. Enterprise Transformation is scoped individually, because price follows the number of flows, platforms and competitors in scope rather than a fixed rate card. We confirm the figure before any work starts, so you never commit to an unscoped budget.

A UX audit can include real-user testing, heuristic evaluation, journey analysis, competitor benchmarking, technical health checks, evidence-backed findings, prioritization, visual concepts, and an implementation-ready backlog. The exact scope depends on the product, the business problem, and the audit tier – Express covers the first two and quick wins; Discovery and Enterprise add the rest.

Yes. An audit can focus on a single high-value journey – registration, checkout, onboarding, withdrawal – when that is where the business problem sits. It follows the same method: real users, recorded sessions, evidence-linked findings, and a prioritized backlog, at a smaller scope and cost.

Between one and four-plus weeks depending on tier. Express covers critical flows and quick wins in about a week. Discovery adds recorded user sessions, competitor benchmarking, visual concepts, and a strategic roadmap in about three weeks. Enterprise extends to cross-platform coverage, accessibility, and design ops over four or more weeks.

Yes – competitor analysis is part of the Product Discovery & Vision and Enterprise tiers, and it is hands-on rather than desk research. On a recent audit for a licensed Italian sportsbook and casino we created and funded live accounts on all three platforms in scope and walked the same six flows end to end, so every comparison came from what the products actually do, not from screenshots or marketing pages. That is how you find issues that only appear as a sequence – on that audit, four separate failures stacked on a single login credential with no recovery path at any point.

A recent example: a competitive UX audit of a licensed Italian sportsbook and casino against two rival operators, run over three weeks on live accounts we created and funded on all three platforms. It covered six flows – registration, deposit, promotions, KYC, withdrawal and transactional email – and produced 75 filed findings: 8 critical, 21 serious, 41 medium, 5 cosmetic. Every flow was scored against Nielsen heuristics plus iGaming-specific criteria, and each finding shipped with annotated screens, screen recordings and columns that map one-to-one onto Jira import fields.

If you are at idea or pre-MVP stage, Pitch Deck & Product Concept or MVP Design & Development fits better. Product Audit & Discovery works when you have live traffic, real users, and an existing codebase – even a messy one. We work from real behaviour and real constraints, not assumptions.

We can still run the audit, but the insights will be shallower on the quantitative side. We will rely more on heuristic evaluation, session recordings if available, and stakeholder interviews. We also recommend setting up basic analytics as part of our Quick Wins deliverable so future decisions are data-driven.

This audit works best for SaaS dashboards, sports analytics platforms, fintech products, iGaming and betting interfaces, and any digital product with real users, live traffic and measurable conversion or retention problems.

You receive a prioritised roadmap broken down into Critical vs Strategic items, a UX/UI and tech health report, and 1-2 visual concepts that show how key screens should evolve. All actions are exported into a Jira or Linear-ready backlog so your team can start implementation on Monday without rewriting our findings.

Yes – most clients continue after the audit. Two paths: a full Product Rebuild & Redesign, or a Dedicated Product Team shipping improvements sprint by sprint. Either way, the audit roadmap becomes the backbone for design, development, and QA.

Most audits stop at a static PDF. Ours is designed to be executed. We connect findings to business impact, rank every item by effort vs ROI, provide visual examples and translate everything into a developer-ready backlog. Your team does not need to decode our audit – they can ship from it directly.

Usability testing is one input into the audit. We add heuristic scoring per flow, competitor benchmarking on the same journeys, technical health checks, and cross-flow analysis that catches failures spanning several screens. The findings are then prioritized by impact and converted into implementation-ready tasks, which standalone usability testing rarely produces.

As many personas as the analysis needs to separate a one-off stumble from a pattern – defined per audit around the journeys in scope. In the operator audit, three testers walked every flow on all three platforms, with a fourth added where a re-verification pass was needed. Persona count is part of scoping.

Yes. Every flow in the operator audit was recorded on desktop and on mobile, and the Figma reconstruction shows both side by side. Native iOS and Android apps are covered in the Enterprise tier as a cross-platform audit, alongside web.

Yes. The backlog is written so an internal team executes it directly, with evidence linked from every task and related low-impact items grouped into batches. Most clients continue with us afterwards, through a rebuild or a dedicated team shipping the roadmap sprint by sprint, but the deliverable stands on its own.

No. We audit the interface on staging or production plus your analytics, such as Google Analytics or Mixpanel. Code, backend, and user databases stay untouched. This is a standing rule rather than a case-by-case decision, and it removes the main security concern regulated operators raise before an audit.