StudioOS: Why We Built a Project Management Tool for Creative Studios (And What We Learned)

Every creative agency I've ever talked to uses either Asana, Monday.com, or — god help them — a combination of Trello boards and Google Sheets. None of these tools were built for how creative work actually happens.

The Creative Workflow Problem

Software development has a well-understood workflow: backlog → sprint → code → review → deploy. Linear, predictable, measurable.

Creative work is nothing like that.

A brand identity project goes through discovery → moodboarding → concepts → client feedback → revisions → more feedback → existential crisis → final revisions → delivery. There are branching revision trees, client approval gates, asset versioning nightmares, and the ever-present scope creep that turns a "simple logo refresh" into a full brand overhaul.

Asana doesn't understand revision rounds. Monday.com doesn't track asset versions. Trello... Trello is a wall of sticky notes pretending to be project management.

What StudioOS Does Differently

StudioOS is project management built specifically for creative studios — design agencies, video production houses, branding firms, and marketing teams.

### Project Workspaces, Not Task Lists

Every project gets a workspace with phases (Discovery, Concept, Production, Delivery). Within each phase, you track deliverables, not tasks. A deliverable might be "Homepage Hero Concept" — it has its own revision history, client feedback thread, and approval status.

### Revision Tracking

When a client says "I liked version 3 better," you can actually pull up version 3. Every deliverable tracks its revision tree — who made changes, what the client said, which version was approved. No more digging through email threads or Slack DMs.

### Client Portals

Clients get a view into their projects without seeing your internal chaos. They can approve deliverables, leave feedback on specific versions, and see timelines — all without a login to your project management tool.

### Time & Budget

Creative projects have budgets, and they almost always go over. StudioOS tracks time against budget in real-time, so the project lead can see "we've used 80% of budget and we're only 60% through production" before it becomes a crisis.

The Build

StudioOS runs on our standard stack: - Next.js with magic-link authentication - Prisma + Postgres for data - Real-time updates via polling (WebSockets planned) - Stripe billing at $79/mo per studio

The magic-link auth was a deliberate choice. Creative teams hate passwords. They hate SSO setup. They want to click a link and get in. Magic links are dead simple — enter email, click the link, you're in.

What We Learned

1. Creative people are opinionated about UI. When your users are designers, your UI better be good. We went through 3 design iterations before the visual language felt right.

2. Approval workflows are the killer feature. The #1 pain point isn't "tracking tasks." It's "where is the client feedback and which version did they approve?" Every conversation about StudioOS ends up here.

3. Integrations matter more than features. Studios live in Figma, Google Drive, and Dropbox. If StudioOS can't connect to those, it's just another silo. This is our top priority for v2.

Current Status

StudioOS is live with magic-link login, project workspaces, and Stripe billing at $79/mo. We're in early validation — talking to studios, getting feedback, iterating.

The creative project management space is crowded but underserved. Every tool tries to be everything for everyone. We're trying to be the one tool that actually understands how creative work flows.