Cut v1 in the browser
Team edits the sequence internally. Internal comments stay internal.
Use case
Sign-off without the ping-pong.
Clients get a link, not an account: comments land on the frame, threads carry decisions, versions keep the history — and the sign-off is exportable when legal asks.
The loop
Four steps. Zero email attachments.
Send the guest link
Expiry in 7 days, optional password, view counts on. Client opens on a phone.
Threads, not emails
Timecoded comments, replies, resolve. Ambiguity dies on contact with the timecode.
Sign off, on record
v2 goes side-by-side with v1. Approval lands in the audit trail — exportable.
What clients can — and can't — do.
- Can: watch, scrub, comment with timecodes, reply in threads, approve
- Can't: see internal team notes, download masters, keep access after expiry
- Every public viewer carries the PREVIEW watermark — feedback flows, copies don't
- Version stacks mean "which cut?" is never a question
- Sign-off exports as JSON/NDJSON for the agency's compliance folder
"Client rounds dropped from five to two — because every note has a timecode and every version has a verdict."
— agencies, on the guest-link loopIn memoriam: file naming
final_final_v3_REALLY.mp4 — 2019–2026.
Versions stack, compare side-by-side, approvals land on record. Survived by: guest links, timecoded threads, and an audit trail legal actually likes.
Send a link insteadSend a link.
Get sign-off.
Free plan includes guest review links. Pro adds master renders.