Skip to content

UX Consulting and Audit that names causes, not complaints.

User experience (UX) consulting is a diagnosis you buy for a live product: a structured review against Nielsen's ten usability heuristics, WCAG 2.1/2.2 and your own funnel, ending in a UX audit report ranked by impact against effort.

  • 120+Projects delivered across 12 countries since 2012
  • 100+Senior in-house engineers, six countries
  • 5.0Unified rating across 61 client reviews on Clutch
  • ISO 9001Certified quality management, audited by Quay Audit UK
  • ISO 27001Certified security practice, audited by Quay Audit UK

01Overview

When you need a UX audit

You need one when a number is falling and nobody inside can say why. Analytics show you where people leave and not what made them leave, and closing that gap is the whole job of an audit. What lands is a ranked list of causes rather than a set of opinions, and every one of them names something you can change.

  • Somebody has to be named to act on itAn audit is worth buying when a person has already been named to act on the findings. We settle who that is while the review is still running, so the report lands on a desk that was waiting for it.
  • Testers who are not your teamThe people we put in front of your product do not work for you and have never seen it before, because nobody who built a product still sees it the way a first-time visitor does.
  • Accessibility inside the reviewAccessibility is checked against WCAG 2.1/2.2 inside the audit, not quoted as a separate job afterwards.
  • When it is one of the other threeUI/UX design when you already know what to change, a design sprint when the product does not exist yet, and a design system when the drift is across screens.

02Proof

What changed after the findings shipped

A UX report is worth exactly what somebody implements from it.

  • The Learning Hub had the traffic and a 1.2% conversion rateThe audit named three causes: interactive elements that disoriented visitors, including a chat pop-up that fired within three seconds of landing before anyone had read the page; discounts sitting on ordinary pages with no landing page of their own, ignored even by visitors arriving from paid ads; and functionality missing where it decides a purchase, from payment options to contact details. The chat and the discount pages were rebuilt first. Over the following year, as the team kept optimizing other parts of the site, the customer base grew by 40%.
    25%higher conversion in the first month after the first fixes shipped
  • A recommendation next to every issueThe audit of a school-meal catering app opened from user feedback about confusing navigation, slow load times, tasks people could not finish and billing nobody could manage. Neutral users matching the app's target demographic ran the tasks, and interviews collected what they had expected instead. It shipped as usability reports listing every issue next to the recommendation for it, plus a stakeholder deck, covering onboarding, registration and account management, meal ordering, order history, notifications and navigation.
    3methods behind one analysis: independent user testing, user interviews and the Nielsen heuristics method
  • An auditor is somebody you let inAn audit runs inside your live product and the data behind it: analytics, session recordings, test accounts for every role a user can have. The certifications are what turns handing that over into an ordinary decision rather than a security review of its own.
    ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK

03Compare

Who should run your UX audit?

Pick on who will implement the findings, not on who runs the deepest research, because an audit nobody acts on is a document you paid for. Two options sit outside the table. Waiting is right when nothing is live, because there is no behavior to audit yet and a design sprint validates the idea for less. A CRO or analytics agency is right when you already know which step leaks and want the numbers tuned, because it owns your funnel dashboards and it does not own your interface or your codebase.

An engineering-led auditunicrew Your own teamIn-house A UX research boutiqueResearch
Best forA live product with real users, where the diagnosis and the build sit inside one engagement. Best forA product your team knows well, with a professional UX designer on staff and calendar space to review it. Best forDeep generative research: moderated lab studies, eye tracking, brand and content strategy.
Trade-offYou are buying a diagnosis and a ranked plan, not a body of research. Generative study run over months is a different firm's product. Trade-offYour team is the most biased audience your product has, and reviewing it always loses to shipping the next feature. Trade-offThe output is a report. The hand-off to engineering costs weeks and loses the reasoning behind each finding.
You end up owningA ranked findings list your developers can build from, and a team that can build it. You end up owningA review by the people closest to the product, and its blind spots. You end up owningA report, and a build project that has not started.

