Hiring a UX Design Agency: What You Actually Get, and How to Measure the Return

Hiring a UX design agency is an opaque purchase: nobody defines the deliverables, and agencies sell the return with numbers that have no source. This guide defines what you actually receive, when an audit alone is enough, and how to measure the return with your own metrics rather than a pitch deck's.

Anyone shopping for a UX design agency runs into a problem that buying a logo or an ad campaign doesn't have: nobody defines what you will actually receive. One proposal says "UX improvements," another says "full redesign," the price gap between them is threefold. and nothing on paper explains the difference.

This article is written from the other side of the table. We sell this service, we build our own product with it, and we know where the details get buried, the ones that separate a successful engagement from a Figma file nobody ever opens. The goal is that you walk into your next agency meeting, with us or anyone else, knowing what to ask for and what to measure.

When you need a UX agency: and when you don't

The signals that your problem is an experience problem, not a marketing problem:

• Visitors arrive and don't buy or sign up. The ad works; the page doesn't. The problem is after the click, not before it. • Support answers the same questions every day. Every recurring question is an interface that failed to answer it. • Every new feature breaks the consistency of your screens. Your team keeps adding and the interface keeps fragmenting, that's the absence of a system, not the absence of a designer. • A product that works but nobody enjoys. Usage is grudging, and churn arrives with the first alternative.

And the honest counter-case: if you don't have users yet, you don't need a UX agency. you need to launch. Experience is improved against real behaviour, not assumptions. And if your problem is that nobody reaches your site in the first place, that's an acquisition problem, and your budget belongs in acquisition channels.

What you're actually buying: the seven deliverables

"Improving the experience" is not a deliverable. These are the UX agency deliverables that should appear by name in any serious proposal, in the order they happen:

1. User research: interviews and observed usage, producing a problem list ranked by evidence rather than taste. 2. A UX audit: a systematic review of the current product (it gets its own section below). 3. User journeys and information architecture: how a user gets from entry to goal, and where the path breaks today. 4. Interactive prototypes: clickable screens tested before a line of code is written. 5. UI design: the final visual layer, built on the decisions above. 6. A design system: colour, type, spacing and components documented as a reusable library. 7. Developer handoff: specifications, states and behaviours, not flat images left to a developer's interpretation.

The decisive difference between two similarly priced agencies is usually item six. When we redesigned the eaalim learning platform, research, then UX, then UI, the most valuable thing we delivered wasn't the screens but the system underneath them: a documented component library that makes every page built afterwards consistent by default, without going back to a designer for each addition.

An agency that delivers pictures keeps you coming back forever. One that delivers a system makes itself unnecessary: the paradox of our industry is that the best deliverable is the one that reduces your need for us.

The UX audit: the smallest, lowest-risk way in

If you're not ready for a redesign, a UX audit is the right way to test an agency before committing to one. A professional audit combines three layers:

• Expert review against documented usability principles: a systematic pass over the interfaces against published standards, not "a designer's opinion." The reference here is explicit: Nielsen Norman Group's definition of an expert review requires every finding to be tied to a specific location and a documented principle, and given a severity rating, an "audit" without those three isn't one. • Analytics and behavioural evidence: where users actually drop off, matched against what the review found. • An accessibility check: can someone with a screen reader, one hand, or a weak connection complete the task?

The correct output is a weighted list: every finding with its severity, its evidence, and a rough cost to fix. so your existing team can ship the highest-impact quarter of it on their own. Beware the audit that ends in a slide deck about "the importance of UX"; you knew it mattered, which is why you paid. And an audit can be the end of the engagement rather than the start: if your problems are the kind your own team can fix, a serious agency says so and leaves.

Measuring the return: without the mythical numbers

The most famous number in this industry's marketing: "every $1 invested in UX returns $100." Thousands of articles attribute it to Forrester and repeat it. and you will not find a published primary report you can read and whose methodology you can check. The oldest traceable appearance is a 2015 Forbes contributor piece that cites no report and even misspells Forrester. It's a zombie statistic: it survives on cross-citation, not on a source. An agency that opens its pitch with it is telling you something useful about how it handles evidence. Treat any ux return on investment figure the same way: ask what it was measured against, and over what period.

What survives verification is less thrilling and more useful. McKinsey's "The Business Value of Design" (2018) tracked 300 listed companies over five years and found that the top quartile of its design index outperformed industry peers by 32 percentage points in revenue growth and 56 points in total shareholder returns: across medical technology, consumer goods and retail banking alike. And Baymard Institute's research documents that shoppers abandon 70.2% of carts before completing checkout (a meta-average of 50 studies, last updated 2025), and that a large e-commerce site can lift conversion by around 35% through better checkout design alone.

But the measurement that matters lives in your numbers, not in other people's studies. Before any UX project, baseline four metrics:

Then ask the agency to name, before signing, which metric it expects to move and in which direction. An agency that won't let its work be measured is asking you for faith, not a contract.

Agency, freelancer, or in-house team?

The deciding factor isn't quality, all three categories have excellent people, it's the size and continuity of the work:

The practical rule: a task → a freelancer. A project → an agency. A living product → an in-house team, with the agency building the design system alongside it and then stepping back. That third path is the most overlooked and often the right one for a growing product: you buy the foundation and the system from the agency, and your team runs the day-to-day on top of it.

How to read a proposal: seven questions before you sign

1. Who actually does the work? The people in the sales meeting are not always the people on your project. Ask for the actual team's names and work.

2. Is the design system included, or "phase two"? It's the item agencies most often cut to lower the price, and the most expensive one to buy separately later.

3. Who owns the source files? Ownership of the Figma files and the component library must transfer to you in full at the final payment, no exceptions.

4. Whose name is on the font licences? A typeface licensed in the agency's name rather than yours means you don't actually own your identity. we covered this trap in our guide to arabic typography in brand identity.

5. How does the agency test its decisions? On real users, or on "the team's experience"? The second is debatable taste; the first is evidence.

6. What happens after launch? Who measures the agreed metrics, and when do you review the results together? A project with no post-launch review is half a project.

7. Where is their work on living products? Ask for a product that launched a year ago and is still consistent. We build and run our own platform, Redod. and an agency that lives with its own product knows the cost of bad decisions because it pays them itself, not because a client complained.

The Saudi market: Arabic-first is not an add-on

The figures from the CST's Saudi Internet Report 2024 settle the picture: internet penetration has reached 99%, mobile is the browsing device in 99.4% of usage, and average data consumption is 48 GB per person per month: three times the global average. Your Saudi user browses mobile-first, with expectations raised by government and commercial apps that now rank among the smoothest anywhere. The floor has risen: an interface users tolerated five years ago, they close from the second screen today.

And your market is most likely bilingual: customers reading Arabic, staff or partners reading English, and one interface that has to serve both equally well. That is an architectural decision made at the start of a project, in the typefaces, the components, the text lengths, and it cannot be patched on later as a translation.

And the fastest test of any agency working in the Saudi market: ask how they design Arabic. If the answer is "we design in English and flip the direction," you will receive an interface that looks Arabic and behaves English, flipped numbers, icons pointing the wrong way, and cramped text because the line height was set for Latin letters. Arabic interfaces are designed Arabic-first from the first decision: the typeface is chosen against Arabic text, components are built for both directions, and numeric fields follow their own rules. This isn't a technical detail; it's the difference between a product that respects its user and a translated one.

Related reading: rtl design, ui/ux design.

Core Web Vitals reference: Google web.dev — Core Web Vitals.