Our approach

We organise and run your user tests from A to Z. You quickly receive clear findings and concrete recommendations, so you can focus on improving your product.

Week 1

Kick-off & planning

We define the objectives and the priority user tasks with you.

We prepare the test guide (tasks, questions) for your approval.

We help you define the right profiles and recruit the participants.

Your part: a one-hour kick-off and access to your website or prototype.

Week 2-3

Test sessions

An experienced UX specialist runs the sessions remotely, in English, French or German.

Your teams can follow the sessions live or watch the recordings.

Optional: a video highlights reel, ideal for convincing stakeholders internally.

Week 3-4

Recommendations

We analyse the observations, participants' comments and rating scales.

You receive a report with findings ranked by severity and prioritised recommendations.

We present the results in a debrief session, answer your questions and plan the next steps with you.

Frequently asked questions

Is participant recruitment included?

Yes, we handle recruitment and it is included in our offers. Depending on the profiles you need, we work with professional recruiters or carry out the selection ourselves, using a screening questionnaire designed for your project. The cost depends on the number of participants and how specific your criteria are: the rarer the profile, the more effort recruitment takes. Where appropriate, we can also use your own channels, for example a customer database, an invitation sent to your customers or a recruitment message displayed on your website. We agree on the best approach together, as the quality of the insights depends largely on the quality of the recruitment.

Is our data kept confidential?

Yes, we are happy to sign a non-disclosure agreement with you. If you wish, we can also ask participants to sign an NDA before the sessions, for example when testing a product that has not yet been launched.

Can you test a prototype?

Yes, we test live websites and apps as well as Figma prototypes and mock-ups. Testing early lets you fix problems before development, when changes cost the least.

When should we test?

As early as possible, and ideally more than once. Testing a mock-up or prototype lets you validate your choices before development, while changes are still inexpensive. Testing before launch prevents your customers from discovering the problems for you. And on a website or app that is already live, testing reveals what holds your users back and shows you where to focus your efforts. In short, it is never too early or too late to test: only the type of test changes.