Project contacts
One roster per job.
Crew, talent, extras, clients and vendors on one per-job roster, with the details each kind of person actually needs: positions and rates for crew, wardrobe and dietary for talent, and files for everyone.
No credit card needed. Set up in minutes.

The problem
The crew list is a spreadsheet, the talent's measurements are in a text thread with wardrobe, and the W-9 is somewhere in email. Every department is asking you, because you are the only index.
A roster with folders
One list per job, organized the way a call sheet thinks: Crew, Talent, Extras, Clients, Vendors, each tab counted.
- Positions from real production vocabulary, seeded per category, free text welcome
- Day rates on crew, visible to the studio and never to the crew themselves
- Pull people in from the client's contact list without retyping
- Vendors get their own folder: CGI houses, color, sound, rentals
Talent is not a name and a number
An actor's record holds what the departments actually come asking for.
- Headshot, billing name, representation and agent contact
- Wardrobe measurements as real fields, sized how wardrobe writes them
- Dietary notes with allergies first, because a truncated line should lead with the hospital risk
- Files on the person: W-9s, releases, agreements
The roster feeds everything
Enter a person once and they follow the job around.
- Call sheet recipients check straight off the roster
- The budget's vendor picker knows the agreed day rate and does the math against the invoice
- Crew meal rounds read the roster, and dietary is on record
- Invite crew into the job itself: they see this project and nothing else
The difference
Everyone sees exactly enough.
Crew need the call sheet and the storyboard. Wardrobe needs the measurements. Nobody outside the studio needs the rates, and here they cannot see them: money lives in tables the database itself refuses to serve to project collaborators. That is enforced access, not a hidden column.
- Invite a freelancer to one job in one click; the rest of the studio does not exist for them
- Rates, budgets and agreements are structurally invisible to non-staff
- The same roster serves the call sheet, the budget and the meal run, typed once
Amara Khan
Lead talent · CAA
More it holds
Project-only access
A DP or editor sees their job, never your studio, your clients, or your money.
Reviewer role
View-and-comment access for people who should not be able to edit.
Gear alongside crew
The kit list with day rates, tracked next to the people running it.
Props with sign-off
Sourced options per prop, and the client picks through the review portal.
Category colors
Cards carry their folder's color, so a glance sorts the roster.
Rate protection by design
Money fields live in studio-only tables, enforced at the database, not the UI.
Also here
Lives alongside it.
Each of these is a page inside the project, on the same spine, so nothing is retyped between them.
People & access
Studio members, project collaborators, and review-only access.
- Invite a freelancer to one job, not the whole studio
- Collaborators never see rates, budgets, or other clients
- A reviewer tier that can comment and approve but not edit
Works with
Call sheets
Sent, seen, confirmed, chased
See how it worksWorks with
Budget & costs
Bid against actual, line by line
See how it worksThe whole toolkit
You just read about one of thirteen.
The rest is already in the box: every plan carries the whole toolkit, and the tiers buy room, never permission. This is the part a point solution cannot say.
Run your next job in Studio Flows.
Your first project is free, with no card and no countdown.
No credit card needed. Set up in minutes.