An Onboarding Feedback Example From One SaaS First-Run

Here is an actual first-run through a project-management SaaS signup, captured as six pinned stills with one short comment each. Nothing fancy. A browser tab, the real signup form, and notes typed while the confusion was still fresh. You can copy the pattern onto your own flow in one sitting.

The point of capturing as you go is that the friction is invisible once you know the product. The second time through the signup, you already know the verification email lands in spam. The first time, you sit there for ninety seconds wondering if the form broke. Capture the moment you feel it, not after.

Screen 1: the signup form asks for a company before you know what the product is

The first still was the landing signup form. It asked for full name, work email, company name, and team size before showing a single screenshot of the product. The pin went on the company name field. The comment, dictated in one breath: "I have not seen what this does yet and it wants my company name. A solo user has nothing to type here and no skip option."

That is the whole item. A cropped still of the form, one numbered pin, one sentence that names the field and the cost. A developer reading it knows exactly which input to make optional. This is the shape of onboarding feedback a team can act on: a specific spot, a specific problem, a specific person it hurts.

Screen 2: the verification email takes 90 seconds and says nothing on the page

After submitting, the page showed "Check your email" with no sender name, no retry link, and no note about delivery time. The still captured that holding screen. The pin sat on the empty space below the message. The comment: "Email took 90 seconds. No 'resend' button and no mention of which address it comes from, so I could not search spam for it."

Timing matters here. The 90 seconds is a real number a developer can check against their own send logs. Vague feedback says "the email was slow." The captured version says how slow, what was missing, and what the user did while waiting.

Screen 3: the welcome screen has three equal buttons and no obvious first move

The third still was the post-verification welcome. Three buttons of equal weight: "Create a project," "Invite your team," "Browse templates." Nothing suggested where to start. The pin landed between them. The comment: "First screen after signup and I have three equal choices. As a new user I want one obvious next step, not a menu."

A numbered pin is doing quiet work across all six items: it forces whoever reads the export to look at the exact spot you mean, not hunt the screenshot for what you were pointing at. The pins and the arrows are baked into the exported image, so the person who opens the PDF sees the same mark you drew.

Screen 4: the empty project state gives no example to copy

Created a project, landed on an empty board. No sample card, no "add your first task" prompt, just three empty columns. The still captured the bare board. A box was drawn around the empty first column, and the comment read: "Empty state with zero guidance. I do not know if I drag, click, or type. A single example card would show me the model."

This is where walking the flow beats auditing pages one at a time. The empty project state only exists after you create a project, and you only create a project after you clear the three-button welcome. A page-by-page look would never reach it. If you want to see how that compares, there is a breakdown of what a flow walkthrough catches versus an onboarding pass.

Screen 5: the invite step on a phone cuts off the email field

Switched to a phone for the invite step, because real users will. On mobile the "invite teammates" modal pushed the email input half off the bottom of the screen, under the keyboard. A normal screenshot was taken on the phone (browsers cannot capture the screen there, so you take an ordinary screenshot and add it), then pinned on the cut-off field. The comment: "On iPhone the email field sits under the keyboard. I cannot see what I am typing."

Same review, two capture methods. The desktop stills were grabbed with Capture screen in the browser; the phone screenshot was dragged in. The receiver cannot tell which was which, and does not need to.

Screen 6: the "you're all set" screen hides where the project went

The final still was a success screen that said "You're all set" with a single "Go to dashboard" button. The dashboard it dropped into did not show the project just created. The pin went on the empty dashboard. The comment: "Signup says done, but the project I made is not here. I have to go find it. End the flow in the thing I built, not a generic dashboard."

What the finished review looked like

Six items, six short comments, under ten minutes of work including the phone switch. On Publish it became a single link anyone could open, no login and no app on their end. The same review was there as a PDF for the founder and as clean markdown at the /markdown URL, which is what a coding agent reads if you hand the work to one.

Two details worth copying from these notes. Every comment names the field or screen (company name, the invite modal, the empty board) so there is no ambiguity about location. And every comment says what it costs the user, not just that something is "off." That is the difference between a note that gets fixed and one that gets filed.

If you want a blank version of this to work from, there is an onboarding feedback template you fill as you go. When you are ready to run your own first-run, start a new review and capture the first screen before you click anything. The free account gives you unlimited reviews and screenshots; a review stays editable for seven days before it goes read-only, and Pro keeps it open for $5 a month if you want to come back and rerun the flow after the fixes land.

Send us feedback

Stuck, or want to do something it won't let you? Tell us what you're trying to do and we'll reply by email as soon as we can. This isn't a live chat.

Powered by AcornReply