AI production assistant
It proposes. You decide.
Runner reads the studio's real data to answer what is stalled, who owes what, and where a job stands. When it wants to change anything, it writes a card listing every value and waits for you to press Create.
No credit card needed. Set up in minutes.
The problem
AI assistants fail producers in one of two ways: they hallucinate answers, or they take actions nobody asked for. A production is a chain of commitments; a tool that invents or improvises inside it is worse than no tool.
Answers from live data
Not a chatbot with opinions: every answer is read out of the same tables the pages render.
- 'What is still waiting on a client?', answered by name
- 'Which vendors are we late paying?', with the amounts
- Questions nobody wrote a report for, answered anyway
- Opens over whatever you are reading, scoped to the project you are on
Proposes, never commits
The contract is the feature: the model assists, the human commits, every time.
- Every change is a card listing every value that would be saved
- Nothing writes until you press Create, and Cancel costs nothing
- Confirming runs the same actions the buttons run, with the same permissions
- No deletes, no sends without a named list of who receives
AI through the whole app
The same assist-and-confirm contract shows up wherever it saves real time.
- An emailed invoice read into a cost draft you check before saving
- A received SOW read into deliverables, proposed as a checklist
- Project summaries and drafted client updates, always yours to edit
- The Polish button in every composer, with undo to your exact words
Or bring your own Claude or ChatGPT
Connect the assistant you already pay for, and talk to your studio from the chat where the brief and the client's email already are.
- A private link from Settings adds Studio Flows as a connector in Claude or ChatGPT
- Ask where a job stands, what is still owed, or which client is slow to sign off
- It can build moodboards and storyboards, with images it generated or found
- It only ever adds, never changes or deletes, and the link turns off in one press
The difference
The card is the contract.
Runner cannot write to your studio. It can only propose, and a proposal is a card you can read in two seconds: every field, every value, Create or Cancel. Confirming runs the exact same code your own buttons run, with the same permissions. There is no second, looser path into your data.
- Zero unattended writes, by architecture rather than by promise
- Every answer traceable to the page that shows the same number
- Boring by design, which is what you want near your money
Proposed cost · nothing saved yet
More about how it behaves
Scoped conversations
Threads belong to a project or the studio, and stale ones retire themselves.
Suggested questions
Seeded from real state: an overdue vendor by name, a stalled job by name.
Dictation
The browser's own speech input; no audio ever leaves your machine.
Private threads
Your conversation log is yours; colleagues cannot read it.
Credential firewall
Tokens, share links and signatures are unreadable to it by construction.
Sensible limits
Burst and daily caps, so a held-down Enter key cannot run up a bill.
Works with
Budget & costs
Bid against actual, line by line
See how it worksWorks with
Production hub
The whole job on one page
See how it worksThe whole toolkit
You just read about one of seventeen.
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.