Skip to content

The client portal for creative review

Every approval, with a name on it.

Nod is where the work goes out and the decision comes back. Notes land on the frame they are about. An approval carries who gave it and when. Nothing important lives in a mailbox.

Sign in

Invite your clients in a minute. No card, and nothing for them to install.

The Nod home queue at 1440 by 900, showing eight deliverables waiting on the agency with the client, the review step and how long each has been waiting.

The problem

Approvals are not slow. They are scattered.

Nobody is dragging their feet. The decision is just spread across four places, and none of them remembers it.

  • How it goes now

    Notes arrive in a chat thread and scroll away by Thursday.

    How it goes in Nod

    Every note is pinned to the asset, and on video to the exact second.

  • How it goes now

    Four files with FINAL in the name and nobody sure which is live.

    How it goes in Nod

    Each upload is a version with its own history. The current cut is obvious.

  • How it goes now

    A yes on a call, and then nothing that says who gave it.

    How it goes in Nod

    One click to approve or request changes, recorded against that version.

  • How it goes now

    Clients handed a tool built for editors and asked to work it out.

    How it goes in Nod

    A portal with nothing to learn before they can review, in their own language.

  • How it goes now

    A dispute six months later, and no record either way.

    How it goes in Nod

    Roles, per project access, and an append only trail of every decision.

Where it lives now

Right now an approval lives in four apps.

The feedback is in chat, the files are in a drive, the status is in a sheet, and the yes was on a call. Here is each one, and where it lands instead.

The chat thread

How it goes now

Client group
the logo is wrong near the endany updates?

Which end? Which cut? By Thursday the note has scrolled away.

In Nod

Nod
0:42The logo is wrong here.

Pinned to the second it is about, on the version it is about.

The inbox

How it goes now

Inbox

Re: Re: Fwd: launch film

launch_film_final_v3.mp4
launch_film_final_v3 (1).mp4

Two attachments, neither current, and a subject line nobody can search.

In Nod

Nod
launch_film.mp4v3, current

One link, and it is always the latest cut.

The shared drive

How it goes now

Shared drive
launch_film_FINAL.mp4
launch_film_USE_THIS.mp4
launch_film_final_v2.mp4

Three files. One is live. Nobody agrees which.

In Nod

Nod
v3
v2
v1

Versions stacked, newest on top, history intact.

The call

How it goes now

Tuesday, 15:00
Looks good, ship it

A yes with no name on it, and nothing to point at later.

In Nod

Nod
Approved by the client12 July, 16:04

A dated approval, on the version it approved.

This is the thing you were assembling by hand.

Open the project and all four are already answered, in one place, on your own brand.

Nod
launch_film.mp4v3, current
v3
v2
v1
0:42The logo is wrong here.
Approved by the client12 July, 16:04

How it works

From upload to sign off in three steps

No accounts for your client to create, no reply all, and nothing to install. The work, the feedback, and a clear yes.

1

Upload the cut, invite the client

Drop in a version and send one link. Each upload keeps its own history, so nothing is overwritten and nothing is lost.

VersionedWatermark optional
v3
v2
v1
layla@lumen.example invited
2

They review on the work itself

Your client comments on the asset rather than about it. On video every note carries the timecode it was left at.

In contextVideo timecodes
0:42The logo is wrong here.
1:18The end card holds too long.
3

One click, and it is on the record

Approve or request changes on the current version. The decision carries who made it and when, and it cannot be quietly edited afterwards.

RecordedPer version
Decided onv3
Approved by the client12 July, 16:04Request changes

What is inside

Everything a review needs, and nothing your client has to learn.

The parts that make an approval worth having later: who saw what, which version, and when they said yes.

Notes on the frame they are about

On video every comment carries its timecode. No more the bit near the end.

A version history nobody can rewrite

Every upload is appended, never overwritten, and the current cut is always obvious.

Gates, in the order you work

Internal first, then the client, then the owner. Each one knows whose move it is.

