Usability testing cost in the Philippines and how long it takes
Usability testing cost in the Philippines is driven by four things: how many users you test, how hard they are to recruit, whether sessions are remote or in person, and how much analysis you want back. A five-user round usually runs about two weeks end to end.
Two quotes for usability testing on the same customer journey can be several times apart. Here is what sits inside the price, how long a round takes, and what you need ready before anyone books a session.
There is no single peso figure, because the price swings on who you recruit and what you get at the end. What follows is the parts of the quote, so you can put two proposals side by side and see what each one actually includes.
Written for digital and operations people at banks and insurers who need to show a boss something real from a customer journey, not another deck.
What you are actually paying for
Most quotes bundle five things: writing the tasks, recruiting the people, incentives for their time, someone moderating each session, and the analysis afterwards.
Recruitment and incentives are the parts that move the price most. Five people off the street is cheap. Five existing customers who opened an account in the last 90 days, on Android, outside Metro Manila, is not. If a vendor's price looks low, check who they are planning to put in front of the screen. Cheap quotes usually mean whoever was easy to find.
Analysis is the other place quotes diverge. A raw folder of recordings costs less than a highlight reel with time stamps and a written list of where people stopped. The folder is cheaper and nobody watches it. Ask what you get on the last day, and in what form, before you compare prices. If the answer is "a report", ask how many pages and whether it includes clips.
Five users, not twenty
The biggest cost decision is how many people you test with, and teams routinely buy too many.
Five people on one customer journey will show you the blocking problems. The sixth and seventh mostly repeat what the first five did. If you have two clearly different groups, say new customers and branch staff doing the same task, then test five in each group rather than ten in one pile.
Testing twenty people starts to make sense when you need a number you can quote, say completion rate on two versions of the same screen. That is a different piece of work at a different price, and most teams are not there yet.
We wrote up the mechanics of a five-user round separately, including how to script the tasks: How to run a usability test with five real users.
How long a round takes
A round on one journey takes about two weeks from agreeing the tasks to watching the clips.
Recruitment is the slow part, not the sessions. Sessions themselves are 45 to 60 minutes each, and five of them fit into two or three days. The waiting happens while a recruiter fills the slots and people no-show and get replaced.
If anyone quotes you six weeks for one journey, ask what is happening in weeks three, four and five. Usually it is internal review cycles, not research.
For comparison, in a series of five-day design sprints with a large insurer, customer-facing journeys that used to take six months or more to get out were designed and tested with customers in two weeks and live in four. Twenty-six weeks down to four. The client measured completion rates on the new journeys going up 80 percent, and the old drop-off points disappeared. The testing was never the slow bit. Getting a decision was.
What you need to bring
Three things. Have them ready and the quote comes down.
First, something a person can click. A rough clickable prototype is fine, as long as a person can get from the start of the task to the end without you explaining it, and it is often better than the live product because you find the problem before you pay for the build. What does not work is testing a PowerPoint of screens.
Second, two or three real tasks, written the way a customer would say them. "Open an account using your phone" works. "Evaluate the onboarding experience" does not.
Third, the current number. Turnaround time on the onboarding flow, completion rate, drop-off at the ID step, whatever your boss will ask about. Pull it before the sessions, even if it is rough and comes off a report nobody trusts. Without it you will have five good videos and no way to answer whether it worked.
The cheapest version, and when it is enough
If you have no budget approved this quarter, there is still something to do.
Walking the journey yourself against a fixed checklist will find the obvious breakages in an hour: unlabelled fields, error messages that do not say what to fix, steps that ask for the same document twice. That is not the same as watching a customer fail, and it will not tell you why someone gave up. It will tell you what to fix before you spend money watching people trip over things you already knew about. We have the method here: How to review a website or app against usability standards in 60 minutes.
Do the review first, fix the obvious items, then test. Otherwise you pay five people to point out an unlabelled field.
What to do this week
- Write down the one journey you will test and the two or three tasks, in customer language.
- Pull the current number for that journey now, before anything changes, and note where it came from.
- Ask each vendor three things: who they will recruit, how many sessions, and what you get on the final day.
- Run the 60-minute review yourself and fix anything obvious, so the sessions are not wasted on it.
- Book 30 minutes for your boss to watch two of the clips. Watching a customer get stuck ends the argument about whether there is a problem.
More on Usability testing
- What is usability testing and what it tells you
- How to run a usability test with five real users
- Instead of another internal review, watch five customers use it
- What AI training for a team costs and how long it takes
- AI Prompting Essentials: what it costs and how long it takes
- Everything on Usability testing
Questions people ask
How many users do you need to test with?
Five is enough for one round on one customer journey. Five people trying the same onboarding flow will surface the same blocking problems, and paying for twenty rarely changes the fix list.
How long does a round of usability testing take?
Around two weeks from agreeing the tasks to watching the clips. Recruitment is usually the slowest part, especially if you need existing customers of a specific product.
What do we need to have ready before testing?
Something a person can click, two or three real tasks written as a customer would describe them, and the current number for the thing you want to improve, such as turnaround time or completion rate.
Can we test a prototype rather than a live product?
Yes. A rough clickable version is often better, because you find out what is wrong before development time is spent on it.
On-Off Group trains teams, tests products with real customers, finds where a transformation has stalled and builds what gets it moving, for banks, insurers and enterprises in the Philippines, since 2015. How we help with usability testing.
