Does my client need an account?

No. They open the link, type a display name, and comment. No email, no verification, no signup, nothing to install for the review-link flow. Their comments stay editable by them because ownership is proven by a token stored in their browser.

Can I stop one client from seeing another client's work?

Yes. Each project has its own review link and a client only ever has the link you sent. Inside your team, admins see everything while editors are assigned to specific projects, so someone brought in for one build does not see the rest of your portfolio.

Can I put my own branding on it?

Partly, and not fully yet. The embeddable widget carries a Powered by Writhink badge. The review link itself is a Writhink URL either way.

What if the client's site is not public yet?

Use the Chrome extension. It reaches what a proxy cannot: staging behind basic auth, a logged-in admin area, a builder preview, a local development URL. Comments land in the same project, with the same pin data and screenshots. The reviewer needs Chrome with the extension installed, which suits your team and technical clients more than a marketing manager — for everyone else, send the link.

Can several people on the client's side comment on the same review?

Yes. Each person gives their own display name and every comment is attributed to it. With live collaboration turned on for the project you can see who is in the review, follow one person's cursor, and watch pins appear as they are placed.

Does it stop a client sending feedback forever?

No, and it does not pretend to. There is no round counter, no lock, no approval gate. What you get is a dated, statused list of what was raised and when — the evidence you need when a request arrives after the round closed. Enforcing the round is still your contract.

For agencies

Run revisions for every client project from one place

Your client opens a link, clicks the exact element they want changed, and types. No account, nothing to install, no "the button under the second photo". Every project you run keeps its comments in one place, and each round ends as one written prompt your developer or your AI coding assistant can build from.

Set up your first client project

No credit card. Your client doesn’t need an account.

Count what a revision round actually costs you

Take the last project that ran over. The build was probably close to the estimate. What ran over was everything after you sent the staging link: a voice note on Friday evening, a screenshot pasted into an email, a document with forty lines in it, three of which say the spacing looks weird and none of which say on which page or at which screen width.

The billable work in that round is small. The unbillable work wrapped around it is not. Someone reassembles the sentences into a list. Someone asks what line 17 means and waits two days. Someone implements a guess, the client says that is not what I meant, and you pay for the change twice. Then three of those items reappear in round three, because nobody confirmed they were done. Four hours of that, at whatever your studio bills, is a bigger number than most of the tools you are comparing.

None of it is a client problem. Describing an interface in writing is a professional skill, and your client is a dentist, a founder, a marketing manager. The fix is not asking them to write better notes; it is not asking them to write notes at all. Someone who types "make it pop" has still told you exactly which element they mean, because they clicked it.

The same feedback, before and after

Four lines from a revision list of the usual shape, and what changes when the client points instead of writes.

What lands in your inbox today	What you do with it	What a pinned comment hands you
"The header looks broken on my phone"	Ask which page, resize your own browser, take three screenshots and hope one matches.	The page, the element, the viewport size, the device type, and a screenshot of what they saw.
"Can we make the button stand out more"	Ask which button. There are nine on that page.	The exact button, on the exact page, with the pin sitting on it.
"Same problem as the other page"	Guess which other page, then check four of them.	Two pins on two pages, merged into one item when you generate the prompt.
"Did you fix the thing from last time?"	Search the email thread. Find two threads.	The comment, its status, and your reply, all still on the pin.

Writhink records the device type — desktop, tablet or mobile — and the viewport size. It does not record the operating system, the browser or the handset model, so "broken on my phone" narrows to a width and a device class, not to a specific handset.

Three ways feedback reaches you

Which one you use depends on where the work lives, not on what the client is willing to learn.

Channel	Use it for	What the client installs
Review link	A staging or live site with a public URL. The page loads through the Writhink proxy, so comments pin to real elements.	Nothing. A display name is all they type.
Chrome extension	Anything a proxy cannot load: a page behind a login, an admin area, a builder preview, a staging URL on your own machine.	The extension, from the Chrome Web Store. Chrome only — no Firefox, Safari or Edge build exists.
Embeddable widget	A permanent channel on a client's live site after launch, so small requests land in the project instead of your inbox.	Nothing. You add one script tag once.

The widget carries a Powered by Writhink badge.

One revision round, end to end

The whole loop for a client who has never seen the tool. The constraint throughout: the moment a client has to learn something, they go back to email.

Step 1
Create the project, send the link
Add the staging URL, copy the review link, paste it into the email you were sending anyway. Two sentences of instruction is the maximum: click the thing you want changed, type what you want. If the page is behind a login, use the Chrome extension instead — comments land in the same project either way.
Step 2
The client comments without an account
They type a display name and start clicking. Each comment stores the element, its position, the page URL, the viewport size and the device type, plus an automatic screenshot of the pinned spot. Up to five files per comment at 10 MB each, and they can edit or delete their own.
Step 3
Say when the round closes
Writhink makes the list legible; it will not stop a client adding a forty-first comment three weeks later. No round counter, no lock. Scope is still your contract — the tool only makes it obvious what was and was not in the round.
Step 4
Answer on the pin, triage the list
Replies are public to the client, so the exchange stays attached to the thing being discussed. Every comment carries one of four statuses — open, in progress, in review, resolved — and your team works the same list, with email digests instead of six review links to refresh.
Step 5
Generate the prompt
Writhink rewrites the vague comments clearly without inventing requests, merges duplicates, groups by page and element, keeps the pin data and screenshot on each item, and sets priorities. Anything still ambiguous is flagged "(unclear — ask the client)" rather than guessed at, and the prompt ends by drafting the questions back to the client for you.
Step 6
Hand it to whoever implements
A developer, a contractor or an AI assistant works from one document instead of a thread. As items ship you move them to in review, the client sees the reply on their own pin, and the round closes without a status call.

