Alex Chen/Mobile Onboarding Redesign
FinovaPM6 months4-person squad

Activation rate from 31% to 58% on iOS in one quarter

Key outcomes
Activation (completing first transfer) up from 31% to 58% on iOS
D30 retention improved from 44% to 56%
Time-to-first-value reduced from 6.2 days to 1.4 days
01

The problem

Finova's iOS onboarding was a 14-step linear flow built for our web product and ported to mobile without adaptation. Users had to verify identity, link a bank, set a PIN, enable notifications, and complete a KYC form before they could do anything. Drop-off was concentrated at two points: the bank-linking step (43% drop) and the KYC form (31% drop among those who reached it). The core problem: we were asking for maximum commitment before delivering any value.

Each percentage point of activation was worth roughly $180k ARR at our current CAC and LTV. The mobile channel was growing 4× faster than web, so fixing mobile onboarding was the highest-leverage growth lever we had.
02

Research & insights

Methods: User interviews (18 sessions, iOS users who dropped in first 7 days), session recordings (FullStory), 6 weeks of exit survey data, competitor teardowns of 8 fintech onboarding flows

Three themes emerged clearly. First: users didn't trust the app enough to hand over their bank credentials before seeing any value — they wanted proof the product worked before committing. Second: the KYC form felt like a government form, not a product — dense, jargon-heavy, with no progress indicator. Third: the notification permission ask came too early (step 3) and was framed around us ("stay updated") rather than them ("know the moment your transfer arrives"). We also discovered that users who completed a single simulated transfer in a demo flow before linking a bank had 2.3× higher completion rates in an informal test run by a previous PM — this was buried in a Notion doc.

03

Solution

We restructured onboarding around value-first: show a demo transfer before asking for any credentials, defer bank linking until after the user experiences the product, and break the KYC form into conversational micro-steps with progress indicators. The notification ask was moved to post-first-transfer with a value-anchored message. We shipped in two phases: the value-first reorder (4 weeks) and the KYC redesign (8 weeks).

Key decisions & trade-offs

The most contested decision was deferring bank linking. The Growth team wanted to keep it early to maximise the number of linked accounts (a key metric). I argued that a linked-but-churned account was worthless, and that improving the activation funnel would drive more net new linked accounts than forcing the link earlier. We aligned by agreeing to measure "linked accounts active at D30" rather than just "linked accounts" — which gave both sides a shared definition of success. We also debated whether to build a full demo mode or just a video. We built a lightweight interactive demo (not a full fake account) because our research showed users wanted to feel the product, not watch it.

04

Results

MetricBeforeAfterDeltaTime
Activation rate (iOS)31%58%+27ppQ3 2024
D30 retention44%56%+12ppQ3 2024
Time-to-first-value6.2 days1.4 days−77%Q3 2024
Bank-link step completion57%81%+24ppQ3 2024
05

Challenges & learnings

Challenges

The KYC redesign required sign-off from our Compliance and Legal teams, which added 5 weeks to the timeline. The first version of the conversational KYC was rejected because one question's wording didn't meet a specific regulatory requirement in Germany. We had to work with Legal to rewrite the question flow while preserving the UX quality — which took two more rounds of review.

What I'd do differently

I spent too long trying to build consensus on the value-first approach internally before running an experiment. We debated the bank-link timing for 6 weeks before I pushed to just test it. The test ran for 2 weeks and gave us a clear answer. I should have moved to experimentation 4 weeks earlier. The lesson: when you have a reasonable hypothesis and the risk of a bad outcome is reversible, run the test and let data end the debate.

Skills demonstrated
GrowthOnboardingAnalyticsA/B testingiOS
Back to Alex's folioBuild your own folio