The review-loop guides · a straight answer
How to share a prototype with a client for comments
You've got something to show. You want the client to react to it — specifically, on the thing itself — without a forty-message email thread that says "the top part."
Short answer: send a live link to the prototype and ask for comments pinned on the page, not typed into an email. When the client can tap the exact element and say "this word" or "this button," their feedback arrives already located — you skip the entire round of "which top part?" A pin-on-the-page review link (no login for them) turns a vague reaction into a punch list.
The thing that makes client feedback painful is never the opinions — it's the translation cost. "Can we make the hero pop more" sent as an email, detached from the hero, means a call to figure out what they meant. The same note pinned on the hero is unambiguous. So the entire game is: get the comment attached to the pixel it's about, and make it effortless for a non-technical client to do that.
Set it up so the feedback is usable
- Send a link, not a file. A live URL renders identically on their phone; a zip or a screenshot doesn't, and can't be commented on in place.
- Ask for pins, not prose. "Tap anything that feels off and leave a note" gets you specific, located feedback. "Let me know your thoughts" gets you a paragraph you have to decode.
- Bound the ask. Tell them what you want eyes on (copy? layout? the flow?) and what's still placeholder, or you'll get notes on lorem ipsum.
- No account for them. Every sign-up wall between the client and the comment box costs you responses. The best tool here asks nothing of the reviewer but a tap.
Draft the message to send them — adjust and copy:
Paste in your real review link where marked.
If an AI agent built the prototype
Keep the loop inside the build. Your agent can share the live prototype through an MCP tool, hand you the review link to forward to the client, then read the pinned comments back and apply the ones you sign off on — so the client's notes become edits without you retyping them as a task list. That's the twocents loop: share, collect pins, apply what you approve.