How to get client feedback on Claude Design

Why this comes up

At Woofocus most new pages now start in Claude Design. The first version is no longer the slow part. The slow part is the round after it: the client looks, says what they think somewhere, and someone has to turn that into changes on the right version.

Below is what we found when we tried to run that round inside Claude itself, and what we do now. Everything about Claude Design comes from Anthropic's help pages as we read them on 24 October 2026; they change often, so check the pages under Sources before you rely on a detail.

How sharing a Claude Design canvas works today

Claude Design now lives inside Claude. Anthropic's getting started page says it is "one of the templates you can start an artifact from", and that "the standalone version at claude.ai/design closes on December 14, 2026". So a design is an artifact, and it is shared the way artifacts are.

The steps, from the same page:

1. Open the design and press Share. "Designs start private to you. To share one, click "Share" and choose who can open it and what they can do."
2. Choose who can open it. On Pro and Max that is only you, anyone with the link, or people you invite by email; on Team and Enterprise it can also be anyone in your organization. For a client outside your organization on a Team plan, "Anyone with the link" "is available only when an Owner has turned on External sharing".
3. Choose what they can do: view, comment or edit. "People you share a design with can view, comment on, or edit it."
4. Send the claude.ai/artifact link. People with comment access click on the canvas to leave a note: "Inline comments let you click directly on a specific part of the canvas and request a targeted change."

For your own team this works well. Designers and the producer comment on the same canvas, and someone with edit access can hand a comment thread to Claude.

Where it falls short for a client review

The trouble starts when the person commenting is the client.

• The client needs a Claude account. The sharing page is plain about it: "Everyone needs a Claude account. People without one can't open a shared artifact, even with the link." Most of our clients do not have one, and the marketing lead who approves the homepage is not going to make one for a review round.
• Comments from outside are limited. For people invited from outside your organization, the page says "they can't mention people or ask Claude in a comment, and they don't get email notifications about comments." So the client does not hear back when you answer.
• Link sharing and comments do not mix. "They can't comment on an artifact that's also shared with "Anyone with the link."" You pick one: easy access, or comments.
• Comments are not always visible. The getting started page lists a known issue: "Inline comments occasionally don't appear on the page, but you can still see them by opening the comments view."
• Versions and approval. Neither page says whether a comment stays with the version it was made on, and there is no Approve button with a record of who approved which version. For a sign-off, that is the part we need most.
• After the design. Once the page is built, the client's notes are about the staging site, which is not in Claude Design at all.

None of this is a flaw in Claude Design as a design tool. It is built for the people making the design. A client round needs something on the other side of the link.

What we do instead

We keep designing in Claude Design and run the review round on our board. The steps are the same every time.

1. Bring the boards in as a version

Share the canvas so it can be read, then paste its claude.ai/artifact link on the task. Claude brings the boards in, desktop and mobile, up to 12 a version. Each import is a new version, so a note from round one never lands on round two.

2. Pin the team's notes first

The designer, the producer and whoever runs the account click on the board where something is wrong. Each note keeps the spot, the words it points at and a screenshot. We fix the obvious things before the client sees anything.

3. Send the client a review link, no account

The task's review link shows the client the newest version. They add a name and an email, pin notes on the board where they see the problem, and press Approve or Request changes. The link works for 30 days. The answer is kept with the person, the time and the version, which is the record an email "looks good" never was. More on that in our page on design approval, and if you send sign-offs by email, our website client sign-off template lists what to ask for.

4. Send the notes back to Claude

Pick the notes and send them. Claude Code opens each one through the connector, screenshot included, makes the change and moves the note to Test for a person to check. Or copy a prompt with the notes and the canvas link into Claude Design or a chat. Claude never approves and never writes to the client; a person does both.

5. The next round is the next version

When the changes are made in Claude Design, paste the link again. The new import is version two, the client's link shows it, and the notes from version one stay where they were made.

After the build, the client keeps leaving notes the same way on the staging site with our website feedback tool, and they land on the same Feedback board.

Side by side

What our way does not do

Being fair about it: our board cannot read Claude Design project links (claude.ai/design/p/...), only a shared canvas's claude.ai/artifact link. It does not proof PDFs, images or video. Clients cannot edit the design, which is on purpose. And it is one more tool, where sharing inside Claude costs nothing extra. If your clients already have Claude accounts and you do not need a recorded approval, Claude's own sharing may be enough.

The full feature, with every step and screenshot, is on our Claude Design feedback page.

Sources

Read on 24 October 2026.

• Anthropic, Get started with Claude Design, shown as updated the day before we read it (23 October 2026).
• Anthropic, Share artifacts, dated 23 September 2026 on the page.