Back to all cases
Web service · Events · CRM

Startlek — a running-events platform

A web service where runners discover races and organizers publish and manage their events — built for Central & Eastern Europe.

This is a real, live product — not a concept. I own it end-to-end: UX/UI and the design system, the front-end (Next.js · TypeScript · Tailwind) and the Supabase back-end (Postgres · Auth · RLS · Edge Functions).

Role
Product Designer & Design Engineer
Design → Front-end → Back-end
Type
Web service + CRM
Timeline
2024 — present
Live
Startlek — running web service
01 — Context

One home for every start line.

Around 80% of organizers have no convenient place to publish and manage their sports events, and runners have to hunt for races across scattered, outdated resources. Startlek fixes both sides in one product: a modern events calendar for athletes and a full management toolkit — a small CRM — for organizers.

The regional focus is endurance sport across Ukraine, Poland and Romania, with a mobile-first, intuitive interface that people actually want to use.

02 — Challenge

Two audiences, opposite needs.

Discovery must stay effortless for runners while organizers get real depth.

01

Hard to find a start

Races are spread across many outdated sites; runners can't scan them in one place.

02

Painful to publish

Existing tools make even a single event slow to set up and manage.

03

High commission

Similar products take a large % per registration, so I had to design a leaner model.

04

One product, many roles

Runner, organizer and admin all live in the same system without noise.

03 — Architecture

Roles and flows, mapped before pixels.

Before UI, I mapped the whole service by role — visitor, participant, organizer and admin — and the key flows, like publishing an event. That structure kept a large product coherent as it grew.

Service by roleService structure by role
The web service structured by role.
Publish an eventEvent publication flow
Organizer navigationOrganizer navigation structure
The event-publication flow and organizer navigation.
04 — Discovery

A calendar you can scan in seconds.

The entry point is a modern calendar with filters and multiple view modes — list, calendar and map. Card previews carry just enough to decide: date, city, distances and price.

CalendarEvents calendar with filters
The events calendar — filters, view modes and card previews.
Calendar detailCalendar day view
Map viewMap view of events
Day view and a geographic map view — browse races the way you think.
05 — Event pages

Structure the event, serve both sides.

A predictable three-part page

Every event splits into Information (general info with the organizer's data block), Regulations (everything a participant should know) and Participants — plus a live chat. Users always know where to look.

Registration built in

Distances, add-ons, promo codes and payment live inside the event, so the path from "I want in" to "I'm registered" is short.

Event — InformationEvent information page
An event page — Information tab with the organizer's data block.
Event — mobileEvent page on mobile
Participants chatEvent participants chat
The event on mobile and the participants' chat.
RegistrationRegistration flow
CheckoutRegistration checkout
Registration and checkout — distances, add-ons and promo codes.
06 — Profiles

A public identity for people and clubs.

Organizers get a public organisation profile to present their brand and events; runners get a profile with their registrations, results and settings.

Organisation profilePublic organisation profile
Public organisation profile — brand, events and social proof.
Runner profileRunner profile
SettingsPersonal settings
The runner's profile and account settings.
07 — Organizer tools

The CRM that makes managing a race simple.

This is where Startlek goes beyond a directory. Organizers create an organisation, publish events and manage everything from one dashboard: event data, distances, participants, finances, promo codes, a participants' chat, an e-mail sender and results publishing.

Create organisationCreate organisation
Organisation dataOrganisation data
Setting up an organisation and its data.
Events dashboardOrganizer events dashboard
The organizer's events dashboard.
Event managementEvent management — data
Editing an event — data, dates, location, distances and pricing.
ParticipantsManage participants
FinancesEvent finances
Managing participants and event finances.
Distances & pricingDistances and pricing
Letter to participantsE-mail to participants
Distances & price rules, and the e-mail sender for participants.
08 — Admin

A control room for the whole platform.

The admin role oversees registrations, users, organisations and platform finances — with filtering and detail views for everything.

RegistrationsAdmin registrations
FiltersRegistration filters
Registrations with rich filtering.
UsersAdmin users
OrganisationsAdmin organisations
Users and organisations management.
FinancesPlatform finances
Platform-level finances.
09 — Design system

One system, every screen.

A single design system — tokens, components, typography and motion — powers the whole product, so features ship consistently and fast. Everything you see above is assembled from it.

Design systemStartlek design system
The Startlek design system — the source of truth for every screen.
10 — Outcome

A shipped product with real traction.

A fully working platform — everything an organizer needs to run an event, from publishing to payments-ready registration.

A seeded catalog of 10,000+ events aggregated across Ukraine, Poland, Romania and the Baltics — so it launched full, not empty.

SEO set up and indexed, with first organic users, plus 100+ invitations sent to organizers and clubs.

Payments (Stripe / Fondy) and a PL + UA beta are next on the roadmap.

Takeaway

Design that ships the whole product.

Owning design, front-end and back-end let me keep one coherent system across a large product — and take Startlek from research all the way to a real, live web service people can use today.