Feature
Client feedback for Claude Design
Your team and your clients pin notes on Claude Design boards and on the staging or live site, clients without an account, and the notes go back to Claude as one clear list.
Client feedback
Claude makes the first version fast. The feedback is where the days go.
At Woofocus, client feedback used to come in by email with a screenshot attached, as pins in BugHerd, in chat threads and on calls. Someone had to gather it, work out which page and which version each note was about, and pass it to the designer or the developer. That was most of a producer's afternoon.
Claude Design gets a first version on the table in minutes, so the rounds of feedback come sooner and more often. In Proofyard every note stays on the board or the page it is about, with the spot, the version and the device, and goes back to Claude as a list it can work through. A person decides what goes to Claude and what the client sees.
- 01
Pin notes on the Claude Design boards
Paste the claude.ai/artifact link of a Claude Design canvas on the task and Claude brings the boards in, desktop and mobile. Each import is a new version, so feedback never lands on the wrong one. Click a spot on the board to leave a note: it keeps the spot, the words it points at and a screenshot. Assign, reply and resolve in the panel beside the board. Clients pin notes on the same design from their review link, with no account.
- 02
Clients leave notes on the staging or live site
Add one script tag, or a Google Tag Manager tag, to the site. Send the client a review link: the site opens with a feedback button for them alone, for 14 days or up to 90. They click the part they mean, write the note and pick a type. No account, no browser extension. Visitors without a link see nothing.
- 03
Every note arrives with what you need to fix it
The page, the element and its text, a screenshot with passwords and card fields greyed out before it is uploaded, the browser and the screen size. Console errors and failed requests come too if you turn them on. Reply to the client, or keep a reply for the team only.
- 04
All feedback on one board
Notes from the design boards and from the site land on the project's Feedback board: New, To do, Doing, Test, Done. Filter by page, device or person, tie notes to a task or make one task from several, and export to CSV, Excel, JSON or PDF. Moving from BugHerd? Import its CSV.
- 05
Send the notes back to Claude
Pick the notes and send them. Claude Code opens each one through the Proofyard connector, screenshots included, makes the change and moves the note to Test for you to check. Or copy a prompt with the notes and the canvas link into Claude Design or a Claude chat. The notes you send move to Doing.
- 06
The client checks the fix and approves
When a note is resolved, the client sees "Marked as resolved. Please check it." on their site. Looks good closes it; Still wrong opens it again with their words. For a sign-off, the task's review link (30 days, no account) has Approve and Request changes. The team is told at once, and an approval moves the task on to its next phase.
The screenshots are from the app with sample data: Acme, Maya and the team are made up.
Where agencies use it
From the first board to the week after launch
First design review
Claude Design makes the homepage. The designer, the producer and the account manager pin their notes on the board before anything goes to the client.
Client feedback from a call or an email
When the client says it on a call, pin it on the board yourself, or add it to the task as a comment marked Client said, so it is kept as their words.
Staging review before launch
The client clicks through the staging site with a review link and leaves notes where they see the problem. Each one has the page and the device.
Bugs after launch
A note from a phone with a console error and a failed request tells the developer more than "the form is broken".
Sign-off
The review link records who approved and when, in the task's activity, instead of a thumbs-up somewhere in an email.
Handing fixes to a developer or Claude Code
Claude Code reads the notes over the Proofyard connector, screenshots and all, and moves each one to Test when it is done.
What it will not do
Claude fixes, a person decides
Claude never writes to a client, never emails one and never approves. Replies a client sees are written by your team.
It does not let clients edit the design or see your team's internal notes. They see the newest version and the notes visible to them, on the review link or in their client area.
It does not proof PDFs, images or video. It works on Claude Design boards and on websites.
Claude Design project links (claude.ai/design/p/...) cannot be read. Share the canvas and paste its claude.ai/artifact link.
Questions
Client feedback
Does the client need an account?
No. The task's review link shows the newest design, where the client pins notes, approves or asks for changes, for 30 days. A site review link opens the site with the feedback button for 14 days, or up to 90 if you choose. Clients you add to a project get a login and see only the work you make visible to them.
Do clients need a browser extension?
No. The site needs one script tag or a Google Tag Manager tag. People without a review link never see the button.
Which designs can we review?
Claude Design canvases, shared as a claude.ai/artifact link. Claude brings in up to 12 boards a version, desktop and mobile, and each new import is a new version.
What does Claude do with the notes?
Only what you send it. Claude Code opens each note, screenshot included, makes the change and moves the note to Test. It cannot mark a note done, approve the work or write to the client.
Can some notes stay internal?
Yes. Each reply is either visible to the client or for the team only, and notes your team leaves on the site stay internal unless someone ticks Visible to client.
What about private details in screenshots?
Passwords, card details and one-time codes are greyed out on the visitor's screen before the screenshot is uploaded. Add the py-mask class to anything else that should be hidden.
How does the client hear back?
Replies visible to the client are emailed to them, and their email reply lands back in the thread.
We use BugHerd today. Can we move?
Yes. Export a CSV from BugHerd and import it on the Feedback board. The notes keep their page, their stage and their comments, and importing the same file twice adds nothing.
Who makes it
Made by Woofocus, a web studio, for its own work first
Woofocus has built and looked after client websites since 2010. We made Proofyard because our own production was spread across a task tool, a feedback tool and long chat threads, and we are moving our studio's work into it now. Any agency can open its own workspace.
Ali Demirci
Founder of Woofocus
Ali has designed, built and looked after client websites since 2010 and runs Woofocus, a small web studio. Proofyard is the board he built to run Woofocus's own production after years of carrying work between Asana, BugHerd and chat.
- 4.99/5rating on Codeable across 219 projects for 74 clientsSource: Codeable profile, October 2026
- Since 2010building and looking after client websitesSource: woofocus.com
- ~7,000tasks in our own Asana workspace, the work Proofyard was built to runSource: Woofocus Asana workspace, read 3 October 2026
“Communication was always clear and timely, making it easy to stay aligned on progress.”
“Ali delivered on time and worked tirelessly with us to make sure that we were satisfied.”
Try it on your next design round
Open a workspace, link a Claude Design canvas and pin your first notes. Free for 14 days, no credit card needed.