Quick self-check

Tick what is true for you. The read-out updates as you go.

0 of 4 true

You already have the diagnosis

Nothing here says you need one. If you can name the screen, the number and the cause, buy the fix rather than the finding: go straight to UI/UX design, or to a design sprint if the product is not live yet.

Tell us anyway

Borderline, worth a short call

One signal usually points at one flow. Reviewing that flow against the ten heuristics is a fraction of a full audit, and it is often enough to settle the argument you are actually having.

Talk it through

Now it is worth the calendar time

Two signals put the cause in the gap between what your analytics can see and what your own team can. Closing that gap is what heuristic evaluation and independent user testing are for.

Book a discovery call

Scope is the only open question

Three signals, and the disagreement is no longer settleable from inside the company. What is left to decide is how wide to look: how many flows, and whether recruited testers are in it.

Book a discovery call

Book it, and decide now who acts on it

All four describe a product whose owners can see the loss and cannot locate it, which is exactly what this engagement is built for. Bring the person who will own the fixes to the scoping call rather than to the read-out.

Scope it with us

Our team recommended a series of enhancements that would improve the user experience and increase conversion rates. Specifically, by implementing the UX audit recommendations, we optimized the chat content and timing to ensure it appeared at the right moments during the customer journey. We also developed customized chat responses to give visitors the necessary support for purchasing decisions.

Olena ZhukUI/UX Designer, unicrew

04Capabilities

What goes into a UX audit?

A UX audit is not one activity. These are the eight reviews it can be built from, run alone or in combination, and which of them you buy depends on what your product is losing users to, which is settled in scoping rather than assumed.

  • Usability audit

    An expert walks your interface against Nielsen's ten usability heuristics, the structured baseline auditors use to find interface problems across ten dimensions, and logs every break: navigation, consistency, error prevention. That is the heuristic evaluation, the fastest route to a list of quick wins and the method behind the catering-app audit.

  • Conversion audit

    We read behavior against the funnel to find where it leaks, which is the interface half of conversion rate optimization (CRO), then map the end-to-end journey, which is the step where a drop-off number turns into a reason. Our published checklist covers the six areas that leak most often: load time, mobile responsiveness, calls to action, user flow, chat and forms.

  • Accessibility audit

    We audit against WCAG 2.1 and 2.2 at level AA, checking screen-reader behavior, color contrast and keyboard navigation, so the product is inclusive and legally sound. Full accessibility compliance was the governing requirement on four corporate sites we built for a financial-services group.

  • Usability testing

    Recruited participants who match your target demographic, meeting your product for the first time with somebody watching. It is a scope decision rather than a default, and one of the things that decides what an audit costs: with it you get evidence about strangers, and without it you get an expert's read and your own analytics.

  • Information architecture audit

    For complex platforms we test how the content is organized: card sorting, where users group your material the way they think about it, and tree testing, where they try to find things in your menu with no design attached. The output is a structure built around how people look, so the paths to what matters are short.

  • UX competitive analysis

    How your experience compares with the products your users already know, and which of those gaps is worth closing. Useful before a redesign, so the brief is grounded rather than aspirational.

  • Mobile and form UX audit

    Slow pages and broken mobile layouts are UX failures as much as technical ones, and forms are where lead generation quietly dies. On one audit, cutting load time from seven seconds to two reduced bounce rate by 30%; on another, reworking form design lifted submission rates by 40%.

  • Design system audit

    When one product spans many screens or many apps, inconsistency reads to users as unreliability. We check whether your components behave the same everywhere, as we did across more than 15 warehouse apps built against one style guide.

05Stack

What every finding is tied to

Every issue we log is tied to one of three things: one of Nielsen's ten usability heuristics, a WCAG 2.1/2.2 accessibility criterion, or a step in your own funnel. A tool can show you a heatmap; it cannot tell you which usability principle a finding breaks. That is what makes a recommendation arguable rather than a matter of taste, and it is what a developer wants before agreeing to build anything.

