You walked a new signup flow this morning and found three things worth fixing before launch. Your product lead does not want a 9-minute recording, and she is not an AI agent reading markdown. She wants to open a link, see exactly what you meant, and reply on the parts she disagrees with. Here is the whole thing, screen by screen, with the real pins and comments as they land.
The flow I walked: three screens, three problems
The flow was email signup, then a plan picker, then a welcome screen. I opened the staging build in one browser tab and started a new review in another. No extension, no app. For each screen I clicked Capture screen, the browser asked which window to share, and it grabbed the current frame as a still. Three stills, three items.
Walking it as a flow walkthrough rather than a single-page review matters here, because two of my three notes are about what happens between screens, not on any one of them. A page-by-page check would have missed them.
Item 1: the email screen, pin 1 on the submit button
The capture is the signup form. I cropped out the browser chrome so only the form shows, then dropped a numbered pin (1) on the Continue button and drew a red box around the password field below it.
The comment, dictated in Chrome rather than typed:
Pin 1: Continue stays greyed out even after both fields are valid. I filled in a real email and an 8-character password and the button never activated. Had to refresh to get it to work. Looks like validation only fires on blur, not on input.
That is the whole item: a cropped still, one pin, a box, and a comment a developer can reproduce. The pin and box are baked into the exported image, so whoever opens the review sees the mark on the pixel, not a vague "the button near the bottom."
Item 2: the plan picker, two pins for order
Screen two is the plan picker. Here I used two numbered pins deliberately, because the problem is a sequence. Pin 1 sits on the Pro plan card, pin 2 on the price toggle at the top.
Pin 1: Pro is pre-selected and highlighted. Pin 2: but the monthly/annual toggle defaults to annual, so the price under Pro reads $50 while the card says "$5/mo." Same screen, two different numbers. Pick one default and make the card price match the toggle.
Numbered pins give the reader a reading order. She looks at 1, then 2, and the contradiction is obvious in that sequence. If you want the reasoning behind that, numbered pins that make a developer read steps in order covers it in more depth.
Item 3: a free-floating note, no screenshot
My third note was not about a screen at all. It was about the gap between the plan picker and the welcome screen: after you pick a plan, there is a two-second blank state with no spinner, and it reads as broken.
You cannot pin a blank screen well, so I made this a free-floating item with no screenshot, just a comment:
Between plan picker and welcome: ~2s blank screen after submit, no loading indicator. First-timers will think it froze and bail. Add a spinner or skeleton.
Not every observation has a pixel to point at. An item without a screenshot is still an item in the list, numbered alongside the others.
What the stakeholder actually opens
I clicked Publish. The review got a short link of the form /r/<slug>, and a cleaner read-only page at /s/<slug> for someone who just wants to read it. Cobalt asked for my email so it could send the link; no password, no credit card. I sent her the /r link.
When she opens it she sees three items in order, each with its cropped still, baked-in pins and boxes, and my comment underneath. She does not install anything and she does not sign in to read. On item 2 she replied in a comment: "Agreed, default to monthly." On item 1 she marked it resolved once the fix shipped. That resolve toggle is mine as the owner; who can see, comment on, and resolve review items spells out exactly which actions belong to whom.
She read it on her phone on the train. A review link opens in any mobile browser with no app, which is why I did not reach for a recording she would have to sit through. If you want the full comparison, what your client sees on a review link walks through the receiver's view.
The same review, a second format, for free
The developer who picked up item 1 did not want my comments reformatted by hand. The same review exports as a PDF and a Word doc, and the plain-text version lives at /r/<slug>/markdown. He pulled the markdown straight into his editor. One capture, two readers, no retyping.
One honest note on timing. A review you make without signing in is kept for 30 days, and after 7 days a review goes read-only for you: editing and exports stop, though the shared link keeps working and nothing is deleted. If you need a review editable past that window, Pro is $5 a month and reopens read-only reviews instantly. For a flow you ship this week, the free tier covers the whole job.
Next time you walk a flow, keep the two-tab setup: the build in one, a capture in the other. Three screens, three items, one link. Your stakeholder reads it in two minutes and replies where it counts.