Production hub

One home for the whole job.

A project in Studio Flows is not a folder of files. It is the production itself: the brief, the boards, the crew, the money and the delivery, organized into the phases a real job moves through.

No credit card needed. Set up in minutes.

The problem

The brief is in email, the boards are in Figma, the budget is a spreadsheet, and the approval is in a text message. You are the only person who knows where all of it is, and that knowledge does not scale past you.

01Shaped by the job

Tell it what kind of job, and it fits.

Start a project by picking what it is: live action, a commercial, AI video or CGI. The stages name themselves the way that kind of job runs, so an AI project moves from Concept to Generation rather than to a shoot, and the modules it needs come forward. Moving a job on is one click on the stage bar.

  • Four kinds of job

    Live action, commercial, AI video and CGI or VFX.

  • Stages in your words

    Pre-pro and Shoot for live action, Concept and Generation for AI.

  • The right modules forward

    An AI job gets the pipeline and elements; everything else stays reachable.

  • Add the client as you go

    A new client can be created from inside the new project form.

02The studio slate

Every live job on one timeline.

Switch the projects page from board or list to the slate: one lane per job, pre-production, shoot and post drawn across the weeks. Two shoots on the same day are flagged, and a job past its due date draws in red all the way to today, so the overrun is the first thing you see.

  • Board, list or slate

    The same projects, three ways, with archived jobs kept out of the way.

  • Shoot clashes

    Days carrying more than one shoot are marked.

  • Overdue runs to today

    A late job keeps growing until it is delivered.

  • 4, 6 or 12 weeks

    Page by the week so nothing shifts under you.

03Documents

Permits, insurance and specs, filed from the email.

The paperwork around a job arrives by email. File an attachment to the project's documents in one click and it keeps where it came from: who sent it, when, and in which thread. Open it to view it right there, and upload a new version when it is reissued.

  • One click from Gmail

    Add to documents, add to assets or log as a cost, from the same attachment.

  • Where it came from

    The sender, the date and the subject stay with the file.

  • Versions, not copies

    A reissued permit is v2 of the same document.

  • Page-one previews

    PDFs show their first page, so you can tell them apart at a glance.

04Project summary

Where does this job stand? Twenty seconds.

Ask for a summary and the hub reads the project and answers in one sentence, then sorts the rest into what is done, what is in progress, what you are waiting on, the next action and what to watch. Fold it down to that one sentence when you just want the headline.

  • One line first

    The status of the job, readable in a glance.

  • Sorted by what it means

    Done, in progress, waiting on, next action and watch, each marked.

  • Folds to the headline

    Collapsed, it still shows the first line.

  • Studio only

    The summary can mention money, so crew on the project do not see it.

05Client binder

Everything the client asked to see, and nothing else.

Bigger clients want the whole job in one place. Build a binder from what the project already has, the shot list, storyboards, moodboards, call sheets and more, where everything starts off and you tick what goes in. Internal notes are removed before it is shown, and it is only visible once you share it.

  • Off by default

    A call sheet added on Friday is not in Monday's binder unless you add it.

  • The real documents

    Each section is the same storyboard or shot list the client already approved.

  • Notes removed

    Hidden notes are left out of the page entirely, not just hidden.

  • Link and PDF

    Share one link, or print the same pages to PDF.

The difference

Modeled on production, not on software.

Most tools hand you generic boards and ask you to rebuild your craft inside them. This one already knows what a job is: it has a shoot date, a client, a review round and a margin, and every page assumes that.

  • The data spine runs Lead to Client to Project to Delivery, connected end to end
  • Nothing is retyped between modules: the shot list feeds the call sheet, the roster feeds the budget
  • Color is a status signal in chips, never a decorative wash
Pre-pro
Shoot
Post
Delivered
Brief
Review
Call sheet
Budget
A job's lifecycle stepper with the second stage active.

More the hub carries

The brief

Creative direction and attachments, on the job they direct.

Asset library

Every file with version history, nothing named FINAL_v2.

Documents

Permits, specs and insurance, with the email they arrived in.

Project calendar

Milestones and producer-entered dates, month and agenda.

KPI row

Days to shoot, days to due, open approvals, unread messages.

First-run checklist

Five real steps derived from real data, not a 'seen it' flag.

Guided tours

Orientation cards over the real UI, replayable from the menu.

Dual theme + paper

Light, dark, and a warm paper theme for long review sessions.

Soft archive

Nothing is ever hard-deleted; finished jobs leave your way, not the record.

Also here

Lives alongside it.

Each of these is a page inside the project, on the same spine, so nothing is retyped between them.

Brief

The creative direction, attached to the job it directs.

  • The brief and its attachments live on the project, not in a search
  • The first thing anyone joining the job reads
  • Its opening lines show on the hub card, so the job introduces itself

Assets & versions

The project's full library, where nothing is named FINAL_v2.

  • Upload from the device, or import from Drive and Figma
  • Every file keeps its version history, with the notes per version
  • Statuses move a file into the review cycle when it is ready

Documents

Permits, certificates and specs, filed with their provenance.

  • One click files a PDF straight out of the linked email
  • Each document remembers who sent it, when, and in which thread
  • Page-one previews, so a folder of PDFs reads at a glance

Project calendar

The job's own dates, month and agenda.

  • Pre-pro, shoot, review and delivery events, color coded
  • Shoot and due dates appear as milestones on their own
  • Multi-day events span the range, the way a shoot actually does

Run your next job in Studio Flows.

Your first project is free, with no card and no countdown.

Start free

No credit card needed. Set up in minutes.