


Oma | Financial Chat Bot
Oma | Financial Chat Bot
Spend More, or Ask Mom? Designing a Financial Bot with Tough Love in a Budgeting App
Spend More, or Ask Mom? Designing a Financial Bot with Tough Love in a Budgeting App
Budgeting apps are everywhere. So why are we still broke? Because they show you numbers, but they don't care. Meet Oma — a financial chatbot with opinions. She tracks your goals, calls out your impulse buys, and makes sure you actually stick to the plan — even when she's nagging you.
Budgeting apps are everywhere. So why are we still broke? Because they show you numbers, but they don't care. Meet Oma — a financial chatbot with opinions. She tracks your goals, calls out your impulse buys, and makes sure you actually stick to the plan — even when she's nagging you.
Conversational UX
Conversational UX
Chatbot
Chatbot
Voice + Text
Design Token
My Role
Conversational UX Design
Voice + Text Chatbot
Visual Identity
Project Management
Team
Conversation Designer
Engineer
Deliverables
Voice + Text Chat Bot
User Interface
Intent & Utterance & Script
Personality Design
Timeline
2026.04 - 2026.05
Contributions
I shaped this bot from concept to conversation.
I shaped this bot from concept to conversation.
💡 Concept & Proposal
Found that tone is the missing layer in fintech UX. So I pitched the "mom voice" financial accountability bot idea.
Found that tone is the missing layer in fintech UX. So I pitched the "mom voice" financial accountability bot idea.
✍️ Script Writing
Wrote the "Should I Buy This?" flow. Both the Yes path (earned approval) and the No path (firm redirection with alternatives).
Wrote the "Should I Buy This?" flow. Both the Yes path (earned approval) and the No path (firm redirection with alternatives).
🗺️ Flowchart
Designed the user flow for conversation architecture and decision logic, mapping the three entry points into the flow.
Designed the user flow for conversation architecture and decision logic, mapping the three entry points into the flow.
🤖 Vibe-coded Bot
Built the prototype with Claude & Figma Make by implementing intents, slots, and conditional branching for all core flows.
Built the prototype with Claude & Figma Make by implementing intents, slots, and conditional branching for all core flows.
01 The Introduction
01 The Introduction
The Conversation That Started It All
"Didn't you just buy a Stanley tumbler last month?"
"Didn't you just buy a Stanley tumbler last month?"
My friend almost bought a $38 water bottle she didn't need. I talked her out of it in four messages. That's when I thought — what if a chatbot could do that?
My friend almost bought a $38 water bottle she didn't need. I talked her out of it in four messages. That's when I thought — what if a chatbot could do that?
This is a real conversation between my friend and me, illustrating how young adults often need a second opinion to curb their impulse spending.
This is a real conversation between my friend and me, illustrating how young adults often need a second opinion to curb their impulse spending.
The Problem
We know we should save. We just don't. 🤥
We know we should save. We just don't. 🤥
Young adults with big financial goals, such as a trip, a degree, or an emergency fund, often fail not from lack of information but from lack of accountability. Budgeting apps give charts, but they don't give you a reaction when you make an unnecessary purchase.
Young adults with big financial goals, such as a trip, a degree, or an emergency fund, often fail not from lack of information but from lack of accountability. Budgeting apps give charts, but they don't give you a reaction when you make an unnecessary purchase.
Main Causes
The real issue isn't math. It's accountability
The real issue isn't math. It's accountability
😶
Data without emotion
Financial dashboards show the numbers, but can't respond to the decision in the moment.
Financial dashboards show the numbers, but can't respond to the decision in the moment.
🎯
Goals without structure
Users set savings goals and forget them. There's no recurring voice reminding them of the goal.
Users set savings goals and forget them. There's no recurring voice reminding them of the goal.
🛍️
Impulse without pushback
At the moment of purchase, no tool asks: " Is this a need, a want, or just a really bad week talking?"
At the moment of purchase, no tool asks: " Is this a need, a want, or just a really bad week talking?"
🤷
No one to disappoint
Self-accountability is hard. The most effective check isn't an algorithm; it's a person who cares.
Self-accountability is hard. The most effective check isn't an algorithm; it's a person who cares.
HMW
How might we give users the emotional accountability of a trusted person, without requiring a real person to be there?
HMW
How might we give users the emotional accountability of a trusted person, without requiring a real person to be there?
💪 - 👩🦰 = ?
💪 - 👩🦰 = ?
Meet the Bot
Introducing Oma — She's warm, she's firm, and she remembers every single thing you said your goal was.
Introducing Oma — She's warm, she's firm, and she remembers every single thing you said your goal was.
The bot is designed around one archetype: the mom who loves you enough to tell you the truth. She celebrates real wins, gives practical alternatives, and holds her position when you try to argue. Her tone isn't punishment — it's investment.
The bot is designed around one archetype: the mom who loves you enough to tell you the truth. She celebrates real wins, gives practical alternatives, and holds her position when you try to argue. Her tone isn't punishment — it's investment.
Personality traits
Warm → Firm → Proud → Disappointed. Never cruel. Always invested. The scale shifts based on urgency and user behavior.
Warm → Firm → Proud → Disappointed. Never cruel. Always invested. The scale shifts based on urgency and user behavior.
Core features
Goal setup · Expense logging · Pre-purchase decision check · Progress check-in · Escalating nag mode
Goal setup · Expense logging · Pre-purchase decision check · Progress check-in · Escalating nag mode
02 The Design Decisions
02 The Design Decisions
The Personality
Why "mom" and not a financial advisor?
Why "mom" and not a financial advisor?
An advisor is authoritative but cold. A mom is authoritative and emotionally invested. The archetype carries warmth that makes the pushback feel supportive rather than punitive — you can argue with a bot, but you can't really argue with your mom.
An advisor is authoritative but cold. A mom is authoritative and emotionally invested. The archetype carries warmth that makes the pushback feel supportive rather than punitive — you can argue with a bot, but you can't really argue with your mom.
✅ 👵 ❌ 👩💼
✅ 👵 ❌ 👩💼
The Name
Why did we name the bot "Oma"?
Why did we name the bot "Oma"?
Oma means grandma in German, mom in Korean (Umma), and mother in many South Asian languages (Amma). Across cultures, it's the person who worries about you and tells you the truth whether you ask or not. That's exactly who this bot is.
Oma means grandma in German, mom in Korean (Umma), and mother in many South Asian languages (Amma). Across cultures, it's the person who worries about you and tells you the truth whether you ask or not. That's exactly who this bot is.
= 🇩🇪 👵 ≈🇰🇷 🇹🇼 🧓
= 🇩🇪👵 ≈🇰🇷🇹🇼🧓
Modality
Voice when you need to feel it. Text when you don't want anyone to hear it.
Voice when you need to feel it. Text when you don't want anyone to hear it.
Oma supports both voice and text and the choice is intentional. Voice makes her feel more like a real person. Hearing "didn't you just buy one last month?" hits differently than reading it. But money is personal. In public, on the subway, at work, sometimes you just need to type it out quietly. Both modes, same Oma.
Oma supports both voice and text and the choice is intentional. Voice makes her feel more like a real person. Hearing "didn't you just buy one last month?" hits differently than reading it. But money is personal. In public, on the subway, at work, sometimes you just need to type it out quietly. Both modes, same Oma.
🔈for feeling & 💬 for Privacy
🔈for feeling
💬 for Privacy
🔈for feeling
& 💬 for Privacy
Features with Conversational Fit
What features are suitable for conversation, and why?
What features are suitable for conversation, and why?
Spending decisions are emotional and happen in the moment. A chart can't respond to that. We used Google's conversation design framework to validate each feature before building it.
Spending decisions are emotional and happen in the moment. A chart can't respond to that. We used Google's conversation design framework to validate each feature before building it.
1
Ask Before You Buy
People already text friends before making a purchase. The decision is brief, personal, and happens on the go. A form can't say, "Didn't you just buy one last month?"
2
Log an Expense
Faster than navigating to a form. One message, one category, done. Conversation reduces the friction that makes people stop logging altogether.
3
Check My Progress
Financial check-ins are inherently conversational — it's how you'd talk to a financial advisor, a parent, or a friend. Numbers alone don't motivate. A reaction does.
Financial check-ins are inherently conversational — it's how you'd talk to a financial advisor, a parent, or a friend. Numbers alone don't motivate. A reaction does.
1
Defined Brand Values
Set up core principles that align with Resy's brand identity and vision.
2
Built the Figma UI Kit
Established style system and component library that can improve working efficiency.
03 The Design
03 The Design
User Flow
Every conversation starts with a goal. Everything else keeps you on track.
Every conversation starts with a goal. Everything else keeps you on track.
Oma onboards you once, then stays out of the way until you need her. The flow is designed around how people actually think about money, not by category, but by moment.
Oma onboards you once, then stays out of the way until you need her. The flow is designed around how people actually think about money, not by category, but by moment.

