Challenge
TL;DR
Problem: Indian couples already manage money together using Splitwise, WhatsApp groups and spreadsheets, but traditional joint accounts only serve married couples, take days to open, and offer no expense tools.
Solution: Coupled is a neo-bank concept that lets any couple open a shared digital wallet in about 60 seconds, track and split expenses automatically, and still keep some money private.
What I did: Interviewed 7 users remotely in 4 days, reviewed competing tools, mapped the end-to-end journey, designed the onboarding and shared-spending flows, resolved usability issues, and built the final UI in Figma.
Result (prototype testing): Usability issues found in testing were fixed before the final UI.
1. Context
In the last two decades, how Indian couples handle money has changed. Many now share rent, groceries, travel and subscriptions well before marriage. Their tools are improvised: a Splitwise group, a Google Sheet, a WhatsApp message saying "you owe me ₹840".
The traditional joint account hasn't kept up. It is built for a legal relationship, not a real one.
A note on scope: Coupled is a concept project inspired by the couples-banking space (for example, Coupl). It is not affiliated with any bank, and I have kept the focus on the design problem rather than business claims.
Why traditional joint accounts fail couples
Only available to married couples
Opening takes days, and often needs a physical branch visit
Newlyweds with different surnames or addresses on IDs get stuck
High minimum balance requirements
No expense management features
Outdated interface and mental model
Process
Interviews
During the ideation phase of the project, I conducted user interviews to build new personas and to inform the design. Together with the team, we prepared an interview script with 32 open-ended questions, focusing on our target audiences’ values, motivations, and daily routines. In 4 days, I recruited and interviewed 7 users remotely. We referenced the user interview findings throughout the entire design process.
1. Introduction:
- Can you tell us a bit about yourself and your relationship status?
- How do you currently manage shared expenses with your partner?
2. Current Financial Tools:
- Are you using any specific apps or tools to track and manage shared expenses & how satisfied are you with current methods
3. Challenges and Pain Points:
- What are the main challenges you face when it comes to managing finances as a couple?
- Can you share any specific pain points or difficulties you've encountered with your current financial tools?
4. Interest in Neo Bank:
- How do you feel about the concept of a neo bank specifically designed for couples?
- What features would you find most appealing in a banking app tailored for couples?
5. Joint Account Experience:
- Have you ever considered opening a joint account with your partner?
- What factors would influence your decision to open a joint account?
6. Digital Preferences:
- How comfortable are you with using digital banking apps for managing your finances?
- What features do you appreciate in your favorite digital apps?
7. Inclusivity:
- How important is inclusivity to you in a banking app designed for couples, regardless of marital status?
- Would you prefer a platform that caters to couples at different relationship stages?
8. Security and Trust:
- How important is security when it comes to managing your shared finances?
- What measures would increase your trust in a neo bank app designed for couples?
9. Future Goals:
- Are there specific financial goals you and your partner are currently working towards?
- How do you envision a neo-bank app supporting you in achieving these goals?
10. Usability and User Interface:
- What aspects of a mobile app's usability are most important to you?
- How do you feel about a user interface designed specifically for couples?
My questions aim to gather insights into users' current financial practices, preferences, and expectations regarding a neo-bank app designed for couples.


Information architecture
A sitemap with five bottom tabs: Home (Ours balance, recent activity), Spend (transactions, splits), Goals (shared pots), Card (controls, limits), Us (partner, permissions, settings).
Key user flow: onboarding
Download the app and sign in with phone number (OTP).
Complete KYC. [Specify the steps in your flow.]
Invite partner via share link or contact.
Partner accepts, completes their own KYC.
Choose rules: contribution style, split default, visibility.
Wallet is created and the RuPay card is issued.
Edge cases I designed for:
The partner hasn't accepted. The wallet is held in a "waiting" state with a reminder nudge, and the first partner can't be blocked from exploring.
KYC fails or is delayed. Clear next steps with an estimated time, not just an error.
Invite sent to the wrong number. Allow cancel and resend.
One partner wants to exit later. See "Uncoupling" below.
Outcome
Key design decisions
Decision 1: "Ours / Mine" instead of a single pooled balance. Alternatives considered: a single shared account only; two linked individual accounts. UI DesignA shared space plus a private space lets couples see joint spending without giving up personal privacy.
Decision 2: Split rules set once, then automatic. Users choose equal, proportional to income, or custom per category (for example rent 60/40, groceries 50/50). New transactions follow the rule, with a one-tap override. Why: Manual logging and splitting were the main frictions in the tools couples use today.
Decision 3: Gentle language for settling up. Instead of "You owe ₹840", the app says "₹840 to even things out". Why: Money between partners is emotionally loaded, and neutral wording reduces friction. [Add an interview quote if you have one.
Decision 4: Trust built into onboarding. A plain-language "Who can do what" screen shows each partner's permissions, spending limits and approval thresholds before the wallet is created. Why: Security and trust were a theme in the interviews, and people want to know who can do what before they share money.
Decision 5: Designing the end of the relationship. We designed an "Uncouple" flow: a respectful, step-by-step exit that freezes shared spending, settles balances and closes the wallet. Why: A banking product for couples that ignores breakups is incomplete, and it also reassures users that they are never trapped. [Keep this only if you designed this flow; otherwise move it to Next steps.
UI Design
Once the usability issues were resolved, I moved on to design the final screens in Figma. My goal was to create a visual identity that aligned with the brand’s values and message, Also, I’ve checked the competition and took a deep dive into my catalog of references for inspiration