Running five clients at the same time

An agency does not have a feedback problem on one project. It has the same problem on every project, all quarter.

One organization, many projects. Each has its own review link, comments and history, and a client only ever holds the link you sent them.
Two roles: admins run the organization and see everything, editors are assigned to specific projects — so a freelancer brought in for one build does not see the other four clients.
Nobody is invited to give a client access and nobody is removed to take it away. Access is the link.
Beyond websites: PDFs reviewed page by page, and image sets reviewed in the browser the same way, with pins and comments on both.
Download the round as a Markdown prompt when a client wants it in their own system, or when you close a project out.
No client-facing dashboard. Clients see the review you gave them, not a portal across everything you do for them.

If your agency builds with AI

Plenty of studios now ship the first version out of an AI builder, or write most of the code with an assistant. The bottleneck moves: making the change is fast, describing it accurately is slow. Raw client feedback is close to the worst possible input for a model — vague, duplicated, stripped of the context of what the person was looking at. That is the gap the generated prompt fills. For builders with no MCP client, such as Lovable, Bolt, v0 or Replit, you paste it into the chat box and each item arrives with its page, element and screenshot attached.

In an MCP-capable client you can skip the copying. Connect the Writhink server with `claude mcp add --transport http writhink https://mcp.writhink.com/mcp` and Claude Code, Cursor or Claude Desktop can work the round where the code is: pull the client's comments with their pin context intact, push each item along the four statuses as it ships, and post the answer the client reads on their own pin. The surface is deliberately narrow and it stops at Writhink — it never reaches your repository, and a session opened for one client has no route into another client's projects. It signs in as you, so it sees what you see; the tool-by-tool reference is on /visual-feedback-for-ai-agents.

Where Writhink fits, and where something else is the right tool

Reach for Writhink when

Your client is not technical and will never log into a project tool, however good it is.
The feedback is about how a page looks: this element, this copy, this spacing, this image.
You want the round as one implementable document instead of forty notifications.
The site is on staging, behind a login, or live and you want a permanent channel on it.
Whoever implements is an AI assistant that needs context it cannot see for itself.

Use a bug tracker or a PM tool when

You need sprints, dependencies, estimates or a roadmap. Writhink has no timeline view.
You need issues to appear in Jira, Linear, GitHub or Trello on their own. No native integration exists; you export, you paste, or an MCP agent files them.
You are tracking engineering bugs. Writhink captures page, element, viewport and device type — not console logs, network traces or session replay.
You want the tool to track hours or raise the invoice. It does neither.

Read this before you standardize your studio on it

There are no native integrations with anything. Not Jira, not Linear, not Slack, not Trello, not Asana, not GitHub, and no plugin, app or connector for Webflow, WordPress, Shopify or Framer. Feedback leaves two ways: the generated prompt, which you copy or download as a .md, and the MCP server. If your operations depend on tickets appearing in a tracker with no human in the loop, that is a real reason to look elsewhere. The extension is Chrome only, and there is no mobile app, desktop app, session replay, video feedback or chat. If a client's procurement asks for SSO, SOC 2 or an accessibility conformance statement, Writhink has none of them today, and you should hear that now rather than in month three.

There is no customer count to quote here and no logos to show. Writhink is young, and if you are choosing a tool for a client relationship starting next week, weigh that. The part you can check in an afternoon is the part that decides it: put your own staging site behind a review link, comment on it the way your most difficult client would, and read the prompt that comes out. If that document is something you would hand to a developer unedited, the rest of this page is detail.

Before you count on it

One caveat on PDFs and image sets: that side is fully built, but it has had far less real use than website review. Treat it as a capability rather than a proven workflow.

The embeddable widget carries a “Powered by Writhink” badge. The white-label add-on that removes it is announced but not purchasable during the beta, so today the badge stays.

Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.

FAQ

Questions people actually ask

Does my client need an account?: No. They open the link, type a display name, and comment. No email, no verification, no signup, nothing to install for the review-link flow. Their comments stay editable by them because ownership is proven by a token stored in their browser.
Can I stop one client from seeing another client's work?: Yes. Each project has its own review link and a client only ever has the link you sent. Inside your team, admins see everything while editors are assigned to specific projects, so someone brought in for one build does not see the rest of your portfolio.
Can I put my own branding on it?: Partly, and not fully yet. The embeddable widget carries a Powered by Writhink badge. The review link itself is a Writhink URL either way.
What if the client's site is not public yet?: Use the Chrome extension. It reaches what a proxy cannot: staging behind basic auth, a logged-in admin area, a builder preview, a local development URL. Comments land in the same project, with the same pin data and screenshots. The reviewer needs Chrome with the extension installed, which suits your team and technical clients more than a marketing manager — for everyone else, send the link.
Can several people on the client's side comment on the same review?: Yes. Each person gives their own display name and every comment is attributed to it. With live collaboration turned on for the project you can see who is in the review, follow one person's cursor, and watch pins appear as they are placed.
Does it stop a client sending feedback forever?: No, and it does not pretend to. There is no round counter, no lock, no approval gate. What you get is a dated, statused list of what was raised and when — the evidence you need when a request arrives after the round closed. Enforcing the round is still your contract.

Start

Send one link. Get feedback you can build from.

Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.