Worth Logging
In For

Ahotu lists endurance races in more than 195 countries. Its Premium membership gives athletes more reasons to return, with access to selected sold-out races, early registration, partner discounts and race packages for €29 a year.

For Ahotu, Premium was an opportunity to improve retention and build closer relationships with race organisers and endurance brands.

My work focused on the membership journey, from the decision to join, through payment, to claiming a first offer.

Ahotu Premium member profile showing event offers and brand offers
ROLE
UX Designer
TEAM
Design lead (UI), PM, Dev lead & developers
SCOPE
Join & pay flow, member profile, offers, consent, cancellation, design reviews
TIMELINE
May–Sep 2026 · Soft launch Aug 2026

Two questions to design for.

For athletes, the hardest part is often getting in at all. Popular races can sell out in hours, and getting a place in a special race can be really hard. Athletes already use Ahotu to find races. The Premium membership adds a new option, a yearly fee in return for benefits they can't get on their own, like entries to sold-out events, early registration, discount codes from endurance brands and race packages. Most of those benefits come from race organisers and partner brands, not from Ahotu itself.

That left two questions to design for. How do you make the value of €29 feel clearly worth it before someone joins? And after paying, how do members find and claim what they paid for?

693
ATHLETES SURVEYED
66.7%
OF MEMBERS (12 OF 18) USED OR CLAIMED A BENEFIT IN THE FIRST MONTH
3
DESIGN REVIEW ROUNDS AGAINST PRODUCTION

Real advantages for athletes, on a tight deadline.

Ahotu wanted a paid membership that gives athletes real advantages, like races they couldn't otherwise enter, earlier registration and discounts from endurance brands. The project started on 11 May with a deadline of 30 July. Summer slowed it down, and the soft launch went live at the end of August.

We designed alongside development, not ahead of it. Most decisions in this case were made while the thing was already being built.

I owned the UX of the membership flows, from upgrade and payment to cancelling, along with consent and the design reviews against the build. The member profile and the offer cards and modals were shared work with our design lead. I iterated on them through many rounds of visual concepts and tested their states. Visual direction and the landing page were led by our design lead.

The PM ran weekly check-ins to track progress and blockers. Throughout the project, the work kept coming back to four questions. Who is it for, what problem are we solving, what does success look like, and what are the risks. For us, success meant one thing first, that members use what they pay for. It's early, so the longer-term picture, like renewals and retention, will only show once more time has passed.

Before joining: had to show the value.

  • Value visible before paying, not after
  • One landing page explaining every benefit
  • Only promise what's ready on launch day

After paying: had to be easy to use.

  • One clear place to find every benefit
  • Simple steps to claim an offer
  • Clear labels when something is sold out

How might we make the value clear before joining, and easy to find and use after paying?

A survey decided what the membership would hold.

Before any screens, the PM surveyed 693 athletes about what a membership should include, and 597 of them answered the question about features. The PM shared the results with the team. Race entry discounts came first (72.5%), then guaranteed entry (61.1%), early access (58.3%) and travel and accommodation discounts (50.3%). Community and VIP perks came last, both below 15%.

That ranking sorted every idea into three tiers, core value drivers, supporting value, and low value for now. The core four became the primary features. It also simplified the offer. The membership went from three levels (Free / Pro / Elite), to Free / Premium / Premium+, and finally to just Free and Premium.

With little time before build, I didn't run research of my own and relied on the PM's survey. My effort went into the flows instead, mapping every way a user could arrive, pay, fail and come back.

Feature tiers. 693 athletes answered the survey; 597 answered the features question.

Access, Rewards, Experiences.

The top results became the three parts of the membership. Access means sold-out races and early registration. Rewards are discounts from partner brands. Experiences are race and travel packages. The landing page uses these three. So does the member profile. What you're promised before paying is exactly what you find after.

What the research couldn't answer.

A survey shows what people want, not what they'll actually do. And some answers weren't ours to give. Would organisers agree to take part, who would pay for the discounts, and would too many members use up the sold-out places?

Because none of that was certain at launch, the copy only promises what we could keep. The landing page says "selected" sold-out races, not all of them. It says availability changes during the year. And the FAQ gives a straight answer to the first thing athletes ask, "Are my race entries guaranteed?"

Planned big, shipped simpler.

The first flow covered everything. It had four ways in, each with its own path, logged out with an account, no account, logged in, or already on the profile. It also planned extras, like a code for email verification, a loading page with an order summary, an Ahotu receipt email and a separate page for partner benefits.

Most of it was simplified on purpose. The team drew an MVP line on the story map, and everything below it moved to v2, including promo codes, changing plans, pausing, win-back offers and notification settings. Some steps were cut because they repeated information. The loading page repeated what the user had just read on the landing page, so it only added a click. And since it was our first time using Stripe (an online payment service that runs the checkout), some planned steps turned out to be things Stripe already handles.

