How Previsto works

Previsto is an AI director's studio: it turns a script into shot lists, storyboards, and a shot-ready plan — while every creative decision stays with you. This page is the five-minute map.

The gate model

Codex (the production engine) does the work; you hold the gates. Nothing creative advances without your approval: the shot list, the pilot panel plan, the prompt packets, and every generation wave stop and wait for you. Approve in the review panel or just say it in chat ("approve the shot list") — both work.

The workflow

1 · Intake — drop a script (PDF works) with a line like "New production: Title — run intake." Codex reads it and builds story units and a shot list, then stops at your first gate.
2 · References — drag in character, vehicle, and location images. They bind to continuity tags (like @char_name_ref) that lock identity across every frame.
3 · Panel plan & prompts — Codex proposes the pilot shots and exact generation prompts. You approve before anything renders.
4 · Generation — panels render in waves with live progress; a visual QA pass checks each frame and retries misses once, then stages a review board for your verdict.
5 · Board & export — the storyboard reads in story order; export a printable board (Open in new tab → Print → Save as PDF) or download any panel.

The screen

Chat (left) — the interface. Speak naturally; decisions you owe are always written out in full. The documents are the record, one click away.
Workbench (right) — AUTO follows the work live; BOARD, REFS, MEDIA, and DOCS are your production surfaces. A gold NEEDS REVIEW chip appears whenever something waits on you.
Render credits — the meter in the left rail shows your monthly generation budget. Rendering pauses honestly at the cap; ask your admin to raise it.

Good to know

Renders take about two minutes per frame — the stage card shows "Rendering 2 of 8" while it works.
Your content is yours; the platform is ours. See the Terms and Privacy Policy.
Questions: contact@previsto.studio.