LemFi · Case study
Designing LemFi Savings, from launch to scale
TL;DR
I designed LemFi's first savings account, from the first concept to launch and its first months of growth. While I led design, the money customers held in savings grew 34 times, and accounts went from under 100 to more than 3,600. The foundations I left in place now carry a product that has grown more than 300 times again since I handed it over.
I was the only designer on the UK Instant Access Savings Account. I designed how people find it, open it, fund it, save automatically, see what they earn and move money out. Three months after launch, I ran a cross-team design audit that showed the real problem was funding, not features, and changed what the team built next.
- Role
- Senior Product Designer, sole designer on Savings
- Timeline
- Spring 2025 to early 2026
- Platforms
- iOS, Android, web, email
- Worked with
- Product, engineering, data, compliance, marketing and our partner bank
- Outcome
- Money held up 34x and 3,600+ accounts while I led design
What I did
- Designed the full savings journey for launch: discovery, opening an account, adding money, interest and moving money out.
- Designed the launch email, banners, website and the monthly emails that show what people earn.
- Designed Smart Autosave and round-ups, so saving could happen without thinking about it.
- Ran a design audit with product, engineering, data and leadership, then wrote the action plan.
- Fixed the funding dead end, added savings to the Add money list and designed paying in straight from a bank.
- Designed the ID check inside savings, which later made over 200,000 more customers eligible.
- Hired a designer to take savings forward, then moved my focus to cross-border payments, payouts and the design system.
The problem
People wanted savings, but most never put money in. The product existed to make LemFi more useful between transfers. Many UK customers send money home every month, and their money sits idle between pay day and send day.
Three months after launch, the numbers told a clear story:
| Step | Result |
|---|---|
| Of people who saw the entry point, tapped through | 96% |
| Of those, finished opening an account | 37% |
| First deposit attempts that failed | 55% |
Our partner bank's rules meant money could only go into savings from the customer's LemFi GBP balance. But most people paid for transfers by card or Apple Pay, so their GBP balance was usually close to empty. When they tried to save, they saw "insufficient balance" and nothing else. To fix it they had to leave savings, top up, and find their way back. Most didn't.
Why people didn't fund
We called 80 customers who had opened an account but never added money, and 49 answered. Their reasons matched the data:
- No spare money right now. Many were "waiting for salary", so timing mattered.
- Didn't understand it. Some didn't know they had an account, or how to add money.
- Didn't trust it yet. No branch, and fear of losing money.
- Things broke. Verification checks failed, or account details were hard to find.
- Better deals elsewhere. Some already saved with another provider.
Most said they would save later, usually around pay day. The intent was there; the path wasn't.
How I approached it
I worked in three steps: launch a lean, compliant first version, add automation, then fix funding once the data showed it was the real blocker.
- Launch one account, not everything. The first version let people open one GBP savings account, add money and move it out. Goals, automation and round-ups showed as "coming soon". This got a regulated product live months earlier.
- Explain before asking. The rate, deposit protection and how interest works sit in short sheets before any commitment. Savings copy has tight rules, so I wrote for clarity within them. I pushed to replace "no minimum deposit" with "save from £1", which was more honest.
- Say "Move", not "Withdraw". Money leaving savings went back into the customer's own LemFi balance. "Withdraw" made it sound like it was leaving LemFi.
- Bring the team into one room. Three months in, I ran a design audit with product, engineering, data and leadership. I brought the funnel data and walked the flows. That night I wrote the action plan: fix the funding dead end first, make Autosave part of the first deposit, then rethink round-ups.
What I designed
By the time I handed it over, savings covered the whole journey: find it, open it, fund it, save automatically, see what it earns and move money out. Each flow below shows the screens in order, with what the user does and what the system does between them.
Opening a savings account
Eight steps from home to a working account. When opening takes longer than usual, a "check back later" state lets people leave without retrying and creating a second account.

Funding: from dead end to a way forward
This was the biggest single fix. A low balance now leads straight to Add money, then brings the user back to finish saving. Savings also sits in the Add money list on the home screen, one tap away.

Paying in straight from your bank
Open banking lets people fund savings from their own bank, skipping the GBP balance and its limits.

Smart Autosave
A regular payment from the user's bank into savings, on the amount and schedule they pick. It's built for people who need saving to happen in the background.

Round-ups on transfers
Spare change from each transfer goes into savings. A 2x, 5x or 10x multiplier lets people choose how much. The audit showed small round-ups barely move total savings, so we agreed to promote them after a transfer, not during it.

Earnings and moving money out
Interest builds daily and is paid monthly, and people can see it on the dashboard. Moving money out needs only an amount and a PIN.

States that keep people moving
Slow, failed and empty moments each get a clear message and a next step, never a dead end.

All of it is built on our design system. The amount input I reworked for savings became the pattern for adding and moving money across the app, and the date picker built for savings became an app-wide component.
Results
While I led design, money held in savings grew 34 times and accounts went from under 100 to more than 3,600. Eligibility widened from a few thousand customers in the first weeks to around 260,000. Growth sped up after the funding fixes: in the four weeks after savings joined the Add money list and Autosave launched, money held doubled.
The product did what it was built to do. Most money taken out of savings went on to fund a transfer, and customers sent more after opening a savings account.
After I handed it over
The biggest jumps came from opening the product to far more people, several built on designs I left in place:
- The ID check inside savings made over 200,000 more customers eligible. Daily account openings went from about a dozen to nearly 800 on the peak day.
- Paying in from your bank helped lift the share of new accounts that got funded from about a third to half.
- A simpler opening flow cut opening to one step that lands on Add money, as the audit had proposed.
A bonus rate, wider eligibility and an app redesign drove growth from there. Money held is now more than 300 times what it was when I handed it over.
Handover
I hired a designer to take savings forward, and moved my focus to cross-border payments, payouts and the design system. I ran the interviews and the hiring process, then handed over a live product with weekly reporting, Autosave on both platforms, bank-transfer funding, the ID check in build, and the audit's agreed direction.
What I learned
Getting money in mattered more than any feature I added.
I spent months on goals, Autosave and round-ups. The audit showed the real blocker was simpler: people could open an account but couldn't easily fund it.
The failed first deposits were there from the first weeks. Earlier tracking would have surfaced them before I moved to new features.
People set up a regular payment when they open an account, not months later from a settings screen.
Funding only from the GBP balance was a bank rule, not a choice. The answer was to design around it, then push for open banking.
One session with data, engineering and leadership changed priorities that months of tickets had not.
What I'd do differently: test the opening flow with real customers before release, and make the first deposit part of opening the account from the start.