How Much Does Usability Testing Cost in Ireland?

If you're building a business case or comparing proposals, “it depends” is not enough. This guide explains the variables that move the price of a study, publishes Usability.ie's own planning bands, and shows what a written quote should make explicit.

It isn't a rate card. Treat it as the buyer-education companion to the questions worth asking a usability testing supplier before you sign — that piece covers how to judge whether a supplier is any good; this one covers why the invoice looks the way it does.

What actually drives the cost

Two studies that both get labelled "usability testing" can cost very different amounts. The gap almost always comes down to four variables, and a proposal that doesn't address them explicitly is one you should ask harder questions about.

• Participant count and recruitment difficulty. A broad consumer screener is a different recruitment task from finding senior clinicians, procurement managers in a narrow business segment, or people who use a particular assistive technology. The quote should separate participant count, recruitment work and incentives instead of hiding all three in one number.
• Number of rounds. A single moderated round answers one set of questions about one version of a journey. Iterative testing — a round on the current site, a round on a redesigned prototype, a validation round after changes ship — multiplies session time, analysis time and reporting, but also produces evidence a single round can't: whether a specific fix actually worked.
• Journey complexity. Testing a single checkout flow is a narrower task than testing an entire onboarding journey that spans account creation, verification, first-use setup and a support handoff. More steps mean longer sessions, more edge cases to script for, and more findings to write up per participant.
• Analysis depth. A top-line findings deck with a handful of themes is faster to produce than a report that ties every finding to a timestamped clip, severity-rates it, and cross-references it against a specific heuristic or business metric. If two quotes differ and you can't see why, ask what "analysis" includes in each — a summary of impressions is not the same deliverable as a report you can act on without re-interpreting it.

None of these variables map to a single multiplier — a supplier who tells you "each extra participant adds a fixed €X" without discussing recruitment difficulty, rounds or journey scope is oversimplifying. A credible quote explains which of the four is pushing your project toward the top or bottom of its price band.

Usability.ie's published planning bands

These are the price bands currently published on our services page. They describe our own offer; they are not presented as an independently researched Irish market average. Treat them as planning ranges, not quotes — the written scope determines the actual fee.

For what's actually included at each price point — deliverables, typical timelines, and which service fits which problem — see the full breakdown on the services page.

Pricing questions to resolve before signing

Our buyer's guide covers method, evidence, recruitment and who does the work. On pricing specifically, resolve these points in writing:

• A number with no scope attached to it. If a quote arrives before anyone has discussed participant count, rounds or which journey is in scope, it isn't a quote — it's a placeholder that will move once the real conversation happens.
• One flat "usability testing package" regardless of project. Testing a five-step checkout and testing a full onboarding journey are different amounts of work. A single fixed package price for both suggests a template, not a plan built around your journey.
• A low price with no explanation of the narrower scope. It may be a sensible smaller engagement. Ask which participants, journeys, evidence and deliverables are included so proposals can be compared like for like.
• Pressure to sign before a written scope exists. A credible supplier can put deliverables, timeline, fee and what's explicitly out of scope on two pages before you commit. If that document doesn't exist yet, the price isn't final either.

How to get a useful planning range from the first call

Our process runs like this:

1. Brief call (free, ~30 min). You describe the problem — the journey that matters commercially, what you already know from analytics or support tickets, and the decision the research needs to support. We tell you which service fits and at what price band. No pitch deck.
2. Written scope. A short document — deliverables, timeline, fee, and what's out of scope — so the number in step one becomes a specific commitment rather than a ballpark.
3. Engagement plan. The proposal sets the timetable for the agreed scope, including dependencies such as participant recruitment, access to systems and client review.
4. Findings session. A live walkthrough of the report, not a deck delivered cold.

Bring three things to the call: the URL or product in question, the specific journey or decision you're trying to settle, and any constraint that affects recruitment — a niche audience, an accessibility requirement or a hard deadline. The call should produce either a reasoned planning band or a short list of facts still needed before one can be given. The written scope, not the call, is the commitment.

Read next

• UX services and price bands — the full breakdown for all five services
• Usability testing service — how we scope and run a study
• 9 Questions to Ask a Usability Testing Supplier in Ireland

← All insights