All cases
Internal ToolVideo coming soon
Showcase — Creative Asset Library
Internal searchable database of every creative the studio has ever shipped — tagged by mechanic, author, producer, and date. Designers stop rebuilding work that already exists.
PythonDjangoReactPostgreSQL
The problem
A studio with a dozen designers accumulates thousands of creatives on Google Drive. There's no way to search by tag, mechanic, author, or producer — you have to remember who made what and when. So new creatives keep duplicating work that already exists.
Before / After
What changed
Before
- Thousands of creatives scattered across Google Drive folders
- No search by tag, mechanic, author, or producer
- Designers rebuild animations that already exist in the company
- Producers rely on memory to know who made what
After
- Every creative indexed in one searchable database
- Filter by mechanic (Match-3, Merge), author, producer, date
- Designer finds a close match → reuses the framework, swaps assets
- Producers see the full studio history in seconds
Results
Numbers that matter
36h → 5h
Per reused creative
2 / mo
People finding reuse wins
x7
Faster than rebuilding
Cost of inaction
Every month without this, the team repays 60-80 hours of animation work that already exists somewhere on Google Drive. Same creatives, built twice, paid twice.
Tech stack
PythonDjangoReactPostgreSQL