← All work
Case study 03 · Activation and analytics

Designing the first user experience

A new visitor decides within a minute whether a product is worth their time. I designed that minute: what they can do, what they see, and the moment the product asks for something in return.

My roleProduct decisions and measurement, built independently
AreaOnboarding, sign-up timing, product analytics
PeriodMay to October 2026

The question

Once videos and search pages began to bring visitors, the important question was no longer how to get more of them. It was what a new visitor should be able to do before the product asks them for anything.

Ask too early, and people leave before they know what they would be signing up for. Ask too late, and the product gives everything away without ever starting a relationship.

The decision

Give the value first. Ask for an account at the moment an account becomes useful to the user.

The first visit, as designed
1 · ARRIVEOne search box and one instruction: enter a company
2 · FIRST VALUEA complete analysis, with no account and no payment details
3 · A REASON TO CONTINUESuggested next steps: compare, track, ask a question
4 · THE ASKA free account, at the point the visitor wants more
5 · GOING DEEPERA free trial of the full product, with no card

Each step is tracked, so a change can be judged by the step it was meant to improve.

What I built

qualtix.app
A complete Qualtix analysis as seen by a first-time visitor with no account
What a first-time visitor gets with no account: the complete analysis.

What I tried and removed

Two early ideas did not survive.

Both changes follow the same rule: nothing stands between a new visitor and the first result.

qualtix.app
After the result, the page suggests a next step: comparing the company with a competitor
After the result, the page suggests what to look at next.

Measuring it

A design like this needs a way to see whether it works. I chose one measure to lead: how many visitors complete a first real analysis. Every later step depends on it.

The outcome

What I took from it

  • Let the product make its own case before asking for anything.
  • The timing of a request matters as much as the request.
  • Removing a step can be the improvement.
  • Check that a number can be true before acting on it.