Install
Who it's for For agencies
Client feedback tool for agencies
Website Feedback Tool is a Chrome extension that lets agencies and their clients leave pinpoint comments and screenshots directly on a live staging site, then hand the whole round to the build team as a single link. No client logins, no accounts, no shared workspace to administer.
Agency work has a step nobody scopes and everybody pays for: turning what the client said into something a developer can act on. This page is about compressing that step.
Round two is where the margin goes
The build is done and staging goes to the client. What comes back is rarely a list. It's an email with four bullets, a WhatsApp screenshot with a red circle drawn on it, a call where someone says "the header feels cramped", and a forwarded message from a stakeholder you've never met.
Then someone on your side spends an afternoon as a translator: matching "the blue button on the pricing bit" to an actual element, guessing whether the screenshot was mobile or a narrow desktop window, and asking the client to clarify two of the four bullets. That afternoon isn't in the estimate, and on a fixed-price build it comes straight out of margin.
The failure isn't the client being vague — they're describing a page they can see and you can't. Feedback goes wrong when it leaves the page.
Keep the feedback on the page
With the extension installed, review happens on the real staging URL rather than in a document about it.
- Click any element to pin a comment to it — that exact button, that exact heading, that exact price card.
- Drag a box when the problem is a whole section, like a broken empty state or a grid that collapses awkwardly.
- Record a short clip (up to two and a half minutes) when the issue only exists in motion — a hover that flickers, a modal that traps scroll.
- Set severity — Low, Medium or High — so "launch stopper" and "nice to have" don't arrive looking identical.
Every comment captures the URL, the viewport size and a screenshot automatically. That kills the two questions that eat a whole reply cycle: which page, and how wide was the window.
Comments group by hostname, so a review of one client's staging site never mixes with another's. Reviews are stored locally in your browser — there's no shared cloud workspace holding your client list.
What the client actually has to do
Being straight about this, because it's the question agencies ask first: to leave comments themselves, the client installs the extension from the Chrome Web Store. It's free and it's one click, but it is a step, and on a corporate laptop it may be a step their IT policy owns.
To read a review, they need nothing. You send a link, it opens in any browser, and they see every comment with its screenshot and page context — no install, no signup, no seat to provision.
Which gives you two workable shapes for a client round:
- Client comments directly. Best with hands-on clients and multi-round projects — they install once and every later round costs nothing extra.
- You drive the call, they watch. Walk the staging site together, pin their remarks as they speak, then send the review link back as the written record of what was agreed. Often faster than teaching a new tool to a client who reviews a site twice a year.
Hand the round to the build team as one link
Once the round is captured, the same review goes to whoever does the work. Your developer opens the link and sees each comment in context; the designer sees the same thing without a re-brief.
- Share the review link — it opens on any browser with the screenshots and page context intact.
- Download PDF or HTML for the artefacts that need to persist: the sign-off pack, the change-request attachment, the file that goes in the project folder.
- Push the batch into an AI coding agent like Claude Code or Codex, element context included, when the fixes are mechanical.
- Copy a single comment's text or its screenshot straight to the clipboard when one item needs to become a ticket in your own tracker.
One thing to plan around: shared review links are temporary and expire a few days after they're created. That's deliberate — client staging sites aren't something to leave publicly readable indefinitely. For anything you need months later, download the PDF or HTML; that's the archival copy.
Where it fits in an agency stack
This isn't a project management tool and doesn't try to be. There's no client portal, no time tracking, no white-labelling. It covers one step — capturing what's wrong with a page and moving it to the person who fixes it — and leaves your tracker, contracts and invoicing alone.
Which is usually the right trade for a small studio. Client-portal platforms charge per seat and ask the client to learn a system for a project that lasts six weeks. Here the artefact is a link, and the client's side of it is a page they can already read.
If most of the reviewing happens in-house rather than with the client, the designers and developers & QA guides cover those workflows. And if you're weighing this against a dedicated client-review platform, Website Feedback Tool vs Pastel is the closest head-to-head.