06Engagement

Three shapes, and who implements the findings in each

What changes across the three is who takes the roadmap when it lands, which is worth settling while the review is running rather than when the report arrives. The audit itself is the same work in all of them, and all three open on the same two stages: the stakeholder session and the analytics review. Whichever shape you pick, the project managers and engineers you work with are in Ukraine, Poland, Estonia and the UK, four of the six countries unicrew's engineering team spans.

  • A fixed-scope audit

    Start here

    You get the diagnosis and the roadmap, and your own team builds the fixes. There is no minimum engagement period, so stopping here is a real option rather than a courtesy, and it is the smallest way to find out whether the problem is the interface at all or something further upstream.

    Best when
    You have engineers and want an outside read on where users are getting stuck
    You pay
    Outcome based, quoted per project
    Typical start
    Two to four weeks
  • We run the audit, then take the prioritized roadmap through design and build. The people who found the problem are in the room when it gets fixed, so nothing is lost in a hand-off document.

    Best when
    The findings need to ship this quarter and your team is already at capacity
    You pay
    Billed hourly, quoted per project
    Typical start
    Two to four weeks
  • An embedded designer on your team

    Long-run

    A designer joins your product team and stays, so usability review becomes continuous instead of an annual event.

    Best when
    The roadmap keeps going and you want the UX judgment permanently inside the team
    You pay
    Billed monthly, per team member
    Typical start
    Two to four weeks
You already ran an audit

A findings triage first, and the redesign is a separate decision

Before a takeover we put two questions to the report you already have: was any finding tied to something a developer could pick up unchanged, and did anyone have capacity in the quarter after it landed. Either way the work starts by re-reading it against your live product and your funnel, and saying which findings still hold. You get that as a written triage.

07Industries

Where we audit, and the work behind it

We audit in the sectors where we also build. That is the difference between reading your domain rules for the first time on your budget and arriving already knowing why a dispatcher never scrolls.

Deepest expertise

Logistics and transportation

Dispatch, order and fleet interfaces used all shift by people who cannot stop to interpret a screen. Here a confusing layout costs the shift rather than the session, and error recovery is the feature.

Deepest expertise

Hospitality and leisure

Booking, membership and venue platforms, including a rebuilt entertainment platform whose original nightlife product no longer met modern usability standards.

EdTech and learning

Search and discovery work on a German teaching-materials platform, and UX improvements shipped alongside the payment work on an online test-prep platform.

E-commerce and retail

Catalogue, search and checkout, where a storefront that converts in one market quietly stops converting in the next. One European manufacturer's re-platform had to hold across seven of them at once.

Warehouse management

Operator-facing apps where inconsistency between screens reads as unreliability. We rebuilt the front end of a Business App Store carrying more than 15 apps, all against one style guide, with Storybook components reused across every one.

Financial services

Four corporate sites for a financial-services group had to hold the same accessibility bar across all four.

Name the number that is disappointing you

Thirty minutes on the product, the number and what you have already tried. You get a straight answer on whether an audit is the right buy, including the answer that it is not. If your product has not launched yet, we will point you at a design sprint instead.

Let's talk

What happens after you contact us

  1. We reply within one business dayNot an autoresponder: the reply says whether what you have described is an audit at all.
  2. A call about the product and the numberWhat the product is, which metric is disappointing you, and whether reviewing one flow would settle it.
  3. A written audit scopeWhich reviews are in it, what access they need, and what lands at the end.
  4. You decide, with no pressureIncluding the answer that you should not buy the audit yet. Most engagements start within two to four weeks.

08Delivery

How does UX Consulting and Audit work?

