№ 01Case study · Competition platform · real-timeBuilt in 14 days · live in production

DriftSetka

From spreadsheets to a live tournament workflow. Fourteen days, end to end.

7
Events run on it
across three cities, organizer-led
150+
Real user accounts
no marketing budget, word-of-mouth
14d
Build cycle
solo, async, no calls
Visit live
driftsetka.ru/en
· press play to watch the workflow in production ·
recording · driftsetka / bracket.mp4
00:00 / 01:50
00:00 / 01:50
§ 01 · Problem
§ AContextWho this was for · what manual looked like
Who this was for

Tournament organizers running competitive motorsport events with dozens of participants, multiple judges, and a community of spectators who wanted to follow live — but had no tool that fit their workflow.

What manual looked like before

Spreadsheets and messenger groups. Brackets drawn on paper, scores tallied by hand, results photographed and posted in chats. No history, no leaderboard, no spectator view. Every event reinvented the same process from scratch.

§ BThe workflow that got built5 steps · end to end

Five steps. One platform running the entire tournament lifecycle.

  1. 01
    Registration

    Participants sign up with profile, car details, and event entry. Organizers see the roster grow in real-time without chasing DMs.

    intake
  2. 02
    Bracket generation

    Double-elimination brackets generated automatically — 64 matches across Winners and Losers sides. No paper, no spreadsheets, no manual seeding errors.

    64 matches
  3. 03
    Multi-judge scoring

    Three judges score each run independently. Base score, deductions, and conflict resolution all logged. Every decision visible to participants.

    real-time
  4. 04
    Live leaderboard

    Spectators and competitors see standings update as scores come in. No more refreshing a Telegram chat for results.

    spectator view
  5. 05
    Season aggregation

    Individual events roll up into championships. Player profiles accumulate history across stages — wins, average scores, garage of cars.

    championships
§ CResult · live in productionReal users · real data

Seven tournaments. Three cities. 150+ users. Zero marketing spend.

7
Tournaments run
organizers adopted it within weeks — and kept using it across seasons.
150+
User accounts
across three cities — Moscow, Yekaterinburg, Novosibirsk. Word-of-mouth only.
14 d
Solo build
one person, end to end. Scope locked day 0, shipped day 14.
production · sample rows
real, redacted
event
city
participants
status
Чемпионат Москвы #1
Moscow
36
completed
Лёгкий ЧМ #1
Moscow
35
completed
ATOM на ВДНХ
Moscow
31
completed
Уральский рассвет
Yekaterinburg
24
completed
Зимний этап
Novosibirsk
12
completed

Event rows from production DB. The platform aggregates these into season-long championships across three cities.

· want one like this? ·

Tell me about your workflow.
I'll respond within 24 hours.

Start the intake
← Back to all workNext case · FixFramer