Scripts
The core logic lives in one diamond: can you make this purchase, or can't you?
The core logic lives in one diamond: can you make this purchase, or can't you?
Scripts aren't just dialogue. They're the design spec. Each scenario was chosen to push a specific edge: what happens when the user argues back? When they celebrate? When they lie to themselves?
Scripts aren't just dialogue. They're the design spec. Each scenario was chosen to push a specific edge: what happens when the user argues back? When they celebrate? When they lie to themselves?
What is this FAQ component?
Can I use multiple sections on one page?
How do I customize fonts, colors, and spacing?
Flowchart
The core logic lives in one diamond: can you make this purchase, or can't you?
The core logic lives in one diamond: can you make this purchase, or can't you?
The flowchart maps three entry points — log an expense, ask, "Should I buy and check my progress — into a single decision system. The purchase decision diamond is the heart of the design: it weighs need/want type, urgency score, and current savings status to route the user toward the right version of the mom.
The flowchart maps three entry points — log an expense, ask, "Should I buy and check my progress — into a single decision system. The purchase decision diamond is the heart of the design: it weighs need/want type, urgency score, and current savings status to route the user toward the right version of the mom.
03 The Design
03 The Design
Impact
Recap: The Problems and How Epicurean Solved all of Them!
Recap: The Problems and How Epicurean Solved all of Them!