What shipped instead:

  • A verification link instead of a code
  • Straight from the landing page to payment in Stripe
  • Stripe sends the receipt; Ahotu sends a welcome email confirming the membership
  • Benefits on the profile, not a separate page

The planned system. Two of the four ways in.

Five places to find it.

Premium can be found in five places on the site. All five use the same button, "Explore all benefits," and lead to one landing page, where the button changes to "Go Premium," because that's where joining starts.

Internal linking. Every path ends on the profile, where members claim their offers.

The long way round is where people drop off.

Signing up with Google goes almost straight to payment. Signing up with email doesn't. You fill in the form, check your inbox, confirm, log in again, then pay. Every step in that detour is a chance to forget why you started.

The design treats intent as something to carry through the flow. The confirmation step tells users their account is confirmed and that the last step is to log in and pay. The login after confirmation keeps them on the path instead of offering new options. Payment happens in Stripe, with states for failure and retry, and a short loading overlay while the payment completes. Success leads to one place, the profile.

One state, three problems.

Anyone who has chosen Premium but not paid sees "Almost there!" on their profile, with one button back to payment. It is stored on the account, not the browser, so it covers someone who closed the tab, someone whose card failed, and someone who started on their phone and continues on a laptop.

We didn't build a separate recovery page or reminder flow. Keeping it on the profile meant members always have one home for their membership, instead of information scattered across emails and pages. As a result, one screen catches abandoned checkouts, failed payments and device switches.

Almost there. One screen for abandonment, failed payment and a device switch.

One profile, three states.

Every path in the membership ends in the same place, the profile. The payment success page, the welcome email and the login all lead there. Because members always come back to it, it had to make sense in every state.

The first plan gave benefits their own page. We moved them onto the profile instead, because a separate page would have been one more place to find.

  • Free shows what Premium includes, the price, and two buttons, explore all benefits or go Premium.
  • Pending payment shows one button, go to payment.
  • Premium shows a member badge next to the name, and three rows of offers, for events, packages and partners.

The cards got calmer too. Early versions stacked four coloured badges on every card. The final version uses one label. A "best deals" row was also cut from the first version. With a tight deadline and only a few deals at launch, it risked looking thin, so it waits until there are enough strong deals to make it worth showing. A "Show all" view, a lightbox listing every event offer when there are more than fit in the row, was designed but cut for the first version.

Three states. One page, three people, one clear thing each.

A patch first, then the structure.

At first, the profile showed one card per race. That worked until an event had several races. After launch, the 3 Days Ultra Trail Ibiza showed up three times in a row, with the same photo, title and date.

Before. One card per race, correct card by card, confusing as a row.

I spotted the duplicates in review and reported them. The first fix was a patch, a distance pill on each card, and a "Sold out race" label for events with several races. Every card was now correct, but the row still showed the same event three times.

So the structure changed. Now there's one card per event, so the profile shows each event once, and members understand the offer before choosing a specific race. All its races are inside the offer modal, grouped by sport, each with its own discount, date and button. Spotted in review on 7 September, patched on 9 September, restructured on staging by 18 September.

It had a cost. Athletes now need one more click to see the race they want, because the card on the profile only shows the event. We accepted that, because a row you can read mattered more than seeing every race at once.

I raised a question the team hadn't settled. Should offers that weren't open yet show at all? We kept them, because they show what's coming, but made them clearly not claimable, with a muted "Coming soon" badge, and always last in the row.

Card explorations. Distance pills, single and multi race, and an early coming-soon state, before the final card.

Inside the modal.

After, desktop and mobile. One card per event, every race inside the modal. On mobile the date and button stack under each race.

The offer modal went through three versions:

  1. Version one described the race, with a single "Register here" button.
  2. Version two explained the offer instead: what you get, and how to claim it. I changed the button from "Register here" to "Claim offer", so it says what the member gets, and the note to "Use this link to claim your offer", so it reads as theirs.
  3. Version three, the one shown above, groups races by sport, shows the real discount ("10% off" rather than "Discount"), folds long text behind "Show more," and explains sold-out access in plain words.

By this point, the member has already picked the race. What they need is the deal and the next step.

Designed for real data.

Every modal was tested at both extremes, a single-ticket event and a 13-race event, plus long race names that wrap. The labels now live on the profile, like "Event sold out", "Sold out race" and "15% off".

A clear yes, and an honest way out.