Six stages. Five of them need something from you, so what actually sets the schedule is how fast permissions and people arrive. All of it runs on read-only, least-privilege access agreed with your technical contact under NDA.

  1. Stakeholder Discovery and AlignmentWe interview the people who own the product, the funnel and the roadmap, so the audit is judged against your goals and constraints rather than against taste. What we ask you for: an hour each with those three, and a name for whoever will own the findings once they land.You getA written statement of the goals, constraints and success metrics the audit is judged against, with the named owner for the findings on it.
  2. Analytics and Funnel ReviewBefore anyone looks at a screen we look at behavior: where sessions end, which steps shed the most users, how mobile differs. What we ask you for: read access to analytics and any session-recording tooling you run.You getA ranked list of the leakiest steps in your funnel, with the traffic volume behind each one.
  3. Comprehensive UX Heuristic AuditThe deep dive. We evaluate the product against Nielsen's ten usability heuristics and against WCAG 2.1/2.2, looking for broken patterns, confusing navigation, and screens that ask a user to hold too much in their head at once. What we ask you for: the live product, plus test accounts for each user role.You getAn issue list where every finding is tied to the heuristic or accessibility criterion it breaks.
  4. Independent User Testing and InterviewsNeutral users who match your target demographic complete real tasks while we watch, and interviews gather what they expected instead. This is what surfaces problems your team has stopped seeing. What we ask you for: your target user, and the tasks that matter commercially.You getUsability reports with findings from each session and one recommendation per issue.
  5. Behavioral and Journey MappingWe turn findings into visual flows, so each drop-off sits next to the behavior causing it. What we ask you for: nothing new, this stage runs on what the earlier ones produced.You getJourney maps that put each drop-off point next to the behavior causing it.
  6. Strategic Roadmap and Executive ReportThe delivery is a prioritized action plan, not a list of complaints: fixes ranked by impact against effort, in an order your developers can work through. What we ask you for: one session with the people who decide what gets built.You getThe UX Audit Report plus a stakeholder deck: findings, prioritized recommendations, and an implementation roadmap with milestones.

09Client voices

Our clients, in their own words

See our client reviews
5.0 unified ratingacross 61 verified client reviewsRead them on Clutch

10Case studies

Where the outcome is on record

Two audits, and what each put on record: a catering app where the findings came from recruited users running real tasks, and a training platform whose conversion rose 25% in the first month after the first fixes shipped. One of the reviews above says Artelogic, the name unicrew traded under until the rebrand and the name that client hired, so it stays as they wrote it.

See all case studies

11Questions

More about UX consulting and audit with unicrew

The words in this market overlap, and the differences change what you pay for. A heuristic review of one flow and a full audit with recruited participants are both honest answers to "a UX audit", and they are not the same purchase.

A ranked set of changes you can act on, and the people who found them. The team spans UI/UX designers, business analysts holding certifications including CBAP, AAC and PMP, marketers, and front-end engineers, so the findings are holistic rather than surface-level, and because we also build software we can implement the changes rather than only hand you a document.

A heuristic evaluation is one method inside a UX audit. One reviewer, working alone, judges your interface against Nielsen's ten usability principles and records every break, which is fast and often enough to settle the argument a team is actually having. A UX audit is the whole engagement: that heuristic evaluation plus the analytics and funnel review, independent user testing with recruited participants, accessibility checks against WCAG 2.1/2.2, and competitive benchmarking, analysed together. You can buy the heuristic evaluation on its own, and on a single flow it is usually the right size. The difference shows up in what a finding is worth to you: an expert review tells you what breaks a usability principle, and the wider audit tells you which of those breaks is costing you money.

A consultant tells you what to change and why; a designer draws it. On a live product the consultant's output is a ranked findings report, each item tied to the heuristic, accessibility criterion or funnel step behind it, and specific enough for your team to start on it the week it lands. The designer's output is the interface itself: wireframes, screens, states and the specification engineering builds from, which is UI/UX design services and a separate purchase here. Most products need both, and the order matters more than the labels: a redesign commissioned before anyone has located the problem is an expensive way to move it somewhere else. If you already know what is wrong and only need the screens drawn, skip the audit and start there.