A clear documented and guidelines to bridge designers, developers and PMs.
A clear documented and guidelines to bridge designers, developers and PMs.

University of Penn
A library of foundations, components, and patterns that ensure visual conhesion.
A library of foundations, components, and patterns that ensure visual conhesion.
Main Problems
Inconsistent Visuals
Typography, colors, spacing, and icons clash across pages with no unified rhythm or usage.
Typography, colors, spacing, and icons clash across pages with no unified rhythm or usage.
Undefined Component Hierarchy
No clear system for when to use specific actions, leaving button prominence and flow guidance
No clear system for when to use specific actions, leaving button prominence and flow guidance
Accessibility Issues
Buttons, controls, and inputs lack consistent visual to show different states.
Buttons, controls, and inputs lack consistent visual to show different states.
Key Improvements
Consistent Visuals
Our reusable UI kit guarantees visual cohesion and consistent usage across the product ecosystem.
Our reusable UI kit guarantees visual cohesion and consistent usage across the product ecosystem.
Common Language
Clear documentation and guidelines bridge communication across designers, engineers, and PMs.
Clear documentation and guidelines bridge communication across designers, engineers, and PMs.
Better Accessibility
The pre-established style system ensures all assets meet WCAG compliance standards.
The pre-established style system ensures all assets meet WCAG compliance standards.
03 The Result
03 The Result
Impact
Recap: The Problems and How Epicurean Solved all of Them!
Recap: The Problems and How Epicurean Solved all of Them!

A clear documented and guidelines to bridge designers, developers and PMs.
A clear documented and guidelines to bridge designers, developers and PMs.

University of Penn
A library of foundations, components, and patterns that ensure visual conhesion.
A library of foundations, components, and patterns that ensure visual conhesion.
Main Problems
Inconsistent Visuals
Typography, colors, spacing, and icons clash across pages with no unified rhythm or usage.
Typography, colors, spacing, and icons clash across pages with no unified rhythm or usage.
Undefined Component Hierarchy
No clear system for when to use specific actions, leaving button prominence and flow guidance
No clear system for when to use specific actions, leaving button prominence and flow guidance
Accessibility Issues
Buttons, controls, and inputs lack consistent visual to show different states.
Buttons, controls, and inputs lack consistent visual to show different states.
Key Improvements
Consistent Visuals
Our reusable UI kit guarantees visual cohesion and consistent usage across the product ecosystem.
Our reusable UI kit guarantees visual cohesion and consistent usage across the product ecosystem.
Common Language
Clear documentation and guidelines bridge communication across designers, engineers, and PMs.
Clear documentation and guidelines bridge communication across designers, engineers, and PMs.
Better Accessibility
The pre-established style system ensures all assets meet WCAG compliance standards.
The pre-established style system ensures all assets meet WCAG compliance standards.
Feedback
“I was impressive that it only took 57 secs to build a page with the design system.”
“I was impressive that it only took 57 secs to build a page with the design system.”
The pitch received positive feedback, validating everything we built. The biggest "wow" moment was definitely how designers can build a page with Epicurean UI kit within a minute. The title quote effectively contrasted the previous state where designers "worked in a mess" with high uncertainty and manual handoffs. The hypothetical Resy's design team strongly appreciated seeing how the Epicurean Design System will help streamline their working flow by enabling them to easily access and implement pre-established components and styles, shifting their focus toward innovation.
Want to learn more about Epicurean Design System? Here is our Pitch Deck.
Want to learn more about Epicurean Design System? Here is our Pitch Deck.


Next Steps
Future Vision: Design System Roadmap
Future Vision: Design System Roadmap
If I were to continue this project, the next phase would be focused on establishing a full, enterprise-ready system. This involves a strategic 2026 roadmap centered on deepening the foundation, expanding core components, and ensuring user validation and internal adoption.

Takeaways
From Creating a UI Kit to Building a Design System.
From Creating a UI Kit to Building a Design System.
This project significantly enhanced my expertise, moving beyond my prior experience leading two design system builds for startups. While those previous efforts successfully established UI Kits and basic documentation, they primarily functioned as design resources and lacked comprehensive guidance. This project provided invaluable growth, particularly in deepening my understanding of Design Tokens. Mastering how to construct a clear and robust color token system with WCAG compliance allowed me to bridge gaps between designers and developers. I also learned how to develop comprehensive design documentation, ensuring the system operates as a reliable, single source of truth for all cross-functional partners.



