Studio home
BuiltOpens on what's in flight, what ships next, and what's under pressure — a per-project score you can override by hand.
A creative operating system
The kitchen before the kitchen.
One place to brief, research, direct, schedule, produce and invoice a creative project — instead of twelve apps that never speak to each other.
19 slides · arrow keys to move · about five minutes.
Slide 04 · Structure
Every project walks the same five stages.
A YouTube video, a brand identity and a comic book share one spine. They only branch at Stage 4.
- 5Stages every project walks, whatever the medium
- 7Mediums, each rebuilding Production with its own tools
- 26Named tools placed across those mediums — built or waiting
- 0Client logins to manage, ever
01 The problem
Brain fog is a tooling problem.
Every restart is a redesign of the puzzle instead of placing the pieces. The Prep Room ships with the puzzle already laid out.
Before
- Brief in Notion, references in Milanote, script in Docs
- Client name typed three times, wrong once
- The "never do this" from round one forgotten by round three
- Deadlines living in a calendar that knows nothing about the work
- A client deck built from scratch on a Friday night
- Invoice written in a fourth app with no memory of the package
After
- One project record, five stages, one screen
- Client entered once, flowing to every document
- Do-nots pinned to the screen for every stage that follows
- Every deadline on one calendar and one timeline, automatically
- Sample Platter turns thinking into a PDF deck
- Contract and invoice generated from the brief you already wrote
02 How it works
Three decisions, then the workspace is already correct.
Pick the medium
Brand identity, short film, photo shoot, comic book. The choice loads Stage 4 with the right tool slots before you type anything.
Brief it once
Client, feeling, audience, deliverables, deadline. That record becomes the contract header, the invoice, the email draft and the client's share page.
Walk the spine
Close each stage with a report. Its do-nots merge into a project-level list that stays visible for everything that comes after.
Desirables & BriefingThe first conversation, captured properly.
ResearchField notes, references, links, attachments.
Visual DirectionMood board and tone agreed before work starts.
ProductionThe only stage that branches by medium.
Results & ReflectionDeliverable, revisions, invoice, what worked.
03 The surfaces
Everything within reach. Nothing in the way.
Brainstorm canvas
BuiltSticky notes, a mind map and a free-writing pad, opened over any stage and saved against the project — not in another app.
Sample Platter
BuiltSend any note, node or mood-board image to a running collection, arrange it into slide groups, export a client PDF.
Client share page
BuiltA read-only link showing only the fields you switch on. No login, no seat, no half-finished thinking on display.
Calendar & unified inbox
BuiltDeadlines, stage dates and tool due-dates land on a month or week view — with Gmail, Discord and WhatsApp threads in the same rail.
Project timeline
ProposedFive stages and every tool deadline on one ruler with today drawn through them. The data exists — stage dates, deadlines, time entries; the view is next.
Document generation
BuiltInvoices that number and split themselves, per-medium contracts assembled at the tier you sold, all auto-filled from the brief.
Email templates
BuiltKickoff, invoice, revision and chase — tokenised and written in a real voice, not CRM filler.
Script & Shot List
BuiltSegments that roll up into a live runtime; shots that inherit the project's constraints instead of ignoring them.
Tasks by project
BuiltA week view that knows which project each task belongs to, and flags what's late before the client does.
Twenty-one waiting slots
SlotStoryboard, call sheet, character web, budget tracker. Not built yet — but already named, deadlined and placed in the plan.
04 The principle
A restaurant prepares your whole dish in one kitchen. Why wouldn't we.
From VISION.md — the document the app is built against
Execution still happens in Affinity, DaVinci, Premiere — wherever the medium lives. This is the room before that one.
Nothing great gets cooked without prep. The stage system is that prep, made structural: the same five steps whatever you're making, branching only where the craft actually differs.
05 Questions
The honest answers.
Is this a design tool?
No. Nothing is finished here. It's where the work is planned, briefed, researched and organised — the finishing happens in Affinity, DaVinci, Premiere or wherever the medium lives.
Do clients get accounts?
Never. Clients receive exports and a read-only share link that shows only the fields you enable. There are no client-facing login flows and there won't be.
What happens if a tool I need isn't built?
Its slot still exists — named, deadlined and sitting in the right place in Stage 4. The structure is always complete; only the content matures. Twenty-one slots are currently placeholders.
Is it multi-user?
No. It's built for a single practice — one designer and director, their projects, their clients, their rates. That constraint is why it can be this opinionated.
Where does the data live?
In the browser today, persisted locally. A real backend is on the roadmap; the deck's closing slide says exactly what's next.
The one principle
Kill brain fog. One place. No switching.
Nineteen slides on how the five stages, seven mediums and every generated document fit together — with the studio's own mock data throughout.
Arrow keys to move · Esc for all slides.