IRL Studio (From Personal Habit to Platform)

Original: 2020 | Updated:2026

TL;DR

Originally a self-initiated exercise that grew into a product. For 35 days I generated a brief and designed a landing page in under an hour, practice to stay sharp. From original to platform for other designers: a Figma plugin that generates the brief, locks the artefacts on the canvas, and enforces a 60-minute timer, paired with a companion web app for exposure, critique, reactions, and reflection.

Figma Plugin: irlstudioWeb App: irlstudio.us

Problem

Designers, if they practise at all, practise in unrealistic conditions: open-ended briefs, infinite time, no peer pressure, no critique loop. My own 35-day challenge sharpened my judgement faster than any portfolio piece - but it lived in my head, with no structure and no way to measure my work against anyone else's. The same gap scales across the industry: portfolios that don't translate to commercial work, vocabulary that buckles under stakeholder pressure, juniors who freeze at their first real constraint. The tools to fix this didn't exist when I started in 2020; now they do - so I built a forcing function with a feedback loop.

Solution

Two touchpoints, both live in production. The Figma plugin generates a brief - business name, hero image, brand palette - drops locked artefacts onto the canvas, and runs a 60-minute timer. Live at Figma.

The companion web app catches each submission and turns it into a public feed with critique, reactions, upvotes, and a reflection editor. Built on React, Neon Postgres, Clerk, and Vercel. Live at irlstudio.us.

Hardened before launch: a 1,500-brief bank that keeps runtime cost near zero, push notifications, search, and five layers of abuse/cost protection.

Results

2
Production surfaces shipped end-to-end (plugin + web app)
1,500
Pre-generated brief bank — unlimited variety at ≈$0 runtime cost
5
Abuse + cost-flood defence layers shipped before launch

Key Learnings

  • A personal habit is a product signal. The 35-day challenge wasn't a project - it was a behaviour I'd already adopted. Building for problems you've already felt is a good place to start - you scope better and ship faster.
  • Ship the constraint, not the tool. The value lives in the 60-minute timer and the locked artefacts. Every decision - no editing after submit, pre-baked briefs, variety of briefs, no timer extensions - compounds the constraint instead of softening it.
  • Harden before there's anything to harden against. Five layers of defence and a 1,500-row brief bank (~$1.50 once, ≈$0/click after) went in before the first user - less fast-paced strategy however, the cheapest time to fix abuse and runaway cost is when there's no traffic to break.