How do I get feedback on an onboarding flow without asking my client to sign up?

Export the flow screens and share a link they can annotate in any browser. Figma and Framer require an account to leave a comment. A proxy-based review link (like Markup.io or Drafty) lets the client click the exact screen they mean and leave a pinned note without creating an account — which is the difference between feedback you get and feedback you have to chase.

What questions should I ask when sharing an onboarding flow for review?

Specific questions get specific answers. Try: 'Is there any step where you'd stop and abandon setup?' and 'Does step two make it obvious what the product is for?' Avoid open-ended prompts like 'What do you think?' — they invite positive replies that don't help you fix anything. Two to three targeted questions per review round is the right amount; more than that and the client skips the hard ones.

Can I collect onboarding flow feedback on mobile?

Browser extension tools don't work on iOS Safari or Android Chrome — so any review method that requires an extension won't reach a client checking on their phone. A shareable link the client opens in their mobile browser works: they tap the screen they're flagging and type the note. For onboarding flows this matters because clients often check mobile rendering before they approve, and they'll test it on their phone anyway.

How is getting feedback on an onboarding flow different from getting feedback on a single screen?

The main difference is sequence. A single screen review is about visual decisions — layout, copy, hierarchy. An onboarding flow review is about the logic between steps: whether the ask at each screen is appropriately timed, whether users can orient themselves when they land on step three without remembering step one. Reviewers need to be able to annotate individual screens while also commenting on transitions — which is why a flat PDF often misses the most useful feedback.

How many rounds of feedback should I expect on an onboarding flow?

Two rounds is typical when reviewers can annotate on the actual screens. The first round catches structural issues — a step that's out of order, an ask that's too early. The second round catches copy and detail. Email-based feedback typically adds one round because each note that says 'step three' requires a reply to confirm which variant of step three they meant.

What is the best format for sharing onboarding flow screens for review?

It depends on whether the reviewer needs to click through the flow or just inspect each screen. For click-through: a Figma prototype link in presentation mode. For screen-by-screen annotation: exported images in a shareable review link. PDFs work for offline situations but drop the flow's interaction logic. The format that most consistently gets you usable, pinned feedback from a client who isn't a designer is the shareable image-based review link — they don't need to know the tool to leave a note.

drafty

How to get feedback on an onboarding flow

Quick answer

To get feedback on an onboarding flow, share a link your client can open in any browser and annotate each screen — the welcome modal, the empty state, the confirmation step — without signing up for anything. For internal rounds, a Figma prototype link with two or three specific questions works well. The review-link method is the only approach that consistently gets you pinned, screen-level feedback from a client before your dev handoff deadline.

Step 1

Share a Figma prototype with targeted questions

Open your Figma file, click Share, set to 'Anyone with the link' in Prototype mode, and copy the URL. The client can click through each step of the flow in any browser without installing Figma. One thing that consistently improves the feedback quality: don't send the link cold. Include two or three questions alongside it — 'On step three, do you understand why we're asking for your role?' and 'Is there any point where you'd have closed this and skipped setup?' Vague prompts like 'let me know your thoughts' invite vague replies. The catch: leaving a Figma comment requires an account. If the client doesn't have one, they'll click through the prototype but have nowhere obvious to type a note. Most default to email, and then you're reconciling screen references and vague descriptions.

Step 2

Record a short walkthrough and ask for timestamped reactions

Use Loom, Screen Studio, or QuickTime to record yourself walking through the onboarding flow with narration: 'At this step we ask for their industry vertical. The reason is X. Does this feel like the right moment, or too early?' Keep it under four minutes. Send the link with a prompt: 'Drop comments on the Loom at the timestamps where something feels off — or just reply with the time range.' This works when you want narrative context in the feedback and when the client is busy enough that they'll watch a short video faster than they'll click through a prototype. The downside is that Loom feedback lives in Loom, separate from your designs, and a Loom comment is harder to trace back to an exact screen than an annotation pinned to the element itself.

Step 3

