A workflow built for production, not for software teams
Tell the AI how your studio works in plain language and it proposes stages, approvals, dependencies and dates. Nothing takes effect until you approve it.
Stages that know the trade
Script, schedule, shoot day, rushes, first cut, internal review, client review, revisions, grade, sound and delivery. Each stage carries its owner and the approval needed to leave it.
Dependencies that prevent rework
Grading cannot start before the edit locks, and delivery cannot happen before the approval lands. When something slips, the system moves what depended on it and shows you what moved and why.
Automations in your own words
Write what should happen, for example when a client approves a final cut, close the project and send the invoice. The sentence compiles into rules, you get a dry run, and only then does it switch on.
Questions that keep coming up
- Do we have to configure everything up front
- No. Answer a few onboarding questions and you get a working template. Edit it whenever you like; a change applies only to new projects unless you ask otherwise.
- Can we run several kinds of production at once
- Yes. Each kind of work gets its own template: commercial, wedding, brand film, web series. A new project starts from the matching one.
- What happens when a client asks for a change after delivery
- A new revision round opens on the same project, counted. Once you pass the number of rounds you agreed, the system flags it so you can bill for the extra.
Start without a card
Fourteen days, everything switched on. Open a workspace, tell the AI how your studio works, invite a client to approve.