Onboarding feedback the eng team can ship from

This page is for PMs and growth teams running an onboarding review, the kind where you sign up as a new user, click through every step of the funnel, and write up what's broken. It's one of the most common workflows on the use cases for visual product feedback hub, and the one where fragmented feedback hurts most. Onboarding is a chain. If step 3 ships a fix but step 5 still has the wrong copy, the funnel still leaks. The review artifact has to hold the whole chain in one place.

The problem

Onboarding reviews live in five places at once. The PM's friction notes are in a PRD section nobody updated. The Mixpanel drop-off chart is a screenshot in a Slack thread. The actual copy issues are in DMs to the designer. The "this step takes too long" complaint is a voice memo from the founder. The dev assigned to fix step 4 gets none of step 3's context and has to guess whether the email-confirmation friction is a copy problem, a timing problem, or a passwordless problem.

The result is a funnel review that takes a week to assemble and an afternoon to act on, in the wrong order. The engineers fix the steps with the loudest complaints, not the highest-impact ones, because impact never made it into the artifact.

The CobaltCapture workflow

Open an incognito window. Sign up for your own product as a new user. At step 1, hit Capture screen at cobaltcapture.com, pick the signup window, and drag a box around the friction, the form field that asks for a phone number you don't have a reason to give yet. Hit Dictate and talk: "We ask for phone before email is verified. Most users won't have a reason to trust us yet. Move this to post-activation or drop it."

Move to step 2. Capture again. Talk through it: "This email confirmation step adds 30 seconds and Mixpanel shows 18% abandon here, this should be optional with passwordless as the default." Repeat the loop through every step of the funnel. Welcome screen, profile setup, plan picker, first-action prompt, paywall. Each capture stamps the page URL it came from so the dev knows exactly which template to open.

Hit Publish. You get a single URL with every step, every screenshot, every dictated note in the order you walked them. Drop the link in the engineering ticket, the PR description, or the next prompt you send to Cursor so the eng team can fix the funnel step-by-step.

What the output looks like

The published review is a markdown document with one section per funnel step. Source URL on every item, dictated commentary as paragraphs, screenshots embedded inline:

# Onboarding review, new user funnel, 2026-05-13

Source: https://app.example.com/signup

![Phone field on signup](https://cobaltcapture.com/r/k7m3xq82/img/1.png)

Step 1 asks for phone number before email verification. No reason
for a brand-new user to trust us with that yet. Mixpanel shows 12%
drop-off on this step alone. Move phone to post-activation or remove
it from required fields.

Source: https://app.example.com/verify-email

![Email confirmation step](https://cobaltcapture.com/r/k7m3xq82/img/2.png)

Email confirmation adds ~30 seconds and 18% drop here. Switch to
passwordless magic link as the default path; keep password as a
"prefer a password" toggle for the minority who want it.

Source: https://app.example.com/onboarding/profile

![Profile setup with 7 fields](https://cobaltcapture.com/r/k7m3xq82/img/3.png)

Seven required fields in profile setup. Three of them (company size,
role, use case) are for our segmentation, not the user's experience.
Defer to a post-first-action prompt; show only name and avatar here.

Why this beats Mixpanel + speculation

Mixpanel tells you WHERE the funnel leaks. It will not tell you WHY. A 22% drop on step 4 could be a copy problem, a load-time problem, a trust problem, a confused form, or all four at once. The Mixpanel dashboard is the question. The walkthrough review is the answer.

CobaltCapture gets you to the answer by forcing you to be the user. You walk the funnel. You feel the friction. You dictate the cause while it's still in your head. The output is a structured document that pairs every drop-off with a hypothesis grounded in the actual screen.

The markdown export then ingests cleanly into Cursor or Claude Code. The engineer paste the review URL into the agent, asks it to fix the funnel step-by-step, and the agent has every screenshot, every source URL, and every dictated note in one context window. No translation layer, no clarifying DMs, no half-fixed funnel.

Who this is for

PMs running quarterly funnel reviews who need an artifact the eng team can actually ship from. Growth teams running onboarding experiments who want the qualitative "why" sitting next to the quantitative "where." Founders rewriting onboarding before a launch and pulling in the engineer day-of. If your current onboarding review is a Notion doc with eight screenshots and a Loom link, this is the workflow that turns it into something a coding agent can fix.