Skip to content
Al Khobar, Saudi Arabia

usability testing services

Watch real people use it, then fix what stops them

Your team knows the product too well to see its problems. We put it in front of target users in Arabic and English, record where they hesitate or fail, and return a short list of fixes ranked by impact.

1 to 2

weeks from plan to ranked findings

5 to 8

participants per user group

2

languages for sessions and reports

Moderated sessionsRemote unmoderated testsTask success measuresThink-aloud protocolArabic and English sessionsAccessibility checksMobile and desktop testingPrototype and live testingSeverity-ranked issuesHighlight reel of clips

The direct answer

Usability testing is watching representative users attempt real tasks with your product, prototype or website, and recording where they struggle. It fits teams about to launch, redesign or fix a flow that is losing users. We recruit participants, run sessions in Arabic or English, and deliver findings ranked by severity with recommended fixes.

Before and after

What this removes.

The team thinks it is obvious

Today

Everyone inside the company knows where the button is, so nobody sees that new users cannot find it.

With the system

Recorded sessions show a first-time user searching for the button, which settles the debate quickly.

Conversion drops and the cause is a guess

Today

Checkout or sign-up completion falls and the team argues about price, trust and design without evidence.

With the system

Task tests pinpoint the step where users stop and the reason they give, so the fix is aimed.

Testing happens once, too late

Today

The only user test was a week before launch, when every finding meant a delay.

With the system

Tests run on prototypes early and on the live product later, when changes are still cheap.

Accessibility is checked by tools only

Today

An automated scan passes, yet screen-reader and keyboard users cannot complete the main task.

With the system

Manual checks and sessions with assistive technology find the barriers scanners cannot detect.

What we build

What lands in your hands.

Test plan and task scripts

Realistic tasks, success criteria and the questions each test must answer.

Participant recruitment

Screened users who match your real audience, scheduled and consented.

Moderated sessions

Live one-to-one sessions in Arabic or English, recorded with consent.

Remote unmoderated tests

Tasks completed in participants' own time, for a wider sample at lower cost.

Accessibility checks

Keyboard, contrast, text scaling and screen-reader review against WCAG.

Ranked findings and clip reel

Issues by severity, each with a clip and a recommended fix.

In depth

How it works, and what to decide.

Moderated, remote or both

A moderated session is a live conversation: a facilitator gives the participant tasks, asks them to think aloud and follows up on what they do. It is the best method for finding why people struggle, and it works well for early prototypes, complex flows and sensitive topics. A session takes thirty to sixty minutes and five to eight sessions per user group usually show the major problems.

A remote unmoderated test sends the same tasks to participants who complete them alone, on their own device, while the screen and voice are recorded. It reaches more people for less money and shows behavior in a natural setting, but you cannot ask a follow-up in the moment. We often combine them: moderated sessions to understand the problems, then an unmoderated round to confirm that the fixes worked across a larger and more varied group.

Measures, severity and accessibility

Every task has a success definition decided before testing: the user reached the right end state, in a reasonable time, without help. We record completion, time on task, errors and the participant's own rating of difficulty. These give you a baseline to compare against after fixes, so improvement is a measurement rather than an impression.

Each finding gets a severity: a blocker stops the task, a major problem slows it significantly, a minor one irritates. The ranked list tells your team what to fix first. Accessibility is part of the plan, not an add-on. We check keyboard-only use, visible focus, color contrast, text resizing and screen-reader behavior against the Web Content Accessibility Guidelines (WCAG) 2.2. Automated scanners catch only a portion of real barriers, which is why manual review and sessions with assistive technology matter.

Running tests in Arabic and with Saudi users

Test in the language your users work in. Arabic participants react to wording, icon meaning and mixed-direction text in ways a translated English script will miss. Our moderators run sessions in Arabic, probe in Arabic, and write findings in both languages. We recruit for the segment that matters: first-time buyers, field staff, branch managers, or citizens using a service, with a spread of devices that reflects the Saudi market, including mid-range Android phones.

Participants' recordings and details are personal data. Each person gives explicit consent for the purpose, we limit who can see the recordings, and we delete them on the date agreed, following the principles of the Personal Data Protection Law (PDPL) issued by SDAIA. A typical engagement takes one to two weeks from plan to ranked findings, with another few days if you want us to re-test the fixes.

The delivery plan

Five stages. You sign off every one.

Read each stage as a small contract: what we need from you, what lands in your hands, and the sentence that has to be true before we move on.

01 / 04

Plan the test

2 to 3 days

We agree what to test, with whom and how success will be measured.

What you do
  • Give us access to the product or prototype
  • Name the tasks that matter most
  • Describe your target users
What we deliver
  • A test plan and task scripts
  • A participant screener
  • Success criteria for each task
Exit criteria

We move on when the tasks, participants and success criteria are approved.

02 / 04

Recruit participants

3 to 5 days

We find and schedule screened participants and collect consent.

What you do
  • Share customer contacts if you want to recruit from your base
  • Approve the participant list
  • Confirm the devices to cover
What we deliver
  • Booked sessions
  • Signed consent records
  • A pilot session to check the script
Exit criteria

We move on when all sessions are booked and the pilot ran cleanly.

03 / 04

Run the sessions

3 to 5 days

We run moderated and, where planned, unmoderated tests, and log every issue as it appears.

What you do
  • Watch live through a private link
  • Hold questions until the break
  • Flag any session you want repeated
What we deliver
  • Recordings and session notes
  • A running issue log
  • A daily summary of what is emerging
Exit criteria

We move on when the planned sessions are complete and new sessions stop revealing new issues.

04 / 04

Report and re-test

3 to 5 days

We rank the findings, produce a clip reel and recommend fixes, then re-test if you ask.

What you do
  • Join the findings walkthrough
  • Decide which fixes go first
  • Book a re-test once fixes ship
What we deliver
  • A severity-ranked findings report
  • A highlight reel of key clips
  • Recommended fixes with design notes
Exit criteria

We move on when your team has a prioritized fix list and owners for the top items.

Buyer questions

Asked before signing.

How many participants do we need?

Five to eight per user group is enough to find most major problems in a moderated test. If you have distinct groups, such as customers and staff, test each group separately. Unmoderated remote tests can use larger samples when you need numbers.

Can you test a prototype before we build?

Yes, and that is often the cheapest time to test. A clickable prototype lets us find structural problems before any code is written. We can then test the live product again closer to launch.

Do you run sessions in Arabic?

Yes. Moderators run and probe sessions in Arabic or English according to the participant, and findings are written in both languages. Original Arabic quotes stay in the report so your team can verify the meaning.

How much does usability testing cost?

The price depends on the number of user groups, the number of sessions, moderated or remote format, and whether we recruit. We quote a fixed price after the planning call, and recruiting from your own customer list lowers it.

What do we receive at the end?

You get a severity-ranked findings report, task success measures, a highlight reel of key clips, and recommended fixes. All recordings and notes are yours, and we delete our copies on the agreed date.

Find the problems before your customers do

Tell us what you want tested and who uses it. We will propose a plan and a fixed price within a few working days.