2026 · Enterprise SaaS · 8 weeks
AI-Powered onboarding scoped for fast testing
How I transformed a PM’s vibe-coded prototype into a focused solution designed to help customers get value faster.
AI Design
Scope
Product Strategy

The Business Problem
Competitors offer free trials. We don't.
Our top competitors in gym management software let prospects start a free trial at sign-up. We couldn’t — onboarding is complex today, and every new customer gets an Onboarding Specialist to help. To open a free-trial path, we first needed a self-serve setup flow.
No free trial option
Competitors offer one at sign-up. Sales flagged it as a reason we lose deals.
No self-serve path
Onboarding today is manual, scattered, and complex. Users would struggle without help.
Onboarding specialists time could be better utilized
They do 3 calls over 3 weeks with customers just to get them started—they could be focusing on more complex setup, and customer success.
—A customer we lost in the sales process
PM's Vibe-coded ideation
PM's idea for a new onboarding experience
The PM vibe-coded a ~12-step wizard that scraped a gym’s website and auto-filled setup. This new flow would redesign all setup pages, in a separate experience before a user enters the product.
The PM's Vibe-Coded Prototype
What I flagged:
ASSUMPTIONS: Do we have data showing that all of our in-app setup pages need a redesign to be self-service ready?
RISK: This is our product’s first AI feature. How can we test the approach fast, before making a large investment?
EFFORT: Rebuilding every setup page and their CRUD flows is a big lift for ENG. Is it the best investment right now?
SOURCES: Do owners actually have the material this needs (a website) or could we support other import types?
REQUIREMENTS: ~12 steps is a lot of upfront work. What's minimally required before users start seeing value?
DISCONNECT: If onboarding looks different from the setup pages owners use later, will that switch cause friction?
My TAKEAWAY
Self-serve guidance is great — but how can we de-risk with a smaller scope, and define a user-focused problem to solve?
Research
Understanding the steps and challenges
I investigated the underlying user and business problems, and identified where the proposed approach introduced potential new friction, to help the team converge on an effective product strategy.
Learning the process, and where users struggle
I watched dozens of recorded Onboarding calls with real customers to map out the actual in-product steps. It was a gold mine for my research!
My thoughts while watching:
What tasks are Specialists doing for them?
Which steps take longer than others, why?
Which steps are tedious vs actually difficult?
What info does the user already have elsewhere?
Where does the user get confused or overwhelmed?
How did they navigate through the process? (linear?)
What requires extra learning or help?
What requires human expertise or judgement?

Key findings:
Manual data entry is a huge burden
Owners type in memberships, pricing, classes and more, one record at a time. It’s the bulk of the setup work.
Nothing tells users where to start
Owners count on their Onboarding Specialist to tell them which settings to prioritize.
Some fields need human judgment
Settings like pricing are costly to get wrong. They need evaluation before finalization (which shaped our AI rules later).
A quick unmoderated test of the concept
To move quickly, I refined the PM’s prototype in Magic Patterns and tested it with customers who had onboarded in the past year. While we had already decided the scope was too large, some concepts were worth getting in front of users: an AI import and onboarding guidance.






KEY INSIGHT
Users loved the idea of a prioritized path and less data entry. But, they were concerned about AI accuracy and how this related to the in-product experience they often edit and refine throughout onboarding.
Customer journey mapping—because self-serve isn't just a UI change
Changing our Onboarding flow isn't just about the product. So my PM and I conducted dozens of internal meetings to understand friction, and help define how process would need to change cross-deparmentally.
Marketing: Website updates, package offerings.
Sales: Restructure lead capture, follow-up after sing-up.
Onboarding: There for support, complex use-cases, customer success.

Strategy & DIRECTION
Reframing the project
FROM
TO
How might we pilot a low-risk self-serve setup that guides users and cuts data entry?
01
Scope small, test fast
Prove AI accuracy and usefulness in a small, Specialist-led pilot before opening it to everyone.
02
Prioritize time to value
Point users to what matters first, so they reach real value (classes scheduled) before setup is “complete.”
03
Start with what users have
Turn any existing resources (websites, spreadsheets, images) into a useful starting point.
04
Let AI do the heavy lifting
Hand AI the tedious data entry, but leave low-confidence, high-risk fields for the owner to decide.
05
Keep users in the product
Reuse existing setup pages instead of building a parallel UI.
06
Design for learning along the way
Let users discover and learn the product through real setup work, setting them up for long-term success.
Design Solution
Import, review drafts, and finalize
A quick import analyzes existing resources to pre-populate the users account. On a new Overview page, there's a summary of imported elements that take users to existing pages to review further. Items are imported in a Draft state, allowing users to review before finalizing.
Importing Data
Upon login, user is prompted to set up their account with our AI data import.