Research produces knowledge; consulting produces decisions. A research engagement asks what your users need and how they behave, and hands back findings you can build a strategy on. UX consulting starts from a product that already exists and a number that is disappointing you, and hands back a ranked list of changes with the order to make them in. We use research methods inside the audit, independent user testing with recruited participants and user interviews among them, but they are there to settle a decision rather than to build a body of knowledge. If what you want is a standing research practice, or generative studies before anything is built, a research firm is the right call and we will say so on the first call.

There is no list price here and there is not going to be one, because what an audit costs is decided by how much product there is to look at. A SaaS platform with several user roles is more product than a marketing website with one conversion path, and they are not the same audit. Four things drive the number: how many flows and screens are in scope, whether independent user testing with recruited participants is included or the review stays heuristic and analytics-based, whether accessibility and competitive benchmarking are in it, and whether you want us to implement the findings afterwards. We settle those with you and quote against them.

A focused heuristic audit of a single product can take three to four hours. A full audit covering analytics, usability testing, accessibility and competitive analysis typically requires two to four weeks, depending on the product's complexity and scope; our published UX audit checklist walks through what fills those weeks. Implementation is separate and depends on what the audit finds; on one training client the conversion lift showed up within the first month of the changes going live.

Yes, and that constraint is part of the audit rather than an afterthought. We review the interface you actually have, in the framework you actually use, and every recommendation is written so your own developers can implement it without a rewrite. On one warehouse-software platform we did the reverse, implementing the client's own style guide and UX concept and using Storybook to build universal components reused across more than 15 applications. If you already run a design system, findings are expressed as changes to your components rather than one-off screen mockups.

The methods are chosen per audit rather than run as a set: heuristic evaluation against Nielsen's 10 usability heuristics, independent user testing with recruited participants, an accessibility review against WCAG 2.1/2.2, competitive benchmarking, and a journey map of the path a user actually takes. All of them start from evidence you already own. We read your analytics, any session recordings you keep, and the support tickets your team is already answering, because a question support answers fifty times a week is a usability finding somebody has been writing down for you.

The key deliverable of UX Consulting Services: a document outlining our findings, insights, and recommendations. It carries an executive summary, a detailed analysis of usability issues and design inconsistencies, prioritized actionable recommendations, and a roadmap for implementation with timelines and milestones. It ships with a presentation deck built to take the insights, the proposed solutions, and the expected impact to stakeholders who will not read the full report.

Every UX consultancy in this market claims the diagnosis and the team that implements it, and so does this page, which makes the category worthless as a filter. What separates them sits one level down, in four questions. What will each finding be tied to? Ours is one of Nielsen's ten usability heuristics, a WCAG 2.1/2.2 criterion, or a named step in your funnel. Can we see a recommendation a developer could pick up unchanged? The catering-app audit shipped usability reports carrying one recommendation per issue, and a deck for the people who sign off. Who actually runs the user testing, an employee or a recruited participant? Ours are recruited to match your target demographic. And whose framework is being sold? unicrew builds to the client's requirements. Put all four questions to every firm on your list, including us.

Three cases. If your product has not launched, there is no behavior to audit, and a design sprint that validates the idea is the better spend. If you already know what is broken and only need the redesign built, go straight to UI/UX design. And if nobody on your side has capacity to act on the findings for the next two quarters, wait: the measurable results we publish came from clients who implemented the recommendations, not from clients who received them. We are also the wrong firm for large moderated lab studies and eye tracking, which we do not run in-house.

At least once a year for most businesses, or whenever a major product change is released. Sites with ongoing paid traffic campaigns or regular feature updates benefit from quarterly reviews, because you are paying for every visitor who bounces off a fixable problem. An audit is also worth running after a redesign if conversion has not improved within three months, which is one of the seven situations our own UX audit checklist names as making an audit non-optional.

Thank you

Thanks for your message. We will get in touch with you shortly.

Book a call