Products

Building RealFevr

RealFevr started with a fantasy-football idea I wanted to build. I invited the people who became CEO and CTO to join me, and we built the company from there. My focus was the product: turning the original idea into a game people could understand and enjoy, then evolving it so multiple leagues and different fantasy formats could live inside the same app.

Context

Fantasy football is a chain of connected decisions. How people enter a competition affects squad construction. Player prices affect which teams they can build. Scoring affects what they watch during a match. Different game formats attract different kinds of players.

The Problem

Make the rules work together, and make them understandable through the interface.

My Role

Owned

  • Original fantasy concept
  • Game / product rules
  • Core UX and flows
  • Wireframes
  • Product and workflow requirements
  • Testing and iteration

Worked with others

  • Visual / UI design
  • Engineering
  • Business development

Did not own

  • Final visual design
  • Software architecture

How It Worked

  1. 01League / format
  2. 02Entry + squad building
  3. 03Constraints + pricing
  4. 04Match data + scoring
  5. 05User decisions + competition
  6. 06Feedback + iteration

Key Decisions

  1. Getting people into the game

    Squad construction was also the entry flow. We iterated on how somebody moved from joining a competition to understanding the constraints and building a valid team without first having to learn the entire ruleset.

  2. Pricing as game design

    In Salary Cap, player prices were not just data. They shaped the game. The pricing structure had to create meaningful trade-offs and avoid everyone converging on the same obvious squad.

  3. Scoring people could follow

    We selected visible football statistics people could understand and follow while watching a match, then added another scoring layer without making outcomes feel arbitrary.

  4. Draft and Salary Cap were different products

    They attracted different users and different behaviours, so they needed different rules, flows and assumptions.

  5. Rules became interface behaviour

    Squad limits, formations, budgets, transfers, deadlines, captain choices and substitutions had to become understandable actions, states and feedback inside the product.

  6. One app, multiple leagues

    We changed RealFevr so multiple leagues could coexist inside the same app while preserving the rules, data and context belonging to each competition.

Inside the Work

  • Squad construction and entry flows
  • Salary Cap player pricing
  • Scoring rules
  • Draft and Salary Cap formats
  • Rules translated into interface states and actions
  • Multiple leagues inside one app

Result

  • 1M+ downloads.
  • Different fantasy formats and multiple leagues inside the same app.