Starting from data
GA4 funnels, Microsoft Clarity or Hotjar heatmaps and session replays show in numbers where users stall, backtrack or leave, before we speak to anyone.
Service · Software testing and QA
Usability and UX testing
A Gaziantep brand sells baklava and pistachios through its own web store. Plenty of visitors arrive and plenty of products land in baskets, yet only a trickle of orders is completed. Analytics says people drop out at checkout; it does not say why. Maybe the delivery charge only appears on the final screen. Maybe someone sending a gift to another city cannot see how to enter a different delivery address. Maybe cash on delivery is buried, or the compulsory Turkish ID number field scares people off. Usability testing replaces those maybes with observation. Real people try to place an order while you watch, narrating what goes through their minds. Even five such sessions usually lay bare the reason for a drop you have been staring at in dashboards for months. Everything happens remotely over Teams or Google Meet, with participants using their own phones and computers.
5 people
expose the biggest obstacles
Thinking aloud
reveals why people quit
WCAG 2.1 AA
accessibility included
Second round
once changes are made
What the work covers in practice
Numbers show where you lose people; people show why. We use both.
Think-aloud sessions
One-to-one moderated calls in which the participant shares their screen and says what they are thinking while working through tasks. No other method exposes the reasons as clearly.
Who takes part
People who look like your customers: regulars, first-time visitors, older shoppers, trade buyers. We also help word the invitation and decide on a small thank-you.
Tasks from real life
Everyday goals that give no hint where to click, such as “Send a kilo of pistachio baklava to your mother's address in İzmir for the holiday.”
Menus and content structure
If category and menu names do not match how people group things in their heads, online card sorting and tree tests help find a structure that does.
Mobile and accessibility
Most tasks are done on participants' own phones. On top of that, keyboard use, navigation with NVDA and VoiceOver, contrast and form labels are checked against WCAG 2.1 AA.
Evidence-backed findings
Each issue comes with a short video clip showing it, the number of participants affected and a concrete proposal for wording, flow or design.
How we approach the job, from first call to handover
From preparation to report, a round tends to take two to three weeks, while the interviews themselves usually fit into three or four working days.
01
Data and hypotheses
Analytics, heatmaps and customer service questions are boiled down to two or three hypotheses worth testing.
02
Invitations and consent
Task scenarios, the call for participants, a KVKK privacy notice and a consent form for recording.
03
Interviews
Video sessions of 40 to 50 minutes per participant, with team members welcome to sit in silently.
04
Findings and a second round
A presentation of findings with video clips, then a quick check with three people once changes are live.
Have at least one person from your team watch a session live. Reading that “users struggled to find the delivery charge” is one thing; watching a customer hunt for it for two whole minutes is another. Managers and designers who have seen it for themselves stop debating recommendations and start implementing them.
Frequently asked questions
The aim is to find obstacles, not to produce statistics. Big obstacles show up clearly within the first few people, and later participants mostly trip over the same things. Budget is better spent on a validation round after the fixes than on extra participants.
Analytics shows that visitors leave on the payment page. It does not show whether they left when they saw the delivery fee or when they reached the ID number field. Testing fills that gap.
On the contrary, it is the cheapest moment. A clickable Figma prototype is enough to test structure and wording before a line of code exists.
Your customer list, newsletter subscribers or social media followers are usually the best source. If needed, we draft a separate call to reach people who fit the target group.
Before recording, participants receive a privacy notice and give explicit consent. Recordings are kept in a restricted-access location and deleted once the agreed period has passed.
Neighbouring services that often go with this one
Service
Functional testing
An independent check that the software you are about to accept really follows your business rules
Service
Load and stress testing
Measure how much traffic your platform survives well ahead of the day it matters
Service
Test automation
Automated checks that flag a broken flow within minutes of a code change
Service
Penetration testing
Authorised, hands-on attacks that uncover weaknesses before someone malicious does
Let's see why visitors give up
On which page or step are you losing people, and what is your hunch about the cause? We will look at your data and propose a test plan.
Availability
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Calls
By video, over Microsoft Teams or Google Meet
By video, over Microsoft Teams or Google Meet
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
- Filling the gaps. If we need more information to judge the job, we send questions by email or propose a quick Teams or Google Meet call.
- A written quote. It lists the scope, a euro price excluding VAT and a realistic start date. No hidden clauses, no items that appear later.
- Your decision. The quote arrives by email. Take whatever time you need, raise questions on any line, and decide when you are ready.