Case study 01 · Fintech · 2026
Fernway onboarding, eleven screens to four
Fernway is a bank account for freelancers. Sign-up asked for a passport before it showed a single feature, and 41% of people left. Here is how we got it to four screens and what it did to activation.
- Client
- Fernway, banking for freelancers
- Role
- Fractional design lead
- Length
- 5 months, Feb to Jun 2026
- Team
- 2 designers, 6 engineers, 1 compliance lead
- Onboarding screens
- 11→4
- Activation in 30 days
- +23%
- To first invoice, from 14
- 4 min
Fig. 02
Eleven screens to four
Switch between the sign-up Fernway had and the one we shipped. Seven screens moved to the first payout, were read from the first invoice, or went away.
Welcome
Dropped
Name and email
Kept
Password
Magic link instead
Verify email
Magic link instead
Passport photo
Moved to first payout
Proof of address
Moved to first payout
Tax number
Read from the invoice
Business type
Read from the invoice
Expected volume
Dropped
Terms
Folded into the last step
Account ready
Dropped
What you do
New
Your first client
New
Your first invoice
New
11 screens before the first invoice
01 / 04
The number nobody liked
Fernway's funnel lost 41% of new sign-ups between the welcome screen and a verified account. The flow was eleven screens long, and seven of them were identity checks: passport, proof of address, tax number, business type, expected monthly volume.
The bank genuinely needed most of that. It did not need it on day one. A freelancer can't receive a payout until they are verified, but they can draft an invoice, add a client and see what the account does.
(The best onboarding question is the one you can answer yourself later.)
02 / 04
What we moved
We sorted every question into three piles: needed to open the account, needed before money moves, and nice to have. Only four questions survived the first pile. Everything in the second moved to the moment of the first payout, where the reason to answer is obvious.
The third pile we prefilled. A freelancer's first invoice already names their business, their address and usually their tax number. We read it back to them and asked them to confirm.
(Compliance agreed in one meeting once we showed them the payout gate.)
03 / 04
What shipped
Four screens: name and email, what you do, your first client, your first invoice. Verification happens on a single screen when the first payment is on its way, with the amount shown at the top so people know what is waiting for them.
We tested it with 26 freelancers in Denver and Lisbon before writing production code, then shipped behind a flag to 20% of sign-ups for three weeks.
(Two engineers built the invoice reader in a sprint. It earns its keep every day.)
04 / 04
What it did
Activation in the first 30 days rose 23%. Median time from sign-up to first invoice fell from 14 minutes to 4. Verification completion did not drop: 88% of people who reached the payout gate finished it the same day, because they had a payment waiting.
One thing to note: support tickets about verification went up for two weeks while we fixed the copy on the payout screen. Measure the week after launch, not the day after.
(The number I am proudest of is the boring one. Verification held steady.)
“Sol made us defend every question. Most of them lost.”
Want this kind of before and after for your product?
Start a project