Export the flow as a PDF and share for markup

From Figma, select all your onboarding screens, File → Export as PDF, and share the file. Clients can annotate it in Preview on Mac, Adobe Reader, or any browser. This works in situations where someone needs to mark up pages offline or forward comments to a team before a review call. The weakness for onboarding flows specifically: a PDF strips out the click-through connections between steps. The client sees screenshots of each screen but not the transitions or the logic of what comes next. If the friction point is at a specific decision branch — the step that shows a different path for solo users versus teams — a static PDF won't reproduce it.

Step 4

Share a review doc the client annotates screen by screen

The most reliable method when the client is non-technical or when sign-off is the goal: export each step of the flow as an image, drop them into a shareable document, and send the link. The client opens it in any browser, clicks the screen they want to flag — 'this step three welcome modal' or 'the empty state before they've added anything' — and leaves a note pinned right there. No account, no install. You see the comment in context: exactly which screen, exactly what element. This is the method that cuts the back-and-forth in half. A pinned note on the step-two tooltip beats three emails that say 'the second screen, not the very first one but the one after the username field.' The other advantage: you can share the same link to multiple stakeholders and all their comments accumulate in one place, in the order they refer to steps in the flow.

The faster way

If you're waiting on a client to sign off on an onboarding flow before dev handoff, drop the exported screens into Drafty and share the link. Your client opens it in their browser, clicks the screen they mean — the step-two tooltip, the empty state, the completion screen — and types a note pinned to that exact spot. No account. When you push a revised version of a screen, it replaces it on the same link so the next round of feedback is on the right version, not last week's export.

Open a live demo

Questions

How do I get feedback on an onboarding flow without asking my client to sign up?: Export the flow screens and share a link they can annotate in any browser. Figma and Framer require an account to leave a comment. A proxy-based review link (like Markup.io or Drafty) lets the client click the exact screen they mean and leave a pinned note without creating an account — which is the difference between feedback you get and feedback you have to chase.
What questions should I ask when sharing an onboarding flow for review?: Specific questions get specific answers. Try: 'Is there any step where you'd stop and abandon setup?' and 'Does step two make it obvious what the product is for?' Avoid open-ended prompts like 'What do you think?' — they invite positive replies that don't help you fix anything. Two to three targeted questions per review round is the right amount; more than that and the client skips the hard ones.
Can I collect onboarding flow feedback on mobile?: Browser extension tools don't work on iOS Safari or Android Chrome — so any review method that requires an extension won't reach a client checking on their phone. A shareable link the client opens in their mobile browser works: they tap the screen they're flagging and type the note. For onboarding flows this matters because clients often check mobile rendering before they approve, and they'll test it on their phone anyway.
How is getting feedback on an onboarding flow different from getting feedback on a single screen?: The main difference is sequence. A single screen review is about visual decisions — layout, copy, hierarchy. An onboarding flow review is about the logic between steps: whether the ask at each screen is appropriately timed, whether users can orient themselves when they land on step three without remembering step one. Reviewers need to be able to annotate individual screens while also commenting on transitions — which is why a flat PDF often misses the most useful feedback.
How many rounds of feedback should I expect on an onboarding flow?: Two rounds is typical when reviewers can annotate on the actual screens. The first round catches structural issues — a step that's out of order, an ask that's too early. The second round catches copy and detail. Email-based feedback typically adds one round because each note that says 'step three' requires a reply to confirm which variant of step three they meant.
What is the best format for sharing onboarding flow screens for review?: It depends on whether the reviewer needs to click through the flow or just inspect each screen. For click-through: a Figma prototype link in presentation mode. For screen-by-screen annotation: exported images in a shareable review link. PDFs work for offline situations but drop the flow's interaction logic. The format that most consistently gets you usable, pinned feedback from a client who isn't a designer is the shareable image-based review link — they don't need to know the tool to leave a note.

Keep exploring

How to get feedback on a Figma design How to get feedback on an app How to annotate a Figma file Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo