Use case · agencies and freelancers
Your client reviews the build without a repository, a branch or a call. Share a link to follow the review, invite them to leave notes — and every note arrives with the element, the page and a screenshot attached.
Let them point at the page itself.
A read-only link that opens in any browser, on any device, with nothing installed and no account. It shows every note with its screenshot and the page it belongs to.
Invite them and they get a free account and the extension — then they click the thing that's wrong and type a sentence. No vocabulary to learn, no form to fill in, and nothing about branches or selectors.
Each note carries the page, the element and a screenshot. What used to arrive as “fix the header” is now a specific element on a specific page at a specific width.
The fix comes back on the same note and the status changes where it was left. Approval stops being an email and becomes a list both sides can see.
The person approving the work has no repository, no branch and no dev server — and shouldn't need any of them. What they can do is look at the page, and it turns out that's enough to produce a task your agent can act on.
Claude Code · via MCP: “Moved the enquiry form above the fold on /contact and made the submit button full width on mobile. Commit 7ac0f1.”
Open it the way a client would: nothing installed, no account, no login. Every pin, its screenshot and its current status — and no way to change any of it.
Read-only by construction: the page has no form of any kind.
Client sign-off is the round where the person paying for the work looks at what was built and says what still has to change before it goes live. In software the same round is usually called user acceptance testing — a stricter name for the same conversation.
It's the round most likely to go wrong, because it's the only one run by someone outside the team. They can't check out a branch, can't open DevTools, and are often looking at a phone rather than a desktop. So feedback arrives in whatever form is available — a screenshot, a phone call, a list written from memory — and the next day goes to working out what each item meant.
The fix is to let them comment where the problem is. Handoff becomes the review surface: a link that needs no account to follow, notes attached to real elements with a screenshot, and a shared list where both sides can see what's been done. The agent that changes the code reads the same notes over MCP.
Not to follow the review — a link opens in any browser with nothing installed. To leave notes that reach your board, yes: a free account through your invite, plus the extension. Still no repository, no branch and no onboarding call.
Yes. They review the page in their own browser, so whatever access they already have is enough — no separate credentials to hand out.
Yes — invited reviewers share one list, so the same thing doesn't get raised twice.
Yes. Access is revocable, so a link shared for one round doesn't stay open forever.
They can follow the review on a phone, but leaving a note needs a desktop browser. Either they capture it from a laptop, or you pin it on their behalf — either way the viewport is recorded with the note.