The Client
A white-label digital coaching ecosystem builder — a two-sided SaaS platform where fitness coaches (B2B) build their own branded apps for their end clients (B2C). The product is built around an 18-interest-tag module system (Bookings, Nutrition, Challenges, Habit Coaching, and more) generating 12+ mini-app configurations. Global product; primary markets include the UAE.
This was conversion rate optimization at the activation layer. In a two-sided SaaS, engagement and retention ARE the conversion metrics — and onboarding UX is where they’re won or lost. The UX research, IA, and Figma specs below are the tools; the service is CRO.
The Challenge
- Complex onboarding with a 9-step Quick Setup users couldn’t navigate.
- No clear guidance between modules — users got lost in configuration depth.
- iOS and Android navigation used conflicting terminology.
- Apple config used technical jargon (“Provisioning Profile”) non-technical coaches couldn’t action.
- The first-time onboarding flow was broken — no clear path from signup to first value.
- 335 contact-intelligence records showed 56.7% general product inquiries and 20% demo requests — users wanted to understand the product before committing.
- Negative sentiment in 14.3% of contacts; primary pain: “Lack of Support / No Response.”
The Strategy & Methodology
Full UX strategy led from scratch — research → IA → interaction design → specs → handoff. Method: 335-contact demand analysis → user-intent categorization → module-demand mapping → onboarding redesign → Quick Setup redesign → component specifications for all settings modules.
Tool Stack: Hotjar (heatmaps + session recordings), Figma, daily scrums + EOD reviews with the product stakeholder.
33+ deliverables included: full onboarding redesign; 9-step Quick Setup redesigned with progressive disclosure; Build-Your-Brand spec with Apple-config UX redesign; separate iOS/Android navigation specs; dashboard, chat, FAQ, and build-history specs; paywall logic; 4 “Learn More” modals; REST API endpoints reference.
10 key design decisions — including: separate iOS/Android navigation modals; “Good vs Avoid” visual comparisons; 130–140-word modal copy for scannability; “Learn More” progressive disclosure; CTAs relabel (never disable) after completion; Soft-Restriction philosophy (guide without blocking); and Apple-config plain-English labels — “Provisioning Profile” → “Files that allow your app to run on iPhones,” which eliminated the #1 technical support escalation.
The Results
These are conversion outcomes. Engagement and retention are how a two-sided SaaS converts — the onboarding rebuild is what moved them.
| Metric | Before | After | Change |
|---|---|---|---|
| User Engagement Rate | Baseline | Baseline × 4 | +300% |
| User Retention Rate | Baseline | Baseline × 1.5 | +50% |
| Deliverables | — | 33+ documented specs | — |
| Contact Intelligence | — | 335 records analyzed | — |
Why It Worked
- Onboarding redesigned around the coach’s goal, not the platform’s feature list.
- Plain-English technical translation removed the biggest drop-off point in Apple config.
- Soft Restriction over hard gates — users explore without fear of mistakes.
- Daily stakeholder loop — scrums + EOD reviews meant zero assumption accumulation.
Key Takeaways
- In SaaS, retention is designed at onboarding — fix the first session, fix the retention number.
- “Provisioning Profile” is a translation problem, not a UX problem — solve translation first.
- Platform-specific specs are not optional — iOS and Android have different mental models.
- 335 contact records is a goldmine of intent data — mine it before building anything.
- Soft Restriction over hard gates always wins — users coached, not blocked.