reviewmy / Products / 02 · Share links
They click the thing they mean.
Send one link to whoever has to sign off. No account, no password, no “third card from the left, below the fold”. Browser, OS, viewport and a screenshot attach themselves to every pin.
1201Headline hides the deadlineNovember 1 is what owners search for. It should be visible without scrolling.
Writing
How it behaves
A pin is a task from the moment it lands.
Context attaches itself
Browser, OS, viewport, scroll position and a screenshot. Your client never has to describe their setup, because they were never going to.
Pins survive a redeploy
They re-anchor to the element. When the element is gone, the pin says so and sits where it used to be rather than quietly moving.
Closed by the person who raised it
Mark it resolved and the client gets a confirm-the-fix step. “Looks good” or “still not right”, with a reason.
- Identity
The reviewer types a name. That is the whole onboarding, no email, no password, no invitation to accept. Each name gets a colour, and their pins carry it.
- Triage
Open, in progress, resolved, plus priority and an assignee. A board across every project, so a morning of client feedback is one queue rather than five inboxes.
- Threads
Replies sit under the pin. State changes render as history lines rather than chat bubbles, so a thread reads as a record.
- Visual edits
Change copy or styling on the proxied page and export the result as CSS. Useful for settling an argument about spacing without a deploy.
- Reports
Publish a frozen snapshot to a token URL, a branded document for the client, separate from the live project, revocable at any time.
- Metering
None of this counts against an allowance. Pins, threads, triage, share links, visual edits and reports keep working even when the AI runs have stopped.
Once the comments land
Turning notes into changes.
Send the link before the next round of feedback.
Your client pins on the real page. You get a queue instead of an email thread.