EliteRank — CTO preview

EliteRank — CTO

Next.js 16ReactSupabaseStripe ConnectTypeScriptPlaywrightTwilio

Paid-voting competition platform with real money moving through it: Stripe Connect onboarding, prize pools with charity splits, platform fees, sales tax, payouts, and refund/dispute handling. The live app is a Vite SPA still shipping to real users while I rebuild it as six private Next.js 16 repositories behind a shared data spine — ~1,200 commits since March.

Competitions, Payments, and a Rebuild That Can't Break Production

EliteRank runs “most eligible”-style competitions: hosts create them, contestants get nominated or claim a profile, and the public votes with paid votes that fund prize pools. Money moves, so the interesting engineering is in the parts that must never be approximately right.

Money and correctness

  • Stripe Connect onboarding for hosts, with connected-account lookup and refund/dispute state tracked as first-class states rather than inferred
  • Prize pools with charity splits, platform fees, host tax handling, and payout eligibility
  • Idempotent vote writes and a vote ledger separated from denormalized counts, so a retried request can't inflate a leaderboard
  • Multi-currency (USD and CAD), double-vote days, timed vote windows, and lifetime vote buckets
  • Judge-weighted ranking alongside public votes, with rounds, review gates, and crowning

Rebuilding a live product without touching it

The legacy app is a Vite + React SPA that serves real users and real revenue today, and it keeps shipping. The replacement is six private repositories on Next.js 16 App Router with Server Actions—app, admin, marketing, registry, shared, and infrastructure—sharing one schema.

Running both at once is the actual risk, so the guardrails are mechanical rather than aspirational: a pre-tool-use hook blocks any write into the legacy checkout or any reference to its database from a v2 session, projects are identified by database ref rather than directory name (both are literally called “eliterank”), and a living feature map has to be updated in the same PR as the code. That last rule exists because duplicate implementations of one capability were this project's most expensive recurring bug—one of them had six separate writers.

My role: CTO and sole engineer across both the live product and the rebuild, plus the migration pipeline between them.

Live Preview
EliteRank — CTO | Guillermo Villegas | Guillermo Villegas