Install
Who it's for For product managers
Website feedback tool for product managers
As a product manager, you're the last set of eyes on the release candidate before it ships. Copy against the brief. Layout against the Figma. Empty state. Error state. Every flow the analytics deck says matters.
The problem is never spotting the issues — it's collecting them without turning a Wednesday afternoon into a 40-message Slack thread that nobody wants to read.
Why the pre-launch review sprawls
A release candidate goes up on staging. You start clicking through. Two minutes in you've already spotted three things: a broken tooltip, a wrong CTA copy, a plan card that doesn't match the pricing decision from Monday.
Now the choices are all bad. Post them one by one in Slack and lose the thread. Open three Jira tickets and drop the context. Take screenshots, annotate in Figma, paste back — and someone still asks "which page was this on?"
By the time the batch reaches design and engineering, half of it needs to be rechecked because the acceptance criteria live in your head.
Run the review as one async batch
Open the extension on the staging URL and just click through the flow you were going to click through anyway. Every time you spot something, pin a note to it and keep going.
- Click a single element to pin a note directly to it — the exact button, the exact card, the exact price.
- Drag a box when the issue is a whole section — a broken empty state, a misaligned pricing grid.
- Mark severity as you go so engineering knows what's blocking launch and what's a nice-to-have.
- Record a short clip when the bug only shows up in motion — a state that flashes, a scroll jump, a toast that hangs.
Every comment stays pinned to its element with the URL and viewport captured automatically. When the developer opens the review, they see it exactly where you saw it — same page, same size, same state.
Hand off in one link, not forty messages
When the pass is done, you send the whole review at once. No copy, paste, and label — one link that opens on the live page.
- Share a link — design and engineering open it and every note is already in context on the real staging URL.
- Download HTML or PDF to attach to the sprint doc, the release-candidate ticket, or the launch runbook.
- Push the whole batch into Claude Code or Codex — your AI coding agent picks up the fixes with the element context intact.
- Keep the review URL — a week later, on the next RC, you can open it again and see what's fixed and what's still open.
Stakeholder review before the exec sees it
Async review isn't only for the build team. Drop the same review link into #product or send it to marketing and legal. They add their notes on the same live page — no screenshots pasted into email threads, no "which button did you mean?" back-and-forths.
Run separate reviews per release for the same domain: one for the pricing revamp, one for the onboarding flow, one for the empty states pass. All in the same place, none of them tangled with each other.
For a look at what design and engineering see on the other end of the handoff, the designers and developers & QA guides walk through their side of the same workflow.