Back to all projects
Case study

Savings Bank Statement on Slice App

Bringing native bank-statement access into Slice so users never have to leave for their primary bank's app.

Role

Product Manager (case study)

Duration

3 weeks

Tools

FigmaUser ResearchCompetitive Analysis
Savings Bank Statement on Slice App
๐Ÿฆ
< 60s
from intent to download
7 โ†’ 1
min reduction
3
presets covering 80% of use-cases
01Problem

Problem

Slice users had to context-switch to their bank's app or net-banking portal every time they needed a savings-account statement (for rent receipts, tax filing, visa applications). This broke Slice's promise of being the single financial hub for young India.

02Users

Users

Slice's core 22-28 year-old cohort โ€” first-job earners, renters, and freelancers who need monthly/quarterly statements for landlords, accountants, and embassies but find traditional banking apps clunky.

03Hypothesis

Hypothesis

If users can request, preview, and download a stamped bank statement directly inside Slice, time-to-statement will drop from 7+ minutes (external app) to under 60 seconds, increasing 30-day app retention.

04Wireframes

Wireframes

Designed three flows: (1) Quick statement โ€” last 30 days, instant PDF; (2) Custom range with calendar picker; (3) Shareable view-only link for landlords / accountants with redacted account number.

05Solution

Solution

An 'Account โ†’ Statements' entry in the home tab with one-tap presets ('Last month', 'This FY', 'Custom'). Statements are pre-stamped server-side and shareable via a tokenized link that expires in 7 days.

Learnings

What I'd take with me.

Embedded micro-utilities (like statement access) drive disproportionate retention because they replace a small but recurring friction point users barely noticed they had.