1
Relaying the prioritized assets the user needs to provide.
2
Option to submit their website, if they have one.
3
Option to upload any asset - PDFs, spreadsheets, images, etc.
4
User still has option to Skip and explore the product. They can revisit this import any time.
5
A task-based loading screen keeps users informed while they wait (only a couple of minutes).
In-Product Overview
A new page to provide priority tasks and review progress.

1
New page at the top of our existing Setup area in our navigation.
2
Welcome banner with information, instruction, and progress chart.
3
This section contains the priority elements a user needs to set up before they start seeing value.
4
User can view or edit assets they've added for import. (see UX below).
5
Cards take user to that element's existing page in our setup space to review the added content.
6
Imported items are saved as Drafts until the user reviews and activates them.
7
We didn't remove expert help — meeting with an Onboarding Specialist is still an option.
Reviewing Data (Memberships)
Users go to our EXISTING setup pages, with instruction to review Drafts.

1
New users haven't learned how to navigate yet, so we provide a quick link back to the Overview page.
2
Instructional banner. Draft items must be reviewed and activated.
3
Users have the option to create their own items (per usual), or Activate All in the Bulk Action menu if they prefer to move forward and correct info as they go.
4
Users click on rows to Review and Edit the newly added items.
5
As items are Activated, they change to the Active status and move to the top of the table.
Editing, Missing Info
Using EXISTING detail pages, users review content. Missing info appears in Error per usual.

1
This is the existing detail page for a Membership, in a Draft state.
2
User can't Activate until all required fields are filled out appropriately.
3
Just as the system does today, if info is missing or incorrect, the field will appear as an Error.
Re-Imports (edge case)
On the Overview page, users can edit or add their imported resources.

1
Warning that re-importing could change info in Drafts, though saved info will NOT be changed.
Basic Onboarding Complete
Overview page provides an account summary with quick links and Recommended next steps.

1
Section condenses to provide an overview of primary assets, and quick links to their setup pages.
2
Recommendations include common next steps, but are not required to start class bookings.
Engineering effort drastically reduced — only one new screen and Draft logic.
AI handles tedious actions that took up the majority of users' onboarding.
We can quickly test this AI feature's UX before changing onboarding entirely.
Users complete a small set of priority tasks to get value faster.
By using our existing setup pages, users learn the product as they go.
Free-Trial potential is unlocked, helping our competitive advantage.
Users aren't blocked from exploring the product before completing setup.
Results & rollout
De-risking the path to a free trial
Some improvements to onboarding were immediate and measurable from day one. Others require testing to validate our core hypothesis: that faster onboarding reduces time-to-value and supports long-term adoption.
Immediate impact
Effort reduction
~85%
of minimum required fields can be pre-filled with AI.
Scope reduced
2 sprints
total eng effort, down from an estimated 6 sprints.
GUIDANCE PROVIDED
6 priorities
identified and displayed to users to guide them through setup.
Rollout planning, with a goal to de-risk
PHase 1
Test AI's accuracy and value
Our Onboarding Specialists use this as a tool with customers during setup.
Avg AI fill rate
How many fields on average is AI pre-populating given different input sources?
Test: Log input sources provided, and number of fields filled upon app entry.
Field fill & acceptance rate
How many AI-filled fields were kept vs edited.
Test: Log AI value, measure against the same value at activation.
Customer experience survey
Users rate their onboarding experience, answer qualitative questions.
Test: Post-onboarding survey.
PHase 2
Open free trial, test self-serve
If phase 1 proves promising, we enable a free-trial option and customers try the UX on their own.
Self-serve completion
How many users finish basic setup without a call.
Test: Track onboarding task completion.
Help requests
How many users scheduled a session with a specialist.
Test: Track call scheduling completion / internal onboarding tickets created for calls.
Customer experience survey
Users rate their onboarding experience, answer qualitative questions.
Test: Post-onboarding survey.
What I Learned
There was a lot to this project, and it moved incredibly fast! Here are my personal takeaways.
Lesson 1
The power of scope reduction
This project started with a massive scope: the PM’s prototype reimagined some of the product’s most core pages and workflows. With our timeline, pursuing that direction would have meant rushing into largely unvalidated redesigns before we’d even proven that AI-powered setup could solve the core problem.
I’m proud that I narrowed the scope to something engineering could build in two sprints, while creating a foundation we can iterate on as we learn. Scope reduction isn’t about doing less. It’s about building smart and learning faster.
Lesson 2
AI perception from our user base
In our tech bubble, AI seems like the coolest thing ever. For the small business owners we serve, the reaction was often very different: skepticism, and high expectations that if we introduced AI, it better work well.
AI is powerful, but only when users trust it enough to use it. I found that keeping AI behind the scenes rather than at the forefront, while still being transparent about where automation was introduced, helped ease users into a new experience designed to genuinely make their work easier.












