Skip the review call. Send the prototype as a private link, let people pin comments to the exact element with no account, and read every note in one place — async, on their schedule and yours.
The standing review call is a strange ritual when you look at it directly. Four people block thirty minutes. One of them screen-shares the prototype. The other three squint, say "can you scroll up," and describe — out loud, in real time — where on the screen the problem is. Someone takes notes that nobody trusts. The decisions get re-litigated in chat the next day anyway.
Almost everything in that meeting is coordination overhead wrapped around a single useful act: a person pointing at a spot and saying change this one. You can have the useful act without the meeting. The trick is to move the pointing onto the prototype itself, where it can happen on anyone's schedule.
Strip a prototype review down and there are only three jobs happening:
A meeting does all three badly. Locating happens by verbal description, which is lossy. Reacting happens out loud, so the quiet reviewer says nothing and messages you privately at 6pm. Recording happens in notes that drift from what was actually said.
A pinned comment on a hosted prototype does all three at once, and does each one better. The reviewer clicks the literal element — locating is now pixel-exact. They type the reaction in their own words. The note is the record, anchored to the thing it's about. No transcription gap, because there was never a spoken layer to transcribe.
Here's the whole thing.
Host the prototype as a private link. Drop the self-contained HTML or zipped build; you get an unguessable URL that opens straight to the work — no account wall for the viewer, no dashboard, no chrome. This is the same private delivery you'd use for sharing a vibe-coded app or a Cursor build; review just rides on top of it.
Turn Review on. One toggle. The link doesn't change — it's the same URL you'd send anyway. A small Review button now sits in the corner of the page.
Send it the way you already send things. A message in the project channel: "prototype's live, leave notes by Thursday, link's open." No invite, no time slot, no "does 2pm work for everyone."
Reviewers pin where it hurts. Each person opens the link on their own time, clicks the exact element that bugs them, and types. They add a name; no sign-up. The note sticks to that point and to the screen size they were viewing — so a comment left on the mobile layout doesn't wander onto the desktop one.
You read every pin in one place. Open the review view and every note is a numbered pin beside the prototype, listed in a panel. You mark each one resolved as you handle it; it greys out, and the thread stays readable instead of becoming a 40-message scroll.
Drop a prototype, turn Review on, and leave yourself a pin from your phone — feel the exact thing a reviewer feels before you send the real link. Free, no card.
Async review has one classic failure mode: you send the thing, and people don't respond. Then you book the meeting anyway, defeated.
Most of that silence isn't apathy — it's friction. A reviewer who has to create an account, confirm an email, and learn a new tool just to say "this headline is wrong" will simply not do it. The cost of the note exceeds the size of the note.
When the reviewer clicks a link, the prototype is right there, and leaving feedback is click-the-spot-and-type, the math flips. The note costs less than the annoyance of holding it. That's why people who'd ghost a request actually leave pins — and why this replaces the meeting instead of just adding another channel to ignore.
A meeting forces simultaneity — its single worst property. Three reviewers, three time zones, one designer on parental leave who has opinions: a call serves none of them. A shared pin layer serves all of them.
Everyone with the link sees the same set of pins, like a shared proofing surface. The reviewer who opens it Tuesday morning sees what a colleague flagged Monday night and doesn't re-report it. Each person edits or deletes only their own notes. The thread accretes calmly across the days you were never all free anyway — and you read the whole thing in five minutes whenever it suits you.
You also get something a meeting never produces: a written, anchored record that survives the week. Nobody has to remember what was decided. The pins are the decision.
When the round is in, you don't retype anything. On Studio, click Export and the whole thread comes out as a clean markdown brief — each note tagged with the element it points at and the layout it was on, grouped as a to-do list rather than a transcript. Paste it into Claude or Codex and say "apply these." The model gets the same pixel-precision the reviewer had. The reaction on the prototype becomes a change in the next version, in one move.
Then you replace the page with the new build. The link is stable, so the same reviewers reopen the same URL, see the update, and leave the next round. No re-sending, no "here's the new one."
This works on prototypes you can host as a self-contained page or a static build. If your prototype needs a live backend to even run — a real database, server-side auth, a payments call — that part belongs on a deploy platform like Vercel or Netlify. Get it running there, then point reviewers at the front-end surface as a private link. Pinned review is for the interface people react to, not the server behind it.
And there's still a place for the call — a kickoff, a hard strategic disagreement, a moment that needs a human voice. The point isn't that meetings are bad. It's that "look at this and tell me what to change" was never one of those moments. Hand that job to a link, and you reclaim the half-hour for the conversations that actually need everyone in the room.
If you want to set the surroundings while you're in there, you can track who opened the link, protect it with a password, or give it an expiry that matches the review window so the prototype doesn't outlive the round.
Comment threads normally require identity, and for good reason — a note has to belong to someone. Here's how a review works when the reviewer signs into nothing, what that costs, and when the trade is the right one.
Website annotation tools start by asking where the page lives — a reasonable assumption that quietly excludes the most common case in 2026: an HTML file your AI just made, sitting in your downloads folder, due in front of a client this afternoon.
Client-side encryption tools turn your page into an encrypted file, so the protection and the artifact are the same object — every edit means re-running the tool and re-uploading. What that actually costs, the salt setting that decides whether your old share links survive, and when a hosted password is the better trade.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.