Access per project, revoked in a click

Give a client one project. They see that project and nothing else in the workspace.

Watermarked delivery

A client download carries your agency name across it. Your originals are never touched.

A trail you can point at

Every decision, access change and download lands in a log that only appends.

Beyond review

Where the whole client relationship lives

Not only where work gets approved. Contracts, invoices, retainers and scope, on your brand, in the same place you sent the work.

One queue, not four inboxes

Everything waiting on you, from every project, in the order it went quiet.

A gate is a decision, not a status

Work moves when somebody named decides it does, and the record says who.

The record outlives the project

Versions, notes, approvals and the contract they sit under, kept together.

Contracts, invoices, retainers, scope baselines, change requests and acceptance windows are all in this build.

MCP friendly

Your assistant can work in here. It still cannot approve anything.

Nod speaks the Model Context Protocol, so Claude, ChatGPT, Cursor, VS Code and Zed can read your projects, versions, comments and decisions and draft the reply. Connecting one takes a single line.

You

What is still waiting on the client, and how long has it been sitting?

N

Read from your workspace

  • nod_docket
  • nod_project_assets
  • nod_asset_versions
  • Reel 09, hook variationsv36d
  • Ramadan bumper, 15sv23d
  • Key visual, final roundv51d

Three are with the client. The oldest has been six days at sign-off. Want me to draft the chase?

It read the workspace and wrote a draft. It cannot approve, reject or sign, it cannot fetch a file, and it sees exactly what the person who connected it sees.

You decide what it may touch

Four permissions, ticked one at a time when you approve a connection. Read is the only one on by default.

  • Read projects, assets, comments and decisionsnod.readOn
  • Read throughput, cycle time and gate ageingnod.analyticsOff
  • Leave a comment as younod.commentOff
  • Start an export and read its statusnod.exportOff
  • Draft projects, scope, invoices, contracts and formsnod.writeOff
  • Send what it drafted, once you allow itnod.sendOff

Works in

  • Claude Code
  • Claude Desktop
  • ChatGPT
  • Cursor
  • VS Code
  • Zed

Trust

Your clients' unreleased work stays theirs.

The database decides who may see each row on every request, so access holds even outside the app.

Checked in the database

Every query asks who is allowed to see each row, so access holds even outside the app.

Invite only

No open sign up. People join by invitation to their own address, and links expire.

Watermarked

A client download carries your agency name across it. Your originals are never touched.

An append only trail

Decisions, access changes and downloads land in a log that adds and never edits.

Arabic, properly

Right to left, not a mirror image.

Every screen is built twice over: the layout flips, the typeface changes, the line height opens up, and numbers stay Western so an invoice total reads the same to everyone in the thread.

The same Nod home queue rendered in Arabic, right to left.

Pricing

One price a month, and the limits are written down.

Every plan carries the whole product: the review stage, the approval ladder, contracts, invoices, retainers and both languages. What changes is how much of it you need.

Solo

$49.00 a month

Projects
5
Client companies
5
Storage
64 GB
Your own domain
Not included

Startup

$99.00 a month

Projects
50
Client companies
15
Storage
256 GB
Your own domain
Not included

Enterprise

$199.00 a month

Projects
Unlimited
Client companies
45
Storage
1 TB
Your own domain
Included

Prices are in USD and exclude tax. Every plan is billed monthly and can be changed or cancelled from your own billing screen.

In every plan

  • Client review, comments and one click approvals
  • Comments pinned to the video timecode
  • Versions and full version history
  • Approval gates, owners and delegation
  • Contracts, estimates and e signatures
  • Invoices, estimates and tax profiles
  • Retainers with drawdown and rollover
  • Scope baselines and change requests
  • Client intake forms with branching
  • Your logo, your colour, your domain
  • Arabic and English, with real RTL
  • An AI connector your assistant can read

Send the work. Get a decision.

Sign in to your agency's workspace.

Sign in

Invite your clients in a minute. No card, and nothing for them to install.