03 / Case Study
Content + community around product development
Fight Legends
Fight Legends was an early-stage Web3 game. The team had to make an unfinished product understandable, keep prospective players engaged between development milestones, and turn ongoing progress into content that could support community growth, awareness, and key-pass sales.

In-development character footage used as source material for recurring content.
Challenge
Fight Legends was an early-stage Web3 game. The team had to make an unfinished product understandable, keep prospective players engaged between development milestones, and turn ongoing progress into content that could support community growth, awareness, and key-pass sales.
My Role
I created and ran a recurring development show that turned weekly product progress into a steady stream of content. I owned the show concept, format, visual direction, editing, and social distribution, while also supporting Discord events, AMAs, contests, and paid promotion that kept the community active between major updates.
Progress Became Content
Source footage
ADevelopment progress

BProduct milestone

CCommunity-facing content
The System
Recurring content engine
Product development → community rhythmResults
Estimated production volume
EstimatesBuilt a recurring content and community rhythm around development updates, AMAs, contests, and game nights
Assets

Character creation
One narrative world, organized over time.
- AFagan City
- BThe Rifts
- CRift Wars
- DThe Agency
Lessons
- Human-led storytelling made the unfinished game feel active, understandable, and worth following. Familiar hosts gave the project continuity, while the recurring format turned scattered development progress into a system that grew attention and engagement.