screenroveAI onboarding examples: agent prompts, MCP steps and paid surveys
AI onboarding examples from 95 SaaS products: 16 offer an AI setup path, from agent prompts to MCP commands, while others pay in credits to finish setup.
Amplitude’s recommended way to install it is no longer a code snippet. It is a prompt you paste into Cursor or Claude. Across the 95 SaaS products on our onboarding screens wall, at least 16 now offer an AI route through setup, and these AI onboarding examples split cleanly in two: five hand the job to the coding agent you already use, and eleven put an AI prompt box inside the product itself.
The same flows are also getting more commercial: steps that pay out tokens and credits, seat prices on invite screens, countdown timers. This piece covers both shifts.
Two kinds of AI onboarding examples
We flagged every step where AI is offered as a way to finish setup, not just mentioned. Sixteen products qualify.
| Approach | Products | What the AI does |
|---|---|---|
| Hand-off to your coding agent | 5: Amplitude, Eraser, GitBook, PostHog, Resend | Installs the SDK, connects MCP or publishes docs from your editor |
| Prompt box inside the product | 11: Checkly, Fibery, Contentsquare, Bubble, WeWeb, UXPin, Taskade, Lucidchart, Smartsheet, Mixpanel, Voiceflow | Builds the first workspace, app or diagram from a sentence |
Thirteen of the 16 also put a non-AI route on the same screen: a snippet tab, a manual link, a blank canvas or a plain Skip. Only Checkly, Voiceflow and Smartsheet show no non-AI button on that step.
Setup steps written for coding agents
In developer tools, the install step now speaks to the agent the developer probably has open in another window.
Amplitude leads its “Let’s get data in!” step with a card labelled “AI prompt” and a “Recommended” badge: “Run this custom prompt in an AI coding tool like Cursor or Claude to set up Amplitude.” The primary button is Copy Prompt; next to it sits Open in Cursor with a dropdown for other tools. The snippet is the second tab, and an Invite Team card offers the human version: “Hand setup to a developer on your team.”
Eraser goes further and makes connecting an agent a numbered onboarding step (4 of 5): “Connect your MCP client”. Ten client tiles, from Claude Code to GitHub Copilot, each swap in their own instructions. For Claude Code that is a single terminal line, claude mcp add --transport http eraser https://app.eraser.io/api/mcp, with a Copy button.
GitBook ends its four-step flow the same way. Step 4/4, “Set up your local workflow”, offers Claude, Cursor and ChatGPT buttons, then “or” a copyable prompt that opens “# GitBook Setup Agent ## Goal Get my docs live on a published GitBook site.” A green “Your docs are ready” sits beside Go to app, so the agent route is offered, not forced.
PostHog sells the hand-off with a time saving: “Skip the install. Get 10–20 minutes back.” The wizard runs from npx -y @posthog/wizard@latest, “detects your framework, installs the right SDK, configures your environment variables”. One small line answers the obvious objection: “LLM inference is on us, no API key needed.”
Resend is the lightest touch: a “Copy for AI” dropdown beside its code sample in ten languages.
The prompt box as step one
Elsewhere, the AI path is a text box that replaces the template picker. Where it sits varies.
First screen. Fibery opens with “Get a head start with AI” and a fill-in placeholder, “Create a workspace for _____ that includes _____”. Bubble asks “What do you want to build?” and adds a door for people who started elsewhere: “Already built an app with AI? Import your code”. WeWeb’s first editor view is “Describe your project and let AI build it for you”.
The whole onboarding. Checkly has no questionnaire at all. A new account lands in the live app on “What do you want to monitor?” with one prompt box and four starter pills (“Marketing site & SSL”, “Checkout with Stripe”). The assistant asks clarifying questions and ends on “Your checks are live”. Contentsquare puts an AI box above “Or select a focus” and four goal cards. Voiceflow runs onboarding as a chat with an assistant, Atlas, promising your first agent “in under 2 minutes”.
The last step. Lucidchart asks its questions first, then closes on “Create a diagram with AI” with the box already filled: “Generate a flowchart for the design process workflow.” Template and blank document are text links underneath. Mixpanel’s first home screen asks “What should we build today?” with “Set Up with Mixpanel Agent” as the main button beside a “Set up manually” card. UXPin and Taskade offer “Generate with AI” and “Start with AI” as one choice among several.
Prefilling matters more than placement. Lucidchart and Smartsheet write the first prompt for you from earlier answers, and Fibery’s placeholder is a fill-in-the-blanks template. The questions these flows ask are increasingly there to write that prompt.
AI also shows up as a channel
Ten products show their “how did you hear about us” answers on screen, and nine include an AI option. Typebot is the only one without. Position varies a lot:
- First: Make (“AI”, of 9 cards) and VEED (“AI chat”, of 8 pills).
- Second: Bolt, “AI Search (ChatGPT, Perplexity, Claude)” right under Google.
- Fourth: Bubble (of 11), Hygraph (of 16), WeWeb (of 8) and Evernote (of 5).
- Fifth or later: Krea, fifth of 10 (“ChatGPT, Gemini, or another AI assistant”), and Runway, eighth of 12.
Relume goes a step further and treats AI as part of your stack: “What platforms are you using with Relume?” lists Claude next to Figma, Webflow and Framer.
Money inside the flow
Twelve screens on the wall are plan steps, from 11 products, and the paywalls wall has 45 paywalls shown during onboarding from 36 products. The more interesting cases are the ones where money appears on steps that are not about plans.
Paying for onboarding behaviour. Bolt’s three-question survey carries “Get 1M tokens for completing the survey!” in its header and ends on “1M extra tokens have been added to your account!” plus another 1M for a work email. Twenty puts credit chips on buttons: Continue on the profile step earns “+0.5”, each contact-sync button “+1”, against a “free credits” meter in the corner. Wrike’s quick-start checklist says “Complete them all to get 1 month free!” Bolt and Twenty pay in their own AI currency, which costs compute rather than cash; Wrike pays in subscription time.
A price on a non-price step. Cap’s “Invite your team” step (4 of 5) shows no email fields. It shows “$8.16/mo per user, billed annually”, “or, $12/mo per user, billed monthly”, a seat stepper and an “Annual (save 32%)” switch.
Discount pressure. Krea’s last onboarding step opens with “Offer ends in: 0h : 59m : 53s” and “up to 40% off Krea Pro”: $35 struck through to $21 a month on yearly billing. Skip it and a “One last offer” modal deepens the cut to 50%, $17.50 a month, with its own timer and a “Decline offer” button. Any.do preselects a 12-month row badged “50% OFF - MOST POPULAR” at $4.99/mo, about 38% below its own $7.99 monthly row.
Trial terms up front. The calmer pattern spells out the trial. Linktree’s 7-day Pro trial is a three-stop timeline ending “Your plan starts on Oct 29th”; Toggl says “Your trial starts now” over “No credit card needed”; Checkly’s banner names the date of the downgrade to Hobby. More in our free trial UX study; browse the rest under onboarding trial offers or the wall’s plan steps.
What to steal
- Ship an agent prompt next to your snippet. If your install step has code, add a Copy prompt button as Amplitude and GitBook do. Write the prompt so it defines “done”, like GitBook’s “Get my docs live on a published GitBook site.”
- Give MCP its own step. If you have an MCP server, Eraser’s tile grid plus one copyable command per client is the cleanest version in the set.
- Name the payoff and the cost. PostHog’s “Get 10–20 minutes back” and “LLM inference is on us” answer the two obvious objections.
- Prefill the prompt box, and keep a non-AI door. Lucidchart never shows an empty box; Fibery’s “Start without AI” is three words.
- Pay in your own currency, and show the meter. Twenty’s chips make each step’s value visible; Bolt names the reward in the header of every survey step.
- Put the date on the trial. Linktree and Checkly say when billing or the downgrade happens, not just how many days.
How we counted
We captured these screens in desktop browsers with research accounts in September and October 2026. A vision model recorded each screen’s attributes, checkable on each screen’s page; the AI-path and channel counts are our own reading, with positions in reading order. We record what we saw on one pass through each flow, not A/B tests, so nothing here says which approach converts better. Offers, timers and prices can differ by account, region and date.
To pull these references into your own build, connect the Screenrove MCP server and ask your agent for “onboarding steps that hand setup to a coding agent”.