Premium members get their own newsletter, and it needed its own consent. The first idea was a checkbox during signup, mixed in with everything else. I looked at how others ask. Strava, for example, asks in a separate modal with two equal answers, yes or no, instead of hiding a box in signup. The final design follows that idea. It asks once, after payment, in an opt-in modal with a clear "I'm in!" and an easy "No, thanks."

Members who say no see a small banner on their profile, with one button if they change their mind. They can also change it anytime in Settings. Cancelling the membership doesn't change their choice without asking. The result is that members choose once, and can change their mind without contacting support.

Cancelling is in Settings, not hidden behind support. The membership block shows when it renews and that you keep access until then. One confirmation, "Yes, please" or "No, never mind," then a cancelled state with a way to renew. No discounts to make you stay, no guilt.

The full lifecycle.

Discover, join, pay, use, manage, leave. Every step has a clear route, from finding Premium to cancelling.

Three rounds, two signatures.

With design and development running in parallel, the design review was where the product actually took shape. I ran three formal rounds, on top of checking production almost daily, two before launch (18 and 24 August) and one after (7 September).

Each board followed the member journey in order, with design next to production on desktop and mobile. Every issue got a priority-tagged note and two sign-off boxes. Dev fixed it, design approved it.

Pre-launch review, 18 Aug. Production with one note per issue, and a Dev and Design check on each.

What the reviews caught.

  • A price of €30 per day in the Stripe sandbox, before launch
  • A "Go to payment" button that didn't reach Stripe (shown above), fixed before launch
  • Ahotu green failing contrast on light grey, which moved small green text to soft black
  • A carousel rule that only shows with more than four cards, tested by adding cards
  • Duplicated event cards, after launch, which became the structural fix in section 07

Knowing when not to add UI.

Two price notes were discussed. A line explaining currency conversion was removed, because the system already handles it and it only added doubt. A line saying local taxes might apply was kept, because it changes what people actually pay.

A soft launch as the test.

Delivered. A working membership journey, discovering Premium, joining, paying, using offers, managing consent and cancelling. Tested inside the team with a written test plan, three design reviews against production and an edge-case document. There was no external usability testing before launch.

Assumed. Before launch we could check that every flow worked, but not whether athletes understood the offer or felt confident paying €29. We accepted that risk because the launch was soft and unmarketed, and planned to learn from how real members behaved.

Observed. Premium launched softly, without marketing. In the first month after launch, 12 of 18 members used or claimed at least one benefit, from buying a ticket to a sold-out race to copying a partner discount code. What members used lined up with the survey, with one difference. Athletes said race discounts mattered most, but the most-claimed benefit was entry to a sold-out race, and race packages had the highest take-up per offer.

Engagement. Compared with logged-in users without Premium, paying members visited about twice as often and viewed about 2.5× as many pages in the first month. That's correlation, not proof. Athletes who are already active may simply be more likely to join.

The drop-off. About two in three people who started checkout didn't finish. We know where people leave, but not why. It could be price, trust, payment friction, or people just looking. The next step is to find out through checkout analytics and short sessions with athletes, before changing the design.

Not yet known. Renewals, revenue and long-term retention. The first renewals are a year away. For partner codes we can see when a member copies one, but not whether they then bought something on the partner's site.

Month one. People use what they pay for. Checkout is the next problem.

Bringing Premium to the moment athletes choose a race.

The first month also showed a pattern. Some athletes joined and claimed a benefit almost straight away. They had found a specific deal first, then became members to get it. Version 1 made Premium easy to find. Version 2, which I'm designing with our design lead, brings it to that moment, on event pages and in the calendar, where athletes actually choose races.

This part is in progress right now. Check back soon to see where it lands.

What worked

Designing for real data. Duplicates, 13-race events, long names and empty states only show up with real content. Every rule that survived was tested against the extremes.
Review as design. With design and build in parallel, reviewing production was where the product got finished. Real bugs were caught before members met them.
One hub. Sending every path back to the profile made three states enough to cover abandonment, failed payments, device switches and active members.
Labels that match reality. "Explore all benefits" on every button leading to the Premium page, "Go Premium" on the page that sells, "Sold out race" when only one race is. Small words, fewer wrong expectations.

What to do differently

Protect the thinking time. We designed alongside development to hit the deadline. It worked, but thinking moved into the middle of the build. Late copy fixes, reworked cards, discussions that went backwards. Rushing doesn't make a project shorter. The time comes back as rework. Next time I'd ask for a short design phase before build starts, and agree the MVP and acceptance criteria with the team first.
Test with athletes before launch, not only after. The soft launch is a good test, but it comes late. Next time I'd run five quick sessions on the join flow before launch, even with a rough prototype.
Plan around the summer. Holidays stalled the project, and restarting cost momentum. Next time I'd write decisions and handovers down before people leave, not after they return.