Product · Client proofing

Sign-off that never goes missing.

Client proofing that stops decisions disappearing into chat. Clients approve or request changes on the exact version – every transition recorded, so 'we never agreed' stops landing.

A real approval workflow

Draft to approved, on the record.

Decide

Clients approve or request changes – right on the version.

Each deliverable carries its own status. The assigned client signs off or asks for changes from the same screen they reviewed on.

  • Versioned status: draft, in review, approved, changes requested
  • Role-aware, only the assigned client can approve

Brand film – 90sv3

Final master · 4K ProRes

In reviewApproved

Prove

An append-only trail of every decision.

Who acted, what they did, when, and the note they left – against the exact version. History can't be quietly rewritten.

  • Immutable approval events for every transition
  • Change requests carry the context that prompted them
DECISION HISTORY Append-only
  • BG

    Bobby G. requested approval · v2

    3d ago
  • MC

    Mara Chen requested changes · v2

    “Trim the intro by 2s”

    2d ago
  • BG

    Bobby G. requested approval · v3

    1d ago
  • MC

    Mara Chen approved · v3

    “Perfect – ship it”

    2h ago

And the essentials

Nothing slips through

Surfaced where it matters

An attention pill counts what's awaiting a client decision, so nothing stalls because someone forgot to look.

Role-gated actions

Staff send work for review; clients approve or request changes. Everyone can only do what their role allows.

Approve, then ship

The moment a client approves, the status flips and the file is ready to send – same link, same place.

How it flows

Draft to approved, on the record

01

Send for review

Mark a deliverable version as in review and the assigned client is prompted to weigh in.

02

Client decides

They approve or request changes from the browser, with a note attached to the version.

03

It's logged for good

Every decision writes an immutable approval event you can point back to later.

When the client asks for changes

When a client requests changes, that decision applies to the version they reviewed. Upload the revised file to the same deliverable and it becomes the next version – v2 – starting as a draft only your team can see.

When v2 is ready, release it to client review. The client is notified that a new cut is ready, and it waits in their Review tab for a decision. They approve it or ask for another round, the same way they did with v1.

Nothing from the earlier round is overwritten. v1 keeps its changes-requested status and the note that came with it; v2 carries its own decision. The approval log is append-only, so the trail from the first request to the final sign-off reads in order, months later.

Now open. Founding studios keep the price they join at.

Folders, scopes, and sign-offbefore the next shoot.

Create my studio

Free to start · founding price locked · no card required

Not ready yet? Get product updates.